Oracle AME

Document Display
Page 1 of 12
AME : How to Diagnose Issues With the Default Approver List in Purchasing When Using
Modified: 29-Oct-2012
Type: TROUBLESHOOTING
Status: PUBLISHED
Priority: 3
In this Document
Purpose
Troubleshooting Steps
How to Enable AME

For Requisitions
For Purchase Orders (starting in 12.1.3)
AME Setup
How the default approval list is built in AME

Approvals matrix
Approval process execution
Review default approval list using Test Workbench

Diagnostic Steps
1. Test Workbench
2. Transactions exception log

3. FND log
4. Approval Workflow
5. PO_WF_DEBUG messages
Example of an AME setup

1. Define attributes
2. Define conditions
3. Define action types

4. Define rules
Still Have Questions?
References
Applies to:
Oracle Purchasing - Version 12.0.0 to 12.1.3 [Release 12 to 12.1]
Oracle iProcurement - Version 12.0.0 to 12.1.3 [Release 12 to 12.1]
Information in this document applies to any platform.
Purpose
Oracle Approvals Management, also known as the Approvals Management Engine (AME) lets you define approval rules ba
Oracle Purchasing handles the approval. AME is designed to generate the approval list according to the conditions and
and help users find solutions for scenarios where the approval list fails to be generated.
Troubleshooting Steps
How to Enable AME
For Requisitions
In order to enable AME for requisitions, follow these steps:
https://support.oracle.com/epmos/faces/ui/km/SearchDocDisplay.jspx?_adf.ctrl-state=... 26/11/2012
Document Display
Page 2 of 12
1. Navigate to Purchasing responsibility > Setup > Purchasing > Document Types
2. Select Purchase Requisition (or Internal Requisition) as the document type
3. Specify Approval Transaction Type = PURCHASE_REQ (or INTERNAL_REQ) to enable AME approvals for Purchase
enabled for purchase requisitions:
For Purchase Orders (starting in 12.1.3)

In order to enable AME for Purchase Orders, create a document style and associate the AME workflow. Refer to
steps to create the document style and enable AME for purchase orders.
Note: AME for purchase orders is available in Procurement rollup Patch 14254641:R12.PRC_PF.B or higher. See
features of AME for purchase orders.
AME Setup
Reference Note 434143.1 How To Setup And Use AME For Purchase Requisition Approvals to learn about AME setup and
Use the Setup report to view and print the approval setup details for your transaction type. To run the setup
1.
2.
3.
4.
Login using Approvals Management Business Analyst responsibility

Click Setup Report in the Quick Links on the Administrator Dashboard to open the Setup Report page.
Query the transaction type for which you want to run the Setup Report and click Go
Click Printable page to enable you to print the report.
Document Display
Page 3 of 12
Here is a fragment of the setup report. Notice it has different sections for each one of the setup categories including
How the default approval list is built in AME

