Search Results iby_irf_pmt_amount




Overview
Explore in AI Chat

Overview

The IBY_IRF_PMT_AMOUNT table is a core data object within the Oracle E-Business Suite Payments (IBY) module, specifically designed for the Payments Risk Management framework. Its primary role is to store configuration data that defines the risk factor associated with the monetary amount of a payment request. This table enables the system to flag potentially fraudulent transactions based on user-defined payment amount thresholds, which vary according to business and payee. The configuration stored here is critical for the automated risk scoring of payments during the creation and validation of payment instructions in releases 12.1.1 and 12.2.2.

Key Information Stored

The table's structure is centered on defining risk thresholds for specific payees. While the full column list is not detailed in the provided metadata, the primary and foreign key relationships indicate its core data elements. The table is uniquely identified by a composite primary key consisting of a sequence number (SEQ) and a payee identifier (PAYEEID). The PAYEEID column is a foreign key linking directly to the IBY_PAYEE table, ensuring that risk rules are associated with valid payees. The table presumably contains columns to define the risk score or tier and the corresponding payment amount thresholds that trigger it, allowing for granular control over risk assessment per payee.

Common Use Cases and Queries

The primary use case is the configuration and maintenance of amount-based risk rules within the Payments Risk Management setup. Administrators would populate this table to establish baseline rules, such as flagging any single payment over a specific value for a given supplier for manual review. A common reporting query would involve joining to the IBY_PAYEE table to list all configured amount risk factors by payee name. For troubleshooting, one might query this table to verify the rules applied to a specific payee when a payment request receives an unexpected risk score. A sample SQL pattern to retrieve configured rules would be:

  • SELECT p.party_name, a.* FROM iby_irf_pmt_amount a, iby_payee p WHERE a.payeeid = p.payeeid;

Related Objects

The IBY_IRF_PMT_AMOUNT table has a direct and documented dependency on the IBY_PAYEE table, which stores master information about payees. The relationship is enforced by a foreign key constraint where the PAYEEID column in IBY_IRF_PMT_AMOUNT references the PAYEEID in IBY_PAYEE. This ensures referential integrity, meaning a risk factor cannot be assigned to a non-existent payee. As a configuration table for the risk engine, it is logically referenced by the core payments processing engine and risk scoring algorithms, though these are typically implemented via internal APIs rather than direct foreign keys.

  • Table: IBY_IRF_PMT_AMOUNT 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_IRF_PMT_AMOUNT,  object_name:IBY_IRF_PMT_AMOUNT,  status:VALID,  product: IBY - Payments ,  description: This table stores information pertaining to the payment amount risk factor involved in the payment request. A payment request that has huge amount is possibly a fraudulent payment. But the value of the amount varies from business to busines ,  implementation_dba_data: IBY.IBY_IRF_PMT_AMOUNT , 

  • Table: IBY_IRF_PMT_AMOUNT 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_IRF_PMT_AMOUNT,  object_name:IBY_IRF_PMT_AMOUNT,  status:VALID,  product: IBY - Payments ,  description: This table stores information pertaining to the payment amount risk factor involved in the payment request. A payment request that has huge amount is possibly a fraudulent payment. But the value of the amount varies from business to busines ,  implementation_dba_data: IBY.IBY_IRF_PMT_AMOUNT , 

  • Table: IBY_PAYEE 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PAYEE,  object_name:IBY_PAYEE,  status:VALID,  product: IBY - Payments ,  description: IBY_PAYEE holds a row for each payee such as a biller or merchant/store at this site. ,  implementation_dba_data: IBY.IBY_PAYEE , 

  • Table: IBY_PAYEE 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PAYEE,  object_name:IBY_PAYEE,  status:VALID,  product: IBY - Payments ,  description: IBY_PAYEE stores a row for each payee, such as a biller, merchant, or store at this site. ,  implementation_dba_data: IBY.IBY_PAYEE ,