Results for “iby_risk_formula_item”

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

Overview

The IBY_RISK_FORMULA_ITEM table is a core configuration object within the Oracle Payments (IBY) module of Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as an intersection (association) table between IBY_RISK_FORMULAS and IBY_RISK_FACTORS, capturing the weighting assigned to each individual risk factor that participates in a given risk formula. Risk formulas are used by the Payments risk management engine to score payment transactions, instruments, and payees during funds capture and disbursement processing. Each row in this table represents the contribution of one risk factor to one formula, expressed through the WEIGHT column. Under the Data Vault classification heuristic applied to the foreign key structure, this object is best modeled as a link table, since it resolves a many-to-many relationship and carries no intrinsic descriptive attributes beyond the weighting measure. The table resides in the IBY schema and is flagged as VALID in the ETRM 12.2.2 metadata.

Key Information Stored

The physical schema documents ten columns, of which the following are the most significant for functional and reporting purposes:

• RISK_FORMULA_ID — Foreign key to IBY_RISK_FORMULAS; identifies the parent formula to which the item belongs.
• RISK_FACTOR_ID — Foreign key to IBY_RISK_FACTORS; identifies the specific factor being weighted within the formula.
• WEIGHT — The numeric weighting applied to the risk factor when the formula is evaluated. This is the principal payload attribute of the intersection row.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting multi-tenant security partitioning.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the OAF/BC4J framework for concurrent update control.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns tracking the identity and timestamp of record creation and modification.

The primary key is defined as IBY_RISK_FORMULA_ITEM_UK1, a composite unique index over (RISK_FACTOR_ID, RISK_FORMULA_ID), also documented as IBY_RISK_FORMULAID_FACORTID_U1. Notably, the composite key itself constitutes the business-key candidate rather than a separate surrogate identifier, meaning uniqueness is enforced on the formula-factor pairing. This reinforces the link-table interpretation: no independent surrogate PK column is documented.

Common Use Cases and Queries

Typical usage centers on inspecting, auditing, or troubleshooting risk formula configuration. For example, retrieving all weighted factors for a given formula:

• SELECT i.risk_formula_id, i.risk_factor_id, f.factor_name, i.weight
• FROM iby.iby_risk_formula_item i, iby.iby_risk_factors f
• WHERE i.risk_factor_id = f.risk_factor_id AND i.risk_formula_id = :formula_id;

Another frequent pattern is identifying formulas that share identical factor sets, or verifying that no factor is duplicated within a formula (a guarantee provided by the unique index). Reporting queries commonly join to IBY_RISK_FORMULAS to consolidate formula names with their constituent weights, supporting risk-tuning and compliance reviews. Because the table is entirely configuration-driven, administrators rarely modify it directly; changes flow through the Payments setup UI, which maintains the audit and version columns automatically.

Related Objects

• IBY_RISK_FORMULAS — Parent table joined on RISK_FORMULA_ID; holds formula headers.
• IBY_RISK_FACTORS — Parent table joined on RISK_FACTOR_ID; holds factor definitions.
• FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID for security partitioning.
• IBY_RISK_SCORES / IBY_RISK_ASSIGNMENTS (related IBY risk configuration objects) — Consume formulas at transaction evaluation time.
• IBY_PAYMENT_TRANSACTIONS / IBY_FUNDS_CAPTURE — Downstream consumers where computed risk scores are applied.