Results for “inv_organization”
2 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
CLN_SYNC_INVENTORY_PKG is an Oracle E-Business Suite PL/SQL package owned by APPS that supports the Cycle Count and Physical Inventory synchronization framework. Its primary business function is to capture the runtime parameters a user supplies through a concurrent program and translate them into a workflow business event that drives generation of an inventory report. The package bridges the Oracle Inventory on-hand data model with the Oracle Workflow event infrastructure, ensuring reporting parameters are persisted as event context before the report document is rendered.
The header comment ($Header: CLNSINVB.pls 120.1 2005/11/03) indicates the package dates to the 11i era and has been carried forward into EBS 12.1.1 and 12.2.2 without structural revision. Its initialization of a debug level from the CLN_DEBUG_LEVEL profile option reflects the wider CLN (Cycle Count/Physical Inventory) debugging convention used across the product line.
Key Procedures and Functions
- RAISE_REPORT_GEN_EVENT — The central procedure of the package. It accepts the reporting criteria entered by the user (operating unit, inventory organization, subinventory, lot number, item category, item number range, revision range, and disposition flags such as available, blocked, and allocated) together with the standard concurrent program error buffer and return code. It validates the request, resolves supporting identifiers such as the transaction header, document number, XML Gateway transaction type and subtype, document ID, trading partner type, ID, site, and party name, and then constructs a Workflow parameter list (wf_parameter_list_t). The procedure raises the report generation business event, supplying an event key and the assembled parameter list so the subscribing workflow process can generate the inventory report. Diagnostic output is controlled through cln_debug_pub using the configured debug level.
- GET_XML_TAG_VALUES — A companion function that resolves the XML tag values associated with the report generation event. It supports the same XML Gateway-oriented metadata assembled by RAISE_REPORT_GEN_EVENT, providing the tag/value pairs required for document generation and downstream event consumption.
Tables Accessed
The package reads from several Oracle Inventory and Cycle Counting tables, accessed through APPS synonyms, to validate user input and assemble event context:
- MTL_ONHAND_QUANTITIES_DETAIL — the on-hand balance source used to scope inventory quantities for the requested organization, subinventory, lot, and disposition.
- MTL_SECONDARY_INVENTORIES — validates and resolves the subinventory parameter.
- MTL_LOT_NUMBERS — validates lot-controlled item inputs.
- MTL_ITEM_CATEGORIES — resolves the item category parameter.
- MTL_CUSTOMER_ITEMS and MTL_CUSTOMER_ITEM_XREFS — map internal items to customer-facing item and cross-reference data used in the XML document.
- CLN_GENERIC_S and CLN_SYNC_INV_DOC_S — CLN-owned sequence and document sources supplying identifiers for the synchronization document.
- ECX_TP_HEADERS — XML Gateway trading partner header data required to build the event transaction context.
- WF_PARAMETER_LIST_T and DUAL — the workflow parameter collection type used to package event arguments, and the standard single-row query source.
Usage Notes
RAISE_REPORT_GEN_EVENT is designed to be invoked from an Oracle EBS concurrent program, where the runtime parameters (operating unit, inv_organization, subinventory, lot, item category, item ranges, revisions, and disposition flags) are passed directly from the concurrent program parameter set. It can also be called from custom PL/SQL that needs to trigger inventory report generation through the Workflow event system, provided the caller supplies a valid event key and parameter list.
The package is not referenced by any other documented package, so it sits at the top of its call chain. Because the report generation is asynchronous, callers should expect the procedure to complete after raising the event rather than after the report itself is produced. Debugging is enabled by setting the CLN_DEBUG_LEVEL profile option, with output directed through cln_debug_pub; values of 2 or lower produce entry-trace messages. In 12.2.2, the package continues to rely on APPS synonyms and the XML Gateway/Workflow schemas, so any change to those underlying objects should be evaluated against its event assembly logic.