Search Results ar_cmgt_data_points_tl_pk

Overview

The AR_CMGT_DATA_POINTS_TL table resides in the AR (Receivables) schema and functions as the multilingual support (MLS) translation table for Credit Management case folder data points. In Oracle Credit Management, a "data point" represents an individual information element—such as a credit score, a DSO calculation, a payment history metric, or a customer attribute—that can be displayed within a case folder during the credit review workflow. The base definition of each data point is stored in the corresponding base table, while AR_CMGT_DATA_POINTS_TL holds the translated display name and description for each installed language, enabling the application to render data point labels in the session language of the user.

From a data modeling perspective, the metadata's heuristic Data Vault classification identifies this table as satellite-leaning. This classification is appropriate: the table carries descriptive, language-dependent attributes (name and description) attached to the business key formed by DATA_POINT_ID and LANGUAGE, rather than representing an independent business entity or an associative relationship between entities.

Key Information Stored

The documented physical schema contains thirteen columns. The most significant are:

• DATA_POINT_ID — The surrogate identifier for the parent data point definition; part of the composite primary key AR_CMGT_DATA_POINTS_TL_PK along with LANGUAGE.
• LANGUAGE — The NLS language code identifying which translation this row supplies. Together with DATA_POINT_ID it forms the primary key.
• DATA_POINT_NAME — The translated, user-facing label for the data point as displayed in case folders.
• DESCRIPTION — The translated explanatory text describing the purpose or meaning of the data point.
• SOURCE_LANG — The source language from which the translation was derived, used by the MLS maintenance utilities.
• APPLICATION_ID — Foreign key to FND_APPLICATION, identifying the owning application context for the data point.
• ZD_EDITION_NAME — Editioning column supporting online patching in EBS 12.2.x; it participates in the unique index AR_CMGT_DATA_POINTS_TL_U1 (DATA_POINT_ID, LANGUAGE, ZD_EDITION_NAME).
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Applications framework during concurrent updates.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns capturing creation and modification metadata.

The surrogate primary key is the pair (DATA_POINT_ID, LANGUAGE); the unique index AR_CMGT_DATA_POINTS_TL_U1 extends this with ZD_EDITION_NAME to accommodate editioning. DATA_POINT_NAME and DESCRIPTION serve as the business-facing descriptive attributes rather than key candidates.

Common Use Cases and Queries

Typical usage centers on reporting data point labels in a specific language. A join between the base table and this translation table is the standard pattern:

• Retrieving display-ready labels: SELECT b.data_point_id, t.data_point_name, t.description FROM ar_cmgt_data_points b, ar_cmgt_data_points_tl t WHERE b.data_point_id = t.data_point_id AND t.language = USERENV('LANG');
• Auditing translation coverage: query for base rows lacking a translation in a given language to identify gaps before go-live in a multilingual implementation.
• Custom reporting: extract all English (or other language) data point names to document which metrics the credit department currently surfaces in case folders.
• Post-patch verification: after an upgrade or edition change, confirm rows exist for the correct ZD_EDITION_NAME and that OBJECT_VERSION_NUMBER values are consistent.

Related Objects

• AR_CMGT_DATA_POINTS — The base (non-translated) table holding the data point definition; joined on DATA_POINT_ID.
• FND_APPLICATION — Referenced via AR_CMGT_DATA_POINTS_TL.APPLICATION_ID; identifies the owning application.
• FND_LANGUAGES — Provides the valid LANGUAGE codes used in the translation rows.
• AR_CMGT_CASE_FOLDERS and related case folder tables — Consume data point definitions when rendering credit case folders.
• Credit Management setup and configuration pages in the Receivables responsibility — Read this table to present translated data point names to administrators.