Search Results termination_status

Overview

CSI_ITEM_INSTANCE_VLD_PVT is a private PL/SQL package owned by the APPS schema in Oracle E-Business Suite, classified as a PVT (private) API within the Complex Maintenance, Repair, and Overhaul (CSI) product family. Its primary business function is to centralize the validation logic applied to item instances — the deployed, serialized, or lot-controlled units tracked in Oracle Installed Base. Rather than permitting every calling module to implement its own checks, this package encapsulates reusable validation routines covering identifiers, revisions, serial and lot numbers, units of measure, quantities, organization-dependent parameters, conditions, and instance status. Because it is a private package, it is not intended to be called directly by external integrations or customer extensions; it exists as an internal validation service consumed by the public CSI APIs and the various grouping and transaction-handling packages that manage the installed base lifecycle.

Key Procedures and Functions

The package exposes 63 documented procedures and functions, consistent with its role as a shared validation utility.

• Parameter checks: CHECK_REQD_PARAM_NUM, CHECK_REQD_PARAM_CHAR, and CHECK_REQD_PARAM_DATE verify that mandatory numeric, character, and date arguments are supplied, providing uniform error reporting across the CSI API stack.
• Instance existence and status: INSTANCEEXISTS and IS_INSTANCENUM_VALID confirm that a referenced instance or instance number resolves to a valid record; TERMINATION_STATUS evaluates whether an instance has been terminated and should therefore be excluded from further activity.
• Tracking and serialization: IS_TRACKABLE determines whether an item is subject to instance tracking; IS_TREATED_SERIALIZED, CREATE_SERIAL, VALIDATE_SERIAL_NUMBER, and VALIDATE_SER_UNIQUENESS govern whether items are serialized, generate serial numbers, and enforce serial-number uniqueness.
• Lot control: CREATE_LOT and VALIDATE_LOT_NUMBER perform the equivalent role for lot-controlled items.
• Revision handling: VALIDATE_REVISION and UPDATE_REVISION confirm that a supplied revision is valid for the item and apply revision changes.
• Attributes and configuration: IS_QUANTITY_VALID, IS_VALID_UOM, IS_VALID_CONDITION, IS_UNIQUE_CONFIG_KEY, and VALIDATE_ORG_DEPENDENT_PARAMS validate quantity, unit of measure, condition, configuration-key uniqueness, and organization-specific parameters respectively.

Tables Accessed

The package reads and writes the core Installed Base tables through APPS synonyms. CSI_ITEM_INSTANCES, along with its _H, _H_S, and _S history and security variants, hold the instance records being validated. CSI_INSTANCE_STATUSES and CSI_TXN_ERRORS support status evaluation and error logging. CSI_I_ASSETS, CSI_I_PARTIES, CSI_I_EXTENDED_ATTRIBS, and CSI_I_VERSION_LABELS supply asset, party-relationship, descriptive-flexfield, and version-label data used during validation. CSI_TRANSACTIONS and CSI_T_TRANSACTION_LINES provide transaction context, while CSI_II_RELATIONSHIPS, CSI_INSTANCE_INTERFACE, and CSI_II_FORWARD_SYNC_TEMP participate in interface and relationship processing.

Usage Notes

CSI_ITEM_INSTANCE_VLD_PVT is referenced by 15 packages, including CSI_ITEM_INSTANCE_PUB, CSI_ITEM_INSTANCE_PVT, CSI_INTERFACE_PKG, CSI_INV_TXN_HOOK_PKG, CSI_ORDER_FULFILL_PUB, CSI_ORDER_SHIP_PUB, CSI_ONT_TXN_PUB, CSI_FA_INSTANCE_GRP, and CSI_DIAGNOSTICS_PKG. It is invoked indirectly during Installed Base instance creation and update, inventory transaction hooks, order fulfillment and shipping, and interface imports. It depends on FND_API and CSI_DATASTRUCTURES_PUB for the standard API error and data-structure conventions. Because the package is private, custom code should call the corresponding public APIs, such as CSI_ITEM_INSTANCE_PUB, rather than this package directly; the naming convention and documentation confirm the same pattern applies across both 12.1.1 and 12.2.2.