Getting Intermittent Errors Calling Oe_order_pub.process_order When Called From SOA
(Doc ID 2497971.1)
Last updated on JUNE 22, 2019
Applies to:Oracle Order Management - Version 12.1.3 and later
Information in this document applies to any platform.
We have existing SOA composites that have been working in production since 2012 that recently started getting intermittent errors when the called procedure uses oe_order_pub.process_order.
The composite named XXXOTCWebSalesOrderIn calls custom package xxotc_web_order and is getting error :
"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"
The composite named XXXOTCEDISalerOrderIn calls custom package xxotc_edi_orders_pkg and is getting error "API Error: Operating unit access is not allowed. Please check that you have access to the operating unit: NNN XXX CUSTOMER OU, NN" in addition to "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".
Both package are autonomous transactions but appear to be failing in call to fnd_global.apps_initialize. Similar issue seen in 2012 and the resolution was to add the autonomous transaction pragma to the packages.
How to resolve the above?
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