Search Results iby_risk_factors




Overview

The IBY_RISK_FACTORS table is a core repository within the Oracle E-Business Suite Payments (IBY) module, specifically for the Risk Management feature. It serves as the master definition table for configurable risk criteria used by merchants to assess the financial risk associated with customers during payment transactions. Each record represents a discrete risk factor—such as a customer's credit score, transaction amount, or geographic location—that can be quantitatively evaluated. The table's role is to provide a centralized, reusable catalog of these factors, enabling the system to calculate an aggregate risk score for a payer, which can then influence payment processing decisions like requiring additional authentication or declining a transaction.

Key Information Stored

The table's structure is designed to uniquely identify and describe each risk factor. The primary identifier is the RISK_FACTOR_ID, a system-generated unique key. For application logic and configuration, the RISK_FACTOR_CODE provides a unique, meaningful identifier for each factor. While the full column list is not detailed in the provided metadata, typical columns in such a master table would include a descriptive name (RISK_FACTOR_NAME), a data type indicator for the factor's value (e.g., NUMBER, VARCHAR2), and columns controlling status and active dates. The unique constraint on RISK_FACTOR_CODE (IBY_RISK_FACTORS_UK1) ensures no duplicate factor codes are entered.

Common Use Cases and Queries

This table is primarily referenced during the setup and execution of payment risk management. Administrators query it to review available factors when building risk formulas. A common reporting need is to list all active risk factors for configuration purposes. During transaction processing, the application joins this table to formula items to retrieve the details of each factor being evaluated. A typical diagnostic query would be:

SELECT risk_factor_code, risk_factor_name
FROM iby_risk_factors
WHERE SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE)
ORDER BY risk_factor_code;

This ensures only currently valid factors are considered for new risk model configurations or transaction evaluations.

Related Objects

The IBY_RISK_FACTORS table has a direct parent-child relationship with the IBY_RISK_FORMULA_ITEM table, as documented by the provided foreign key. This relationship is fundamental to the Risk Management feature's architecture.

  • IBY_RISK_FORMULA_ITEM: This table stores the specific risk factors assigned to a particular risk calculation formula. The foreign key column IBY_RISK_FORMULA_ITEM.RISK_FACTOR_ID references IBY_RISK_FACTORS.RISK_FACTOR_ID. A single risk factor defined in IBY_RISK_FACTORS can be used in multiple formulas, with each instance potentially having a different weight or scoring rule stored in IBY_RISK_FORMULA_ITEM.

This relationship illustrates how master risk factor definitions are linked to their operational use within payment risk scoring models.