Results for “cln_sync_inventory_pkg”

48 results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CLN_SYNC_INVENTORY_PKG is an Oracle EBS inventory reporting package owned by APPS within the CLN (Supply Chain/Logistics) module. It is classified as an OTHER API with AUTHID CURRENT_USER, indicating that it executes with the privilege set of the calling user rather than the definer. Its primary business function is to support the inventory report generation workflow by capturing user-supplied selection criteria entered through a concurrent program, resolving the underlying on-hand inventory and disposition data, and passing it to the report generation layer. This package sits at the front end of the inventory sync/reporting process, bridging user-defined parameters with Oracle Inventory's native quantity-on-hand logic. Two procedures, RAISE_REPORT_GEN_EVENT and GET_XML_TAG_VALUES, constitute the package's complete documented API surface.

Key Procedures and Functions

The package exposes two documented procedures, each aimed at a distinct stage in the inventory report lifecycle.

  • RAISE_REPORT_GEN_EVENT — This is the entry point. Its stated purpose is to capture the parameters required for generation of the inventory report as inputted by the user via a concurrent program. It accepts the standard concurrent program OUT parameters (x_errbuf and x_retcode) along with a parameter set covering the inventory user, inventory organization, subinventory, lot number, item category, item number range, item revision range, and the three disposition flags (available, blocked, allocated). It effectively gathers the report request context and raises the report generation event.
  • GET_XML_TAG_VALUES — This procedure performs the substantive data resolution. Its documented purpose is to call the inventory API INVPQTTS.pls and, based on user input passed through the concurrent program together with a profile option, calculate quantity on hand, available to use, quantity blocked, and quantity allocated. It accepts a broader parameter list including organization, disposition flags, subinventory, lot number, item number, item revision, lot control number, revision control number, and trading partner context (type, ID, and site ID), returning status and message data to the caller.

Tables Accessed

The package references a concentrated set of Oracle Inventory and CLN tables through APPS synonyms. The CLN tables CLN_GENERIC_S and CLN_SYNC_INV_DOC_S support the CLN-side synchronization and document structures. Trading partner context is derived from ECX_TP_HEADERS. Core inventory reporting is sourced from MTL_ONHAND_QUANTITIES_DETAIL (the primary on-hand quantities source), MTL_LOT_NUMBERS (lot validation and enumeration), MTL_SECONDARY_INVENTORIES (subinventory validation), and MTL_ITEM_CATEGORIES (category-based item filtering). Customer-specific item references are resolved through MTL_CUSTOMER_ITEMS and MTL_CUSTOMER_ITEM_XREFS, relevant where trading partner or customer item numbering is used. DUAL supports parameter-lookup and defaulting logic. WF_PARAMETER_LIST_T stores concurrent/report parameter lists associated with the event raised by the package. These tables are read predominantly to validate inputs and derive the quantity and disposition figures that feed the generated report.

Usage Notes

CLN_SYNC_INVENTORY_PKG is invoked from the concurrent program interface. RAISE_REPORT_GEN_EVENT is registered as a concurrent program executable or is called from the submission layer, receiving the user's report criteria and raising the report generation event. GET_XML_TAG_VALUES is then called to populate the report's data tags, delegating the quantity calculations to INVPQTTS.pls and factoring in the governing profile option. The package is not referenced by any other package (referenced by 0 other packages), so it is intended to be called directly from concurrent processing or, where variation is required, from custom extension code. Because it runs AUTHID CURRENT_USER, the invoking session must hold the necessary privileges on the underlying MTL and CLN objects. Typical consumers should supply a valid inventory organization and item identifier, as these drive the on-hand calculations, and should ensure trading partner parameters are populated when customer item cross-reference filtering is required. Status and error data returned through the OUT parameters should be checked by the caller before relying on the generated report content.