Search Results csi_systems_vl




Overview

CSI_SYSTEMS_VL is an APPS-owned, multilingual (VL) view within the Oracle E-Business Suite Install Base module (CSI). In Release 12.1.1 and 12.2.2, it presents the user-facing, language-translated representation of customer systems maintained in Oracle Install Base. A "system" in Install Base is a logical grouping of related instances (for example, a configured server with its dependent components, or a customer site treated as a single maintainable unit). The VL view joins the language-independent base table to the translation table so that the NAME and DESCRIPTION columns are returned in the session language of the querying user, resolved through USERENV('LANG'). Because it carries the translated attributes, CSI_SYSTEMS_VL is the appropriate access point for any reporting, integration, or custom code that must display system names and descriptions, while CSI_SYSTEMS_B remains the object used for DML and for language-independent attribute access. The view is reported as VALID in the ETRM registry.

Underlying Base Objects

The documented definition of CSI_SYSTEMS_VL is an equi-join between two base objects, both referenced through APPS synonyms:

  • CSI_SYSTEMS_B — the language-independent base table holding system identifiers, foreign keys, descriptive flexfield context and attributes, and audit columns.
  • CSI_SYSTEMS_TL — the translation table supplying NAME and DESCRIPTION per installed language.

The join predicate is CSB.SYSTEM_ID = CST.SYSTEM_ID combined with CST.LANGUAGE = USERENV('LANG'). Consequently, the view returns exactly one row per system for the language of the current session, and joins made against it in SQL inherit that language filter. Rows are only returned for systems that have a translation row in the session language, which in a normally configured EBS instance is guaranteed for each defined system.

Key Columns

Common Use Cases and Queries

Typical scenarios include reporting on customer systems by name, listing active systems for a given operating unit, and driving integrations that must publish translated system names. The following query lists active systems for a specific customer:

SELECT system_id, system_number, name, system_type_code
FROM csi_systems_vl
WHERE customer_id = :p_customer_id
AND (end_date_active IS NULL OR end_date_active > SYSDATE)
ORDER BY name;

Because the view is keyed on SYSTEM_ID, it is frequently joined to CSI_ITEM_INSTANCES or to the Install Base instance views to enumerate the instances belonging to each system, and to CSI_SYSTEMS_B when non-translated attributes or DML access is required. Reporting users should note that the view performs no operating unit (MOAC) filtering; the OPERATING_UNIT_ID column must be constrained explicitly when multi-org security is required. In release 12.2.2 the object remains unchanged in structure from 12.1.1, so existing custom queries remain portable across both releases.