Search Results cs_systems_all_tl

Overview

CSI_CP_SYSTEMS_ALL_V is a backward-compatibility view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the CSI (Install Base) product family. Its documented purpose is to expose system-level data from the translation table CS_SYSTEMS_ALL_TL in a form compatible with earlier releases of the Install Base module. The view is classified as VALID in both Oracle EBS 12.1.1 and 12.2.2, and it is intended primarily for read access by reporting, integration, and legacy code paths that predate the current translation-aware data model.

In the Install Base data model, the term "system" refers to a configuration of related installed base items — assemblies, components, and their relationships. CSI_CP_SYSTEMS_ALL_V surfaces the textual attributes of these systems (name and description) along with the standard Oracle audit columns, allowing external consumers to retrieve translated system records without querying the underlying TL table directly. The "_ALL_" naming convention reflects the view's role in presenting records across languages, while "CP" in the object name denotes the Install Base component group to which it belongs.

Underlying Base Objects

The view is defined exclusively over the synonym CSI_SYSTEMS_TL, which resolves to CS_SYSTEMS_ALL_TL, the translation base table for systems. CS_SYSTEMS_ALL_TL follows the standard Oracle multi-language support (MLS) pattern: it stores the translatable attributes (NAME, DESCRIPTION) keyed by SYSTEM_ID and LANGUAGE, together with SOURCE_LANG to indicate the originating language of each record.

Because CSI_CP_SYSTEMS_ALL_V is a compatibility shim rather than a native base table view, it does not join to any additional objects. It is a thin projection of the columns available in CSI_SYSTEMS_TL. This design means the view inherits the row-level granularity of the translation table — one row per SYSTEM_ID per installed LANGUAGE — and reflects the same data security and translation semantics as its base object.

Key Columns

• SYSTEM_ID — Primary identifier of the system record; the foreign key linking to the system's non-translated attributes elsewhere in the Install Base schema.
• LANGUAGE — The language in which the NAME and DESCRIPTION values for that row are stored.
• SOURCE_LANG — The language of the original record from which a translation was derived; used by MLS consumers to identify the base language row.
• NAME — The translated name of the system.
• DESCRIPTION — The translated description of the system.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard Oracle audit columns. Note that these audit values are inherited from the TL table and, in an MLS context, reflect audit activity on the translation row rather than the parent entity.
• MIGRATED_STATUS_FLAG — This column is supplied by the view as a literal NULL (NULL MIGRATED_STATUS_FLAG) rather than being selected from the base table. It exists solely to preserve column-level compatibility with the historical interface of the view. Consumers should not rely on it for any business logic, as it will always return NULL.

Common Use Cases and Queries

The primary use case for CSI_CP_SYSTEMS_ALL_V is backward compatibility with legacy customizations, reports, and interfaces that were written against the pre-MLS version of the systems interface. For example, a custom BI Publisher report or a legacy interface program referencing this view will continue to function after upgrade, because the MIGRATED_STATUS_FLAG placeholder keeps the projected column list stable.

A typical query selects translated system names for a specific language:

SELECT system_id,
       name,
       description,
       language,
       source_lang
  FROM apps.csi_cp_systems_all_v
 WHERE language = USERENV('LANG')
   AND system_id = :p_system_id;

Because the view returns one row per language, callers requiring a single row per system must filter by LANGUAGE or aggregate appropriately. A common pattern joins the view to non-translated system tables on SYSTEM_ID to obtain both descriptive and structural attributes. When filtering or joining on MIGRATED_STATUS_FLAG, developers should recognize that any predicate on this column — such as WHERE migrated_status_flag = 'Y' — will return no rows, since the value is always NULL. Any legacy logic depending on this flag must be refactored to use the appropriate Install Base status columns instead. For new development, Oracle recommends querying CSI_SYSTEMS_TL or the current supported system views directly rather than relying on this compatibility object.