Search Results csi_ont_txn_pub




Overview
Explore in AI Chat

Overview

CSI_ONT_TXN_PUB is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It belongs to the CSI (Customer Intelligence / Install Base) product family and bridges the Order Management (ONT) transaction model with the Install Base transaction model. Its purpose is to convert an Oracle Order Management order line into a CSI (Install Base) transaction record, so that shipped or fulfilled order lines can be processed into Install Base inventory and instance tracking.

The package is declared with AUTHID CURRENT_USER, meaning its SQL statements execute under the privileges of the calling user rather than the package owner. The header indicates that the specification has been stable since the 12.0 code line, which is consistent with its availability across both 12.1.1 and 12.2.2. It exposes a single public entry point, POSTTRANSACTION, and is referenced by two other packages within the EBS codebase, indicating it is intended as a reusable integration API rather than a private helper.

Key Procedures and Functions

  • postTransaction — The sole documented procedure. It accepts an order line identifier as input and returns status and diagnostic outputs, including a return status code, a message identifier, an error code, and an error message. Its purpose is to post a single Order Management order line into the Install Base transaction interface so that the line can be picked up by CSI transaction processing (batch transaction lines) for Install Base updates. The message identifier output enables the caller to retrieve the associated message text from the Oracle message dictionary (FND_MESSAGES) for translated, context-aware diagnostics.

No other public procedures or functions are documented in the ETRM metadata for this package. Callers should treat POSTTRANSACTION as the only supported public interface and rely on the return status to determine success or failure prior to further processing.

Tables Accessed

The documented tables accessed through APPS synonyms indicate both the source and target sides of the integration:

  • OE_ORDER_LINES_ALL — The Order Management order line source. The package reads the line identified by the input parameter to derive the item, quantity, and transaction context for posting.
  • MTL_SYSTEM_ITEMS and MTL_SYSTEM_ITEMS_B — Item master and item master base tables, used to validate and resolve the item associated with the order line, including whether the item is Install Base tracked.
  • CSI_BATCH_TXN_LINES — The CSI batch transaction interface table. This is the primary write target: the procedure inserts (or updates) the Install Base transaction line that will be processed by the CSI batch transaction concurrent program.
  • FND_CONCURRENT_QUEUES — Used to identify or validate the concurrent queue context, supporting the interaction with concurrent processing that consumes the staged CSI transaction lines.

Usage Notes

CSI_ONT_TXN_PUB is typically invoked programmatically rather than from an end-user form. Common invocation scenarios include:

  • Custom integration code — Customer or partner extensions that need to push a specific Order Management line into the Install Base transaction interface can call POSTTRANSACTION directly, checking x_return_status for FND_API.G_RET_STS_SUCCESS (or equivalent) before proceeding.
  • Other EBS packages — The metadata records two referencing packages, confirming it is called from within Oracle-delivered code as part of the Order Management to Install Base flow.
  • Concurrent processing context — Because the staged rows land in CSI_BATCH_TXN_LINES, the procedure is generally paired with the CSI batch transaction concurrent program, which subsequently processes those lines into Install Base. Callers should not assume the Install Base update is complete immediately after POSTTRANSACTION returns success; success indicates the line was posted to the interface.

Developers should always honor the output parameters (message ID, error code, error message) and log them for troubleshooting. Direct DML against CSI_BATCH_TXN_LINES should be avoided in favor of this API, since it encapsulates the validation and structure required by CSI processing. Because the package runs with AUTHID CURRENT_USER, invoking environments must grant the necessary privileges to the calling schema.