Results for “pofv_inbound_shipments”

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

Overview

POFV_INBOUND_SHIPMENTS is an APPS-owned database view within the Oracle E-Business Suite Purchasing (PO) module. It is classified as VALID and functions as a consolidated reporting and integration layer over inbound shipment data captured in the Receiving module. The view resolves a wide range of descriptive attributes — vendor names, organization codes, location codes, currency names, unit of measure descriptions, carrier descriptions, and buyer or employee details — that physically reside in disparate base tables. Rather than requiring report authors or integration developers to write and maintain numerous outer joins, the view exposes the shipment header facts in a denormalized, human-readable form suitable for concurrent programs, Oracle Reports, BI Publisher data templates, and interface extraction routines. It is commonly referenced where inbound ASN (Advance Shipment Notice) and receipt header information must be presented with full referential context. The object is available in both Oracle EBS 12.1.1 and 12.2.2, with the documented metadata reflecting the 12.2.2 ETRM repository.

Underlying Base Objects

The defining query draws from RCV_SHIPMENT_HEADERS as the driving table, joined by outer joins to a set of reference and lookup entities. The documented referenced base objects are: AP_TERMS, FND_CURRENCIES_VL, GL_DAILY_CONVERSION_TYPES, HR_ALL_ORGANIZATION_UNITS, HR_GENERAL (package), HR_LOCATIONS, HR_PERSON_NAME (package), HR_SECURITY (package), MTL_PARAMETERS, MTL_UNITS_OF_MEASURE, ORG_FREIGHT, PER_PEOPLE_F, PO_VENDORS, and RCV_SHIPMENT_HEADERS. In the physical query text, the joins resolve as follows: RCV_SHIPMENT_HEADERS is joined to GL_DAILY_CONVERSION_TYPES on CONVERSION_RATE_TYPE, to FND_CURRENCIES_VL on CURRENCY_CODE, to MTL_UNITS_OF_MEASURE twice (gross and net weight UOMs), to PO_VENDORS on VENDOR_ID, to HR_ALL_ORGANIZATION_UNITS and MTL_PARAMETERS on ORGANIZATION_ID, to HR_LOCATIONS on SHIP_TO_LOCATION_ID, to ORG_FREIGHT on both FREIGHT_CARRIER_CODE and ORGANIZATION_ID, to PER_PEOPLE_F on EMPLOYEE_ID, and to AP_TERMS on PAYMENT_TERMS_ID. All of these are implemented as outer joins, which preserves shipment rows even when a referenced lookup value is missing. The presence of Flexfield usage markers — specifically the descriptive flexfield reference to PO.RCV_SHIPMENT_HEADERS and the lookup codes reference to SHIPMENT SOURCE TYPE — indicates that the view participates in the Oracle Applications Flexfield and Lookup framework. The HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY packages are leveraged to resolve person and organization names while respecting HR security profiles.

Key Columns

The view exposes the shipment header identifier (SHIPMENT_HEADER_ID) and natural shipment number (SHIPMENT_NUM) as primary identification. Receipt and scheduling information includes RECEIPT_NUM, EXPECTED_RECEIPT_DATE, SHIPPED_DATE, and RECEIPT_SOURCE_CODE. Shipping logistics are represented by SHIPPED_DATE, ASN_TYPE, NUM_OF_CONTAINERS, BILL_OF_LADING, WAYBILL_AIRBILL_NUM, FREIGHT_AMOUNT, and FREIGHT_CARRIER_CODE. Commercial and invoice-related attributes include INVOICE_STATUS_CODE, INVOICE_AMOUNT, INVOICE_DATE, INVOICE_NUM, TAX_AMOUNT, and TAX_NAME. Weight metrics are captured via GROSS_WEIGHT, NET_WEIGHT, and their associated UOM codes. Descriptive resolved columns include VENDOR_NAME, ORGANIZATION_CODE, SO.NAME (organization unit), LOCATION_CODE, CU.NAME (currency name), RT.USER_CONVERSION_TYPE and RT.DESCRIPTION, UOM descriptions, FR.DESCRIPTION for the carrier, and RV.EMPLOYEE_NUMBER and RV.FULL_NAME for the responsible employee. Standard who-columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) are also present.

Common Use Cases and Queries

Typical uses include inbound shipment tracking reports, ASN reconciliation, freight analysis by carrier, and integration extracts feeding external logistics or customs systems. A representative query retrieving recent inbound shipments with vendor and location detail:

• SELECT shipment_num, receipt_num, expected_receipt_date, vendor_name, organization_code, location_code FROM pofv_inbound_shipments WHERE expected_receipt_date >= SYSDATE - 30.
• SELECT freight_carrier_code, description, SUM(freight_amount) FROM pofv_inbound_shipments GROUP BY freight_carrier_code, description.
• SELECT receipt_num, invoice_num, invoice_amount, currency_code FROM pofv_inbound_shipments WHERE invoice_status_code IS NOT NULL.

Because the joins to reference entities are outer joins, queries should anticipate nulls in descriptive columns when the corresponding lookup is unavailable. Filtering on the foreign key identifiers rather than the resolved descriptive values is recommended for performance.