Results for “document_payable_history_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

IBY_DOCUMENT_LINES_H is a history table in the Oracle Payments (IBY) module of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. It stores historical or versioned snapshots of payment document line records and is owned by the IBY schema. Where the base table IBY_DOCUMENT_LINES holds the current state of payable document lines, this history table preserves prior states, capturing changes over time as the associated payable document is created, modified, or transitioned through the payment lifecycle. This design supports auditability and point-in-time reporting for payment processing.

The table is identified by the primary key constraint IBY_DOCUMENT_LINES_H_PK on the column DOCUMENT_LINE_HISTORY_ID. Based on the heuristic Data Vault classification derived from the foreign key structure, this object is modeled as a link. It is a modeling suggestion rather than a fixed rule: the table associates a document payable identifier with a document payable line identifier while anchoring a history/version record, which is characteristic of a link construct relating the parent document history to the underlying line entity.

Key Information Stored

The table contains 21 documented columns. The most significant include:

• DOCUMENT_LINE_HISTORY_ID — surrogate primary key uniquely identifying each historical line record.
• DOCUMENT_LINE_HISTORY_DATE — timestamp indicating when the historical snapshot was captured.
• DOCUMENT_PAYABLE_HISTORY_ID — link to the parent payable document history record.
• DOCUMENT_PAYABLE_LINE_ID — reference to the current line in IBY_DOCUMENT_LINES.
• DOCUMENT_PAYABLE_ID — foreign key to IBY_DOCS_PAYABLE_ALL, linking the line to its parent payable document.
• CALLING_APP_DOCUMENT_LINE_CODE — the originating application's document line identifier.
• LINE_NUMBER, LINE_TYPE, LINE_NAME — descriptive attributes defining the line.
• LINE_AMOUNT, UNIT_PRICE, QUANTITY, UNIT_OF_MEASURE — monetary and quantitative attributes.
• DESCRIPTION — free-text detail for the line.
• Standard audit columns CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, OBJECT_VERSION_NUMBER, LAST_UPDATE_LOGIN.

The business-key candidates are the combination of the parent DOCUMENT_PAYABLE_ID together with DOCUMENT_PAYABLE_LINE_ID and the history date, while the surrogate key remains DOCUMENT_LINE_HISTORY_ID.

Common Use Cases and Queries

Typical use cases include audit reporting on how payment document lines changed, reconstruction of historical line amounts for reconciliation, and discrepancy analysis between current and prior states. A representative query retrieves the history of a specific payable document:

• Join IBY_DOCUMENT_LINES_H to IBY_DOCS_PAYABLE_ALL on DOCUMENT_PAYABLE_ID and filter by a payment document number.
• Correlate IBY_DOCUMENT_LINES_H.DOCUMENT_PAYABLE_LINE_ID with IBY_DOCUMENT_LINES.DOCUMENT_PAYABLE_LINE_ID to compare historical versus current values.
• Order by DOCUMENT_LINE_HISTORY_DATE descending to produce a change timeline for auditors.

Related Objects

The most significant related objects, derived from defined foreign key relationships, are:

• IBY_DOCS_PAYABLE_ALL — referenced via DOCUMENT_PAYABLE_ID; the parent payable document.
• IBY_DOCUMENT_LINES — referenced via DOCUMENT_PAYABLE_LINE_ID; the current line record.
• IBY_DOCUMENT_LINES_H self-reference via DOCUMENT_PAYABLE_HISTORY_ID, relating history records to one another.
• The parent history object associated with DOCUMENT_PAYABLE_HISTORY_ID, which anchors the document-level history chain.

Together these relationships allow the IBY payment engine and downstream reporting tools to trace a document line from its live state back through every recorded historical revision.