Search Results a breakpoint could not be inserted visual studio resharper




The IBY_ACCTTYPE table in Oracle E-Business Suite (EBS) 12.1.1 or 12.2.2 is a critical component of the Oracle Payments module (IBY), which facilitates payment processing across various financial transactions. This table stores account type definitions, serving as a reference for classifying bank accounts used in payment processing, such as disbursements, receipts, or fund transfers. Below is a detailed analysis of its structure, purpose, and integration within Oracle EBS.

Purpose and Functional Role

The IBY_ACCTTYPE table acts as a lookup repository for account types, ensuring standardized categorization of bank accounts. It supports payment workflows by associating accounts with specific attributes (e.g., "Internal," "Customer," "Supplier," or "Payroll"). This classification is essential for payment validation, bank account validation (BAV), and compliance with financial regulations. For example, supplier payments require distinct account types compared to customer refunds, and this table enforces such distinctions.

Table Structure and Key Columns

The table's structure includes the following key columns:

  • ACCOUNT_TYPE_CODE: A unique identifier (e.g., 'INTERNAL', 'SUPPLIER') for the account type.
  • ACCOUNT_TYPE_NAME: A descriptive name for the account type (e.g., "Internal Bank Account").
  • DESCRIPTION: Additional details about the account type's usage.
  • ENABLED_FLAG: A Boolean flag ('Y'/'N') to activate/deactivate the account type.
  • CREATION_DATE and LAST_UPDATE_DATE: Audit columns tracking record creation/modification.
These columns ensure referential integrity with related tables like IBY_EXT_BANK_ACCOUNTS, where bank account details are stored.

Integration with Oracle EBS Modules

IBY_ACCTTYPE integrates with multiple EBS modules:

  1. Payables (AP): Validates supplier bank accounts during payment processing.
  2. Receivables (AR): Classifies customer accounts for refunds or direct debits.
  3. Payroll (HRMS): Identifies employee bank accounts for salary disbursements.
  4. Treasury (CE): Manages internal accounts for cash positioning.
The table's data is referenced in payment APIs, such as IBY_FNDCPT_PUB, to enforce business rules during transaction processing.

Customization and Extensibility

While Oracle provides seeded account types, organizations can extend the table by adding custom types (e.g., "Vendor Commission Account") via the Oracle Payments Administrator responsibility. However, modifications require careful testing to avoid conflicts with existing payment workflows. Custom types must adhere to the IBY_ACCTTYPE structure and integrate with the IBY_EXT_BANK_ACCOUNTS relationship model.

Data Security and Access Control

Access to IBY_ACCTTYPE is restricted via Oracle's Function Security, typically granted to Payment Administrators. Sensitive operations (e.g., disabling an account type) may require approval workflows to prevent disruptions. The table's data is also audited through Oracle Audit Vault or custom triggers.

Conclusion

