Search Results mtl_transaction_id

Overview

XNP_CSIWIPBR_U is an Oracle E-Business Suite messaging package that belongs to the XNP (XML Network Protocol / Oracle EBS messaging) framework. Its core purpose is to construct, publish, and send XML-based outbound business messages associated with Work In Process (WIP) and inventory movement events. The package name suffix "CSIWIPBR" indicates that the messages it builds relate to WIP build/discrete job processing, where the trigger driver is an inventory transaction. The presence of the XNP$MTL_TRANSACTION_ID parameter confirms that the message generation logic is keyed directly to a row in the material transaction stream, which is why a search for mtl_transaction_id surfaces this object. In the context of Oracle EBS 12.1.1 and 12.2.2, the package acts as an integration adapter: it converts a WIP-related material transaction into a structured XML message and dispatches it through the XNP messaging infrastructure to downstream consumers such as trading partners, EDI gateways, or external supply chain systems.

Key Procedures and Functions

• CREATE_MSG — The central builder routine. It accepts the driving identifiers (notably the material transaction ID and organization/inventory item context) plus optional routing attributes such as sender name, recipient list, version, reference IDs, order ID, WIP instance ID, FA instance ID, delay, and interval. It initializes the XML document, retrieves a message sequence, populates header and body elements using XNP_XML_UTILS, and returns the assembled message header and text along with error code and message outputs. It raises e_MISSING_MANDATORY_DATA when required inputs are absent.
• VALIDATE — Performs pre-processing checks on the input context to confirm that the transaction payload is eligible for messaging, guarding against incomplete or invalid source data.
• PUBLISH — Stages the constructed message into the XNP outbound queue for asynchronous delivery.
• SEND — Enqueues the message to the AQ-based messaging transport so it can be transmitted to the designated recipient.
• PROCESS — The primary orchestration entry point that drives the end-to-end flow (build, validate, publish, send) for a transaction.
• DEFAULT_PROCESS — A default processing path used when the caller does not supply a specialized handler, ensuring a consistent fallback workflow.

Tables Accessed

The documented table reference for this package is DBMS_AQ. Although DBMS_AQ is a PL/SQL-supplied package rather than a base table, its inclusion confirms that the package interacts with the Advanced Queueing infrastructure to enqueue outbound XML messages. Message metadata and sequence values are sourced through XNP framework objects such as XNP_MESSAGE (used via get_sequence). The material transaction and WIP context is passed in as scalar parameters (for example XNP$MTL_TRANSACTION_ID) rather than being read by direct table joins within the documented body, so the transaction source data is resolved by the caller before invocation.

Usage Notes

XNP_CSIWIPBR_U is typically invoked from within the WIP transaction processing flow or from XNP message dispatch logic rather than being called directly from a form. It is referenced by two other packages within the ETRM classification, indicating it sits in a layered call chain where a parent process supplies the material transaction identifier. The PROCESS and DEFAULT_PROCESS routines are the usual entry points for standard integration, while CREATE_MSG is called directly by custom code that requires finer control over header parameters such as recipient lists, versions, and reference identifiers. Administrators troubleshooting outbound WIP messaging should enable XNP logging, verify the message sequence and AQ queue state, and confirm that the originating material transaction is committed before the package is executed.