Search Results iby_document_lines




Overview
Explore in AI Chat

Overview

The IBY_DOCUMENT_LINES table is a core data object within the Oracle Payments (IBY) module of Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It functions as a detailed line-level repository for documents payable processed through the payment engine. While the primary header information for a payable document is stored in IBY_DOCS_PAYABLE_ALL, this table holds the individual line items that constitute those documents. Its primary role is to support the granular tracking, validation, and settlement of payment obligations, enabling complex payment scenarios where individual invoice lines may have distinct payment terms, accounting distributions, or supplier information. The integrity of its data is critical for accurate payment execution, reconciliation, and financial reporting.

Key Information Stored

The table's structure is designed to link line details to their parent payable document and store line-specific attributes. The metadata explicitly identifies the primary key as DOCUMENT_PAYABLE_LINE_ID, a unique system-generated identifier for each line record. A critical foreign key relationship is defined via the DOCUMENT_PAYABLE_ID column, which links each line to its corresponding header record in the IBY_DOCS_PAYABLE_ALL table. While the provided excerpt does not list all columns, typical columns in this table would include amounts (line, tax, discount), accounting distribution codes, payment priority flags, and references to the original source transaction line identifiers (e.g., from Payables or Purchasing). This structure allows the Payments module to aggregate and process lines at the most granular level required by business rules.

Common Use Cases and Queries

This table is central to queries and reports that require analysis below the document header level. A common use case is investigating payment validation failures or holds that are specific to certain line items within an invoice batch. Another is reconciling payment amounts by drilling down from a payment batch to individual invoice lines. A fundamental query pattern involves joining to the document header to retrieve a complete payable view. For example, to find all lines for a specific document payable identifier, one would use:

  • SELECT dline.* FROM iby_document_lines dline WHERE dline.document_payable_id = :p_doc_payable_id;

Reporting on total payable amounts by general ledger account or cost center also necessitates querying this table to access the line-level accounting distributions. Troubleshooting often involves tracing a line using its unique DOCUMENT_PAYABLE_LINE_ID or by joining back to source transaction tables via the embedded source line reference.

Related Objects

The most significant related object, as defined by the documented foreign key, is the IBY_DOCS_PAYABLE_ALL table. This is the parent table, and every record in IBY_DOCUMENT_LINES must correspond to a single record in IBY_DOCS_PAYABLE_ALL via the DOCUMENT_PAYABLE_ID foreign key. The table is also intrinsically linked to various Payment Process Request (PPR) and payment instruction entities within the IBY schema, though these relationships are often mediated through the document header. Key APIs, such as those in the IBY_PAYMENT_ADAPTER package, populate and interact with this table during the creation and validation of payment instructions. For reporting, several Payment Manager and reconciliation views may reference or aggregate data from this underlying table.