Search Results ins_count_rec
Overview
APPS.CSI_ITEM_INSTANCE_PVT is a private PL/SQL package within the Oracle E-Business Suite Install Base (CSI) module. It encapsulates the core business logic for creating, maintaining, validating, and expiring item instances — the individual records that represent tracked assets, equipment, and serially or lot-controlled items held by an organization. In EBS 12.1.1 and 12.2.2 this package serves as the implementation layer behind the public Install Base APIs, providing the structures, validation rules, and persistence routines required to keep the CSI_ITEM_INSTANCES repository consistent with downstream transactional data.
The package header declares several PL/SQL record and table types — ITEM_ATTRIBUTE_REC/TBL, GENERIC_ID_REC/TBL, LOOKUP_REC/TBL, LOCATION_REC/TBL, and INS_COUNT_REC — which are used to pass and validate collections of attributes, generic identifiers, lookup codes, and locations when manipulating item instances. The naming convention and package classification (PVT) indicate that the package is intended for internal use by other Install Base packages rather than direct customer invocation.
Key Procedures and Functions
The documented API exposes 55 procedures and functions. Representative members include:
- IS_PARENT / GET_PARENT_SORT_ORDER — Determine parent-child relationships among item instances and the ordering used when presenting hierarchical component structures.
- HAS_TRACKABLE_COMPONENT — Evaluates whether an instance contains components subject to serial, lot, or revision tracking.
- CHECK_ITEM_INSTANCE_LOCK / GET_INSTANCE_LOCK_STATUS / LOCK_ITEM_INSTANCES / UNLOCK_ITEM_INSTANCES — Implement concurrency control, preventing simultaneous updates to the same instance.
- CREATE_ITEM_INSTANCE / UPDATE_ITEM_INSTANCE — Persist new or modified item instance records following validation.
- EXPIRE_ITEM_INSTANCE / EXPIRE_CHILD_INSTANCES — Terminate an instance and cascade that termination to dependent child instances, supporting de-installation and retirement scenarios.
- GET_INST_COLUMN_VALUES / GET_INSTANCE_COL_VALUES / RESOLVE_ID_COLUMNS / DEFINE_INST_COLUMNS / BIND_INST_VARIABLE / GEN_INST_WHERE_CLAUSE — Dynamically resolve and bind attribute columns, constructing the WHERE clauses and query fragments used by the reporting and synchronization routines in the package.
- INITIALIZE_INST_REC / CONSTRUCT_INST_FROM_HIST / CONSTRUCT_INST_HEADER_REC — Populate the internal record buffers that carry instance data through validation and persistence.
Tables Accessed
Through APPS synonyms the package references a broad set of base and Install Base tables. BOM_DEPARTMENTS, BOM_EXPLOSION_TEMP_S, and BOM_SMALL_EXPL_TEMP support bill-of-material explosion, which is the mechanism that drives explode_bom processing and populates child instances from a parent assembly. CSD_REPAIRS links instances to depot repair activity. CSI_COUNTER_ASSOCIATIONS and CSI_CTR_ITEM_ASSOCIATIONS maintain counter relationships for metered equipment. CSI_IEA_VALUES and CSI_IEA_VALUES_H store instance attribute values and their history. CSI_II_RELATIONSHIPS and CSI_II_RELATIONSHIPS_H hold the parent-child relationships between instances. CSI_II_FORWARD_SYNC_TEMP_S is a staging area for forward synchronization to downstream applications. CSI_INSTALL_PARAMETERS, CSI_INSTANCE_STATUSES, and CSI_IP_ACCOUNTS (with history in CSI_IP_ACCOUNTS_H) govern installation configuration, valid instance lifecycle statuses, and instance party account assignments.
Usage Notes
CSI_ITEM_INSTANCE_PVT is a private package and should not be called directly from custom code. It is invoked by the Install Base public APIs and by 24 other packages that depend on it. In practice it is exercised from the Install Base workbench forms, from Oracle Inventory and Order Management flows that create tracked items, from depot repair processing, and from concurrent programs performing forward synchronization and BOM explosion. The presence of BOM_EXPLOSION_TEMP_S and BOM_SMALL_EXPL_TEMP confirms that explode_bom activity is a core trigger for creation of child item instances during installation of configured assemblies. Customizations should always be routed through the supported public Install Base APIs, leaving this package to be reached indirectly.