Search Results get_cz_relations

Overview

APPS.CSI_INTERFACE_PKG is a PL/SQL package in the Oracle E-Business Suite Applications schema that supports the Oracle Installed Base (CSI) module by managing the interface of transactional configuration, instance, and inventory data into the CSI data model. It serves as an internal processing workhorse for converting transactional context — orders, inventory movements, configuration relationships, and instance keys — into the installed base structures held in the CSI_ITEM_INSTANCES family of tables. The package is documented in ETRM as VALID and is classified under the generic "OTHER" API category, indicating that it is not an officially supported public API surface but an internal utility relied upon by other CSI components.

Its dependency footprint confirms this role. CSI_INTERFACE_PKG depends on CSI_DATASTRUCTURES_PUB, the CSI_T_DATASTRUCTURES_GRP and CSI_UTILITY_GRP table-partitioned groups, and the FND_API standard error and message handling layer. In turn it is referenced by seven other packages, most notably CSI_ONT_TXN_PUB, CSI_ORDER_FULFILL_PUB, CSI_ORDER_SHIP_PUB, CSI_CZ_INT, CSI_UTL_PKG, and CSI_DEBUG_PKG, placing it at the centre of order-to-installed-base and shipping-to-installed-base integration.

Key Procedures and Functions

ETRM documents twenty-three procedures and functions, reflecting the breadth of the interface workload:

• Source and attribute retrieval: GET_SOURCE_INFO, GET_ORDER_LINE_SOURCE_INFO, GET_ITEM_ATTRIBUTES, and GET_EXTENDED_ATTRIB_VALUES supply the descriptive data required to populate instance records.
• Transaction detail construction: BUILD_DEFAULT_TXN_DETAIL, REBUILD_TXN_DETAIL, GET_CZ_TXN_DETAILS, PROCESS_CZ_TXN_DETAILS, GET_MTL_TXN_TBL, PRE_PROCESS_MTL_TXN_TBL and SYNC_TXN_DTL_AND_MTL_TXN assemble, reconcile, and align the transaction line detail with the inventory transaction table.
• Configuration and relationship logic: GET_CONFIG_KEYS_FOR_ORDER, GET_RELATIONS, and GET_CZ_RELATIONS derive configured-item keys and parent-child relationships.
• Instance management: GET_INVENTORY_INSTANCES, DECREMENT_INVENTORY_INSTANCES, and CHECK_MACD_PROCESSING handle instance retrieval and quantity adjustment.
• Diagnostic and integration utilities: DUMP_INSTANCE_KEY, DUMP_INSTANCE_KEYS, and INTERFACE_IB provide debugging output and the core interface entry point to the installed base.

Tables Accessed

The package reads and writes CSI master and transaction tables through APPS synonyms: CSI_ITEM_INSTANCES, CSI_INSTANCE_STATUSES, CSI_IEA_VALUES, CSI_II_RELATIONSHIPS, CSI_T_II_RELATIONSHIPS, CSI_INSTALL_PARAMETERS, CSI_IP_ACCOUNTS, CSI_I_ORG_ASSIGNMENTS, CSI_I_PARTIES, and CSI_I_PRICING_ATTRIBS hold the instance, relationship, account, and pricing context. Staging and detail data pass through CSI_T_TRANSACTION_LINES and CSI_T_TXN_LINE_DETAILS. Customer data is resolved via HZ_CUST_ACCOUNTS, HZ_CUST_ACCOUNT_ROLES, and HZ_CUST_ACCT_SITES_ALL, linking an installed instance to the correct customer account and site.

Usage Notes

CSI_INTERFACE_PKG is invoked internally rather than directly by end users. It is called by order management and shipping flows (CSI_ONT_TXN_PUB, CSI_ORDER_SHIP_PUB, CSI_ORDER_FULFILL_PUB), by the configuration integration layer (CSI_CZ_INT), and by utility packages (CSI_UTIL_PKG, CSI_UTILITY_GRP). Because it is not a published API, customisations should call the supported public interfaces — CSI_ITEM_INSTANCE_PUB or CSI_DATASTRUCTURES_PUB — rather than this package. On both EBS 12.1.1 and 12.2.2 the object is present and VALID; the 12.2 online patching model requires that any custom callers be kept out of the AD_ZD-editioned dependency chain to avoid invalidation during patching cycles.