Search Results a




The IBY_PAYMENT_RULES table in Oracle E-Business Suite (EBS) 12.1.1 or 12.2.2 is a critical component of the Oracle Payments module, which facilitates the processing of electronic and manual payments. This table stores payment rules that define the conditions and criteria for determining how payments should be processed, including payment methods, payment formats, and bank account assignments. Below is a detailed summary of its structure, purpose, and key attributes in the context of Oracle EBS.

Purpose and Functionality

The IBY_PAYMENT_RULES table serves as a repository for payment rule definitions, which are used to automate and standardize payment processing across various Oracle applications, such as Accounts Payable (AP), Accounts Receivable (AR), and Payroll. Payment rules are essential for ensuring consistency in payment execution, reducing manual intervention, and improving efficiency in financial operations. These rules are evaluated during payment process requests to determine the appropriate payment method, bank account, and other payment attributes.

Key Attributes

The table includes several columns that define the payment rule's behavior and applicability. Some of the most important columns are:
  • PAYMENT_RULE_ID: A unique identifier for the payment rule.
  • PAYMENT_RULE_NAME: A descriptive name for the rule, often used for reference in user interfaces.
  • PAYMENT_METHOD_CODE: Specifies the payment method (e.g., ELECTRONIC, CHECK, WIRE) associated with the rule.
  • PAYMENT_FORMAT_CODE: Defines the format of the payment file (e.g., BACS, NACHA) for electronic payments.
  • BANK_ACCOUNT_ID: Links to the bank account from which payments will be issued.
  • APPLICATION_ID: Identifies the Oracle application (e.g., AP, AR) to which the rule applies.
  • ENABLED_FLAG: Indicates whether the rule is active (Y/N).
  • START_DATE and END_DATE: Define the validity period of the rule.
  • PRIORITY: Determines the order in which rules are evaluated when multiple rules match the same criteria.

Integration with Other Modules

The IBY_PAYMENT_RULES table integrates with other Oracle Payments tables, such as IBY_PAYMENT_PROFILES, IBY_BANK_ACCOUNTS, and IBY_PAYMENT_METHODS, to provide a comprehensive payment processing framework. For example:
  • Payment rules reference payment methods (IBY_PAYMENT_METHODS) to define how payments are executed.
  • Bank account details (IBY_BANK_ACCOUNTS) are linked to rules to specify the funding account.
  • Payment profiles (IBY_PAYMENT_PROFILES) may use rules to enforce organizational policies.

Usage in Payment Processing

During payment processing, the Oracle Payments engine evaluates payment rules based on predefined conditions, such as invoice attributes (e.g., supplier, currency, amount) or organizational hierarchies. The engine selects the highest-priority rule that matches the criteria and applies its settings to generate payments. For example:
  • An AP invoice may trigger a rule that routes payments to a specific bank account for electronic transfers.
  • A payroll payment may use a rule to generate checks for employees without bank details.

Customization and Extensions

Organizations can customize payment rules to align with their business requirements. This includes:
  • Creating rule sets with complex conditions using Oracle's rule engine.
  • Extending rules to support custom payment formats or third-party integrations.
  • Leveraging APIs to programmatically manage rules for bulk operations.

Conclusion

