Search Results csi_systems_pub




Overview
Explore in AI Chat

Overview

CSI_SYSTEMS_PUB is a public PL/SQL API package in the APPS schema that provides the supported programmatic interface for creating, maintaining, and retiring system definitions within Oracle E-Business Suite's Installed Base (CSI) module. Systems in the CSI data model represent logical groupings of items, instances, and configurations that customers own or operate, and the CSI_SYSTEMS_PUB package acts as the single controlled gateway through which external callers manipulate the underlying system records instead of writing directly to the base tables.

The package is classified as a PUB API, indicating it is a published, supported interface intended for use by other Oracle applications, forms, and customer extensions. It encapsulates the business rules, validation logic, and multi-row language handling required to keep CSI system data consistent. The ETRM registry lists the object as VALID in both the 12.1.1 and 12.2.2 releases, and the documented metadata identifies four exposed procedures covering the full lifecycle of a system record.

Internally, CSI_SYSTEMS_PUB depends on CSI_DATASTRUCTURES_PUB and FND_API. The dependency on FND_API confirms that the package follows the standard Oracle Application Object Library API conventions, including the use of standardized return status and message handling. CSI_DATASTRUCTURES_PUB provides shared data structure utilities used to pass and validate system attribute information.

Key Procedures and Functions

The package exposes four documented procedures, each addressing a distinct phase of the system record lifecycle:

  • GET_SYSTEMS — Retrieves existing system records. This procedure supports querying system definitions by their identifying attributes and returning the associated descriptive and operational data to the caller.
  • CREATE_SYSTEM — Inserts a new system definition. This procedure applies the required validations and writes the corresponding rows into the base and translation tables.
  • UPDATE_SYSTEM — Modifies an existing system definition, allowing attributes of a previously created system to be changed while preserving referential integrity with dependent Installed Base records.
  • EXPIRE_SYSTEM — Retires or end-dates a system definition. This procedure implements the logical deletion pattern used throughout CSI, marking the record inactive rather than physically removing it, thereby preserving historical and audit relationships.

Tables Accessed

The documented metadata identifies two base tables accessed through APPS synonyms:

  • CSI_SYSTEMS_B — The primary base table storing the core, language-independent attributes of each system record. CREATE_SYSTEM, UPDATE_SYSTEM, and EXPIRE_SYSTEM write to this table, while GET_SYSTEMS reads from it.
  • CSI_SYSTEMS_TL — The translation table holding language-specific descriptive fields such as the system name and description. Records in this table are maintained in parallel with the base table so that system information can be presented in the user's session language.

Usage Notes

CSI_SYSTEMS_PUB is typically invoked from Oracle Installed Base forms, concurrent programs, and other Oracle application modules that need to establish or maintain system hierarchies. Within the CSI product family, the package is referenced by CSI_ORDER_SHIP_PUB and by its own internal and wrapper objects (CSI_SYSTEMS_PUB and CSI_SYSTEMS_PUB_W), confirming that order-shipping and internal CSI flows rely on this API to synchronize system data.

Custom code and extension developers should call CSI_SYSTEMS_PUB rather than issuing direct DML against CSI_SYSTEMS_B and CSI_SYSTEMS_TL. Doing so ensures that FND_API-based validation, message propagation, and translation maintenance are applied consistently, and it safeguards compatibility across EBS 12.1.1 and 12.2.2 releases.