Results for “source_column_name”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AR_CMGT_DNB_ELEMENTS_VL is a seeded, read-only database view in the Oracle E-Business Suite Receivables (AR) module, owned by the APPS schema and marked VALID. It belongs to the Credit Management (CMGT) feature set associated with Dun & Bradstreet (DNB) credit scoring integration. As its name indicates, the view conforms to the Oracle multi-language "VL" (view of translated and base) pattern: it joins a single-language base table, AR_CMGT_DNB_ELEMENTS_B, to its translation table, AR_CMGT_DNB_ELEMENTS_TL, to present a language-specific, denormalized result set.

The view defines the set of individual "data elements" that make up a D&B credit risk score model in Receivables. Each row represents one discrete input or output element of a scoring request — for example, a financial ratio, a vendor-provided attribute, or a derived return value. The view exposes the element name in the user's session language (resolved through USERENV('LANG')), the flag that indicates whether the element can be scored, and the technical metadata needed to source the element's value from the underlying application tables. In EBS reporting and integration, the view serves as the integration dictionary that Receivables and external credit-scoring procedures consult when assembling or interpreting a D&B score request.

Underlying Base Objects

The view is defined over two synonyms that resolve to the following base tables:

• AR_CMGT_DNB_ELEMENTS_B — the base table holding non-translatable attributes of each D&B data element, including its scorable flag, source table and column names, return data type, date format, application identifier, and standard WHO audit columns.
• AR_CMGT_DNB_ELEMENTS_TL — the translation table holding the translatable DATA_ELEMENT_NAME, keyed by DATA_ELEMENT_ID and LANGUAGE.

The join is performed on DATA_ELEMENT_ID, with the translation side restricted to the language returned by USERENV('LANG'). Because the view reads from base and translation tables only, it contains no data of its own and is not directly insertable or updatable. The ROW_ID column is populated from B.ROWID, providing a unique row identifier derived from the base table while retaining the translatable name from the TL table.

Key Columns

• ROW_ID — Rowid of the underlying base record; uniquely identifies the element at the physical level.
• DATA_ELEMENT_ID — Primary surrogate key linking the base and translation rows and identifying the D&B element.
• DATA_ELEMENT_NAME — The language-specific display name of the element, sourced from the TL table.
• SCORABLE_FLAG — Indicates whether the element participates in the credit score calculation.
• SOURCE_TABLE_NAME / SOURCE_COLUMN_NAME — The application table and column from which the element's value is derived.
• RETURN_DATA_TYPE / RETURN_DATE_FORMAT — The expected data type and, where applicable, the date format of the returned element value.
• APPLICATION_ID — The EBS application owning the source data, used for context and reference integrity.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns inherited from the base table.

Common Use Cases and Queries

Typical uses include reviewing the configured D&B scoring elements for a Receivables implementation, auditing which source columns feed a credit score, and joining the view to determine the user-facing name of each element. A representative query returns all scorable elements and their source mapping:

• SELECT data_element_id, data_element_name, scorable_flag, source_table_name, source_column_name, return_data_type FROM ar_cmgt_dnb_elements_vl WHERE scorable_flag = 'Y' ORDER BY data_element_name;
• SELECT data_element_name, application_id, return_data_type, return_date_format FROM ar_cmgt_dnb_elements_vl ORDER BY data_element_id;
• SELECT v.data_element_name, v.source_table_name, v.source_column_name FROM ar_cmgt_dnb_elements_vl v WHERE v.source_table_name = 'HZ_CUST_ACCOUNTS';

Because the view filters translations by the session language, results reflect the user's NLS configuration, making it suitable for localized reporting and integration lookups in both Release 12.1.1 and 12.2.2.