Search Results shipping instructions




The IBY_INSTR_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 facilitates the processing of payment instructions. This table stores rules that govern the creation of payment instructions, ensuring compliance with business requirements, banking standards, and regulatory mandates. Below is a detailed analysis of its structure, purpose, and integration within Oracle EBS.

Purpose and Functional Overview

The IBY_INSTR_CREATION_RULES table defines the criteria for generating payment instructions, such as electronic funds transfers (EFT), checks, or other payment methods. These rules determine how payments are grouped, formatted, and transmitted to banks or financial institutions. Key functionalities include:
  • Rule Definition: Specifies conditions for payment instruction creation, such as payment method, currency, or bank account.
  • Grouping Logic: Controls how payments are batched (e.g., by supplier, invoice date, or payment currency).
  • Validation: Ensures adherence to banking formats (e.g., BACS, SEPA) and organizational policies.

Table Structure and Key Columns

The table comprises columns that define rule attributes, including:
  • RULE_ID: Primary key, uniquely identifying each rule.
  • RULE_NAME: Descriptive name for the rule.
  • PAYMENT_METHOD_CODE: Links to IBY_PAYMENT_METHODS, specifying the payment type (e.g., CHECK, EFT).
  • BANK_ACCOUNT_ID: References CE_BANK_ACCOUNTS, associating the rule with a specific bank account.
  • CREATION_CRITERIA: XML or structured data defining conditions for instruction creation (e.g., minimum/maximum payment amounts).
  • STATUS: Indicates whether the rule is active or inactive.
  • START_DATE/END_DATE: Defines the rule's validity period.

Integration with Oracle EBS Modules

The table interacts with several EBS modules:
  1. Oracle Payables: Rules are applied during payment batch creation in AP, ensuring payments align with vendor terms and banking requirements.
  2. Oracle Receivables: Supports refund processing by validating instruction rules against customer bank details.
  3. Cash Management: Validates payment instructions against reconciled bank statements.

Configuration and Usage

Administrators configure rules via the Oracle Payments Manager responsibility:
  1. Navigate to Setup > Payments > Instruction Creation Rules.
  2. Define rules using criteria like payment method, currency, or bank account.
  3. Assign rules to payment process profiles (IBY_PAYMENT_PROFILES).
Example: A rule may group all USD EFT payments exceeding $10,000 for a specific bank account, ensuring compliance with anti-money laundering (AML) thresholds.

Technical Considerations

  • Performance: Complex rules with multiple criteria may impact payment batch processing speed.
  • Customization: Extensions via PL/SQL or Oracle Workflow are possible but require thorough testing.
  • Audit: Changes to rules are logged in IBY_INSTR_CREATION_RULES_AUDIT for compliance tracking.

Conclusion