The IBY_PAYMENT_RULES table is a foundational element of Oracle Payments in EBS 12.1.1 and 12.2.2, enabling organizations to automate and streamline payment processing. By defining rules that align with business policies, companies can ensure accuracy, reduce manual effort, and enhance operational efficiency in financial transactions. Understanding its structure and functionality is essential for configuring and maintaining an effective payment processing system in Oracle EBS.

  • Lookup Type: IBY_N/A 12.1.1

    product: IBY - Payments ,  meaning: Not Applicable ,  description: Not Applicable , 

  • Lookup Type: IBY_N/A 12.2.2

    product: IBY - Payments ,  meaning: Not Applicable ,  description: Not Applicable , 

  • Table: IBY_PAYMENT_RULES 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PAYMENT_RULES,  object_name:IBY_PAYMENT_RULES,  status:VALID,  product: IBY - Payments ,  description: IBY_PAYMENT_RULES stores the header-level information for a payment method defaulting rule. A defaulting rule enables the user to define the default payment method with respect to multiple factors of a transaction context. A defaulting rule ,  implementation_dba_data: IBY.IBY_PAYMENT_RULES , 

  • Lookup Type: IBY_YES_NO 12.1.1

    product: IBY - Payments ,  meaning: IBY_YES_NO ,  description: Y/N Flag , 

  • Lookup Type: IBY_YES_NO 12.2.2

    product: IBY - Payments ,  meaning: IBY_YES_NO ,  description: Y/N Flag , 

  • Table: IBY_EXTRACT_ACTIVATIONS 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_EXTRACT_ACTIVATIONS,  object_name:IBY_EXTRACT_ACTIVATIONS,  status:VALID,  product: IBY - Payments ,  description: IBY_EXTRACT_ACTIVATIONS defines which computed fields within an extract are unnecessary for a particular format, with each row corresponding to a single field for that extract. When the extract engine is called for a particular format, ever ,  implementation_dba_data: IBY.IBY_EXTRACT_ACTIVATIONS , 

  • Table: IBY_PAYMENT_METHODS_TL 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PAYMENT_METHODS_TL,  object_name:IBY_PAYMENT_METHODS_TL,  status:VALID,  product: IBY - Payments ,  description: IBY_PAYMENT_METHODS stores the payment methods that Oracle Payments supports. A payment method is a payment attribute on a document payable that indicates how the first party payer is going to make the payment. Examples of payment methods i ,  implementation_dba_data: IBY.IBY_PAYMENT_METHODS_TL , 

  • Table: IBY_BEPKEYS 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_BEPKEYS,  object_name:IBY_BEPKEYS,  status:VALID,  product: IBY - Payments ,  description: IBY_BEPKEYS contains a list of all the keys that identifies a payee or payer with a Back End Payment System. ,  implementation_dba_data: IBY.IBY_BEPKEYS , 

  • Table: IBY_EXT_PARTY_PMT_MTHDS 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_EXT_PARTY_PMT_MTHDS,  object_name:IBY_EXT_PARTY_PMT_MTHDS,  status:VALID,  product: IBY - Payments ,  description: IBY_EXT_PARTY_PMT_MTHDS stores payment method applicability driven by the preferences of the external party. A payment method is applicable to a party and payment function combination and, optionally and additionally, to a party site and/or ,  implementation_dba_data: IBY.IBY_EXT_PARTY_PMT_MTHDS , 

  • Lookup Type: IBY_TRANSACTION_STATUS 12.1.1

    product: IBY - Payments ,  meaning: Transaction Statuses ,  description: Transaction Status defined in Oracle Payments , 

  • Table: IBY_PAYMENT_METHODS_B 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PAYMENT_METHODS_B,  object_name:IBY_PAYMENT_METHODS_B,  status:VALID,  product: IBY - Payments ,  description: IBY_PAYMENT_METHODS stores the payment methods that Oracle Payments supports. A payment method is a payment attribute on a document payable that indicates how the first party payer is going to make the payment. Examples of payment methods i ,  implementation_dba_data: IBY.IBY_PAYMENT_METHODS_B , 

  • Table: IBY_PAYMENTS_ALL 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PAYMENTS_ALL,  object_name:IBY_PAYMENTS_ALL,  status:VALID,  product: IBY - Payments ,  description: "This table contains records of the payments which are created by system while processing 'Build payments' program. A payment can be a single check or an electronic fund transfer between first party payer and third party payee. A row in ,  implementation_dba_data: IBY.IBY_PAYMENTS_ALL , 

  • Lookup Type: IBY_TRANSACTION_STATUS 12.2.2

    product: IBY - Payments ,  meaning: Transaction Statuses ,  description: Transaction Status defined in Oracle Payments , 

  • Table: IBY_BEPINFO 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_BEPINFO,  object_name:IBY_BEPINFO,  status:VALID,  product: IBY - Payments ,  description: IBY_BEPINFO has a row for every BEP(Back End Payment System) configured in system. A BEP is a payment provider such as Cybercash, Verifone etc ,  implementation_dba_data: IBY.IBY_BEPINFO , 

  • Table: IBY_PMTSCHEMES 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PMTSCHEMES,  object_name:IBY_PMTSCHEMES,  status:VALID,  product: IBY - Payments ,  description: IBY_PMTSCHEMES contains a list of Payment Schemes that will be supported by a BEP ,  implementation_dba_data: IBY.IBY_PMTSCHEMES , 

  • Table: IBY_PMTSCHEMES 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PMTSCHEMES,  object_name:IBY_PMTSCHEMES,  status:VALID,  product: IBY - Payments ,  description: IBY_PMTSCHEMES stores a list of payment schemes that are supported by a payment system. ,  implementation_dba_data: IBY.IBY_PMTSCHEMES , 

  • Table: IBY_MAPPINGS 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_MAPPINGS,  object_name:IBY_MAPPINGS,  status:VALID,  product: IBY - Payments ,  description: IBY_MAPPINGS stores mapping of codes with risk scores. Each row includes a code and a value for that code. ,  implementation_dba_data: IBY.IBY_MAPPINGS , 

  • Table: IBY_MAPPINGS 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_MAPPINGS,  object_name:IBY_MAPPINGS,  status:VALID,  product: IBY - Payments ,  description: IBY_MAPPINGS stores mapping of codes with risk scores. Each row includes a code and a value for that code. ,  implementation_dba_data: IBY.IBY_MAPPINGS , 

  • Table: IBY_ACCPPMTMTHD 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_ACCPPMTMTHD,  object_name:IBY_ACCPPMTMTHD,  status:VALID,  product: IBY - Payments ,  description: IBY_ACCPPMTMTHD contains a list of all the payment instrument methods that are accepted by a iPayment. ,  implementation_dba_data: IBY.IBY_ACCPPMTMTHD , 

  • Table: IBY_ACCPPMTMTHD 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_ACCPPMTMTHD,  object_name:IBY_ACCPPMTMTHD,  status:VALID,  product: IBY - Payments ,  description: IBY_ACCPPMTMTHD contains a list of all the payment instrument methods that are accepted by a iPayment. ,  implementation_dba_data: IBY.IBY_ACCPPMTMTHD , 

  • Table: IBY_IRF_TRXN_AMT_LIMIT 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_IRF_TRXN_AMT_LIMIT,  object_name:IBY_IRF_TRXN_AMT_LIMIT,  status:VALID,  product: IBY - Payments ,  description: IBY_IRF_TRXN_AMT_LIMITstores information pertaining to the transaction amount limit risk factor. It is a limit on the total amount of payments made using the same instrument in a particular duration. ,  implementation_dba_data: IBY.IBY_IRF_TRXN_AMT_LIMIT , 

  • Concurrent Program: IBY_FC_ACP_LTR_FORMAT 12.1.1

    execution_filename: FCAccompanyLetter ,  product: IBY - Payments ,  user_name: Settlement Batch Accompanying Letter ,  description: Creates accompanying letter to summarize contents of a settlement batch ,  argument_method: Standard ,  enabled: Yes ,  execution_method: Java Concurrent Program , 

  • Concurrent Program: IBY_FD_REG_RPT_FORMAT 12.1.1

    execution_filename: FDRegulatoryReporting ,  product: IBY - Payments ,  user_name: Create Regulatory Reporting of Payments ,  description: Creates and formats regulatory reporting for a central bank ,  argument_method: Standard ,  enabled: Yes ,  execution_method: Java Concurrent Program , 

  • Concurrent Program: IBY_FD_ACP_LTR_FORMAT 12.2.2

    execution_filename: FDAccompanyLetter ,  product: IBY - Payments ,  user_name: Payment File Accompanying Letter ,  description: Creates accompanying letter to summarize contents of a payment file ,  argument_method: Standard ,  enabled: Yes ,  execution_method: Java Concurrent Program , 

  • Concurrent Program: IBY_FC_ACP_LTR_FORMAT 12.2.2

    execution_filename: FCAccompanyLetter ,  product: IBY - Payments ,  user_name: Settlement Batch Accompanying Letter ,  description: Creates accompanying letter to summarize contents of a settlement batch ,  argument_method: Standard ,  enabled: Yes ,  execution_method: Java Concurrent Program , 

  • Concurrent Program: IBY_FD_REG_RPT_FORMAT 12.2.2

    execution_filename: FDRegulatoryReporting ,  product: IBY - Payments ,  user_name: Create Regulatory Reporting of Payments ,  description: Creates and formats regulatory reporting for a central bank ,  argument_method: Standard ,  enabled: Yes ,  execution_method: Java Concurrent Program , 

  • Concurrent Program: IBY_FD_ACP_LTR_FORMAT 12.1.1

    execution_filename: FDAccompanyLetter ,  product: IBY - Payments ,  user_name: Payment File Accompanying Letter ,  description: Creates accompanying letter to summarize contents of a payment file ,  argument_method: Standard ,  enabled: Yes ,  execution_method: Java Concurrent Program , 

  • Table: IBY_SYS_PMT_PROFILES_TL 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_SYS_PMT_PROFILES_TL,  object_name:IBY_SYS_PMT_PROFILES_TL,  status:VALID,  product: IBY - Payments ,  description: IBY_SYS_PMT_PROFILES stores seeded information that specifies the bulk of payment processing behavior. The rest of the behavior is specified in a user-defined account payment process profile stored in IBY_ACCT_PMT_PROFILES. A combination of ,  implementation_dba_data: IBY.IBY_SYS_PMT_PROFILES_TL , 

  • Concurrent Program: IBYREPICP 12.2.2

    execution_filename: RebuildPI ,  product: IBY - Payments ,  user_name: Re-build Payment Instruction ,  description: Re-creates a payment instructions that was not originally created successfully ,  argument_method: Standard ,  enabled: Yes ,  execution_method: Java Concurrent Program , 

  • Table: IBY_DEFAULT_BEP 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_DEFAULT_BEP,  object_name:IBY_DEFAULT_BEP,  status:VALID,  product: IBY - Payments ,  description: IBY_DEFAULT_BEP stores information that will allow a payment system account and funds capture process profile to be derived for a transaction should the routing rules fail to yield them. ,  implementation_dba_data: IBY.IBY_DEFAULT_BEP , 

  • Table: IBY_IRF_TRXN_AMT_LIMIT 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_IRF_TRXN_AMT_LIMIT,  object_name:IBY_IRF_TRXN_AMT_LIMIT,  status:VALID,  product: IBY - Payments ,  description: IBY_IRF_TRXN_AMT_LIMITstores information pertaining to the transaction amount limit risk factor. It is a limit on the total amount of payments made using the same instrument in a particular duration. ,  implementation_dba_data: IBY.IBY_IRF_TRXN_AMT_LIMIT , 

  • 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 , 

  • Lookup Type: IBY_PROCESS_TYPES 12.2.2

    product: IBY - Payments ,  meaning: Process Types ,  description: Processes by which documents payable can be built into payments, and payments into payment instructions , 

  • Concurrent Program: IBYREPICP 12.1.1

    execution_filename: IBY_BUILD_INSTRUCTIONS_PUB_PKG.rebuild_pmt_instruction ,  product: IBY - Payments ,  user_name: Re-create Payment Instruction ,  description: Re-creates a payment instructions that was not originally created successfully ,  argument_method: Standard ,  enabled: Yes ,  execution_method: PL/SQL Stored Procedure , 

  • 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 , 

  • Lookup Type: IBY_PROCESS_TYPES 12.1.1

    product: IBY - Payments ,  meaning: Process Types ,  description: Processes by which documents payable can be built into payments, and payments into payment instructions , 

  • Table: IBY_VALIDATION_VALUES 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_VALIDATION_VALUES,  object_name:IBY_VALIDATION_VALUES,  status:VALID,  product: IBY - Payments ,  description: IBY_VALIDATION_VALUES stores the values for each validation parameter. For example, one validation controls the maximum amount that can be paid in a single payment instruction. The maximum amount parameter is stored in this table, and the a ,  implementation_dba_data: IBY.IBY_VALIDATION_VALUES , 

  • Lookup Type: IBY_PAYMENT_REJECTION_LEVELS 12.1.1

    product: IBY - Payments ,  meaning: Payment Rejection Levels ,  description: Defines how much of a payment process request can be rejected when a proposed payment fails validation , 

  • Lookup Type: IBY_REMIT_ADVICE_CONDITIONS 12.1.1

    product: IBY - Payments ,  meaning: Remittance Advice Conditions ,  description: Conditions in which remittance advice is generated , 

  • Lookup Type: IBY_REMIT_ADVICE_CONDITIONS 12.2.2

    product: IBY - Payments ,  meaning: Remittance Advice Conditions ,  description: Conditions in which remittance advice is generated , 

  • Lookup Type: IBY_PAYEE_LOCATION_CONDITIONS 12.2.2

    product: IBY - Payments ,  meaning: Payment Location Conditions ,  description: Location of a payee relative to the first party for the purpose of creating a payment method defaulting rule condition , 

  • Lookup Type: IBY_PAYEE_LOCATION_CONDITIONS 12.1.1

    product: IBY - Payments ,  meaning: Payment Location Conditions ,  description: Location of a payee relative to the first party for the purpose of creating a payment method defaulting rule condition , 

  • 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 , 

  • Lookup Type: IBY_PAYMENT_REJECTION_LEVELS 12.2.2

    product: IBY - Payments ,  meaning: Payment Rejection Levels ,  description: Defines how much of a payment process request can be rejected when a proposed payment fails validation , 

  • Lookup Type: IBY_DOCUMENT_REJECTION_LEVELS 12.2.2

    product: IBY - Payments ,  meaning: Documents Payable Rejection Levels ,  description: Defines how much of a payment process request can be rejected when a document payable fails validation , 

  • 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 , 

  • Lookup Type: IBY_DOCUMENT_REJECTION_LEVELS 12.1.1

    product: IBY - Payments ,  meaning: Documents Payable Rejection Levels ,  description: Defines how much of a payment process request can be rejected when a document payable fails validation , 

  • Lookup Type: IBY_TRXNTYPES 12.1.1

    product: IBY - Payments ,  meaning: IBY TRANSACTION TYPES ,  description: Common interface across multiple payment stystems , 

  • Lookup Type: IBY_TRXNTYPES 12.2.2

    product: IBY - Payments ,  meaning: IBY TRANSACTION TYPES ,  description: Common interface across multiple payment stystems , 

  • Lookup Type: IBY_PMT_MTHD_AVAILABILITY 12.1.1

    product: IBY - Payments ,  meaning: Payment Method Availability ,  description: Payment Method Availability ,