Search Results ar_cmgt_dnb_mappings_u1




Overview
Explore in AI Chat

Overview

The AR.AR_CMGT_DNB_MAPPINGS table is a reference and mapping table within the Oracle Receivables (AR) schema that supports Oracle Credit Management integration with Dun & Bradstreet (D&B) Global Data Product reports. Its purpose is to identify each data point contained within D&B Global Data Product reports and map those data points to the corresponding data elements consumed by Oracle Credit Management. When a checklist is defined in a case folder that requires Dun & Bradstreet data, this mapping table enables the application to retrieve the underlying information from its source tables and present it in the appropriate credit management context.

The object holds a status of VALID, resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, and is owned by the AR schema. From a Data Vault modeling perspective, the heuristic classification for this object is standalone. This suggests the table is best modeled as a reference or cross-reference structure rather than a pure hub, link, or satellite. Practitioners designing an analytical or integration layer around Credit Management data should treat AR_CMGT_DNB_MAPPINGS as a static mapping/conversion construct that bridges external D&B data-point identifiers to internal Oracle Credit Management data-element identifiers.

Key Information Stored

The table is compact, and its documented columns consist of the two-part mapping key and the standard Oracle "Who" audit columns. The most important columns are described below.

  • DATA_ELEMENT_ID (NUMBER 15, mandatory) — Identifier of the D&B data element. This is the left-hand component of the primary key and of the unique index.
  • DATA_POINT_ID (NUMBER 15, mandatory) — Identifier of the data point. This is the right-hand component of the primary key and unique index, and it pairs with DATA_ELEMENT_ID to define the mapping relationship.
  • ZD_EDITION_NAME — The edition name associated with the mapping row. This column participates in the documented unique index AR_CMGT_DNB_MAPPINGS_U1 alongside the two identifier columns, making it a business-key candidate that distinguishes mappings across D&B data editions.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Who columns capturing the user, timestamp, and login context of the most recent modification to the row.
  • CREATED_BY, CREATION_DATE — Standard Who columns recording the creating user and creation timestamp.

The surrogate/primary key is documented as AR_CMGT_DNB_MAPPINGS_PK (DATA_ELEMENT_ID, DATA_POINT_ID). The unique index AR_CMGT_DNB_MAPPINGS_U1 is defined on (DATA_ELEMENT_ID, DATA_POINT_ID, ZD_EDITION_NAME) and is a business-key candidate, since it enforces uniqueness across the edition dimension in addition to the primary identifier pair. The unique index resides in the APPS_TS_TX_IDX tablespace.

Common Use Cases and Queries

Typical use cases center on validating, auditing, and reporting the mapping between D&B data points and Oracle Credit Management data elements. Because the table is small and read-mostly, queries are straightforward lookups or joins against Credit Management configuration tables.

A basic verification query returns the complete mapping rows:

  • SELECT DATA_ELEMENT_ID, DATA_POINT_ID, ZD_EDITION_NAME, LAST_UPDATE_DATE FROM AR.AR_CMGT_DNB_MAPPINGS;
  • Filter a specific data element: SELECT DATA_POINT_ID FROM AR.AR_CMGT_DNB_MAPPINGS WHERE DATA_ELEMENT_ID = :element_id;
  • Audit recently changed mappings: SELECT * FROM AR.AR_CMGT_DNB_MAPPINGS WHERE LAST_UPDATE_DATE > SYSDATE - 30;
  • Resolve the edition-scoped business key: SELECT DATA_ELEMENT_ID, DATA_POINT_ID, ZD_EDITION_NAME FROM AR.AR_CMGT_DNB_MAPPINGS WHERE DATA_ELEMENT_ID = :e AND DATA_POINT_ID = :p;

These queries support credit analysts and technical teams in confirming that checklist data points resolve to the correct Oracle Credit Management elements, and in troubleshooting missing or duplicated mappings when D&B data is not populated in a case folder.

Related Objects

The documented dependency metadata states that AR_CMGT_DNB_MAPPINGS does not reference any database object; it is a standalone mapping table. However, the schema exposes the object to the APPS layer, and the Who columns establish implicit foreign-key relationships to standard EBS foundation tables. The most significant related objects include:

  • FND_USER — referenced via LAST_UPDATED_BY and CREATED_BY (FND_USER.USER_ID).
  • FND_LOGINS — referenced via LAST_UPDATE_LOGIN (FND_LOGINS.LOGIN_ID).
  • AR_CMGT_DNB_MAPPINGS (APPS synonym/view) — the APPS-layer access path exposing the AR table to Credit Management and reporting.
  • Dun & Bradstreet source tables consumed through the mapping — joined on the D&B DATA_ELEMENT_ID/DATA_POINT_ID identifiers.
  • Oracle Credit Management case-folder / checklist configuration tables that reference the mapped DATA_ELEMENT_ID values.

No indexing columns beyond the documented unique index are implied, reinforcing the table's role as a lightweight bridge between D&B report data and Oracle Credit Management.