Search Results is_cbod_out_reqd

Overview

APPS.OE_ORDER_IMPORT_WF is a workflow-enabled PL/SQL package in Oracle E-Business Suite that orchestrates the Order Import process for the Order Management module. It functions as the integration layer between the Oracle Workflow engine and the Order Import concurrent program, providing the selector functions, activity result handlers, and event-raising routines that drive the Order Import workflow. The package is central to converting staged data from the Order Management interface tables into live sales orders, and it coordinates downstream activities such as order acknowledgment, XML message processing, and change-management events. The package holds a VALID status in both 12.1.1 and 12.2.2 and is maintained under the APPS schema. Its API classification in ETRM is OTHER, meaning it is not a public inbound API but an internal workflow support package referenced by several other Order Management packages, including OE_ACKNOWLEDGMENT_PUB, OE_DELAYED_REQUESTS_UTIL, and OE_ERROR_WF.

Key Procedures and Functions

The package exposes 17 documented procedures and functions supporting the Order Import workflow:

• Workflow selector functions — OEOI_SELECTOR, OESO_SELECTOR, and OEOA_SELECTOR return the next activity or process for Order Import, Sales Order, and Order Acknowledgment workflow branches respectively.
• START_ORDER_IMPORT — initiates the Order Import workflow for a given run.
• IS_OI_COMPLETE — determines whether the Order Import process has finished for the workflow item.
• CALL_WF_PURGE — invokes the Workflow purge utility to clean up completed workflow data.
• SET_DELIVERY_DATA — populates delivery-related workflow item attributes.
• IS_PARTNER_SETUP — checks whether partner/trading-partner configuration exists for the order.
• PROCESS_XML_ACKNOWLEDGMENT_WF — drives XML acknowledgment processing within the workflow.
• GET_ACTIVITY_RESULT — retrieves the outcome of a completed workflow activity.
• RAISE_EVENT_SHOWSO_WF — raises the business event that surfaces the sales order.
• SET_USER_KEY — sets the workflow user key for the item.
• IS_CBOD_OUT_REQD — determines whether a CBOD (canonical business object document) outbound message is required.
• POPULATE_CBOD_OUT_GLOBALS — initializes global variables for CBOD outbound processing.
• SET_CBOD_EVENT_KEY — assigns the event key for the CBOD outbound event.
• RAISE_EVENT_XMLINT_WF — raises the XML integration event used by the workflow.
• IS_OAG_OR_ROSETTANET — determines whether the trading partner is an Oracle Application Gateway or RosettaNet partner, affecting message handling.

Tables Accessed

The package reads and writes several Order Management and foundation tables through APPS synonyms. OE_HEADERS_INTERFACE is used to retrieve and process staged order data prior to import, while OE_ORDER_HEADERS stores the resulting imported sales orders. ECX_TP_HEADERS provides trading-partner configuration used by IS_PARTNER_SETUP and the CBOD/XML logic. HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, and HZ_CUST_SITE_USES_ALL supply customer account and site information needed to validate order data during import. FND_CONCURRENT_REQUESTS links the workflow to the parent concurrent request. Workflow tables WF_ITEMS, WF_ITEM_ACTIVITY_STATUSES, and WF_PROCESS_ACTIVITIES provide the item and activity state used by the selector and result functions. OE_XML_MESSAGE_SEQ_S supplies sequence numbers for XML message processing, and DUAL is used for singleton queries.

Usage Notes

OE_ORDER_IMPORT_WF is not invoked directly by end users or standard forms. It is called by the Order Import workflow process launched from the Order Import concurrent program and by Oracle Workflow activity definitions configured for that process. In custom extensions, it is most commonly encountered indirectly: integrators subscribing to the Sales Order acknowledgment event surfaced through RAISE_EVENT_SHOWSO_WF reference OE_ACKNOWLEDGMENT_PUB, which in turn calls this package. Because the package manipulates workflow item state and interface tables, custom code should not call its procedures out of sequence. It is referenced by OE_ACKNOWLEDGMENT_PUB, OE_DELAYED_REQUESTS_UTIL, OE_ERROR_WF, and itself, confirming its role as an internal workflow orchestration utility rather than an open API.