The IBY_ACCTTYPE table is a foundational element in Oracle Payments, ensuring accurate bank account classification and seamless interoperability across EBS modules. Its design supports both out-of-the-box functionality and organizational-specific extensions, making it indispensable for payment processing in Oracle EBS 12.1.1 and 12.2.2. Proper configuration and maintenance of this table are crucial for compliance and operational efficiency.

  • 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_ACCTTYPE 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_ACCTTYPE,  object_name:IBY_ACCTTYPE,  status:VALID,  product: IBY - Payments ,  description: IBY_ACCTTYPE contains a list of various account types supported. For example for bank account, the account types could be Checking, Savings etc, for Credit Card, the account types could be Visa, MasterCard, Discover etc... ,  implementation_dba_data: IBY.IBY_ACCTTYPE , 

  • Table: IBY_ACCTTYPE 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_ACCTTYPE,  object_name:IBY_ACCTTYPE,  status:VALID,  product: IBY - Payments ,  description: IBY_ACCTTYPE contains a list of various account types supported. For example for bank account, the account types could be Checking, Savings etc, for Credit Card, the account types could be Visa, MasterCard, Discover etc... ,  implementation_dba_data: IBY.IBY_ACCTTYPE , 

  • Table: IBY_RISK_FORMULAS 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_RISK_FORMULAS,  object_name:IBY_RISK_FORMULAS,  status:VALID,  product: IBY - Payments ,  description: IBY_RISK_FORMULAS stores risk formula retaled information . Risk Formula is used by merchants to evaluate the risk of the customer. This formula could be different for different goods/services offered by the merchants. A Risk Formula may be ,  implementation_dba_data: IBY.IBY_RISK_FORMULAS , 

  • Table: IBY_RISK_FORMULAS 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_RISK_FORMULAS,  object_name:IBY_RISK_FORMULAS,  status:VALID,  product: IBY - Payments ,  description: IBY_RISK_FORMULAS stores risk formula retaled information . Risk Formula is used by merchants to evaluate the risk of the customer. This formula could be different for different goods/services offered by the merchants. A Risk Formula may be ,  implementation_dba_data: IBY.IBY_RISK_FORMULAS , 

  • Lookup Type: IBY_TRANSACTION_STATUS 12.1.1

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

  • Lookup Type: IBY_TRANSACTION_STATUS 12.2.2

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

  • Lookup Type: IBY_REQUEST_STATUSES 12.1.1

    product: IBY - Payments ,  meaning: Payment Process Request Statuses ,  description: Payment process request statuses , 

  • Lookup Type: IBY_REQUEST_STATUSES 12.2.2

    product: IBY - Payments ,  meaning: Payment Process Request Statuses ,  description: Payment process request statuses , 

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

  • 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_CURRENCY_CONDITIONS 12.1.1

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

  • Lookup Type: IBY_CURRENCY_CONDITIONS 12.2.2

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

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

  • Table: IBY_FNDCPT_PAYEE_APPL 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_FNDCPT_PAYEE_APPL,  object_name:IBY_FNDCPT_PAYEE_APPL,  status:VALID,  product: IBY - Payments ,  description: IBY_FNDCPT_PAYEE_APPL is a mapping table between internal payees and operating units. One payee may be associated with many operating units. An operating unit may be associated with at most one payee. ,  implementation_dba_data: IBY.IBY_FNDCPT_PAYEE_APPL , 

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

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

  • Table: IBY_INSTRUCT_SOURCE_APPS 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_INSTRUCT_SOURCE_APPS,  object_name:IBY_INSTRUCT_SOURCE_APPS,  status:VALID,  product: IBY - Payments ,  description: IBY_INSTRUCT_SOURCE_APPS stores a list of source products that submitted documents to be paid in each payment instruction. ,  implementation_dba_data: IBY.IBY_INSTRUCT_SOURCE_APPS , 

  • Lookup Type: IBY_PAYMENT_SORT_ORDERS 12.1.1

    product: IBY - Payments ,  meaning: Payment Sort Order ,  description: Defines the order in which payments in a payment instruction can be sorted. , 

  • Lookup Type: IBY_PAYMENT_SORT_ORDERS 12.2.2

    product: IBY - Payments ,  meaning: Payment Sort Order ,  description: Defines the order in which payments in a payment instruction can be sorted. , 

  • Lookup Type: IBY_DELIVERY_METHODS 12.2.2

    product: IBY - Payments ,  meaning: Delivery Methods ,  description: Defines delivery methods that can be used to deliver remittance advice to payees , 

  • Lookup Type: IBY_DELIVERY_METHODS 12.1.1

    product: IBY - Payments ,  meaning: Delivery Methods ,  description: Defines delivery methods that can be used to deliver remittance advice to payees , 

  • Table: IBY_INSTRHOLDER 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_INSTRHOLDER,  object_name:IBY_INSTRHOLDER,  status:VALID,  product: IBY - Payments ,  description: IBY_INSTRHOLDER stores the information about the holder of the instrment. A payment instrument can be held by different users or payees or payers. ,  implementation_dba_data: IBY.IBY_INSTRHOLDER , 

  • Table: IBY_INSTRHOLDER 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_INSTRHOLDER,  object_name:IBY_INSTRHOLDER,  status:VALID,  product: IBY - Payments ,  description: IBY_INSTRHOLDER stores the information about the holder of the instrment. A payment instrument can be held by different users or payees or payers. ,  implementation_dba_data: IBY.IBY_INSTRHOLDER , 

  • Table: IBY_VALIDATION_PARAMS_TL 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_VALIDATION_PARAMS_TL,  object_name:IBY_VALIDATION_PARAMS_TL,  status:VALID,  product: IBY - Payments ,  description: IBY_VALIDATION_PARAMS stores parameters for each validation. 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 actual valu ,  implementation_dba_data: IBY.IBY_VALIDATION_PARAMS_TL , 

  • Table: IBY_VALIDATION_PARAMS_B 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_VALIDATION_PARAMS_B,  object_name:IBY_VALIDATION_PARAMS_B,  status:VALID,  product: IBY - Payments ,  description: IBY_VALIDATION_PARAMS stores parameters for each validation. 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 actual valu ,  implementation_dba_data: IBY.IBY_VALIDATION_PARAMS_B , 

  • Table: IBY_ACCOUNT_OWNERS 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_ACCOUNT_OWNERS,  object_name:IBY_ACCOUNT_OWNERS,  status:VALID,  product: IBY - Payments ,  description: This table contains records of the account owners of the external bank accounts entered manually. This table corresponds to the Banking details page of supplier or customer. When an external bank account is created a row will be stored in ,  implementation_dba_data: IBY.IBY_ACCOUNT_OWNERS , 

  • Table: IBY_BATCHES_ALL 12.1.1

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_BATCHES_ALL,  object_name:IBY_BATCHES_ALL,  status:VALID,  product: IBY - Payments ,  description: IBY_BATCHES holds the information about batch operations for SSL credit card transactions. A terminal based merchant will need to have batch operations. The status of the payees batch will be contained in this table. ,  implementation_dba_data: IBY.IBY_BATCHES_ALL , 

  • Lookup Type: IBY_PAYMENT_SORT_OPTIONS 12.1.1

    product: IBY - Payments ,  meaning: Payment Sort Options ,  description: Defines the options by which payments in a payment instruction can be sorted. , 

  • Table: IBY_FNDCPT_TX_EXTENSIONS 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_FNDCPT_TX_EXTENSIONS,  object_name:IBY_FNDCPT_TX_EXTENSIONS,  status:VALID,  product: IBY - Payments ,  description: "The data in this table will be created by the source products through the public API IBY_FNDCPT_TRXN_PUB, Create_Transaction_Extension and Copy_Transaction_Extension to register a Funds capture transaction. IBY_FNDCPT_TX_EXTENSIONS table ,  implementation_dba_data: IBY.IBY_FNDCPT_TX_EXTENSIONS , 

  • Lookup Type: IBY_PAYMENT_SORT_OPTIONS 12.2.2

    product: IBY - Payments ,  meaning: Payment Sort Options ,  description: Defines the options by which payments in a payment instruction can be sorted. , 

  • Lookup Type: IBY_MARK_COMPLETE_EVENTS 12.1.1

    product: IBY - Payments ,  meaning: Mark Payments Complete Events ,  description: Defines the events in the payment process at which the payments in a payment instruction can be marked complete , 

  • Lookup Type: IBY_MARK_COMPLETE_EVENTS 12.2.2

    product: IBY - Payments ,  meaning: Mark Payments Complete Events ,  description: Defines the events in the payment process at which the payments in a payment instruction can be marked complete , 

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

  • Lookup Type: IBY_PAYMENT_STATUSES 12.1.1

    product: IBY - Payments ,  meaning: Payment Statuses ,  description: Payment statuses , 

  • Lookup Type: IBY_PAYMENT_STATUSES 12.2.2

    product: IBY - Payments ,  meaning: Payment Statuses ,  description: Payment statuses , 

  • Lookup Type: IBY_PAY_INSTRUCTION_STATUSES 12.2.2

    product: IBY - Payments ,  meaning: Payment Instruction Statuses ,  description: Payment instruction statuses , 

  • Lookup Type: IBY_TRXNTYPES 12.1.1

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

  • Lookup Type: IBY_PAY_INSTRUCTION_STATUSES 12.1.1

    product: IBY - Payments ,  meaning: Payment Instruction Statuses ,  description: Payment instruction statuses , 

  • Lookup Type: IBY_TRXNTYPES 12.2.2

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