Search Results payable




The IBY.IBY_PMT_CREATION_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 governs the rules for payment creation and processing. This table stores configuration data that determines how payments are generated, formatted, and transmitted to banks or other financial institutions. Below is a detailed summary of its structure, purpose, and usage within Oracle EBS. ### **Purpose and Overview** The IBY_PMT_CREATION_RULES table defines the business rules that control payment creation for various payment methods, such as checks, electronic funds transfers (EFT), or wire transfers. These rules ensure compliance with organizational policies, banking requirements, and regulatory standards. The table acts as a repository for payment processing logic, enabling Oracle Payments to dynamically generate payments based on predefined criteria. ### **Key Columns and Their Significance** 1. **PMT_CREATION_RULE_ID** A unique identifier for each payment creation rule, ensuring traceability and reference in related transactions. 2. **PAYMENT_METHOD_CODE** Specifies the payment method (e.g., CHECK, EFT, WIRE) to which the rule applies. This links to the IBY_PAYMENT_METHODS table. 3. **DOCUMENT_SEQUENCE_ID** Associates the rule with a document sequence for audit and tracking purposes. 4. **PAYMENT_FORMAT_CODE** Defines the format (e.g., BACS, NACHA, SEPA) used for generating payment files, referencing the IBY_PAYMENT_FORMATS table. 5. **PAYMENT_PROCESS_PROFILE_ID** Links to the IBY_PAYMENT_PROCESS_PROFILES table, which contains processing instructions for payment batches. 6. **ACTIVE_FLAG** Indicates whether the rule is active (Y/N), allowing for temporary deactivation without deletion. 7. **CREATION_DATE and LAST_UPDATE_DATE** Audit columns tracking when the rule was created or modified. 8. **CREATED_BY and LAST_UPDATED_BY** User identifiers for accountability. 9. **ORG_ID** Specifies the operating unit (OU) to which the rule applies, supporting multi-org setups. 10. **PAYMENT_DOCUMENT_ID** References the IBY_PAYMENT_DOCUMENTS table, which stores templates for payment instruments like checks. ### **Functional Role in Payment Processing** - **Rule Evaluation:** During payment batch creation, Oracle Payments evaluates the criteria in IBY_PMT_CREATION_RULES to determine the appropriate payment method, format, and processing profile. - **Dynamic Payment Generation:** Rules ensure payments adhere to bank-specific requirements (e.g., file formats, transmission protocols). - **Multi-Org Support:** Rules can be configured per operating unit, enabling localized payment processing. - **Integration with Other Modules:** The table interacts with AP (Accounts Payable), AR (Accounts Receivable), and CE (Cash Management) to streamline end-to-end payment workflows. ### **Example Use Case** A company may define separate rules for domestic and international wire transfers: - **Domestic Wires:** Use NACHA format, process via ACH, and apply a specific processing profile. - **International Wires:** Use SEPA format, process via SWIFT, and enforce additional validations. ### **Conclusion** The IBY.IBY_PMT_CREATION_RULES table is foundational to Oracle Payments, enabling flexible, rule-based payment processing. Its configuration directly impacts payment accuracy, compliance, and efficiency. Administrators must carefully define and maintain these rules to align with organizational and banking requirements.