Results for “interface_name”

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

Overview

IBY_RISK_FACTORS is an Oracle Payments (IBY) base table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the catalog of risk factors used by the Risk Management feature. A risk factor represents an individual attribute that a merchant deems relevant when assessing the risk of a customer purchasing goods or services — for example, attributes drawn from payment, order, or customer context. The table acts as the master definition list from which risk scoring formulas are constructed; each factor can be referenced by formula items that combine factors into a scoring or decision rule. The object is owned by the IBY schema and holds a VALID status in the documented environment.

Based on the foreign key topology mined from the data dictionary, the table is heuristically classified as hub-leaning in Data Vault terms. It carries a single-column surrogate primary key and a small number of descriptive attributes, and it is referenced by dependent tables rather than acting as a transactional event or a pure descriptive extension of another entity. This classification is a modeling suggestion only: an implementer building a dimensional or Data Vault layer could treat RISK_FACTOR_ID as a hub key, with the descriptive columns staged as a satellite.

Key Information Stored

The documented physical schema exposes twelve columns. The most significant are:

• RISK_FACTOR_ID — the surrogate primary key, enforced by IBY_RISK_FACTORS_PK. This is the value propagated to dependent tables.
• RISK_FACTOR_CODE — the business identifier for the factor. It is the leading column of the unique index IBY_RISK_FACTOR_NAME_U2 and is the natural key by which integrations and reporting typically reference a factor.
• FACTOR_TYPE — categorizes the factor, distinguishing the kind of risk attribute being defined.
• INTERFACE_NAME — identifies the interface or source binding associated with the factor, used when the factor is resolved at evaluation time.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-tenant or security-group partitioning of the definition rows.
• ZD_EDITION_NAME — the editioning column introduced by the EBS Online Patching (adop) infrastructure in 12.2.x; it participates in the unique indexes IBY_RISK_FACTORS_FACTORID_U1 and IBY_RISK_FACTOR_NAME_U2.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF/ADF framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS who-column audit set.

Note the distinction between the surrogate key (RISK_FACTOR_ID) and the business-key candidates represented by the two unique indexes: RISK_FACTOR_ID plus ZD_EDITION_NAME for internal identity, and RISK_FACTOR_CODE plus ZD_EDITION_NAME for business identity.

Common Use Cases and Queries

Typical uses include listing available risk factors for configuration review, tracing which formula items consume a given factor, and validating that a factor code is unique before deployment. A basic lookup:

SELECT risk_factor_id, risk_factor_code, factor_type, interface_name
FROM   iby.iby_risk_factors
WHERE  zd_edition_name = 'SET1'
ORDER  BY risk_factor_code;

To find factors used by scoring formulas, join to the dependent formula item table:

SELECT f.risk_factor_code, i.formula_id
FROM   iby.iby_risk_factors f,
       iby.iby_risk_formula_item i
WHERE  f.risk_factor_id = i.risk_factor_id;

Reporting scenarios frequently join to FND_SECURITY_GROUPS on SECURITY_GROUP_ID to attribute factor definitions to a security group, and filter on LAST_UPDATE_DATE to support audit and change-tracking extracts.

Related Objects

• IBY_RISK_FORMULA_ITEM — the principal dependent table; joined on IBY_RISK_FORMULA_ITEM.RISK_FACTOR_ID = IBY_RISK_FACTORS.RISK_FACTOR_ID. It maps factors into risk formulas.
• FND_SECURITY_GROUPS — referenced by IBY_RISK_FACTORS.SECURITY_GROUP_ID; governs row-level security partitioning.
• IBY_RISK_FORMULAS — the parent formula definition to which formula items and, transitively, risk factors belong.
• IBY_RISK_SCORES / IBY_RISK_SCORE_ITEMS — store evaluated results produced when factors are applied during a transaction.
• IBY_SECURITY_GROUPS_VL — the translatable view commonly used to resolve security group names in reporting joins.

Because formula items are the only documented inbound foreign key, all risk-factor consumption flows through IBY_RISK_FORMULA_ITEM; any query that reports on factor usage should therefore treat that table as the primary bridge to formula and scoring logic.