Search Results payment_document_id




Overview
Explore in AI Chat

Overview

The IBY_USED_PAYMENT_DOCS table is a core data object within the Oracle E-Business Suite (EBS) Payments (IBY) module, specifically in versions 12.1.1 and 12.2.2. It functions as a control and tracking mechanism for payment document numbers, such as check numbers or electronic payment identifiers. Its primary role is to maintain a historical record of every unique document number that has been utilized or issued by the system. This ensures the integrity and uniqueness of payment document identifiers, preventing accidental or duplicate usage across different payment documents and processes. The table is critical for audit trails, reconciliation, and maintaining the sequential integrity of payment instruments generated by the Oracle Payments engine.

Key Information Stored

The table's structure is defined by a composite primary key, which consists of two critical columns. The PAYMENT_DOCUMENT_ID column is a foreign key that links to the specific payment document definition or instruction. The USED_DOCUMENT_NUMBER column stores the actual, unique sequential number that has been consumed or issued, such as "1001" for a specific check. Together, these columns form a record that a particular document number has been assigned to a specific payment document. This simple but essential structure provides a definitive log of used numbers, which is referenced whenever the system needs to generate a new, unused payment document identifier.

Common Use Cases and Queries

The primary use case is verifying the usage status of a payment document number during payment instruction creation or voiding processes. For instance, before printing a check, the system queries this table to confirm the proposed check number has not already been used. A common reporting need is to audit all document numbers used for a specific payment document over time. A sample query to retrieve this information would be: SELECT USED_DOCUMENT_NUMBER FROM IBY.IBY_USED_PAYMENT_DOCS WHERE PAYMENT_DOCUMENT_ID = :doc_id ORDER BY USED_DOCUMENT_NUMBER; Another critical scenario is troubleshooting duplicate number errors or gaps in payment document sequences, where analysts query this table to understand the historical issuance pattern.

Related Objects

The table's main relationship is defined by its primary key constraint, IBY_USED_PAYMENT_DOCS_PK, on the columns (PAYMENT_DOCUMENT_ID, USED_DOCUMENT_NUMBER). The PAYMENT_DOCUMENT_ID column is a foreign key (FK) that references the primary key of a parent table defining the payment document setup. While the exact parent table name is not specified in the provided metadata, it is logically related to core IBY tables such as IBY_PAYMENT_DOCUMENTS or IBY_DOCS_PAYABLE_ALL, which manage the definition and status of payment instruments. Any process or report that requires a list of consumed payment document numbers will join to this table using the PAYMENT_DOCUMENT_ID as the key column.