Search Results get_extended_attrib_values




Overview

APPS.CSI_ITEM_INSTANCE_PUB is the public PL/SQL API for Item Instance management within Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the CSI (Install Base) product and is classified as a PUB API, meaning Oracle supports its direct invocation from custom code. The package is declared with AUTHID CURRENT_USER, so execution privileges follow the calling schema rather than the APPS owner.

The business entity it governs is CSI_ITEM_INSTANCE — the record of a tracked, serialized, or otherwise identifiable item held by a party in the Install Base. The package exposes routines to create, update, copy, expire, and query item instances and their subordinate structures, including extended attributes and version labels. It is a heavily reused asset: the ETRM metadata records that 65 other packages reference it, which makes it a foundational dependency for Install Base, Service Contracts, and asset lifecycle flows.

Key Procedures and Functions

The API surface comprises 15 documented procedures and functions:

Tables Accessed

The package reads and writes the following objects through APPS synonyms. CSI_ITEM_INSTANCES and its history table CSI_ITEM_INSTANCES_H hold the current and prior instance records. CSI_I_PARTIES and CSI_IP_ACCOUNTS store the party and party-account associations. CSI_I_EXTENDED_ATTRIBS stores extended attribute values, while CSI_I_VERSION_LABELS holds version label definitions. CSI_II_RELATIONSHIPS records relationships between instances. CSI_TRANSACTIONS captures Install Base transactions generated by instance activity. CZ_CONFIG_HDRS supports configuration header data, and MTL_ITEM_CATEGORIES provides item category validation. DBMS_SQL and PLITBLM are used internally for dynamic SQL and PL/SQL table handling.

Usage Notes

CSI_ITEM_INSTANCE_PUB is normally invoked by Oracle forms and concurrent programs within Install Base and Service, and by custom extensions that must register or retire tracked items. The EXPIRE_ITEM_INSTANCE routine is the standard supported mechanism for retiring an instance; clients should call it rather than performing direct DML on CSI_ITEM_INSTANCES. Because the package is a supported PUB API, custom code should rely only on the documented signatures, honor the p_api_version, p_init_msg_list, p_commit, and p_validation_level conventions, and inspect the returned message stack after each call.