The default approval list(s) is built based on the conditions (included in rules) that the document meets. Here is a
subassemblies.
Condition
Document total
Category in subassemblies
Up to $10000
Over $10000 and not over $100000
Over $100000
Requisition total
Over $100000
Approvals matrix
This table represents a simple business case and includes the possible approval actions based on the category and amoun
1.
2.
3.
4.
User creates a requisition with product category Subassemblies and amount > $100000
AME validates the conditions against the requisition data
For each condition, AME performs the action associated to the condition in the rule
The document meets two conditions as the category is subassemblies and amount is over $100000. The
'Special audit' approval group. This will be the approval list that AME will communicate to the calling application (P
The most common reason AME raises an exception (which typically results in the related application's stopping a
in the hierarchy is indeterminate. For example, in the case of the HRMS supervisory hierarchy, an approver may have a n
offending transaction's workflow.
Document Display
Page 4 of 12
Approval process execution
Purchasing communicates with AME when a requisition is submitted for approval and also each time an approver respond
transaction and recalculates the approval list for the requisition based on the approver's response. This ensures that any
that the application follows when managing a transaction's approval process with AME:
1.
2.
3.
4.
5.
6.
7.
8.
9.
Ask AME for a transaction's entire approver list

Display the approver list to the requestor, optionally prompting them to suppress or add approvers
Communicate any approver suppressions or additions to AME
Ask AME whether the transaction's approval process is complete, and if not, what approvers (if any) to notify
If AME indicates that no further approvals are required, stop
Notify any approvers identified by AME in step 5
Wait until an approver responds to a notification
Communicate the response to AME
Return to step 4 and repeat the process until completion.
Review default approval list using Test Workbench

Use the Test Workbench to validate that the approval list is correctly generated for the possible business cases. You can
stages of the default approval list along with the applicable rules.
Steps:
1.
2.
3.
4.
5.
6.

Click on Business analyst dashboard
Select the transaction type 'Purchase Requisition Approval'
Click on Test Workbench
Click on Run Real Transaction Test (1)
For requisitions, type the transaction id (requisition header id) and click on Go to see the attributes and v
SQL > select hr.name, prh.segment1, prh.requisition_header_id
from po_requisition_headers_all prh,
hr_all_organization_units hr
where prh.org_id = hr.organization_id and
prh.segment1 = '&Enter_Req_Number';
7. For purchase orders, type the transaction id (ame_approval_id) and click on Go to see the attributes and
SQL > select hr.name, poh.segment1, poh.org_id, poh.ame_approval_id
from po_headers_all poh,
hr_all_organization_units hr
where poh.org_id = hr.organization_id and
poh.segment1 = '&Enter_PO_Number';
8. Click on Run Test Case (2) to review the applicable rules and default approval list.
Here is an example of the default approval list for one requisition in the Test workbench for the business case of our app
Document Display
Page 5 of 12
The first region represents the rules that are applicable for the document or simulated test. You can expand on the rules
that the approvers will be notified.
Note: AME does not have any test functionality that would let you update an approver's approval status such as a forwar
generated by the approval workflow and then test with the transaction id using the run real transaction test.
Note: To access the test workbench tab, you must grant individual permission sets to your application user. See
Diagnostic Steps
1. Test Workbench
Use the test workbench functionality to confirm that the default approval list is correctly generated. The screen will displa
attributes. In many of the cases, errors are self-explanatory and indicate the action to be taken. Examples of some messa
No rules are applicable to this transaction. At least one rule must apply to this transaction when the value of the attribute
The action for this error is to define additional rules to ensure that there is at least one rule for all the possible business
The transaction ID specified returned an incorrect number of rows for NON_DEFAULT_POSITION_STRUCTURE_ID. Ensur
The action for this error is to ensure that the script associated to this attribute NON_DEFAULT_POSITION_STRUCTURE_I
the parameters with the appropriate values of the transaction.
Here is an example of the result of running a test in the workbench against one requisition:
Document Display
Page 6 of 12
In this scenario for absolute job action type, the real transaction test finishes with error 'Acaccia, Mary lacks a supervisor,
to an approval authority 1. There is an active rule that requires approval from a user with at least level 4. AME cannot as
2. Transactions exception log
A transaction's exception log contains exceptions raised by AME when it processes the transaction. It can be useful to vie
To view the exception log:
Use the Transaction Exception page.
1. Click Exception Log in the Quick Links on the Administrator Dashboard to open the Transaction Exception Log
2. Query the transaction type to view the exception details for all the transactions in the specific transaction type. Oth
transaction.
The log will include the package name and specific routine that failed with the exception. Here is the log information for t
Document Display
Page 7 of 12
3. FND log
Once the approval list displays correctly in the test workbench proceed to submit the approval process from the integratio
submission and the list is not generated, obtain the FND debug log.
Reference Note 759359.1 How To Engage And Retrieve FND Logging Messages From Within iProcurement? for instruction
Here are relevant error messages for a testcase where iProcurement fails with message: Approval List could not be gener
Example of FND debug is:
Notice that for this testcase the error ora-6502 occurs after validating the information for user with orig_system_id 10008
to the FND user record.
Note: If unable to submit the requisition via iProcurement, when possible test with the core Purchasing application
4. Approval Workflow
If the document is successfully submitted for approval but the error occurs before the document is approved, review the
Reference Note 134960.1 Running WFSTAT and WFRETRY For Oracle Purchasing Workflows to obtain instructions to run
Here is the relevant workflow activity for the testcase used in the previous step.
Document Display
Page 8 of 12
The wfstat output confirms that the error is with the setup of the approver as the workflow is not able to identify the reci
5. PO_WF_DEBUG messages
Follow the steps in Note 1103068.1 'How to enable and collect approval debug data in table PO_WF_DEBUG?' to enable w
will help to troubleshoot the issue.
Example of an AME setup

This testcase uses the absolute job level action type. This action type generates a chain of authority by ascending
the rule will require approvals of a user with at least level 4 for a specific item category.
1. Define attributes
The attributes are business variables with a single value for a particular transaction. Following are the required attributes
JOB_LEVEL_NON_DEFAULT_STARTING_POINT_PERSON_ID
INCLUDE_ALL_JOB_LEVEL_APPROVERS
TOP_SUPERVISOR_PERSON_ID
TRANSACTION_REQUESTOR_PERSON_ID
Steps to define the attribute values:

1.
2.
3.
4.
5.
6.
7.

Click on attributes
Click on update to modify the value for each one of the attributes. i.e. click on update for attribute INCLUDE_ALL_
Click on update
Set the value accordingly to your business requirements. For example, if INCLUDE_ALL_JOB_LEVEL_APPROVERS i
INCLUDE_ALL_JOB_LEVEL_APPROVERS is true, then the chain includes and ends with the last approver with the r
8. Repeat steps 4-7 for the remaining attributes. Here is an example of the definition of attribute INCLUDE_ALL_JOB_
Document Display
Page 9 of 12
Note: To identify the required attributes for other pre-defined action types, see Oracle Approvals Management
2. Define conditions
A condition is a statement that is either true or false, for a given transaction. For the rule to apply to a transaction, all of
Steps to define the conditions:
1.
2.
3.
4.
5.

Click on conditions
Create conditions for your rules. For this testcase, a condition is defined to validate the item category ITEM_CATEG
Document Display
Page 10 of 12
3. Define action types
An action is an instruction to AME to modify a transaction's approval process in the manner you specify. An approval rule
Steps to enable an existing action type are:
1.
2.
3.
4.

If the action type to be used is not list, click on 'Use Existing Action Type' to enable the action type:
-
Click on Use existing action type'

Select the action type. Enable the Absolute job level action type (or the action type needed).
Click on continue
Click on finish
This scenario does not require approver groups, so this step can be skipped.
4. Define rules
The rules consist of one or more conditions and one or more actions that apply for a specific business case.
Steps to create a rule are:
1.
2.
3.
4.
5.
6.
7.
8.
9.

Click on rules
Click on Create
Type the rule name and start date
Add a condition
Add an action. Select the action type 'Absolute job level'. As it is required to have approvals of a user with at least
Save changes
Document Display
Page 11 of 12
Still Have Questions?

Join our growing Oracle Procurement Community and learn from your peers and Oracle on how to address your unique
You can access the main Oracle Communities page at http://communities.oracle.com (If you are enrolled, the Procurem
already enrolled in the Procurement community, you can do so by clicking on the link Edit Subscriptions).
OR
From "My Oracle Support" as follows:
1.
2.
3.
4.
5.
Log into My Oracle Support

Click on the 'Community' link at the top of the page
Click in 'Find a Community' field and enter Procurement
Double click on Procurement in the list
Click on the 'Create a Community Post' button and submit your question.
Document Display
Page 12 of 12
References
NOTE:759359.1 - How To Engage And Retrieve FND Logging Messages From Within iProcurement?
NOTE:134960.1 - Running WFSTAT and WFRETRY For Oracle Purchasing Workflows
NOTE:1103068.1 - How to enable and collect approval debug data in table PO_WF_DEBUG?
NOTE:434143.1 - How To Setup And Use AME For Purchase Requisition Approvals
NOTE:1487661.1 - 12.1 AME : Approval, E-Review, E-Sign and Withdrawal Features for Purchase Orders
NOTE:1487713.1 - 12.1.3 - Required Setups For Purchase Order Approval Using Approvals Management Engine (AME)

Oracle AME

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Oracle AME

Загружено:

Авторское право:

Доступные форматы

Document Display

How to Enable AME

For Purchase Orders (starting in 12.1.3)

How the default approval list is built in AME

Approval process execution

Review default approval list using Test Workbench

2. Transactions exception log

Example of an AME setup

3. Define action types

Still Have Questions?

For Purchase Orders (starting in 12.1.3)

Login using Approvals Management Business Analyst responsibility

How the default approval list is built in AME

Over $10000 and not over $100000

Approval process execution

Ask AME for a transaction's entire approver list

Review default approval list using Test Workbench

Login using Approvals Management Business Analyst responsibility

2. Transactions exception log

Example of an AME setup

Steps to define the attribute values:

Login using Approvals Management Business Analyst responsibility

Login using Approvals Management Business Analyst responsibility

3. Define action types

Login using Approvals Management Business Analyst responsibility

Click on Use existing action type'

Login using Approvals Management Business Analyst responsibility

Still Have Questions?

Log into My Oracle Support

Вам также может понравиться