Search Results iby_payments_h




Overview
Explore in AI Chat

Overview

The IBY_PAYMENTS_H table is a core data object within the Oracle E-Business Suite Payments (IBY) module, specifically designed for audit and historical tracking. It serves as a historical snapshot repository for payment records. Unlike transactional tables that hold the current state of a payment, this table captures denormalized versions of payments at specific, significant points in their lifecycle, such as when a payment is submitted to an external payment system. This design allows the system to preserve an immutable record of what a payment looked like at a given historical moment, enabling detailed audit trails, compliance reporting, and analysis of payment state changes over time.

Key Information Stored

The table's primary key is PAYMENT_HISTORY_ID, which uniquely identifies each historical snapshot. The data stored is a comprehensive denormalized record of a payment. Based on its foreign key relationships, critical columns include PAYMENT_INSTRUCTION_ID (linking to the source IBY_PAY_INSTRUCTIONS_ALL), PAYMENT_SERVICE_REQUEST_ID, and PAYMENT_INSTRUCTION_HISTORY_ID. It also stores payment-specific attributes like BANK_INSTRUCTION1_CODE, BANK_INSTRUCTION2_CODE, PAYMENT_REASON_CODE, and COUNTRY. The denormalized structure means each row contains a complete set of payment data as it existed at the snapshot time, facilitating efficient historical queries without complex joins to multiple transactional tables.

Common Use Cases and Queries

The primary use case is auditing the complete state of a payment at the moment it was processed or transmitted. This is crucial for regulatory compliance and dispute resolution. Common reporting scenarios include tracing the evolution of a specific payment or generating reports on all payments submitted to a banking partner on a given date. A typical query pattern involves joining to the payment instructions table to filter on original payment criteria before analyzing the historical snapshot.

SELECT iph.payment_history_id,
       iph.payment_instruction_id,
       iph.payment_status,
       iph.payment_amount,
       iph.payment_date
FROM iby_payments_h iph,
     iby_pay_instructions_all ipi
WHERE iph.payment_instruction_id = ipi.payment_instruction_id
  AND ipi.internal_bank_account_id = 12345
  AND TRUNC(iph.creation_date) = :p_snapshot_date;

Another key use is investigating the lineage between a payment instruction and its related documents, often by joining to IBY_DOCUMENTS_PAYABLE_H.

Related Objects

IBY_PAYMENTS_H is centrally connected to several key Payments tables. Its main foreign key relationships are:

  • IBY_PAY_INSTRUCTIONS_ALL: The source transactional payment instruction.
  • IBY_PAY_INSTRUCTIONS_H: The historical snapshot of the related payment instruction.
  • IBY_PAY_SERVICE_REQUESTS: The overarching payment process request.
  • IBY_DOCUMENTS_PAYABLE_H: A critical relationship where historical documents (invoices) reference the payment snapshot via PAYMENT_HISTORY_ID.
  • IBY_BANK_INSTRUCTIONS_B & IBY_PAYMENT_REASONS_B: Reference data for bank instructions and payment reasons.
  • FND_TERRITORIES: Reference data for the payment country.
  • Table: IBY_PAYMENTS_H 12.2.2

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

  • Table: IBY_PAYMENTS_H 12.1.1

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

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

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

  • 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_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_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_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_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_PAYMENT_REASONS_B 12.2.2

    owner:IBY,  object_type:TABLE,  fnd_design_data:IBY.IBY_PAYMENT_REASONS_B,  object_name:IBY_PAYMENT_REASONS_B,  status:VALID,  product: IBY - Payments ,  description: IBY_PAYMENT_REASONS stores payment reasons that are used as lookup values for payee records or documents payable, that is, invoices. This table is similar to FND_LOOKUPS, but with a new column for territory identification. Products that use ,  implementation_dba_data: IBY.IBY_PAYMENT_REASONS_B ,