Search Results ar_cmgt_dnb_mappings




Overview
Explore in AI Chat

Overview

The AR_CMGT_DNB_MAPPINGS table is an Oracle Receivables (AR) reference table that supports Oracle Credit Management integration with Dun & Bradstreet Global Data Product reports. Its purpose is to identify each individual data point delivered within the D&B Global Data Product report set and to define how that data point maps to the corresponding scoring, decision, or attribute element used by Oracle Credit Management. In practice, the table functions as the translation layer between externally sourced D&B credit data and the internal credit management model, ensuring that incoming D&B values are interpreted consistently when credit reviews, scoring models, and limit recommendations are generated.

The documented physical schema places the table in the AR schema with eight columns and the primary key AR_CMGT_DNB_MAPPINGS_PK, defined on the column pair (DATA_ELEMENT_ID, DATA_POINT_ID). The heuristic Data Vault classification mined from the foreign-key structure is standalone, meaning the table is not modeled as a dependent hub, link, or satellite within the ETRM perspective. From a modeling standpoint, it is most naturally treated as a reference or lookup structure rather than a transactional entity.

Key Information Stored

The most significant columns in AR_CMGT_DNB_MAPPINGS are:

  • DATA_ELEMENT_ID — Part of the composite primary key. Identifies the Oracle Credit Management data element to which a D&B data point is mapped. This is the internal target identifier used by credit management processing.
  • DATA_POINT_ID — Part of the composite primary key. Identifies the D&B data point from the Global Data Product report set that supplies the value for the mapped data element.
  • ZD_EDITION_NAME — Identifies the edition of the mapping. This column participates in the unique index AR_CMGT_DNB_MAPPINGS_U1 (DATA_ELEMENT_ID, DATA_POINT_ID, ZD_EDITION_NAME), which represents the business-key candidate for the table and distinguishes mapping versions across editions.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS WHO columns recording the creation and last modification audit trail for each mapping row.

The surrogate primary key is the composite (DATA_ELEMENT_ID, DATA_POINT_ID). The unique index U1 extends this pair with ZD_EDITION_NAME and is the appropriate business-key candidate for lookups requiring edition awareness. The table carries no non-key descriptive attribute beyond the edition column and the auditing columns.

Common Use Cases and Queries

Typical scenarios involve validating that a required credit management data element has a corresponding D&B data point defined for the active edition, and reporting on coverage gaps before a D&B data load is executed.

  • Resolving a data element to its D&B source point: 
    SELECT data_element_id, data_point_id, zd_edition_name
FROM   ar.ar_cmgt_dnb_mappings
WHERE  data_element_id = :p_element_id
AND    zd_edition_name = :p_edition;
  • Confirming completeness of mappings for an edition: 
    SELECT zd_edition_name, COUNT(*) mapped_points
FROM   ar.ar_cmgt_dnb_mappings
GROUP  BY zd_edition_name;
  • Auditing recently maintained mappings using the WHO columns: 
    SELECT data_element_id, data_point_id, last_updated_by, last_update_date
FROM   ar.ar_cmgt_dnb_mappings
WHERE  last_update_date >= :p_since;

Because the table is reference data rather than transactional data, query volumes are low and results are frequently cached by integration logic.

Related Objects

The ETRM metadata classifies this table as standalone, with no documented foreign keys. Its principal relationships are therefore logical rather than enforced:

  • AR_CMGT_DATA_ELEMENTS — the credit management data element definition, logically joined on DATA_ELEMENT_ID.
  • AR_CMGT_DNB_* — companion D&B integration objects in the AR schema that consume the same data point identifiers.
  • AR_CMGT_SCORING_* and AR_CMGT_DECISION_* objects that evaluate the mapped data elements during credit review.
  • AR_CMGT_BATCHES / AR_CMGT_PARTY_* — credit management case and party objects that ultimately reference the values populated through these mappings.

Administrators should treat AR_CMGT_DNB_MAPPINGS as configuration data, maintaining it through supported Credit Management setup and D&B integration flows rather than by direct DML.