Search Results iby_pay_instructions_h




Overview
Explore in AI Chat

Overview

The IBY_PAY_INSTRUCTIONS_H table is a core data object within the Oracle Payments (IBY) module of Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2. It functions as a historical audit trail for payment instructions. When a payment instruction is created, processed, or its status changes, a snapshot of its key attributes is recorded in this table. This provides a complete, immutable history of each payment instruction's lifecycle, which is critical for audit compliance, troubleshooting payment processing issues, and generating detailed historical reports on payment activities. The table's primary key, PAYMENT_INSTRUCTION_HISTORY_ID, uniquely identifies each historical record.

Key Information Stored

The table stores a comprehensive set of attributes captured at specific points in a payment instruction's history. Based on the provided metadata, critical columns include the primary identifier, PAYMENT_INSTRUCTION_HISTORY_ID, and several foreign key columns that link to related configuration entities. These foreign keys are BEPID (linking to IBY_BEPINFO for the Business Event Processor), PAYMENT_FORMAT_CODE, PAYMENT_REASON_CODE (linking to IBY_PAYMENT_REASONS_B), TRANSMIT_CONFIGURATION_ID, and POSITIVE_PAY_FORMAT_CODE. While the specific content columns are not detailed in the excerpt, such a table typically captures data points like the payment instruction ID, status, amount, currency, payment process request ID, and the timestamp of the historical snapshot.

Common Use Cases and Queries

This table is primarily used for auditing and investigative reporting. A common scenario involves tracing the status evolution of a specific payment instruction to identify when and why it failed or was put on hold. Analysts may also query it to report on all payment instructions processed by a specific format or through a particular transmission configuration over a given period. A sample query pattern to retrieve the history for a payment instruction would be:

  • SELECT * FROM iby.iby_pay_instructions_h WHERE payment_instruction_id = :p_inst_id ORDER BY creation_date;

Another typical use case is joining this history table with the current payment instructions table (IBY_PAY_INSTRUCTIONS_ALL) to compare current state against past states for reconciliation purposes.

Related Objects

The IBY_PAY_INSTRUCTIONS_H table has defined relationships with several other IBY configuration tables, as indicated by its foreign keys. Key related objects include:

  • IBY_BEPINFO: References the BEPID to provide details about the Business Event Processor involved.
  • IBY_PAYMENT_REASONS_B: References the PAYMENT_REASON_CODE to provide the descriptive reason for the payment.
  • IBY_PAY_INSTRUCTIONS_ALL: The primary transactional table for which this table provides the historical audit trail. The relationship is typically maintained via the PAYMENT_INSTRUCTION_ID column.

These relationships ensure that the historical snapshot retains contextual information about the system configuration at the time the record was created.