Search Results ar_cmgt_data_points_tl_u1

Overview

AR.AR_CMGT_DATA_POINTS_TL is the multilingual support (MLS) translation table for the case folder data points that are available for display in Oracle Credit Management. Oracle Credit Management allows credit analysts to assemble case folders that present scoring, aging, exposure, and customer-attribute information. Each displayable field in a case folder is defined as a data point, and the translation table stores the language-specific name and description associated with each data point. Multilingual support enables an implementation to define a data point in one language, such as English, and translate it into additional languages, such as Spanish or Japanese, so that credit analysts can view and print the case folder in their own language. A translation row is created for every language into which a given data point has been localized, and the LANGUAGE column holds the NLS language code for that row.

From a Data Vault modeling perspective, the metadata heuristic classifies this object as satellite-leaning. The reason is that AR_CMGT_DATA_POINTS_TL carries descriptive, language-dependent attributes (the data point name and description) that change over time and are qualified by a parent identifier plus a language code, rather than acting as an independent business entity or as a many-to-many association between two hubs. It is best treated as a descriptive satellite attached to the base data point entity, keyed by the data point identifier and the language.

Key Information Stored

The table stores the translated presentation attributes for credit management data points. The columns of greatest analytical importance are:

• DATA_POINT_ID — Numeric (15) identifier of the data point; the foreign-key column that ties this translation row back to the base data point definition. It is part of the primary key.
• LANGUAGE — The NLS language code for the row; also part of the primary key and the discriminator that makes this an MLS table.
• DATA_POINT_NAME — The translated display name of the data point, maximum length 60. This is the business-key candidate referenced by the non-unique index AR_CMGT_DATA_POINTS_TL_N1 (DATA_POINT_NAME, LANGUAGE).
• DESCRIPTION — A translated description of the data point, maximum length 120.
• SOURCE_LANG — The language in which the row was originally authored, used by the MLS translation maintenance process.
• APPLICATION_ID — The FND application identifier that owns the data point; carries a foreign key to FND_APPLICATION.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Applications Framework to detect concurrent updates.
• ZD_EDITION_NAME — Editioning qualifier that permits multiple editions of the same row set to coexist in a single schema.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns that record the user and timestamp of creation and last modification.

The surrogate primary key is AR_CMGT_DATA_POINTS_TL_PK, composed of DATA_POINT_ID and LANGUAGE. The unique index AR_CMGT_DATA_POINTS_TL_U1 (DATA_POINT_ID, LANGUAGE, ZD_EDITION_NAME) is the enforcement index for the primary key in the editioned schema, and AR_CMGT_DATA_POINTS_TL_N1 provides a non-unique access path by name and language for translation lookups.

Common Use Cases and Queries

Typical uses include translation maintenance, listing all localized names for a data point, and joining the translations to the base data point definition for reporting or user-interface rendering. A common pattern retrieves the translated name and description for a single language:

• SELECT data_point_id, data_point_name, description FROM ar_cmgt_data_points_tl WHERE language = USERENV('LANG'); — returns the data point labels in the session language.
• SELECT data_point_id, language, data_point_name, source_lang FROM ar_cmgt_data_points_tl WHERE data_point_id = :p_id ORDER BY language; — lists every translation for one data point.
• SELECT t.language, t.data_point_name FROM ar_cmgt_data_points_tl t WHERE t.data_point_name LIKE 'Aging%'; — searches translated names, optionally using the AR_CMGT_DATA_POINTS_TL_N1 index.

Reporting use cases include building a translation inventory to identify data points missing a required language, auditing last-updated metadata for data point changes, and joining to the base table on DATA_POINT_ID and LANGUAGE to produce a complete bilingual case folder legend. Because the MLS columns are language-qualified, reports should always filter or join on LANGUAGE to avoid cross-language duplication.

Related Objects

The following objects are most significant in the dependency chain of this table:

• AR.AR_CMGT_DATA_POINTS — the base (non-translated) data point definition table, joined on DATA_POINT_ID. This is the parent object that this MLS table translates.
• FND_APPLICATION — the application registry, joined through AR_CMGT_DATA_POINTS_TL.APPLICATION_ID to identify the owning FND application.
• FND_LANGUAGES — the NLS language registry, joined on LANGUAGE to resolve language names and installed-language status.
• FND_USER — the user registry, joined through LAST_UPDATED_BY and CREATED_BY for audit reporting.
• FND_LOGINS — the login registry, joined through LAST_UPDATE_LOGIN for audit tracing.
• AR_CMGT_DATA_POINTS_TL_U1 (DATA_POINT_ID, LANGUAGE, ZD_EDITION_NAME) — the unique index enforcing the primary key.
• AR_CMGT_DATA_POINTS_TL_N1 (DATA_POINT_NAME, LANGUAGE) — the non-unique index supporting name-based translation lookups.

These relationships confirm that AR_CMGT_DATA_POINTS_TL is a dependent satellite of the data point definition entity and should be queried in conjunction with AR_CMGT_DATA_POINTS rather than as a standalone source of case folder metadata.