Depending on the AME setup, the Approvers region includes persons who are approvers, reviewers, and signers. In the Add Adhoc Approver region, buyers can select additional approvers and specify their position in the approval chain using insertion point.
To add a person for e-signature, buyer can select an existing signer and must add that person before or after the existing signer.
However, buyers cannot add adhoc reviewers. If you use AME for purchase order review, approval, and multiple E-Signatures, then the following business rules apply:.
Buyers cannot update the purchase order if the order is in the In Process or Pre-Approved status. They can add approvers and e-signers only. Buyers have the flexibility to send purchase order documents to approvers, reviewers, or e-signers based on the AME setup.
If the e-signature feature is not enabled, then the purchase order status is set to Approved after all approvals are in. Approvers can approve, approve and forward, reject, or reassign the purchase order notification.
They can add their comments to the notification page. Multiple E-signatures can be provided during the post approval phase only. During the post approval process, approvers cannot be added and document cannot be sent for approval. Esigners have to provide their login credentials to provide their e-signature.
If the purchase order is rejected during the approval, review, or e-signature stage, then the status of the purchase order changes to Rejected. Buyers can update and resubmit such rejected purchase orders. The following example describes the business flow if AME is setup for purchase order review, approval, and multiple e-signatures. Buyer creates and submits the PO for approval.
If review is required, then based on AME rule, Purchasing routes the document to reviewer for review. If review is not required, then the application sends the PO directly to approvers based on AME rule. If e-signature is enabled for the purchase order document, after approval it goes to supplier for E-Sign and then based on AME rule, Purchasing routes the document to signers for e-signature.
If e-signature is not enabled and approvers approve the purchase order document, then the application sets the document status to Approved. If supplier signature is enabled and there are esigners as well, then after approvers have approved, Purchasing sets the document status to the Pre-Approved status and sends the document to the supplier.
After supplier signature, the document is routed to esigners. Once all esigners have signed, the document will be set in Approved status. If the purchase order is in the In Process or Preapproved status, then the buyer cannot update the document. Specify justification and relevant dates for the newly assigned roles, and click Apply to assign the roles to the user. Grant users access to the transaction types using the Grants page.
Set up user access as follows: 1. Navigate to the Personal Home Page. Select Functional Administrator Responsibility 3. From the Grants page, press on the Create Grant button 4. Click Next, review the setups and then Finish the process. This whitepaper focuses on Purchase Requisition Approval, however, many of the concepts are applicable to the other two requisition transaction types as well.
Likewise, some examples and comments in this paper are written in iProcurement context, but the same AME concepts apply to core apps requisitions also. Choose the Business Analyst Dashboard menu from the responsibility 3.
Action Types 1. An action type is a collection of actions having similar functionality. Every action belongs to an action type. Action types are enabled or disabled for a particular transaction type. AME may give an error when attempting to enable an action type for a transaction if the transaction is not designed to allow that action type.
To disable or enable action types for the transaction, select the Action Types link 3. The Action Types page shows the action types that are currently enabled for the transaction type Purchase Requisition Approval. Use the Previous and Next links to scroll through the list of enabled action types. Some of these may or may not be applicable to the currently select transaction type; AME will give an error if the user tries to add a non-relevant action type for the selected transaction type.
Attributes 1. Attributes are the base element for an AME Rule. Attribute values are retrieved from the Oracle EBusiness Suite Applications database or derived from values in the database. Select the Attributes link to view or add attributes for the selected transaction type 3. Use the Previous and Next links to scroll through the existing attributes. When AME approvals is enabled for purchase requisitions, these values are retrieved for the relevant requisition while navigating through iProcurement checkout or core apps requisition create, and AME uses this information to determine the appropriate AME rule s to use.
In addition to the seeded attributes, a customized attribute can be created. Thank you soo much. Simply wish to say your article is as astonishing. The clarity in your post is simply great, and I could assume you are an expert on this subject. Same as your blog i found another one apex oracle. Thanks a million and please keep up the gratifying work. Those guidelines additionally worked to become a good way to recognize that other people online have the identical fervor like mine to grasp a great deal more around this condition.
Same as your blog i found another one Oracle Fusion Financials. Actually I was looking for the same information on internet for Oracle Financials Cloud and came across your blog.
We are committed to providing excellent online recommendation for home buyers and sellers of personal information. You can see the newly created condition along with existing conditions. Also add the approvers and click apply button. Working in Oracle E-Business Suite for past 9 years. View All Posts. You are commenting using your WordPress. You are commenting using your Google account. You are commenting using your Twitter account. You are commenting using your Facebook account.
Notify me of new comments via email. Notify me of new posts via email. Grant Transaction Type Access to Users 1. Click Next, review the setups and then Finish the process Create new transaction Type 1.
Click Next and then Finish button. AME Setup 1. Attributes: 1.
0コメント