Search Results csi_systems




Overview
Explore in AI Chat

Overview

APPS.CSI_ORDER_SHIP_PUB is a public (PUB-classified) PL/SQL package body within the Oracle E-Business Suite Customer Intelligence (CSI) / Enterprise Installation Base family. In Oracle EBS 12.1.1 and 12.2.2, its primary business function is to interface order shipment activity from Order Management (OE) into the CSI installation base and transaction repository. When order lines are shipped, the package determines which shipped items are trackable in the installation base, constructs and validates the corresponding CSI transaction records, and updates the installed base (item instances, assets, and relationships). It also handles configured (ATO) items by processing their option lines so that the correct instances and transactions are generated for each option. The package is invoked as part of the ship-confirm flow and interacts with the event queue that drives downstream CSI processing.

Key Procedures and Functions

  • ORDER_SHIPMENT — The main entry point that processes an order shipment, orchestrating construction of transaction data, validation, matching with shipping information, and updates to the installation base.
  • GET_ORDER_SHIPMENT_REC — Retrieves the order shipment record/context used as input to the processing logic.
  • BUILD_SHTD_TABLE — Builds the in-memory shipping/transaction detail table used during processing.
  • CONSTRUCT_FOR_TXN_EXISTS — Determines whether a CSI transaction already exists, preventing duplicate interface records.
  • UPDATE_INSTALL_BASE — Applies the shipment results to the installation base records (instances, assets, and related attributes).
  • MATCH_TXN_WITH_SHIP — Matches existing CSI transactions against shipped lines to reconcile quantities and instances.
  • PROCESS_TXN_DTL — Processes transaction line details for the shipment.
  • PROCESS_OPTION_ITEM — Processes ATO option items; the source excerpt shows process_ato_options cursor logic joining OE_ORDER_LINES_ALL with MTL_SYSTEM_ITEMS to identify trackable, shippable option lines and publish the CSISOFUL event (via XNP_CSISOFUL_U.publish), honoring the CSE_BYPASS_EVENT_QUEUE profile.
  • REBUILD_SHIPPING_TBL — Reconstructs the shipping table, typically for retry or correction processing.
  • VALIDATE_TXN_TBL — Validates the assembled transaction table before writing to CSI.
  • DECODE_MESSAGE — Decodes message/error codes returned during processing.
  • OKE_SHIPMENT — Integration hook for Oracle Contracts (OKE) shipment handling.
  • GET_COMP_INSTANCES_FROM_WIP — Retrieves component instances originating from WIP for configured items.

Internal helper procedures such as debug and api_log wrap calls to CSI_T_GEN_UTILITY_PVT for logging when the debug level is enabled, and set the API name context.

Tables Accessed

Usage Notes

CSI_ORDER_SHIP_PUB is not typically called directly by end users; it is invoked by the Order Management ship-confirm process and by CSI event-handling infrastructure when shipments occur. It is referenced by seven other packages, indicating it forms part of a shared CSI interface layer. The presence of the CSE_BYPASS_EVENT_QUEUE profile check shows that deployments may bypass XML event publishing and process synchronously. Customizations that need to create or reconcile installation base records from shipments should call ORDER_SHIPMENT rather than individual internals, and any extension should respect the existing record structures (order_line_rec, transaction_error_rec) and return-status conventions of FND_API.