Search Results iby_acct_pmt_profiles_b




The IBY_ACCT_PMT_PROFILES_B table in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 is a critical component of the Oracle Payments module, which facilitates payment processing across various Oracle applications. This table serves as the foundation for storing payment profile details at the account level, enabling organizations to define and manage payment processing rules, formats, and methods for different bank accounts. Below is a detailed analysis of its structure, purpose, and integration within Oracle EBS.

Purpose and Functional Overview

The IBY_ACCT_PMT_PROFILES_B table stores payment profile configurations linked to specific bank accounts. These profiles determine how payments are processed, including payment methods, formats (e.g., EFT, check, wire), and validation rules. The table acts as a bridge between bank account setups (CE_BANK_ACCOUNTS) and payment instructions (IBY_PAYMENTS_ALL), ensuring consistency in payment execution. Key functionalities include:

  • Payment Method Assignment: Defines allowed payment methods (e.g., ACH, SWIFT) per account.
  • Format Customization: Specifies payment file formats (e.g., BAI2, NACHA) for electronic payments.
  • Validation Rules: Enforces business rules (e.g., minimum/maximum payment amounts) during payment creation.

Table Structure and Key Columns

The table’s structure includes columns that map payment profiles to bank accounts and define processing attributes. Notable columns include:

Column Name Data Type Description
ACCOUNT_PMT_PROFILE_ID NUMBER Primary key; unique identifier for the payment profile.
BANK_ACCOUNT_ID NUMBER Foreign key linking to CE_BANK_ACCOUNTS.
PAYMENT_PROFILE_ID NUMBER References IBY_PMT_PROFILES_B for shared profile settings.
ORG_TYPE VARCHAR2(30) Indicates the owning entity type (e.g., 'LE', 'OU').
ORG_ID NUMBER ID of the owning organization (Legal Entity/Operating Unit).
ENABLED_FLAG VARCHAR2(1) Activates/deactivates the profile ('Y'/'N').

Integration with Oracle EBS Modules

The table integrates with several EBS modules:

  • Accounts Payable (AP): Payment profiles determine how supplier invoices are paid.
  • Accounts Receivable (AR): Defines formats for customer receipt processing.
  • Cash Management (CE): Links bank accounts to payment instructions for reconciliation.

Technical Considerations

In EBS 12.2.2, the table leverages Oracle’s Online Patching (ADOP) framework, ensuring zero downtime during updates. Indexes like IBY_ACCT_PMT_PROFILES_B_N1 (on BANK_ACCOUNT_ID) optimize query performance. Customizations should avoid direct DML on this table; instead, use Oracle Payments’ APIs (IBY_PROFILE_PUB) to maintain data integrity.

Conclusion