The IBY_INSTR_CREATION_RULES table is pivotal in Oracle EBS Payments, enabling automated, compliant payment instruction generation. Its configuration demands a deep understanding of organizational payment workflows and banking standards. Properly defined rules enhance efficiency, reduce errors, and ensure seamless integration with financial systems.

  • Concurrent Program: IBY_FD_PAYMENT_FORMAT 12.1.1

    execution_filename: FDExtractAndFormatting ,  product: IBY - Payments ,  user_name: Format Payment Instructions ,  description: Formats payment instructions ,  argument_method: Standard ,  enabled: Yes ,  execution_method: Java Concurrent Program , 

  • Concurrent Program: IBY_FD_PAYMENT_FORMAT 12.2.2

    execution_filename: FDExtractAndFormatting ,  product: IBY - Payments ,  user_name: Format Payment Instructions ,  description: Formats payment instructions ,  argument_method: Standard ,  enabled: Yes ,  execution_method: Java Concurrent Program , 

  • Concurrent Program: IBYPICPE 12.1.1

    execution_filename: IBY_BUILD_INSTRUCTIONS_PUB_PKG.build_electronic_instructions ,  product: IBY - Payments ,  user_name: Create Electronic Payment Instructions ,  description: Creates payment instructions by grouping payments ,  argument_method: Standard ,  enabled: Yes ,  execution_method: PL/SQL Stored Procedure , 

  • Concurrent Program: IBYPICP 12.1.1

    execution_filename: IBY_BUILD_INSTRUCTIONS_PUB_PKG.build_printed_instructions ,  product: IBY - Payments ,  user_name: Create Printed Payment Instructions ,  description: Creates payment instructions by grouping payments ,  argument_method: Standard ,  enabled: Yes ,  execution_method: PL/SQL Stored Procedure , 

  • Lookup Type: IBY_FD_DASHBOARD_PROCESS_TYPES 12.2.2

    product: IBY - Payments ,  meaning: Funds Disbursement Process Types ,  description: Funds Disbursement Process Types , 

  • Lookup Type: IBY_FD_DASHBOARD_PROCESS_TYPES 12.1.1

    product: IBY - Payments ,  meaning: Funds Disbursement Process Types ,  description: Funds Disbursement Process Types , 

  • Concurrent Program: IBYPICP 12.2.2

    execution_filename: CreatePrintedPI ,  product: IBY - Payments ,  user_name: Printed Payment Instructions ,  description: Creates payment instructions by grouping payments ,  argument_method: Standard ,  enabled: Yes ,  execution_method: Java Concurrent Program , 

  • Concurrent Program: IBY_FD_PAYMENT_FORMAT_TEXT 12.1.1

    execution_filename: FDExtractAndFormatting ,  product: IBY - Payments ,  user_name: Format Payment Instructions ,  description: Formats payment instructions ,  argument_method: Standard ,  enabled: Yes ,  execution_method: Java Concurrent Program , 

  • Concurrent Program: IBY_FD_PAYMENT_FORMAT_TEXT 12.2.2

    execution_filename: FDExtractAndFormatting ,  product: IBY - Payments ,  user_name: Format Payment Instructions ,  description: Formats payment instructions ,  argument_method: Standard ,  enabled: Yes ,  execution_method: Java Concurrent Program , 

  • Concurrent Program: IBYPICPE 12.2.2

    execution_filename: CreateElectronicPI ,  product: IBY - Payments ,  user_name: Electronic Payment Instructions ,  description: Creates payment instructions by grouping payments ,  argument_method: Standard ,  enabled: Yes ,  execution_method: Java Concurrent Program , 

  • Lookup Type: IBY_DIRDEB_BANK_INSTR 12.1.1

    product: IBY - Payments ,  meaning: Direct Debit Bank Instructions ,  description: Direct Debit Bank Instructions , 

  • Lookup Type: IBY_DIRDEB_BANK_INSTR 12.2.2

    product: IBY - Payments ,  meaning: Direct Debit Bank Instructions ,  description: Direct Debit Bank Instructions , 

  • Concurrent Program: IBY_FD_EXTRACT_AND_FORMATTING 12.1.1

    execution_filename: FDExtractAndFormatting ,  product: IBY - Payments ,  user_name: Format Payment Instructions ,  description: Formats payment instructions ,  argument_method: Standard ,  enabled: No ,  execution_method: Java Concurrent Program , 

  • Concurrent Program: IBY_FD_EXTRACT_AND_FORMATTING 12.2.2

    execution_filename: FDExtractAndFormatting ,  product: IBY - Payments ,  user_name: Format Payment Instructions ,  description: Formats payment instructions ,  argument_method: Standard ,  enabled: No ,  execution_method: Java Concurrent Program , 

  • Concurrent Program: IBY_FD_RECORD_PRINT_STATUS 12.2.2

    execution_filename: IBY_DISBURSE_UI_API_PUB_PKG.record_print_status ,  product: IBY - Payments ,  user_name: Record Print Status ,  description: Records the Print Status for Printed Payment Instructions ,  argument_method: Standard ,  enabled: Yes ,  execution_method: PL/SQL Stored Procedure , 

  • Table: IBY_INSTR_CREATION_RULES 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_INSTR_CREATION_RULES,  object_name:IBY_INSTR_CREATION_RULES,  status:VALID,  product: IBY - Payments ,  description: IBY_INSTR_CREATION_RULES specifies how payments are grouped into payment instructions. Payment instructions are always grouped by internal bank account and payment process profile but additional items stored in this table can be added for f ,  implementation_dba_data: IBY.IBY_INSTR_CREATION_RULES , 

  • Table: IBY_PAY_INSTRUCTIONS_H 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PAY_INSTRUCTIONS_H,  object_name:IBY_PAY_INSTRUCTIONS_H,  status:VALID,  product: IBY - Payments ,  description: IBY_PAY_INSTRUCTIONS_H stores historical snapshots of payment instructions. This table contains denormalized versions of payment instructions from specific points in time, including when the payment instruction was submitted to a payment sy ,  implementation_dba_data: IBY.IBY_PAY_INSTRUCTIONS_H , 

  • Table: IBY_PAY_INSTRUCTIONS_ALL 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PAY_INSTRUCTIONS_ALL,  object_name:IBY_PAY_INSTRUCTIONS_ALL,  status:VALID,  product: IBY - Payments ,  description: "This table contains records of the payment instructions. Instructions are created based on the Payment Process Request options. Data is inserted in to the table IBY_PAY_INSTRUCTIONS_AL after payment instruction creation, based on the opt ,  implementation_dba_data: IBY.IBY_PAY_INSTRUCTIONS_ALL , 

  • Table: IBY_BANK_INSTRUCTIONS_TL 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_BANK_INSTRUCTIONS_TL,  object_name:IBY_BANK_INSTRUCTIONS_TL,  status:VALID,  product: IBY - Payments ,  description: IBY_BANK_INSTRUCTIONS stores bank instructions that are used as lookup values for payment process profiles and external payee setup. This table corresponds to the Bank Instruction Codes page. ,  implementation_dba_data: IBY.IBY_BANK_INSTRUCTIONS_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 , 

  • 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_ACCT_PMT_PROFILES_TL 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_ACCT_PMT_PROFILES_TL,  object_name:IBY_ACCT_PMT_PROFILES_TL,  status:VALID,  product: IBY - Payments ,  description: IBY_ACCT_PMT_PROFILES stores account-related information that completes the specification of the handling of payment instructions. Entries in this table are based on entries in the IBY_SYS_PMT_PROFILES table. A combination of the two tables ,  implementation_dba_data: IBY.IBY_ACCT_PMT_PROFILES_TL , 

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

  • Lookup Type: IBY_VALIDATION_LEVELS 12.2.2

    product: IBY - Payments ,  meaning: Validation Levels ,  description: Validation levels , 

  • Lookup Type: IBY_PAYMENTS_COMPLETE 12.1.1

    product: IBY - Payments ,  meaning: Payments Complete ,  description: Completion of a payment instructions constituent payments , 

  • Lookup Type: IBY_PAYMENTS_COMPLETE 12.2.2

    product: IBY - Payments ,  meaning: Payments Complete ,  description: Completion of a payment instructions constituent payments , 

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

  • Lookup Type: IBY_VALIDATION_LEVELS 12.1.1

    product: IBY - Payments ,  meaning: Validation Levels ,  description: Validation levels , 

  • Table: IBY_BANK_INSTRUCTIONS_B 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_BANK_INSTRUCTIONS_B,  object_name:IBY_BANK_INSTRUCTIONS_B,  status:VALID,  product: IBY - Payments ,  description: IBY_BANK_INSTRUCTIONS stores bank instructions that are used as lookup values for payment process profiles and external payee setup. This table corresponds to the Bank Instruction Codes page. ,  implementation_dba_data: IBY.IBY_BANK_INSTRUCTIONS_B , 

  • Table: IBY_ACCT_PMT_PROFILES_B 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_ACCT_PMT_PROFILES_B,  object_name:IBY_ACCT_PMT_PROFILES_B,  status:VALID,  product: IBY - Payments ,  description: IBY_ACCT_PMT_PROFILES stores account-related information that completes the specification of the handling of payment instructions. Entries in this table are based on entries in the IBY_SYS_PMT_PROFILES table. A combination of the two tables ,  implementation_dba_data: IBY.IBY_ACCT_PMT_PROFILES_B , 

  • Lookup Type: IBY_RISK_FACTOR_NAME 12.1.1

    product: IBY - Payments ,  meaning: IBY RISK FACTOR NAME ,  description: Risk Factors , 

  • Lookup Type: IBY_RISK_FACTOR_NAME 12.2.2

    product: IBY - Payments ,  meaning: IBY RISK FACTOR NAME ,  description: Risk Factors ,