Search Results po_shipment_num

Overview

RCV_FTE_LINES_V is a shipped, APPS-owned database view in Oracle E-Business Suite Release 12.1.1 and 12.2.2, registered under the PO - Purchasing product family. Its stated purpose is to expose "Transaction Lines for logistics," meaning it consolidates receiving and inbound shipment line detail with the associated purchasing document context into a single queryable structure. The view is a read-only reporting and integration object: it does not perform validation or processing of its own, but it presents shipment lines joined to their corresponding purchase order headers, lines, and line locations.

The name prefix RCV_ reflects its origin in the Receiving module (RCV is the standard EBS schema object prefix for receiving), while the FTE designation and the logistics description indicate a supply-chain oriented presentation layer. It is typically consumed by logistics dashboards, ASN (Advance Shipment Notice) tracking reports, inbound shipment audit queries, and custom interfaces that need to reconcile what was shipped against what was received. Because it draws only from standard Purchasing and Receiving tables, it is also a common substitute for writing ad-hoc joins across RCV_SHIPMENT_LINES, PO_HEADERS_ALL, and PO_LINE_LOCATIONS_ALL directly.

Underlying Base Objects

The ETRM 12.2.2 metadata documents the following referenced base objects, all resolved through APPS synonyms: RCV_SHIPMENT_LINES, RCV_SHIPMENT_HEADERS, PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_LINE_TYPES_B, and MTL_UNITS_OF_MEASURE_VL (a view).

The FROM clause confirms this composition. RCV_SHIPMENT_LINES is the driving table. It joins to PO_HEADERS_ALL via PO_HEADER_ID, to PO_LINE_LOCATIONS_ALL via PO_LINE_LOCATION_ID, and to PO_LINES_ALL via PO_LINE_ID. The shipment header relationship is established through SHIPMENT_HEADER_ID linking to RCV_SHIPMENT_HEADERS. The unit-of-measure aliases MUL and MUL1 are outer-joined ((+)) to MTL_UNITS_OF_MEASURE_VL, so a missing UOM definition will not suppress the shipment line. PO_LINE_TYPES_B is joined via LINE_TYPE_ID to restrict results to quantity-based lines, and the header is filtered to STANDARD and BLANKET type lookup codes with a non-null SHIPPING_CONTROL.

Key Columns

• SHIPMENT_HEADER_ID / SHIPMENT_LINE_ID — Primary identifying keys for the receiving shipment header and its lines.
• PO_HEADER_ID, PO_LINE_ID, PO_LINE_LOCATION_ID, PO_RELEASE_ID — Foreign keys back to the purchasing document hierarchy, including blanket release linkage.
• ITEM_ID, ITEM_REVISION, ITEM_DESCRIPTION — Inventory item identity and revision detail pulled from the shipment line.
• QUANTITY_SHIPPED, QUANTITY_RECEIVED, SECONDARY_QUANTITY_SHIPPED, SECONDARY_QUANTITY_RECEIVED — Primary and secondary unit quantities used for receipt reconciliation.
• SHIP_TO_LOCATION_ID (multiple aliases), TO_ORGANIZATION_ID — Destination location and organization for the receipt.
• PO_SEGMENT1 — The purchase order number (SEGMENT1 from PO_HEADERS_ALL).
• PO_SHIPMENT_NUM — The shipment number from PO_LINE_LOCATIONS_ALL.SHIPMENT_NUM. This is the column users typically locate when searching for "po_shipment_num," and it is exposed here under the name PO_SHIPMENT_NUM.
• PO_LINE_NUMBER — The purchase order line number from PO_LINES_ALL.LINE_NUM.
• ASN_LINE_FLAG, ASN_LPN_ID — Flags and identifiers indicating whether the line arrived via ASN and its associated license plate number.
• TRUCK_NUM, CONTAINER_NUM, PACKING_SLIP — Logistics-specific shipment detail.
• UOM_CODE / UNIT_OF_MEASURE — Unit of measure derived through the two MTL_UNITS_OF_MEASURE_VL aliases.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN sourced from the shipment line.

Common Use Cases and Queries

The view is most often queried to track inbound logistics lines by PO shipment number, by item, or by destination location. A typical pattern is to filter on PO_SHIPMENT_NUM or PO_SEGMENT1 to reconcile expected against received quantities.

• Shipment tracking by PO shipment number: SELECT po_segment1, po_shipment_num, po_line_number, item_description, quantity_shipped, quantity_received FROM rcv_fte_lines_v WHERE po_shipment_num = :shipment_num;
• Outstanding receipt analysis: SELECT po_segment1, po_shipment_num, item_description, quantity_shipped - quantity_received variance FROM rcv_fte_lines_v WHERE quantity_shipped > quantity_received;
• Logistics inbound status by destination: SELECT ship_to_location_id, truck_num, container_num, packing_slip, quantity_shipped FROM rcv_fte_lines_v WHERE ship_to_location_id = :loc_id;
• ASN-originated lines: SELECT po_segment1, po_shipment_num, asn_lpn_id FROM rcv_fte_lines_v WHERE asn_line_flag = 'Y';

Because the view already applies the STANDARD/BLANKET header filter and restricts to QUANTITY line types, queries against it inherently exclude non-quantity purchasing lines and non-standard document types.