Results for “update_row_for_mu”

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

Overview

APPS.CSI_SYSTEMS_B_PKG is a public PL/SQL package in the Oracle E-Business Suite (EBS) Applications schema (APPS), classified under the ETRM metadata as an "OTHER" API object. It belongs to the installation and systems foundation of Oracle Enterprise Asset Management and the CSI (Customer and Supplier Item / Install Base) module. Its core responsibility is to provide the low-level Data Manipulation Language (DML) layer for the CSI_SYSTEMS entity, which stores the definition of systems — hierarchical groupings of items or assets used in install-base, maintenance, and asset-tracking scenarios.

The package operates strictly as a table-handler (B / base-table API). The "_B_" naming convention indicates it encapsulates the base-table operations for the CSI_SYSTEMS family of tables, including row insertion, update, deletion, concurrency control, and multi-language translation support. It is not a business-process API; higher-level business logic is delegated to the companion package CSI_SYSTEMS_PVT, which in turn invokes this package for its physical database operations. This separation of concerns is consistent with the standard EBS "B / PVT / Public API" architecture.

Key Procedures and Functions

The documented interface exposes seven procedures, split between transactional operations and translation maintenance:

• INSERT_ROW — Creates a new record in the CSI_SYSTEMS base tables, initializing the mandatory columns for a system definition.
• UPDATE_ROW — Modifies an existing system record, applying changed attribute values to the base table.
• UPDATE_ROW_FOR_MU — A variant of the update routine designed to support Multi-Update (MU) processing, typically used in bulk or set-based update contexts where several rows are affected in one transaction.
• LOCK_ROW — Acquires a row-level lock on the target system record, enforcing optimistic/pessimistic concurrency control so concurrent sessions cannot silently overwrite one another's changes.
• DELETE_ROW — Removes a system record from the base tables.
• ADD_LANGUAGE — Inserts the translated (language-specific) rows for a system into the _TL translation table, invoked when a new language installation or translation seed is required.
• TRANSLATE_ROW — Updates an existing translated row in the _TL table for a given language and system.

Parameter lists are intentionally not enumerated here; the ETRM metadata documents only the procedure names and their purpose, and, as with all Oracle-seeded APIs, the exact signatures carry a large number of standard WHO columns (created_by, creation_date, last_update_* etc.).

Tables Accessed

The package reads and writes the following base tables (referenced through APPS synonyms):

• CSI_SYSTEMS_B — The base table holding the language-independent system record. INSERT_ROW, UPDATE_ROW, UPDATE_ROW_FOR_MU, LOCK_ROW and DELETE_ROW act on this table.
• CSI_SYSTEMS_S — The "security" child table, storing organization- or security-level access attributes linked to the system.
• CSI_SYSTEMS_TL — The translation table holding language-specific columns (name, description) for each system, managed by ADD_LANGUAGE and TRANSLATE_ROW.
• FND_LANGUAGES — The Oracle Foundation language repository, used by ADD_LANGUAGE / TRANSLATE_ROW to validate the target language code and drive translation row creation.

Usage Notes

CSI_SYSTEMS_B_PKG is not intended to be called directly by end users or custom applications in routine integration work. It is the physical DML engine underlying CSI_SYSTEMS_PVT, which is the documented business API for creating and maintaining systems. The ETRM dependency listing confirms a strict one-directional relationship: CSI_SYSTEMS_B_PKG is referenced by CSI_SYSTEMS_PVT (and, in practice, by itself in recursive/reference contexts), and it in turn depends only on the FND_API and STANDARD packages.

Because the package is marked VALID and status ACTIVE on both 12.1.1 and 12.2.2, it is safe to assume it is installed and maintained by the standard EBS patching process. Typical invocation paths are: (1) the Systems and Install Base setup windows in the CSI application, which call the PVT layer, which then calls this B package; and (2) concurrent or interface programs that bulk-load systems and require the multi-update variant UPDATE_ROW_FOR_MU. Custom code should call the PVT or public API layer rather than this package directly, since the B package performs no business validation, does not enforce entity-level validation rules, and, being an Oracle-internal handler, is subject to change between application releases.