Results for “org_freight_vl”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

RCV_FTE_HEADERS_V is a read-only Oracle EBS view owned by the APPS schema and shipped as part of the Purchasing (PO) product family. Its documented description is "Header Lines for logistics," reflecting its purpose: to present shipment-header-level logistics attributes drawn from the receiving schema in a single, denormalized projection suitable for reporting and integration. The view is supplied primarily to support the Freight and Transportation Execution (FTE) functionality and logistics-facing screens that require shipment, carrier, freight term, weight, and timing information without exposing the full normalized structure of the receiving tables.

For the user who searched on "tare_weight," the object is directly relevant: the view surfaces the shipment header's TAR_WEIGHT column under the alias TARE_WEIGHT, together with TARE_WEIGHT_UOM_CODE. This makes RCV_FTE_HEADERS_V one of the few standard EBS views where tare (empty container) weight is exposed at the shipment header level, alongside gross and net weight.

Because the view is defined in the APPS schema and is a view rather than a table, it carries no independent storage and is always current with the underlying shipment data. It is valid in both 12.1.1 and 12.2.2; the documented metadata set is from ETRM 12.2.2.

Underlying Base Objects

The view text joins four objects, all resolved through the APPS synonym or view layer:

• RCV_SHIPMENT_HEADERS (SYNONYM) — aliased RSH; the driving table supplying shipment number, receipt number, bill of lading, vendor, packing slip, weights, packaging code, and ASN type.
• FND_LOOKUP_VALUES (SYNONYM) — aliased FLV; outer-joined on LOOKUP_TYPE = 'FREIGHT TERMS' and MEANING = RSH.FREIGHT_TERMS to derive FREIGHT_TERMS_CODE.
• ORG_FREIGHT_VL (VIEW) — aliased OFT; outer-joined on ORGANIZATION_ID and FREIGHT_CODE = RSH.FREIGHT_CARRIER_CODE to derive the carrier PARTY_ID.
• RCV_TRANSACTIONS (SYNONYM) — aliased RT through an inline view; a correlated subquery returns the single latest TRANSACTION_ID per SHIPMENT_HEADER_ID, yielding TRANSACTION_DATE and EMPLOYEE_ID as fallback values.

All lookups are outer joins (FLV and OFT carry the (+) operator, and the RT inline view is outer-joined on SHIPMENT_HEADER_ID). Consequently, every shipment header row is preserved even when freight terms, carrier, or transactions are missing.

Key Columns

• SHIPMENT_NUM, RECEIPT_NUM, SHIPMENT_HEADER_ID — identifiers for the shipment and its associated receipt.
• VENDOR_ID, VENDOR_SITE_ID — supplier and supplier site.
• EXPECTED_RECEIPT_DATE — NVL of the header expected receipt date and the latest transaction date.
• FREIGHT_TERMS_CODE, CARRIER_ID — decoded freight terms and carrier party from the lookup and freight views.
• BILL_OF_LADING, WAYBILL_AIRBILL_NUMBER, PACKING_SLIP — transport documents.
• GROSS_WEIGHT, NET_WEIGHT, TARE_WEIGHT — with matching UOM codes; TARE_WEIGHT maps to RSH.TAR_WEIGHT and represents container/packaging weight.
• NUM_OF_CONTAINERS, PACKAGING_CODE, ASN_TYPE, ORGANIZATION_ID, SHIP_TO_LOCATION_ID, SHIP_FROM_LOCATION_ID — logistics and organization context.
• EMPLOYEE_ID — employee from the latest receiving transaction.

Common Use Cases and Queries

Typical uses include logistics dashboards, tare/gross/net weight reconciliation for container shipments, carrier and freight-term reporting, and inbound ASN analysis. To isolate shipments where tare weight is captured:

• SELECT shipment_num, tare_weight, tare_weight_uom_code FROM apps.rcv_fte_headers_v WHERE tare_weight IS NOT NULL;
• Join to PO_HEADERS/PO_LINES via receipt and shipment identifiers for procurement reporting.
• Aggregate weights by carrier: SELECT carrier_id, SUM(gross_weight), SUM(net_weight), SUM(tare_weight) FROM apps.rcv_fte_headers_v GROUP BY carrier_id;
• Filter by SHIP_TO_ORG_ID to report by receiving organization.

Because the view is unpaginated and unrestricted, queries should always be bounded by date, organization, or shipment identifiers to control execution cost.