Results for “csi_i_assets_pkg”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CSI_I_ASSETS_PKG is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Install Base (CSI) product family, which maintains the repository of customer assets and their configurations. The package name follows the standard Install Base interface naming convention, where the I_ prefix denotes an interface-layer object that performs low-level row manipulation against the Install Base asset tables. In practice, CSI_I_ASSETS_PKG provides the primitive insert, update, lock, and delete operations that the higher-level Install Base public APIs and internal processing logic call when they need to persist changes to the CSI_I_ASSETS entity and its related tables.

The ETRM metadata classifies this package as API classification OTHER, meaning it is not one of the documented public APIs intended for direct customer invocation. It is a supporting package used internally by the Install Base application. The package is reported as VALID, and it references the SYS.STANDARD package, which indicates standard PL/SQL type and exception declarations rather than any dependency on Oracle Application Object Library or other EBS schema-level packages. This limited dependency footprint is consistent with its role as a focused table-access layer.

Key Procedures and Functions

The ETRM documentation lists four procedures within CSI_I_ASSETS_PKG. The package contains no documented functions.

• INSERT_ROW — Creates a new row in the Install Base asset entity, populating the asset columns with the values supplied by the caller. It is the entry point used when a new asset record must be persisted.
• UPDATE_ROW — Modifies the mutable attributes of an existing asset row. It is invoked when attribute values on an existing Install Base asset change and the change must be written to the base table.
• LOCK_ROW — Acquires a row-level lock on the target asset record. This is typically called before an update or delete so that concurrent sessions cannot modify the same asset simultaneously.
• DELETE_ROW — Removes an asset row from the entity. Consistent with Install Base practice, deletion is generally the final step after dependent child records have been removed or invalidated.

The metadata does not document parameter lists for any of these procedures, and none should be assumed. In the Install Base architecture, the standard pattern is that each procedure accepts a primary key identifier for the target row along with a column-value record or set of scalar parameters representing the current attribute values.

Tables Accessed

CSI_I_ASSETS_PKG operates against two documented tables, accessed through APPS synonyms:

• CSI_I_ASSETS — The primary Install Base asset interface/base entity table. INSERT_ROW, UPDATE_ROW, LOCK_ROW, and DELETE_ROW all operate against this table as the principal storage location for asset records.
• CSI_I_ASSETS_S — The corresponding language or secondary row table, conventionally paired with the primary entity table in EBS to hold translated, descriptive, or related attribute records. The _S suffix in Install Base and related schemas denotes a companion table keyed to the primary entity.

Because the package manipulates both the primary table and its companion, any transactional use of these procedures must be executed within a single unit of work to keep the two tables synchronized.

Usage Notes

CSI_I_ASSETS_PKG is referenced by CSI_ASSET_PVT, a private package in the Install Base schema that encapsulates the business logic for asset maintenance. When CSI_ASSET_PVT needs to physically write, lock, or remove an asset row, it delegates to CSI_I_ASSETS_PKG rather than issuing DML against CSI_I_ASSETS directly. The package is also documented as referenced by itself, reflecting internal cross-references within its own specification and body.

Direct invocation of CSI_I_ASSETS_PKG from forms, concurrent programs, or custom extensions is not the supported pattern. Because the package is classified as OTHER rather than as a public API, there are no documented guarantees regarding its interface stability across patches or upgrades. Concurrent programs and forms in the Install Base application reach this code only indirectly, through CSI_ASSET_PVT and the public Install Base APIs built on top of it. Custom code that requires asset creation or maintenance should call the supported Install Base public APIs, which internally invoke CSI_I_ASSETS_PKG as part of a controlled, validated transaction, ensuring that row locking, concurrency handling, and companion-table consistency are applied correctly.