Process_Order_25 Is Not Able To Process All OU Under A Security Profile
(Doc ID 2333062.1)
Last updated on FEBRUARY 16, 2019
Applies to:Oracle Order Management - Version 12.2.5 and later
Information in this document applies to any platform.
On : 12.2.5 version, Transaction Entry
Process_Order_25 is not able to process All OU installed under a Specific Security Profile
Using OE_INBOUNT_INT.process_order_25 as a web service to create orders in EBS.
However its not working as expected in Sync with MO Setups, Noticed the below issues:
First Case : If I set MO: Security Profile alone for Order Management Super User, Process Order API Call is failing with ORA-20001: SQL_PLSQL_ERROR: N, ROUTINE, MO_GLOBAL.VALIDATE_ORGID_PUB_API, N, ERRNO, -20001, N, REASON, ORA-20001: in Package OE_Order_PUB Procedure Process_Order
Second Case: If I set MO: Security Profile and MO: Default Operating Unit both for Order Management Super User, The API works only for single OU that means if AB OU is there in Default Operating Unit Profile Option, it will run only for that Operating Unit.
Also we are passing operating unit Name only in P_Operating_unit parameter in Process_order_25 API.
Have tried passing Org_id in P_HEADER_REC, then it is working fine, but as its a interface between OMC & EBS so we will not be able to derive any ID using OU Name.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document