Results for “mapping_code”

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

Overview

IBY_MAPPINGS is a reference and configuration table owned by the IBY schema within the Oracle Payments (IBY) module of Oracle E-Business Suite. As documented in the ETRM metadata for release 12.2.2, the table stores mappings of codes to associated values, most notably risk scores used by Oracle Payments' payment risk and fraud evaluation framework. Each row captures a single code-to-value pairing, together with descriptive and sequencing attributes, allowing the Payments engine to translate a classification or lookup code into a numeric or textual value consumed during payment processing and risk scoring.

From a data modeling perspective, the heuristic Data Vault classification of IBY_MAPPINGS is satellite-leaning. This classification is a modeling suggestion rather than a physical implementation fact: the table records descriptive attributes and code-to-value assignments attached to a business key (the mapping type and mapping code combination), which is characteristic of satellite behavior. The presence of a foreign key to IBY_PAYEE further suggests the mapping rows may function as contextual descriptors tied to a payee entity, reinforcing the satellite interpretation.

Key Information Stored

The documented physical schema contains 14 columns. The most significant of these are:

• MAPPING_TYPE — The category or domain of the code being mapped. This column participates in both the primary key, IBY_MAPPINGS_UK1, and the unique index IBY_MAPPINGS_TYPE_CODE_U1.
• MAPPING_CODE — The specific code within the mapping type that is assigned a value. Also a component of the primary key and the unique index.
• VALUE — The value associated with the code, such as a risk score or other mapped outcome.
• DESCRIPTION — A textual description of the mapping entry.
• SEQ — A sequence number controlling ordering or display precedence of the rows.
• PAYEEID — A foreign key reference to IBY_PAYEE, allowing mappings to be scoped to a particular payee.
• SECURITY_GROUP_ID — A reference to FND_SECURITY_GROUPS, used for multi-org / security-based data partitioning.
• ZD_EDITION_NAME — An editioning column used in support of Oracle EBS edition-based redefinition and online patching in 12.2.
• OBJECT_VERSION_NUMBER — Used for optimistic concurrency control in the Oracle Application Framework.
• Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN capture standard who-column auditing.

There is no single-column surrogate primary key; the business key is defined by the composite unique index IBY_MAPPINGS_TYPE_CODE_U1 over (MAPPING_TYPE, PAYEEID, MAPPING_CODE, ZD_EDITION_NAME), while the primary key constraint IBY_MAPPINGS_UK1 is documented over (MAPPING_TYPE, MAPPING_CODE).

Common Use Cases and Queries

IBY_MAPPINGS is typically queried when validating payment risk configuration, reviewing which codes have been assigned specific risk values, or auditing mapping definitions per payee. A common reporting pattern joins mappings to payees:

• Look up all mappings for a given type: SELECT mapping_code, value, description FROM iby_mappings WHERE mapping_type = :type ORDER BY seq;
• Scope mappings to a payee: SELECT m.mapping_type, m.mapping_code, m.value FROM iby_mappings m, iby_payee p WHERE m.payeeid = p.payeeid;
• Audit recent changes through the standard who-columns, filtering on LAST_UPDATE_DATE and LAST_UPDATED_BY.
• Validate uniqueness against MAPPING_TYPE, PAYEEID, and MAPPING_CODE before inserting configuration rows.

These queries support risk score verification, configuration migration checks, and data-quality reconciliation between environments.

Related Objects

• IBY_PAYEE — Referenced by IBY_MAPPINGS.PAYEEID; the parent entity for payee-scoped mappings.
• FND_SECURITY_GROUPS — Referenced by IBY_MAPPINGS.SECURITY_GROUP_ID for security partitioning.
• IBY_MAPPINGS_UK1 — The primary key constraint (MAPPING_TYPE, MAPPING_CODE).
• IBY_MAPPINGS_TYPE_CODE_U1 — The unique index (MAPPING_TYPE, PAYEEID, MAPPING_CODE, ZD_EDITION_NAME).
• Oracle Payments (IBY) risk and configuration functions — The application logic that reads mapped values during payment risk evaluation.