Search Results po_segment1

Overview

APPS.RCV_FTE_LINES_V is an Oracle E-Business Suite internal view registered under the FND design data namespace PO.RCV_FTE_LINES_V. It is a View Type "Internal" object, and Oracle documents it with an explicit restriction: it is provided for Oracle Internal Use Only and is not supported for direct access by customer code except from standard Oracle Applications programs. The "FTE" prefix reflects its origin in the Receiving "First Time Event" / shipment-tracking processing performed by the Receiving Open Interface, Confirm Receipts, and the missing-ASN item processor.

Functionally, the view presents a flattened, cross-referenced picture of inbound shipment lines combined with their corresponding purchasing document context. Each row represents a shipment line, with denormalized attributes for the shipment header, item, purchase order, purchase order line, and purchase order shipment, plus shipped and received quantities in both primary and secondary units of measure. It therefore serves as a convenience read layer over the RCV_SHIPMENT_HEADERS/RCV_SHIPMENT_LINES transactional tables joined to the PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, and PO_LINE_TYPES_B purchasing tables, with unit of measure conversion information sourced from MTL_UNITS_OF_MEASURE_VL.

Underlying Base Objects

The documented base objects referenced by the view are:

• RCV_SHIPMENT_HEADERS and RCV_SHIPMENT_LINES — the receiving shipment header and line tables that supply shipment identifiers, truck, container, packing slip, and shipped/received quantities.
• PO_HEADERS_ALL — supplies purchase order header information including PO_HEADER_ID and the document number exposed as PO_SEGMENT1.
• PO_LINES_ALL — supplies PO_LINE_ID and PO_LINE_NUMBER for the ordered item line.
• PO_LINE_LOCATIONS_ALL — supplies PO_LINE_LOCATION_ID, ship-to location, and PO_SHIPMENT_NUM.
• PO_LINE_TYPES_B — supplies the purchasing line type context used to classify the document line.
• MTL_UNITS_OF_MEASURE_VL — supplies unit of measure definitions used when reporting primary and secondary quantity values.

The joins correlate an RCV shipment line back to its originating PO shipment (line location), which in turn resolves to the PO line and PO header. This makes the view usable wherever a shipment must be traced to the purchase order that authorized it.

Key Columns

• SHIPMENT_HEADER_ID and SHIPMENT_LINE_ID — unique identifiers for the shipment header and line; the primary correlation keys back to RCV.
• ASN_LINE_FLAG — indicates whether the item arrived on an Advance Shipment Notice; used by the missing-ASN items processor to determine whether shipped items were actually received.
• PO_HEADER_ID, PO_LINE_ID, PO_LINE_LOCATION_ID — purchasing document keys.
• PO_SEGMENT1 — the purchase order document number, exposed as a VARCHAR2(20). This is the attribute commonly searched for when analysts locate shipments by PO number rather than by internal ID.
• PO_SHIPMENT_NUM, PO_LINE_NUMBER — the shipment and line numbers within the purchasing document.
• ITEM_ID, ITEM_REVISION, ITEM_DESCRIPTION — item identification and descriptive attributes.
• QUANTITY_SHIPPED, QUANTITY_RECEIVED, plus SECONDARY_QUANTITY_SHIPPED and SECONDARY_QUANTITY_RECEIVED — quantities in primary and secondary units of measure.
• SHIP_TO_LOCATION_ID and PO_SHIP_TO_LOCATION_ID — ship-to destination identifiers from the shipment and purchasing sides respectively.
• TRUCK_NUM, CONTAINER_NUM, PACKING_SLIP, LINE_NUM, SHIPMENT_UNIT_PRICE — logistics and valuation attributes.
• LAST_UPDATE_DATE, LAST_UPDATED_BY and the remaining WHO columns — standard audit information.

Common Use Cases and Queries

The primary practical use of this view is diagnostic: locating the shipment lines associated with a purchase order number (PO_SEGMENT1) and comparing shipped against received quantities to identify short receipts, unreceived ASN lines, or lines awaiting the missing-ASN item processor.

SELECT shipment_header_id,
       shipment_line_id,
       po_segment1,
       po_line_number,
       po_shipment_num,
       item_description,
       quantity_shipped,
       quantity_received,
       asn_line_flag
FROM   apps.rcv_fte_lines_v
WHERE  po_segment1 = :p_po_number;

A second common pattern reconciles quantities in the secondary unit of measure, where the purchasing agreement is denominated differently from the receiving transaction:

SELECT po_segment1,
       item_id,
       quantity_shipped - quantity_received AS primary_variance,
       secondary_quantity_shipped - secondary_quantity_received AS secondary_variance
FROM   apps.rcv_fte_lines_v
WHERE  po_header_id = :p_po_header_id;

Because Oracle classifies this object as internal and unsupported for direct customer access, any query should be treated as diagnostic or investigative rather than as the basis of a production interface. Supported reporting should use the Receiving and Purchasing public APIs, open interfaces, or Oracle-provided extracts; direct reads risk breakage across patch levels, including between 12.1.1 and 12.2.2.