Search Results line_gross_amount




Overview
Explore in AI Chat

Overview

APPS.AR_DOCUMENT_LINES_V is an Oracle E-Business Suite internal view owned by the APPS schema, with FND design data registered as AR.AR_DOCUMENT_LINES_V. It exposes line-level detail for Oracle Receivables documents, including purchasing references, line types, quantities, pricing, tax attributes and descriptive flexfield columns. In EBS 12.1.1 and 12.2.2 the object is documented as VALID and is flagged as Oracle Internal Use Only: Oracle Corporation does not support access to applications data through this object except from standard Oracle Applications programs. Consequently, the view is best understood as a reporting and integration surface used internally by Receivables code paths rather than a publicly supported API. The column most commonly referenced by developers and analysts is LINE_GROSS_AMOUNT, the gross monetary value of a document line prior to or inclusive of adjustments depending on the source line's configuration.

Underlying Base Objects

The documented dependency list for this view comprises four objects:

  • AR_PAYMENT_SCHEDULES (SYNONYM) — supplies transaction, due-date and balance context for the document to which the line belongs.
  • RA_CUSTOMER_TRX (SYNONYM) — the Receivables transaction header, providing document-level attributes such as transaction number, currency and customer.
  • RA_CUSTOMER_TRX_LINES (SYNONYM) — the principal line table, contributing line number, line type, description, unit price, quantity, unit of measure and the inventory item identifier.
  • ARP_TRX_LINE_UTIL (PACKAGE) — a Receivables utility package used internally to derive or aggregate line values, including gross, extended, discount and tax amounts.

Because the view is defined over these objects rather than duplicating data, any change to a transaction line in RA_CUSTOMER_TRX_LINES is immediately reflected when the view is queried. The package dependency indicates that portions of the projection are computed rather than selected directly, which is a key reason Oracle restricts supported access to internal programs.

Key Columns

Common Use Cases and Queries

Typical scenarios include line-level revenue reporting, gross amount reconciliation against the transaction header, and currency-specific analysis. A representative query is:

  • SELECT doc_unique_ref, line_number, line_type, line_gross_amount, invoice_currency_code FROM apps.ar_document_lines_v WHERE doc_unique_ref = :p_doc_ref ORDER BY line_number;
  • Summation by document: SELECT doc_unique_ref, SUM(line_gross_amount) FROM apps.ar_document_lines_v GROUP BY doc_unique_ref;

Because the view is designated Oracle Internal Use Only, production code should prefer supported Receivables APIs and public views. Where the view is queried for diagnostics or reporting, access should be read-only and constrained by ORG_ID-aware security and standard Receivables responsibilities. In 12.2.2 the structure and dependencies remain consistent with 12.1.1, so queries written for one release generally execute unchanged in the other, subject to the online patching editioning model.