Search Results document_line_num

Overview

The APPS.POS_LINES_V view is a Purchasing (PO) module reporting object that consolidates line-level receipt and shipment data sourced primarily from the Receiving Open Interface tables. Its name reflects its function: it exposes point-of-shipment (ASN) and receipt line attributes, drawing first from RCV_TRANSACTIONS_INTERFACE and, through a UNION, from RCV_SHIPMENT_LINES. This makes the view particularly relevant to inbound logistics, advance shipment notice (ASN) processing, and receipt correction reporting.

The view carries a documented status of VALID and is owned by the APPS schema. Because the user search term po_revision_num surfaces in its projection list, POS_LINES_V is frequently consulted when reporting on PO revision context for pending or historical receipt transactions — a value not directly adjacent to receipt lines in the base interface tables in a denormalized form. It serves as a convenient integration and reporting facade over receipt interface and shipment data rather than as a transactional table itself.

Underlying Base Objects

The documented base objects for POS_LINES_V span several schemas and include both tables and views:

• RCV_TRANSACTIONS_INTERFACE — the primary source of receipt line data (aliased RTI in the view text).
• RCV_HEADERS_INTERFACE — joined on HEADER_INTERFACE_ID to supply shipment/header context.
• RCV_SHIPMENT_HEADERS and RCV_SHIPMENT_LINES — used in the second branch of the UNION for ASN/shipment records.
• PO_HEADERS_ALL, PO_LINE_LOCATIONS_ALL, and PO_RELEASES_ALL — outer-joined to enrich lines with PO number, shipment number, ordered and received quantities, and release information.
• FND_TERRITORIES_VL — resolved via TERRITORY_SHORT_NAME for country-of-origin display.
• PO_VENDORS, PO_VENDOR_SITES_ALL, MTL_SYSTEM_ITEMS_KFV, PER_ALL_PEOPLE_F, HR_LOCATIONS_ALL_TL, HZ_LOCATIONS — supporting vendor, item, deliver-to person, and location descriptions.
• FND_GLOBAL and POS_CANCEL_ASN — packages referenced for session context and cancellation logic.

Because the view unions two distinct receipt sources, its row count can exceed either source alone; consumers should filter by PROCESSING_STATUS_CODE or TRANSACTION_STATUS_CODE to scope to a single logical stream.

Key Columns

• PO_REVISION_NUM — the PO revision associated with the receipt line; the column most relevant to purchasing revision audits.
• PO_NUMBER — a DECODE that renders the segment1 value, appending release number where a release exists.
• PO_HEADER_ID, PO_LINE_ID, PO_LINE_LOCATION_ID — keys linking back to purchasing documents.
• QUANTITY, UNIT_OF_MEASURE, UOM_CODE, PO_UNIT_PRICE — receipt quantity and pricing context.
• QUANTITY_ORDERED, QUANTITY_RECEIVED — sourced from PO_LINE_LOCATIONS_ALL for receipt-to-order reconciliation.
• VENDOR_ID, VENDOR_NAME, VENDOR_SITE_ID, VENDOR_ITEM_NUM — supplier identification and cross-reference.
• DELIVER_TO_LOCATION_CODE, DELIVER_TO_PERSON_NAME, SHIP_TO_LOCATION_CODE — destination routing information.
• PROCESSING_STATUS_CODE, TRANSACTION_STATUS_CODE — interface processing state, critical for error triage.
• COUNTRY_OF_ORIGIN_CODE, COUNTRY_OF_ORIGIN_DISPLAYED — origin territory code and its display value.

Common Use Cases and Queries

Typical scenarios include reviewing in-flight receipt interface records before processing, auditing PO revision activity against receipts, and validating ASN details. A representative query filtering on revision values is:

• SELECT po_number, po_revision_num, quantity, processing_status_code FROM apps.pos_lines_v WHERE po_revision_num IS NOT NULL;
• SELECT po_number, quantity_ordered, quantity_received FROM apps.pos_lines_v WHERE po_line_location_id = :location_id;
• SELECT po_number, vendor_name, country_of_origin_displayed FROM apps.pos_lines_v WHERE processing_status_code = 'ERROR';

The view is best used for reporting and interface monitoring, while direct DML should be performed against the underlying RCV and PO tables.