You can set up journal approval using the following features:
Use General Ledger's Journal Approval feature to ensure that journal entries and batches are approved by appropriate individuals before the journals can be posted to your account balances.
Journal Approval uses Oracle Workflow to control and monitor the approval process, sending notifications to journal batch preparers and approvers when needed. Some of the Journal Approval components can be customized to meet your organization's specific needs. See: Journal Approval.
Before you use Journal Approval, you must enable journal approval for your ledgers. You must also set up your journal sources to use journal approval. Finally, you must create an approval hierarchy and define your approver authorization limits.
You can also restrict who a journal approval request is reassigned to by running a program that restricts the assignee list of values. The restricted list of values includes valid employees or contract (contingent) workers who are application users with journal authorization limits. Otherwise, the assignee list of values lists employees or contract (contingent) workers, whether they have or do not have journal authorization limits or they are or are not associated with application users.
Prerequisites
Before you use Journal Approval, you or your system administrator must:
Set up Oracle Workflow. See: Setting Up Oracle Workflow
Set the two profile options Journals: Allow Preparer Approval and Journals: Find Approver Method. See: Setting General Ledger Profile Options.
Configure the GL Journal Approval Process in Oracle Workflow Builder. Specifically, you must set the performer for the Notify System Administrator - No Approver and Notify System Administrator - No Approver Manager activities. Also, you can change the default settings for Request Approval From Approver timeout and the Reached Manager Notification Resend Limit. See: Journal Approval.
Enable Journal Approval for your ledger in Accounting Setup Manager.
When you define your ledgers using Accounting Setup Manager, mark the Enable Journal Approval check box on the Ledgers page.
If you use reporting currencies (journal or subledger level), you can enable Journal Approval for your reporting currencies in Accounting Setup Manager.
See: Defining Ledgers
See: Creating Accounting Setups.
On the Journal Sources window, mark the Require Journal Approval check box for each journal source that should be subject to approval.
When a journal entry or batch is created using one of these journal sources, the journal must be approved before it can be posted.
Use the Enter Person window in Oracle General Ledger to enter all of your employees or contract (contingent) workers who are involved in preparing and approving journal entries and batches.
When you enter an employee or contract (contingent) worker, you also enter the supervisor or manager name. The supervisor is the default next approver for journal entries and batches. Likewise, the supervisor's manager is the next approver after the supervisor.
Navigate to the Journal Authorization Limits window.
Enter the ledger in the Ledger column. You can select a ledger in your data access set if you have read/write access to at least one or more balancing segment values or management segment values in the ledger.
Note: If you use reporting currencies (journal or subledger level), you can enter a reporting currency in the Ledger column if you have read/write access to one or more balancing segment values or management segment values in the reporting currency.
The Currency column defaults to the currency of the ledger or reporting currency you entered in the previous step.
Enter the Employee name, or select it from the list of values.
Enter the amount of the employee's Authorization Limit.
Repeat the previous two steps for each employee for whom you want to define authorization limits.
Save your work.
Navigate to the Journal Authorization Limits window.
In the Find Journal Authorization Limits window, enter the ledger and or employee you are trying to find.
Note: You can select a ledger in your data access set if you have read access to at least one or more balancing segment values or management segment values in the ledger.
Note: If you use reporting currencies (journal or subledger level), you can enter a reporting currency in the Ledger field if you have read access to one or more balancing segment values or management segment values in the reporting currency.
To restrict the assignee list of values for journal approval requests, perform the following steps.
From the Submit Requests window, run the program named Program - Maintain Authorized Users for Journal Approval Reassignment to restrict the assignee list of values to valid application users who have journal authorization limits.
Run this program as frequently as needed to include any changes to employees' statuses, application user effective dates, or to journal authorization limits.
If any of the preceding changes occur, run this program to update the assignee list of values to reflect the changes for journal approval requests.
To restrict the notification reassignment list to employees or contract (contingent) workers who have journal authorization limits in your Oracle Applications instance, run the program Maintain Authorized Users for Journal Approval Reassignment. Run the program as needed to implement changes to employees' or contract (contingent) workers' statuses, application users, or journal authorization limits. The reassignment list will display active employees or contract (contingent) workers associated with valid application users who have journal authorization limits.
You can also set up journal approval by integrating with Oracle Approvals Management and Oracle Workflow. With this feature you can configure flexible rules for the routing of journals to one or more approvers, sequentially or in parallel, as well as tracking the approval status for the journals processed.
Install the Oracle Workflow Builder client component program to modify the Journal Approval Workflow.
Set up approvers to receive notifications. You can set up Oracle Workflow Notification Mailer so the Journal Approval Workflow Program uses e-mail, and your system administrator can grant approvers access to view journal approval notifications from the Oracle Workflow Notification Worklist web page.
Complete additional Oracle Workflow setup steps. Specify the timeout value, the time period in which an approver needs to respond before sending a reminder notification or escalating the request to the approver's manager.
(Optional) Modify the Journal Approval Workflow. For example, you can modify the message text that appears on your notifications.
Set up a designated person who receives notification of workflow errors through the Oracle Workflow Default Error Process. Oracle recommends that the person who receives Oracle Approvals Management error notifications should also receive Oracle Workflow process error notifications.
Suggestion: If you are an existing Oracle E-Business Suite customer who has already integrated another Oracle E-Business Suite product with Oracle Approvals Management and Oracle Workflow, such as the Oracle Payables invoice approval process, you may already have installed the Oracle Workflow Builder client component program and Oracle Approvals Management. You will not need perform this installation again.
Install and set up Oracle Approvals Management (AME).
Suggestion: If you are an existing Oracle E-Business Suite customer who has already integrated another Oracle E-Business Suite product with Oracle Approvals Management and Oracle Workflow, such as the Oracle Payables invoice approval process, you may already have installed the Oracle Workflow Builder client component program and Oracle Approvals Management. You will not need perform this installation again.
Enable Journal Approval for relevant ledgers.
The check box for Enable Journal Approval must be selected in the Journal Processing region of the Ledger setup within the Accounting Setup Manager for each ledger that requires the journal approvals process.
Two new profile options must be reviewed and set for the Oracle General Ledger (GL) Journal Approvals Management Integration with Oracle Approvals Management and Oracle Workflow, as follows:
GL: Use Approval Management (AME) for journal approval - Determines if Oracle Workflow will follow the existing process of approving journals using the Supervisor hierarchy and Employee Limits form, or if it will use the new integration with Oracle Approvals Management and Oracle Workflow.
Attention: Set this profile option to Yes at Site level to use Oracle Approval Management (AME) and Oracle Workflow for journal approval in Oracle General Ledger.
GL: Number of journal lines to display in AME journal approval notification - Determines the maximum number of lines to display in the journal approvals notification, which is sent to the journal approvers. The default value is set to 5. If the journal contains more than five lines, a hyperlink enables the approvers to access the full journal in Oracle General Ledger.
Suggestion: It is recommended that you do not set the value to higher than 10 due to a limitation with the file size of the workflow approval notification.
Create a HR Supervisor Approval Hierarchy Use the Enter Person window in Oracle General Ledger to enter all of your employees who are involved in preparing and approving journal entries and batches.
For more information see the Entering a New Employee section of the Oracle Human Resources Management System User's Guide
When you enter an employee, you will also enter the employee's supervisor or manager name. The supervisor is the default next approver for journal entries and batches. Likewise, the supervisor's manager is the next approver after the supervisor.
Create and maintain approval limits. This is an optional step but is useful for subsequent AME definitions.
Navigate to the Journal Authorization Limits form within the Oracle General Ledger Super User responsibility to create and maintain the approver limits:
Enter the ledger in the Ledger column. You can select a ledger in your data access set if you have read/write access to at least one or more balancing segment values or management segment values in the ledger.
Note: If you use reporting currencies (journal or subledger level), you can enter a reporting currency in the Ledger column if you have read and write access to one or more balancing segment values or management segment values in the reporting currency.
The Currency column defaults to the currency of the ledger or reporting currency that you entered in the previous step.
Enter the Employee name, or select it from the list of values.
Enter the amount of the employee authorization limit. Repeat the previous two steps for each employee for whom you want to define authorization limits.
Save.
Configure Oracle Approvals Management (AME) Rules.
Note: Use the Approvals Management Business Analyst responsibility
A prerequisite to using the Approvals Management Business Analyst responsibility and the Business Analyst Dashboard is to first add roles to the AME Setup user through the User Management responsibility, and to grant data access to the AME Setup user through the Functional Administrator responsibility. Without the proper roles and data access the AME Setup user will not be able to define AME rules.
In AME, you will define the rules that the system uses to determine the appropriate approvers for a journal batch or journal in Oracle General Ledger.
Navigate to the Business Analyst Dashboard and click on the setup for GL Journal Approval transaction type.
Navigate to the Conditions tab and set up a new condition to enable the rule for AME.
After all the conditions are set, click on the Rules tab and create rules to check for AME Approval.
Set up the Action type and define Voting Method, which will be followed by the Oracle Workflow integration with Oracle Approvals Management for journal approval in Oracle General Ledger.
Action Types can be set up at Supervisor level or Approval Group chain of authority. To set up Dynamic Approvers, the Action type should be set as Approval Group chain of Authority and Voting Method should be set. To set up a normal HR Supervisor Hierarchy level approval, select the Action Type as Supervisory Level and set the Voting method.
If the approver level needs to be Dynamic or Static, then you must create a new Approver Group and select the Usage Type field as Static or Dynamic.
If the usage type selected is Dynamic, then you must write a SQL Query to derive the approver list. For more details on how to use the AME Attributes refer Oracle Approvals Management Implementation Guide.
If the usage type selected is Static, then the Approver Type must be updated.
Test your AME rules for Oracle General Ledger journals.
To ensure that the AME rules satisfy the conditions and actions you can create a journal and then test it using the AME Test Workbench before submitting the journal for approval. It is advisable to test every time AME rules are modified or for debugging of journals.
If the submitted journal satisfies AME rules, it will follow the approval hierarchy in the AME setup for the Action Type.
In case the journals do not satisfy any of the AME rules, and complete in error, use the Test Workbench to troubleshoot.
AME Rules
Typically a system administrator works with the finance department to configure and maintain the approval rules utilizing the Approvals Management Business Analyst responsibility. You can use conditions to identify values and value ranges for the attributes. Conditions can be created using the AME Business Analyst Dashboard by selecting the Conditions link. From the dashboard you can also create rules by selecting the Rules link.
Business Rules and Logic
The following business rules and logic apply to the journal approvals process in Oracle General Ledger when integrating with Oracle Approvals Management and Oracle Workflow:
Enable Journal Approval should be checked in the Accounting Setup Manager for the ledger.
Journal Approval in Oracle General Ledger is required when a journal is input or reversed using the Journals page in Oracle General Ledger, but only when the journal source is set to Require Journal Approval.
Batches may consist of multiple journals with many lines. A batch may have two journals, where the first journal relates to ledger A, and the second journal relates to ledger B. For each of the journals a different approver may be required. You can define the rules to track a journal batch as approved only after approvals are received from all approvers for all journals (related to different ledgers) in the batch.
The approval list generation is controlled through AME. This enables you to modify the conditions for the business rules. Those rules are also available for use by other subscribing applications to AME.
When an approver receives a journal approval notification, the approver reviews the journal details and selects one of the following:
Approve
Reject
Reassign: Delegate authority to another Oracle user
Request Information: Request more information from the journal preparer
The approver is approving or rejecting all relevant lines within a journal. There is no option to approve some journal lines while rejecting other journal lines for a journal. The journal batch is approved after all of the required responses are positive.
If a journal is rejected, a Rejection Notification is sent to both the preparer and all approvers.
You must define a business process to handle the subsequent actions after the rejection of journals by approvers.
Approvers can use the standard vacation rules to route to other approvers in the event of vacation or absence. If a notification times out, then the HR Supervisor Hierarchy is used in the AME rules. In this case the approver's supervisor receives the notifications to approve or reject. If the supervisor approves, then the journal is approved after all other approvers approve and if supervisor rejects then the journal is rejected.
When no approver can be found for a journal in Oracle General Ledger, the workflow system administrator and the preparer receives a notification. The notification to the preparer is for information purposes only.
The AME or workflow system administrator and preparer receive notifications on two occasions, when the AME Rule:
setup is invalid.
has no approvers.
After the system administrator fixes the AME rule, and the administrator resubmits the journal batch for approval, then the preparer receives a notification that the problem is fixed and that the journal is resubmitted for approval.
Journals created from previously approved journals with an auto-reversal element, do not require approval again, because the original journal was already approved.
Journals that are generated using an auto-reversal process occur at the start of accounting periods.
Time-outs within Oracle Workflow are set to a 7 day default.
Monitor Exceptions
The Workflow system administrator should monitor the Journal Batch workflow type for workflows that end in an error state.
Action History
There is an history table named GL_WF_ACTION_HISTORY that tracks approver responses to the Oracle Workflow journal approval notifications. You can use table to create custom reports to audit the current status of journals approvals.
The following Oracle General Ledger attributes are available in Oracle Approvals Management to build your approval rules:
Item Class - Header (Matches with Journal Batch Level Attributes)
| Attribute Name | Description |
| BATCH_PERIOD | Specify separate approval chain for journals submitted for instance in adjustment periods or for instance for journals submitted in the final period of the financial year. |
| BATCH_DEBIT_RUNNING_TOTAL | Specify separate approver groups depending on the journal batch debit amount. For instance, if the journal batch debit amount is greater than 1 million USD then request for approval should go to senior management group. |
| BATCH_CREDIT_RUNNING_TOTAL | Specify separate approver groups depending on the journal batch credit amount. For instance if the journal batch credit amount greater than 1 million USD then request for approval should go to senior management group. |
| BATCH_ATTRIBUTE1 | Used for any specific client business requirement, information for which is captured in journal batch Descriptive Flexfield segment 1. |
| BATCH_ATTRIBUTE2 | Used for any specific client business requirement, information that is captured in journal batch Descriptive Flexfield segment 2. |
| BATCH_ATTRIBUTE3 | Used for any specific client business requirement, information that is captured in journal batch Descriptive Flexfield segment 3. |
| BATCH_ATTRIBUTE4 | Used for any specific client business requirement, information that is captured in journal batch Descriptive Flexfield segment 4. |
| BATCH_ATTRIBUTE5 | Used for any specific client business requirement, information that is captured in journal batch Descriptive Flexfield segment 5. |
| BATCH_ATTRIBUTE6 | Used for any specific client business requirement, information that is captured in journal batch Descriptive Flexfield segment 6. |
| BATCH_ATTRIBUTE7 | Used for any specific client business requirement, information that is captured in journal batch Descriptive Flexfield segment 7. |
| BATCH_ATTRIBUTE8 | Used for any specific client business requirement, information that is captured in journal batch Descriptive Flexfield segment 8. |
| BATCH_ATTRIBUTE9 | Used for any specific client business requirement, information that is captured in journal batch Descriptive Flexfield segment 9. |
| BATCH_ATTRIBUTE10 | Used for any specific client business requirement, information that is captured in journal batch Descriptive Flexfield segment 10. |
| FISCAL_YEAR | Used along with combination of other attributes, in order to create conditions to select approvers. |
| PERIOD_START_DATE | Select a separate approver groups based on journal dates. For instance, if the date falls during the last week of the period then approver group to be separate from normal dates. |
| PERIOD_END_DATE | Select a separate approver groups based on journal dates. For instance, if the date falls during the last week of the period then approver group to be separate from normal dates. |
| JOURNAL_TYPE | Approve journals based on the journal types, such as Actual, Budget, and Encumbrance. |
Item Class - Line (Matches with Journal Header Level Attributes)
| Attribute Name | Description |
| JOURNAL_CATEGORY | Identify approval groups based on journal categories. JOURNAL_SOURCE Used for identifying approval groups based on journal source. |
| JOURNAL_DATE | Identify approval groups based on journal date. |
| JOURNAL_HEADER_DEBIT_RUNNING_TOTAL | Specify separate approver groups depending on the journal header debit amount. For instance, if the journal header debit amount is greater than 1 million then request for approval should go to senior management group. |
| JOURNAL_HEADER_CREDIT_RUNNING_TOTAL | Specify separate approver groups depending on the journal header debit amount. For instance, if the journal header debit amount is greater than 1 million then request for approval should go to senior management group. |
| JOURNAL_HEADER_ATTRIBUTE1 | Used for any specific client business requirement, information that is captured in journal header Descriptive Flexfield segment 1. |
| JOURNAL_HEADER_ATTRIBUTE2 | Used for any specific client business requirement, information that is captured in journal header Descriptive Flexfield segment 2. |
| JOURNAL_HEADER_ATTRIBUTE3 | Used for any specific client business requirement, information that is captured in journal header Descriptive Flexfield segment 3. |
| JOURNAL_HEADER_ATTRIBUTE4 | Used for any specific client business requirement, information that is captured in journal header Descriptive Flexfield segment 4. |
| JOURNAL_HEADER_ATTRIBUTE5 | Used for any specific client business requirement, information that is captured in journal header Descriptive Flexfield segment 5. |
| JOURNAL_HEADER_ATTRIBUTE6 | Used for any specific client business requirement, information that is captured in journal header Descriptive Flexfield segment 6. |
| JOURNAL_HEADER_ATTRIBUTE7 | Used for any specific client business requirement, information that is captured in journal header Descriptive Flexfield segment 7. |
| JOURNAL_HEADER_ATTRIBUTE8 | Used for any specific client business requirement, information that is captured in journal header Descriptive Flexfield segment 8. |
| JOURNAL_HEADER_ATTRIBUTE9 | Used for any specific client business requirement, information that is captured in journal header Descriptive Flexfield segment 9. |
| JOURNAL_HEADER_ATTRIBUTE10 | Used for any specific client business requirement, information that is captured in journal header Descriptive Flexfield segment 10. |
| LEDGER_NAME | Used to select approver groups based on the Ledger assigned to the journal. |
| LEDGER_CURRENCY | Used to select approver groups based on the Ledger currency assigned to the journal. |
| LEDGER_CURRENCY_TYPE | Used to select approver groups based on the Ledger Currency Type assigned to the journal such as the Journal is for Statistical or Entered currency. |
Item Class - Distribution (Matches with Journal Line Level Attributes)
| Attribute Name | Description |
| JOURNAL_LINE_BSV | Create AME conditions based on balancing segment value, such as depending on Balancing Segment (Qualifier) values forward the journal to a specific approver group. |
| JOURNAL_LINE_COST_CENTRE | Create AME conditions based on Cost Centre segment value, such as depending on Cost Centre Segment (Qualifier) values forward the journal to specific approver group. |
| JOURNAL_LINE_NATURAL_ACCOUNT | Create AME conditions based on Natural Account segment value, i.e. depending on Natural Account Segment (Qualifier) Values forward the journal to specific approver group. |
| JOURNAL_LINE_INTERCOMPANY | Create AME conditions based on Intercompany segment value, such as depending on Intercompany Segment (Qualifier) Values forward the journal to specific approver group. |
| JOURNAL_LINE_MANAGEMENT_SEG | Create AME conditions based on Management segment value, such as depending on Management Segment (Qualifier) Values forward the journal to specific approver group. |
| JOURNAL_LINE_SECONDARY_TRACKING | Create AME conditions based on Secondary Tracking segment value, such as depending on Secondary Tracking Segment (Qualifier) Values forward the journal to specific approver group. |
| JOURNAL_LINE_ATTRIBUTE1 | Used for any specific client business requirement, information that is captured in journal line Descriptive Flexfield segment 1. |
| JOURNAL_LINE_ATTRIBUTE2 | Used for any specific client business requirement, information that is captured in journal line Descriptive Flexfield segment 2. |
| JOURNAL_LINE_ATTRIBUTE3 | Used for any specific client business requirement, information that is captured in journal line Descriptive Flexfield segment 3. |
| JOURNAL_LINE_ATTRIBUTE4 | Used for any specific client business requirement, information that is captured in journal line Descriptive Flexfield segment 4. |
| JOURNAL_LINE_ATTRIBUTE5 | Used for any specific client business requirement, information that is captured in journal line Descriptive Flexfield segment 5. |
| JOURNAL_LINE_ATTRIBUTE6 | Used for any specific client business requirement, information that is captured in journal line Descriptive Flexfield segment 6. |
| JOURNAL_LINE_ATTRIBUTE7 | Used for any specific client business requirement, information that is captured in journal line Descriptive Flexfield segment 7. |
| JOURNAL_LINE_ATTRIBUTE8 | Used for any specific client business requirement, information that is captured in journal line Descriptive Flexfield segment 8. |
| JOURNAL_LINE_ATTRIBUTE9 | Used for any specific client business requirement, information that is captured in journal line Descriptive Flexfield segment 9 . |
| JOURNAL_LINE_ATTRIBUTE10 | Used for any specific client business requirement, information that is captured in journal line Descriptive Flexfield segment 10. |
| JOURNAL_LINE_ATTRIBUTE11 | Used for any specific client business requirement, information that is captured in journal line Descriptive Flexfield segment 11. |
| JOURNAL_LINE_ATTRIBUTE12 | Used for any specific client business requirement, information that is captured in journal line Descriptive Flexfield segment 12. |
| JOURNAL_LINE_ATTRIBUTE13 | Used for any specific client business requirement, information that is captured in journal line Descriptive Flexfield segment 13. |
| JOURNAL_LINE_ATTRIBUTE14 | Used for any specific client business requirement, information that is captured in journal line Descriptive Flexfield segment 14. |
| JOURNAL_LINE_ATTRIBUTE15 | Used for any specific client business requirement, information that is captured in journal line Descriptive Flexfield segment 15. |
| JOURNAL_LINE_ATTRIBUTE16 | Used for any specific client business requirement, information that is captured in journal line Descriptive Flexfield segment 16. |
| JOURNAL_LINE_ATTRIBUTE17 | Used for any specific client business requirement, information that is captured in journal line Descriptive Flexfield segment 17. |
| JOURNAL_LINE_ATTRIBUTE18 | Used for any specific client business requirement, information that is captured in journal line Descriptive Flexfield segment 18. |
| JOURNAL_LINE_ATTRIBUTE19 | Used for any specific client business requirement, information that is captured in journal line Descriptive Flexfield segment 19. |
| JOURNAL_LINE_ATTRIBUTE20 | Used for any specific client business requirement, information that is captured in journal line Descriptive Flexfield segment 20. |
| GL_JOURNAL_LINE_DEBIT_AMOUNT | Used to specify separate approver groups depending on the journal lines debit amount. For instance, if the journal line debit amount is greater than ten thousand USD, then approver should go to Accountants/Supervisors. |
| GL_JOURNAL_LINE_CREDIT_AMOUNT | Specify separate approver groups depending on the journal lines credit amount. For instance, if the journal line credit amount is greater than ten thousand USD, then approver should go to Accountants/Supervisors. |
Suggestion: When you define approval rules and conditions in Oracle Approvals Management using any of the preceding attributes you must consider whether attributes at journal line level will clash with any other attributes you might use for rules definitions at a higher level such as at journal header or journal batch level.
The action history table tracks the journal status based on the responses the approvers give to the Oracle Workflow routed journal approval notifications. Refer to the Implementation Considerations for further information about the Action History table.
Action History Table
| Column Name | Data Type | Column Description |
| OBJECT_TYPE_CODE Name of the object. | VARCHAR2 | GLJOURNAL for Journal Batch Approval. |
| OBJECT_ID | NUMBER | Journal batch Id. |
| SEQUENCE_NUM | NUMBER | Sequence number of the record. |
| WF_ITEM_TYPE | VARCHAR2 | Workflow Item type of parent process GLBATCH for 'Journal Batch Approval. |
| WF_ITEM_KEY | VARCHAR2 | Workflow Item key of parent process. |
| WF_PREPARER_NAME | VARCHAR2 | Name of the preparer who submitted the journal batch for approval. |
| WF_APPROVER_NAME | VARCHAR2 | Name of the approver who responded to the journal batch approval notification. |
| LAST_UPDATE_DATE | DATE | Last update date for the notification. |
| LAST_UPDATED_BY | NUMBER | Last updated by for the notification. |
| CREATION_DATE | DATE | Creation date for the notification. |
| CREATED_BY | NUMBER | Created by for the notification. |
| ACTION_CODE | VARCHAR2 | Current status for the notification. |
| ACTION_DATE | DATE | Date when the action was updated. |
| EMPLOYEE_ID | NUMBER | Approver to whom the notification is sent. |
| NOTE | VARCHAR2 | Comments from the responder of the notification. |
| LAST_UPDATE_LOGIN | NUMBER | Last updated logic. |
| APPROVAL_GROUP_ID | NUMBER | Approval group Id to which the employee_id belongs. |
Suggestion: The Action History table tracks the status only for the Oracle General Ledger Integration with Oracle Approvals Management and Oracle Workflow.
This section provides guidance on Oracle Approvals Management (AME) rules setup for the Oracle General Ledger Journal Approvals process. You must first complete you the setup steps previously outlined.
To Create a GL Journal Approval Rule in Oracle Approvals Management:
Navigate to Business Analyst Dashboard.
Select the GL Journal Approval transaction type and select (I) Setup.
Navigate to the Conditions tab to set up a new condition and enable the rule for AME.
Select Create to create new AME Conditions and enter details.
Select the Action Types tab to create new Actions.
Create new Approver Groups to use Static or Dynamic approvers.
If the approver level needs to be Dynamic or Static, then you must create a new approver group and set the Usage Type field as Static or Dynamic. If the usage type selected is:
Dynamic, then you must write a SQL Query to derive the approver list.
Static, then the approver type must be updated.