Search Results csi_item_instance_grp




Overview
Explore in AI Chat

Overview

CSI_ITEM_INSTANCE_GRP is a PL/SQL package in the APPS schema that belongs to Oracle's Enterprise Asset Management / Installed Base (CSI) product family. The suffix "GRP" reflects its classification as a group API — a package that bundles related procedures and functions into a cohesive interface for managing item instance records rather than exposing a single atomic operation. Its principal business purpose is to support the lifecycle management of item instances (installed base records) within Oracle E-Business Suite Release 12.1.1 and 12.2.2.

The package acts as the consolidated entry point for creating, updating, expiring, locking, and unlocking item instances, and for navigating the hierarchical relationships that connect an instance to its parents and to its bill of materials components. Because installed base data underpins service contracts, depot repair, field service, and asset tracking, this package forms part of the foundation on which downstream CSI processing depends. It is a validated dependency of numerous CSI public and private APIs, including CSI_ITEM_INSTANCE_PUB, CSI_ITEM_INSTANCE_PVT, CSI_MASS_EDIT_PUB, CSI_ML_CREATE_PUB, CSI_ORDER_FULFILL_PUB, CSI_ORDER_SHIP_PUB, CSI_RMA_FULFILL_PUB, and CSI_SYSTEMS_PVT.

Key Procedures and Functions

The documented API surface comprises eight procedures and functions:

  • LOCK_ITEM_INSTANCES — Places a lock on one or more item instance records, preventing conflicting concurrent modifications during processing.
  • UNLOCK_ITEM_INSTANCES — Releases previously acquired locks on item instance records.
  • CHECK_ITEM_INSTANCE_LOCK — Verifies whether a given item instance is currently locked, allowing callers to avoid contention.
  • CREATE_ITEM_INSTANCE — Inserts a new item instance record and its associated history and transaction rows, serving as the primary creation entry point.
  • UPDATE_ITEM_INSTANCE — Modifies attributes of an existing item instance while preserving the corresponding historical versions.
  • EXPIRE_ITEM_INSTANCE — Marks an item instance as expired, ending its active lifecycle.
  • GET_ALL_PARENTS — Traverses the instance relationship hierarchy to return all parent instances of a given instance, supporting genealogy and structural queries.
  • EXPLODE_BOM — Explodes the bill of materials associated with an instance to enumerate its component instances.

Tables Accessed

The package reads and writes a defined set of CSI tables through APPS synonyms. Item instance data is maintained across CSI_ITEM_INSTANCES, CSI_ITEM_INSTANCES_H, and CSI_ITEM_INSTANCES_H_S, with CSI_CTR_ITEM_ASSOCIATIONS linking instances to counter data. Attribute values are stored in CSI_IEA_VALUES, CSI_IEA_VALUES_H, and CSI_IEA_VALUES_H_S. Instance-to-instance hierarchy is held in CSI_II_RELATIONSHIPS, and lifecycle statuses derive from CSI_INSTANCE_STATUSES. Accounting data is captured in CSI_IP_ACCOUNTS, CSI_IP_ACCOUNTS_H, and CSI_IP_ACCOUNTS_H_S. Upload staging occurs via CSI_CTR_UPLOAD_INSTANCES and CSI_CTR_UPLOAD_INSTANCES_S. The "_H" and "_H_S" variants retain historical and secondary versions of the base records.

Usage Notes

CSI_ITEM_INSTANCE_GRP is normally invoked indirectly. Public and private CSI APIs, order fulfillment and shipping routines, mass edit, RMA fulfillment, and multi-lingual interface packages call it on behalf of concurrent programs, Oracle Forms, and integration interfaces. Direct invocation from custom code is possible but should respect the locking sequence — LOCK_ITEM_INSTANCES before modification and UNLOCK_ITEM_INSTANCES afterward — to prevent concurrency issues.