Search Results get_instance_party

Overview

APPS.CSI_UTL_PKG is a utility PL/SQL package in the Oracle E-Business Suite (12.1.1 and 12.2.2) that supports the Oracle Installed Base (CSI) application and its integration with order management and shipping flows. Its role is to provide reusable helper logic for retrieving and validating installed base data — parties, accounts, instances, descriptive flexfield attributes, object version numbers, and organization assignments — so that higher-level CSI APIs and transaction processors can operate consistently. The package is registered in the ETRM repository under the APPS schema with a classification of OTHER and a status of VALID. It is a widely reused dependency: the ETRM documentation lists fourteen referencing packages and ten caller packages, indicating that CSI_UTL_PKG functions as a common infrastructure layer within the CSI module rather than a standalone business API.

Key Procedures and Functions

The ETRM documentation identifies sixty-eight documented procedures and functions. The most significant of these include:

• Party and account retrieval — GET_CURR_PARTY, GET_PARTY_ID, GET_PARTY_ACCOUNT, GET_INSTANCE_PARTY, and VALIDATE_INST_PARTY handle resolution of the current party, instance party, and associated customer account for a given installed base context.
• Instance and relationship logic — GET_INSTANCE, CHECK_RELATION_EXISTS, CHECK_CONFIG_EXISTS, and VALIDATE_INST_PARTY determine whether an instance or a configuration relationship exists before downstream processing proceeds.
• Attribute and flexfield access — GET_EXT_ATTRIBS and GET_PRICING_ATTRIBS retrieve extensible attributes and pricing-relevant attributes associated with instances.
• Version number resolution — GET_II_OBJ_VER_NUM, GET_ORG_OBJ_VER_NUM, GET_EXT_OBJ_VER_NUM, GET_PTY_OBJ_VER_NUM, and GET_ACCT_OBJ_VER_NUM return object version numbers required by the CSI object-versioning mechanism.
• Organization, UOM, and entitlement — GET_ORG_ASSIGN, GET_PRIMAY_UOM, and ENTITLEDCONTRACTS provide organization assignment lookup, primary unit of measure, and contract entitlement checks.
• Transaction detail construction — SPLIT_SHIP_REC and CREATE_TXN_DETAILS support ship-record splitting and creation of transaction detail rows.

These routines are exposed as reusable building blocks; their internal signatures are not enumerated in the ETRM excerpt.

Tables Accessed

The package operates against the core CSI and trading-partner tables through APPS synonyms:

• CSI_ITEM_INSTANCES and CSI_ITEM_INSTANCES_H — current and historical item instance records; central to instance and party resolution.
• CSI_I_PARTIES and CSI_IP_ACCOUNTS — instance-party associations and installed base accounts.
• CSI_I_ORG_ASSIGNMENTS — organization assignments for instances.
• CSI_II_RELATIONSHIPS and CSI_T_II_RELATIONSHIPS — instance-to-instance relationship definitions used by CHECK_RELATION_EXISTS and CHECK_CONFIG_EXISTS.
• CSI_INSTALL_PARAMETERS and CSI_INSTANCE_STATUSES — installation parameters and instance status lookups.
• CSI_TRANSACTIONS, CSI_T_TRANSACTION_LINES, and CSI_T_TXN_LINE_DETAILS — transaction and transaction-line staging used by CREATE_TXN_DETAILS and related processing.
• CSI_IEA_VALUES and CSI_SOURCE_IB_TYPES — extensible attribute values and source installed base types.
• HZ_CUST_ACCOUNTS — trading community customer accounts referenced during party/account resolution.

Usage Notes

CSI_UTL_PKG is an internal utility package and is not intended to be called directly from Oracle Forms or from concurrent program parameters by end users. It is invoked programmatically by the CSI public and private APIs that depend on it, including CSI_INTERFACE_PKG, CSI_ORDER_SHIP_PUB, CSI_ORDER_FULFILL_PUB, CSI_RMA_FULFILL_PUB, CSI_PROCESS_TXN_PVT, CSI_WIP_TRXS_PKG, CSI_INV_TXNSTUB_PKG, CSI_T_TXN_DETAILS_PVT, and CSI_INTERFACE_PKG. In turn, it depends on CSI_DATASTRUCTURES_PUB, CSI_ORDER_SHIP_PUB, CSI_T_DATASTRUCTURES_GRP, FND_API, and OE_ORDER_PUB, confirming its position between the Order Management APIs and the Installed Base data model. Custom code should invoke the documented public CSI APIs rather than calling CSI_UTL_PKG directly, since its procedures are primarily internal helpers. The presence of FND_API and STANDARD dependencies indicates use of the standard EBS error-handling and API framework conventions.