The IBY_ACCT_PMT_PROFILES_B table is a cornerstone of Oracle Payments, enabling granular control over payment processing. Its design ensures scalability and compliance with global banking standards, making it indispensable for organizations leveraging Oracle EBS for financial operations.

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

  • Table: IBY_ACCT_PMT_PROFILES_B 12.1.1

    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 ,  implementation_dba_data: IBY.IBY_ACCT_PMT_PROFILES_B , 

  • Table: IBY_PAY_SERVICE_REQUESTS 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PAY_SERVICE_REQUESTS,  object_name:IBY_PAY_SERVICE_REQUESTS,  status:VALID,  product: IBY - Payments ,  implementation_dba_data: IBY.IBY_PAY_SERVICE_REQUESTS , 

  • Table: IBY_DOCUMENTS_PAYABLE_H 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_DOCUMENTS_PAYABLE_H,  object_name:IBY_DOCUMENTS_PAYABLE_H,  status:VALID,  product: IBY - Payments ,  implementation_dba_data: IBY.IBY_DOCUMENTS_PAYABLE_H , 

  • Table: IBY_SYS_PMT_PROFILES_B 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_SYS_PMT_PROFILES_B,  object_name:IBY_SYS_PMT_PROFILES_B,  status:VALID,  product: IBY - Payments ,  implementation_dba_data: IBY.IBY_SYS_PMT_PROFILES_B , 

  • Table: IBY_TRANSMIT_CONFIGS_B 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_TRANSMIT_CONFIGS_B,  object_name:IBY_TRANSMIT_CONFIGS_B,  status:VALID,  product: IBY - Payments ,  implementation_dba_data: IBY.IBY_TRANSMIT_CONFIGS_B , 

  • Table: IBY_BEPKEYS 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_BEPKEYS,  object_name:IBY_BEPKEYS,  status:VALID,  product: IBY - Payments ,  description: IBY_BEPKEYS stores information about the payment systems accounts. ,  implementation_dba_data: IBY.IBY_BEPKEYS , 

  • Table: IBY_PAY_INSTRUCTIONS_ALL 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PAY_INSTRUCTIONS_ALL,  object_name:IBY_PAY_INSTRUCTIONS_ALL,  status:VALID,  product: IBY - Payments ,  implementation_dba_data: IBY.IBY_PAY_INSTRUCTIONS_ALL , 

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

  • Table: IBY_PAY_SERVICE_REQUESTS 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PAY_SERVICE_REQUESTS,  object_name:IBY_PAY_SERVICE_REQUESTS,  status:VALID,  product: IBY - Payments ,  description: "This table contains records of the payment process requests which are created by system while processing 'Build payments' program.IBY_PAY_SERVICE_REQUESTS stores payment process requests from source products. A payment process request is ,  implementation_dba_data: IBY.IBY_PAY_SERVICE_REQUESTS , 

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

  • View: IBY_ACCT_PMT_PROFILES_VL 12.1.1

    owner:APPS,  object_type:VIEW,  fnd_design_data:IBY.IBY_ACCT_PMT_PROFILES_VL,  object_name:IBY_ACCT_PMT_PROFILES_VL,  status:VALID,  product: IBY - Payments ,  implementation_dba_data: APPS.IBY_ACCT_PMT_PROFILES_VL , 

  • View: IBY_ACCT_PMT_PROFILES_VL 12.2.2

    owner:APPS,  object_type:VIEW,  fnd_design_data:IBY.IBY_ACCT_PMT_PROFILES_VL,  object_name:IBY_ACCT_PMT_PROFILES_VL,  status:VALID,  product: IBY - Payments ,  implementation_dba_data: APPS.IBY_ACCT_PMT_PROFILES_VL , 

  • Table: IBY_DOCUMENTS_PAYABLE_H 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_DOCUMENTS_PAYABLE_H,  object_name:IBY_DOCUMENTS_PAYABLE_H,  status:VALID,  product: IBY - Payments ,  description: IBY_DOCUMENTS_PAYABLE_H stores historical snapshots of documents payable. This table contains denormalized versions of documents payable from specific points in time, such as when the payment for this document was submitted to a payment sys ,  implementation_dba_data: IBY.IBY_DOCUMENTS_PAYABLE_H , 

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

  • Table: IBY_DOCS_PAYABLE_ALL 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_DOCS_PAYABLE_ALL,  object_name:IBY_DOCS_PAYABLE_ALL,  status:VALID,  product: IBY - Payments ,  description: "This table contains records of the documents payable which are updated by system while processing 'Build payments' program. IBY_DOCS_PAYABLE_ALL stores Oracle Payments' representation of source products' documents payable. A document pay ,  implementation_dba_data: IBY.IBY_DOCS_PAYABLE_ALL , 

  • Table: IBY_SYS_PMT_PROFILES_B 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_SYS_PMT_PROFILES_B,  object_name:IBY_SYS_PMT_PROFILES_B,  status:VALID,  product: IBY - Payments ,  description: "This table stores Payment Process Profile setup for Funds Disbursement transactions. This table also stores information of the seeded Payment process profiles. IBY_SYS_PMT_PROFILES_B stores information that specifies the bulk of payment ,  implementation_dba_data: IBY.IBY_SYS_PMT_PROFILES_B ,