Search Results shipment_line_number

Overview

POFV_RECEIVING_TRANSACTIONS is an APPS-owned, VALID database view within the Purchasing (PO) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It is documented in ETRM as "Retrofitted," indicating its definition was carried forward across release boundaries to preserve a stable reporting contract. The view presents receiving transaction activity in a denormalized, lookup-translated form: rather than exposing raw codes, it embeds Oracle Applications Flexfield/lookup translation directives (the _LA: and _DF: prefixes) so that transaction type, destination type, inspection status, source document type, and similar attributes are rendered as user-facing descriptions. It joins receiving transactions to their full procurement context — shipment headers and lines, purchase order headers, lines, line locations, releases, requisitions, and distributions — making it a single-source reporting surface for the "receipt to PO" chain. Because it is a view rather than a table, it carries no storage of its own and reflects the current state of the underlying operational tables at query time.

Underlying Base Objects

The view is anchored on RCV_TRANSACTIONS (aliased RT), which supplies the core receiving transaction record, and RCV_SHIPMENT_HEADERS (SH) and RCV_SHIPMENT_LINES (SL), which supply shipment numbers and line numbers. Procurement context is drawn from PO_HEADERS_ALL (PH), PO_LINES_ALL (PL), PO_LINE_LOCATIONS_ALL (PS), PO_RELEASES_ALL (PR), PO_DISTRIBUTIONS_ALL (PD), PO_REQUISITION_HEADERS_ALL (RH), PO_REQUISITION_LINES_ALL (RL), and PO_REQ_DISTRIBUTIONS_ALL (RD). Supporting lookups and descriptive data come from MTL_UNITS_OF_MEASURE, MTL_TRANSACTION_REASONS, MTL_ITEM_LOCATIONS, MTL_SECONDARY_INVENTORIES, MTL_PARAMETERS, MTL_MATERIAL_TRANSACTIONS, FND_CURRENCIES_VL, GL_DAILY_CONVERSION_TYPES, PO_VENDORS, PO_VENDOR_SITES_ALL, HR_ALL_ORGANIZATION_UNITS, HR_LOCATIONS, PER_PEOPLE_F, RCV_ROUTING_HEADERS, and the WIP entities (WIP_ENTITIES, WIP_LINES, WIP_OPERATIONS, WIP_OPERATION_RESOURCES). Packages FND_GLOBAL, HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY are referenced, the last of which applies organization-level access control.

Key Columns

• TRANSACTION_ID / PARENT_TRANSACTION_ID — primary identifier and self-referencing parent linkage for receipt/delivery hierarchies.
• SHIPMENT_HEADER_ID, SH.SHIPMENT_NUM, SHIPMENT_LINE_ID, SL.LINE_NUM — shipment header and the shipment line number, the object most commonly located through the "shipment_line_number" search term.
• PO_HEADER_ID (PH.SEGMENT1), PO_LINE_ID (PL.LINE_NUM), PO_LINE_LOCATION_ID (PS.SHIPMENT_NUM), PO_RELEASE_ID (PR.RELEASE_NUM), PO_DISTRIBUTION_ID (PD.DISTRIBUTION_NUM) — the PO document chain down to distribution.
• REQUISITION_LINE_ID (RH.SEGMENT1, RL.LINE_NUM), REQ_DISTRIBUTION_ID (RD.DISTRIBUTION_NUM) — requisition context.
• TRANSACTION_DATE, QUANTITY, PRIMARY_QUANTITY, SOURCE_DOC_QUANTITY — receipt quantities and timing.
• UNIT_OF_MEASURE, PRIMARY_UNIT_OF_MEASURE, SOURCE_DOC_UNIT_OF_MEASURE — with UOM_CLASS and DESCRIPTION from MTL_UNITS_OF_MEASURE.
• TRANSACTION_TYPE, DESTINATION_TYPE_CODE, INSPECTION_STATUS_CODE, SOURCE_DOCUMENT_CODE, RECEIPT_EXCEPTION_FLAG — translated lookup values.
• EMPLOYEE_ID (RV.EMPLOYEE_NUMBER, RV.FULL_NAME), ORG_ID (OP.NAME) — receiving actor and operating unit.

Common Use Cases and Queries

The view supports receipt reconciliation, PO-to-receipt audit, and receiving performance reporting. A typical query filters by shipment line to trace activity for a specific receipt line:

• SELECT transaction_id, shipment_num, line_num, transaction_date, transaction_type, quantity, uom_class, segment1, line_num, shipment_num
• FROM apps.pofv_receiving_transactions
• WHERE shipment_line_id = :p_shipment_line_id
• ORDER BY transaction_date;

Because FND_GLOBAL and HR_SECURITY are referenced, results are naturally scoped by the caller's session and organization access. For aggregate reporting, grouping by segment1, transaction_type, and transaction_date yields receipt volumes by PO, while joining the view to MTL_MATERIAL_TRANSACTIONS on inv_transaction_id links receiving events to on-hand inventory movements. Analysts should expect DISTINCT semantics in the view definition and verify performance on wide date ranges, since the join graph spans roughly thirty base objects.