Search Results csi_counter_properties_tl




Overview
Explore in AI Chat

Overview

CSI_COUNTER_PROPERTIES_TL is a translation (TL) table within the CSI — Install Base product module of Oracle E-Business Suite, holding the translated counter instance property data. In EBS, counter properties describe measurable attributes attached to a counter instance (for example meters, gauges, or usage readings recorded against an asset in the Install Base). Because the descriptive text for these properties must be presented in multiple installed languages, Oracle stores the language-independent and language-dependent attributes separately. CSI_COUNTER_PROPERTIES_TL is the language-dependent companion that stores the translated NAME and DESCRIPTION values, keyed by language, while the base table (CSI_COUNTER_PROPERTIES_B) holds the language-independent columns.

The documented physical schema for release 12.2.2 shows 12 columns under the CSI schema, with a composite primary key CSI_COUNTER_PROPERTIES_TL_PK defined on (LANGUAGE, COUNTER_PROPERTY_ID). From a Data Vault modeling perspective, the metadata classifies this object heuristically as standalone. A satellite classification is the more natural analytical fit, since the table carries descriptive, language-specific attributes (NAME, DESCRIPTION) attached to the counter property business key; however, no parent hub or link relationship is confirmed in the documented FK structure, so the standalone designation is retained here as a modeling suggestion only. The one documented foreign key reference is SECURITY_GROUP_ID pointing to FND_SECURITY_GROUPS.

Key Information Stored

The table's most important columns fall into three functional groups — keys, translated content, and audit/security metadata:

  • COUNTER_PROPERTY_ID — surrogate identifier of the counter instance property. Together with LANGUAGE it forms the primary key CSI_COUNTER_PROPERTIES_TL_PK, and it is also the leading column of the unique index CSI_COUNTER_PROPERTIES_TL_U01 (COUNTER_PROPERTY_ID, LANGUAGE). This column is the join path back to the base counter property record.
  • LANGUAGE — the installed language code for the translated row. It is part of both the primary key and the U01 business-key candidate index.
  • SOURCE_LANG — the language from which the current translation was derived, used by the EBS Translation (TL) framework to track translation origin.
  • NAME — the translated display name of the counter property, presented to users in forms, lists of values, and reports.
  • DESCRIPTION — the translated descriptive text for the property.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard EBS WHO-column audit set that records insert and update accountability.
  • SECURITY_GROUP_ID — the foreign key to FND_SECURITY_GROUPS, supporting multi-tenant or secured data partitioning where applicable.
  • MIGRATED_FLAG — a flag indicating whether the row was introduced through a data migration rather than native application entry.

The surrogate primary key should be distinguished from the business-key candidate: the PK (LANGUAGE, COUNTER_PROPERTY_ID) is the physical uniqueness guarantee, while U01 (COUNTER_PROPERTY_ID, LANGUAGE) provides the same column pair in a reverse-ordered index optimized for lookups by property.

Common Use Cases and Queries

The table is primarily referenced when resolving translated labels for counter properties. A typical reporting query joins the translation table to its base counterpart and filters by the session or reporting language:

  • Retrieve translated property labels: SELECT counter_property_id, name, description FROM csi_counter_properties_tl WHERE language = USERENV('LANG') AND counter_property_id = :p_id;
  • List all translations of one property (translation completeness checks): SELECT language, name FROM csi_counter_properties_tl WHERE counter_property_id = :p_id ORDER BY language;
  • Detect untranslated rows: compare distinct LANGUAGE values against FND_LANGUAGES to find properties missing translations in an installed language.
  • Migration auditing: filter on MIGRATED_FLAG = 'Y' to isolate rows loaded by data conversion programs.
  • Security-scoped reporting: join SECURITY_GROUP_ID to FND_SECURITY_GROUPS when reporting must honor group-level data segregation.

Because both the primary key and U01 index lead with different columns, queries filtered by COUNTER_PROPERTY_ID alone benefit from U01, whereas range scans over LANGUAGE can leverage the leading column of the primary key. Reporting against textual labels should always be constrained by LANGUAGE to avoid returning multiple rows per property.

Related Objects

  • CSI_COUNTER_PROPERTIES_B — the language-independent base table holding the same COUNTER_PROPERTY_ID; joined to the TL row on COUNTER_PROPERTY_ID for full property metadata.
  • FND_SECURITY_GROUPS — referenced through the documented foreign key SECURITY_GROUP_ID; supplies the security group definition.
  • FND_LANGUAGES — the language registry that validates LANGUAGE and SOURCE_LANG values and supports translation-completeness reporting.
  • CSI_COUNTER_INSTANCES — counter instances whose properties are described; the property records resolved through this table relate to instance-level counter data.
  • CSI_ITEM_INSTANCES — the Install Base instance records to which counters and their properties ultimately attach.
  • FND_USER — resolves CREATED_BY and LAST_UPDATED_BY to user names for audit reporting.
  • CSI_COUNTER_PROPERTIES_TL_PK / CSI_COUNTER_PROPERTIES_TL_U01 — the primary-key constraint and unique index enforcing row uniqueness and supporting lookups by COUNTER_PROPERTY_ID.

Together these objects position CSI_COUNTER_PROPERTIES_TL as the language layer of the Install Base counter property model, joined on COUNTER_PROPERTY_ID and filtered by LANGUAGE in virtually every application and reporting access path.