Results for “iby_document_lines”

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

Overview

IBY_DOCUMENT_LINES is a table owned by the IBY schema within the Oracle Payments (IBY) product module of Oracle E-Business Suite. It stores Oracle Payments' representation of individual line items belonging to documents payable, such as invoice lines associated with an Oracle Payables invoice. The table captures the line-level detail that Payment Instruction formatting and payment processing consume when a document payable is selected for a payment run. Per the documented description, this information is passed according to the payment format but is not used to affect funds disbursement in the same manner as header-level document information.

Within the Payments data model, IBY_DOCUMENT_LINES behaves as a child of IBY_DOCS_PAYABLE_ALL, the header-level table for documents payable. From a Data Vault modeling perspective, the mined foreign-key structure classifies this table as satellite-leaning: it carries descriptive attributes tied to a parent business key rather than acting as an independent hub or a pure associative link. In EBS 12.1.1 and 12.2.2 the physical structure is identical, with 18 documented columns in the 12.2.2 ETRM schema.

Key Information Stored

The primary key is IBY_DOCUMENT_LINES_PK, defined on the surrogate column DOCUMENT_PAYABLE_LINE_ID. A unique index, IBY_DOCUMENT_LINES_U1, also exists on DOCUMENT_PAYABLE_LINE_ID, and in practice this surrogate identifier often serves as the business-key candidate for integration and interface loads.

• DOCUMENT_PAYABLE_LINE_ID — Surrogate primary key uniquely identifying each line record.
• DOCUMENT_PAYABLE_ID — Foreign key to IBY_DOCS_PAYABLE_ALL; links the line to its parent document payable header.
• CALLING_APP_DOCUMENT_LINE_CODE — Identifier of the source application's line, such as an invoice line identifier from Oracle Payables.
• PO_NUMBER — Purchase order number associated with the line, used for reconciliation and reporting.
• LINE_NUMBER — Sequential line number within the document payable.
• LINE_TYPE — Classifies the nature of the line (for example, item, tax, or freight).
• LINE_NAME — Descriptive name of the line.
• LINE_AMOUNT — Monetary amount attributed to the line.
• DESCRIPTION — Free-text description of the line.
• UNIT_PRICE — Price per unit for the line item.
• QUANTITY — Quantity associated with the line.
• UNIT_OF_MEASURE — Unit of measure for the quantity.
• OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Applications framework.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns.

Common Use Cases and Queries

Typical usage centers on reporting and reconciliation of payment detail. Analysts join IBY_DOCUMENT_LINES to IBY_DOCS_PAYABLE_ALL to retrieve header context such as payment status and amount for each line.

• Listing all lines for a given document payable: SELECT * FROM iby_document_lines WHERE document_payable_id = :id;
• Summing line amounts against header totals to detect variance between IBY_DOCS_PAYABLE_ALL.AMOUNT and the sum of LINE_AMOUNT.
• Joining to Payables invoice lines via CALLING_APP_DOCUMENT_LINE_CODE to trace payment lines back to source AP_INVOICE_LINES records.
• Auditing PO_NUMBER-level spend by aggregating LINE_AMOUNT across payment runs.
• Reviewing the IBY_DOCUMENT_LINES_H history table to track changes to line records over time.

Related Objects

• IBY_DOCS_PAYABLE_ALL — Parent header table; joined on IBY_DOCUMENT_LINES.DOCUMENT_PAYABLE_ID = IBY_DOCS_PAYABLE_ALL.DOCUMENT_PAYABLE_ID.
• IBY_DOCUMENT_LINES_H — History/audit table referencing DOCUMENT_PAYABLE_LINE_ID, maintaining prior versions of line rows.
• IBY_DOCUMENT_LINES_PK / IBY_DOCUMENT_LINES_U1 — Primary key constraint and unique index on DOCUMENT_PAYABLE_LINE_ID.
• IBY_PAYMENTS / IBY_PAYMENT_INSTRUCTIONS — Formatting and instruction objects that consume line data when producing payment output.
• AP_INVOICE_LINES_ALL — Source invoice lines referenced through CALLING_APP_DOCUMENT_LINE_CODE.
• Oracle Payments public APIs that build documents payable typically populate this table as part of the document build process.