Oracle Apps Essentials

JDR_UTILS JDR_UTILS.LISTDOCUMENTS Use this API to list of all OA Framework the documents in a path/module. This script is very handy, as it provides a list of all the desired documents/extensions/personalizations in one go. DECLARE BEGIN jdr_utils.listdocuments('/oracle/apps/per', TRUE); END; The script above will produce a list of all the MDS Documents in HRMS plus all the BC4J extensions done to HRMS module will be listed here too. Surely you can run this for whatever module/application you desire. Notes on jdr_utils.listdocuments First parameter of this API can take the full path or partial path of the MDS** Page. Second parameter being TRUE will direct the API to list all Child Documents underneath that tree path You can use this API to know all the objects that have been extended/personalized in any specific module. For this, simply dump the output in a file and grep for customizations BC4J extensions [or call them substitutions] will be visible t

Order to Cash Process The end result will be a working Order to Cash Business Process.  The ability to take a Sales Order through the following phases: Entry, Booking, Shipping, and Invoice.  Showing the working steps through each phase. The areas of focus are: Required Setup Create Customer Create Item Organization Overview Available Inventory Price List Defaulting Rules Create Order Shipments Pick Release Ship Confirm Interface Trip Stop (ITS) Invoice All users who wish to set up, troubleshoot or debug a basic Order to Cash cycle in Order Management (OM), that is to say from order creation to invoicing. NOTE:  This flow is for a shippable item.  Please refer to the following Notes for additional flows: Bill Only: How Do I Use Workflow Process, LINE FLOW - GENERIC, BILL ONLY WITH INVENTORY INTERFACE Note 1069241.1 Back to Back order: Back-to-Back Sales Order Cycle In Order Management Note 751325.1 Drop ship: Drop Ship Sales Order Cycle In Order Man

AME Issue - Incorrect entry in WF_ROLES Symptom: A.  User received following error for Purchase Requisition AME workflow.   ORA-20001: The approver identified by the following parameters is invalid: originating system PER originating-system ID PER_ID. Please delete or replace this approver wherever they occur in AME data, including approval groups, list-modification conditions, and substitution actions. This approver does not have an entry in wf_roles. (ORIG_SYSTEM_ID=3783).   B.  Error occurs attempting to approve a Quote: ORA-20001: The approver identified by the following parameters is invalid: originating system PER originating-system ID PER_ID. Please delete or replace this approver wherever they occur in AME data, including approval groups, list-modification conditions, and substitution actions. This approver does not have an entry in wf_roles. (ORIG_SYSTEM_ID=1)     C.  In 11.5.10, the following errors occur when submitting Requisiti

Approval Management Engine - AME For Purchase Requisition Approvals Purchase Requisitions can be routed for approval using the AME Approval Management Engine. This whitepaper describes how to setup AME for use with requisition approvals, and shows how a requisition approval list is built based on the AME setup. Approvers in the AME based approver list are assigned to the requisition based on the AME rules setup for the Purchase Requisition Approval transaction. Similar setup can be done for Requester Change Order Approval and for Internal Requisition Approval, although those are not specifically covered in this whitepaper. The screenshots provided are based on 11i.AME.B, and some of the navigation details are specific to 11i.AME.B. However, most of the details provided are applicable to 11i.AME.A and higher including R12. Assign AME Roles and Responsibilities AME responsibilities in 11i.AME.A are assigned directly to the users. However, In R12 or 11i.AME.B and higher, AME respons

Document Open State Errors Document Manager failures are classified as Doc Mgr Error 1 (Document Approval Manager timeout) or Doc Mgr Error 2 (Document Approval Manager Not Active). Any other document manager exception is considered a Doc Mgr Error 3 and the cause can be related to setup issues or a code fix. How to find additional error messages When the purchase order or requisition approval workflow fails with a Doc Mgr Error 3 exception, the POERROR workflow will send a notification to the preparer or owner of the document. This notification will display additional error messages. These messages come from the SYSADMIN_ERROR_MSG workflow attribute that is populated by the purchase order or requisition approval workflow during its execution. 1. In order to see the errors via the application, log in as the preparer or document owner and go to the worklist to review the 'Document manager failed' notification. This is an example of one notification sent to the preparer