Search Results fv_po_master_v




Overview
Explore in AI Chat

Overview

FV_PO_MASTER_V is a database view owned by the APPS schema in Oracle E-Business Suite, defined within the Federal Financials (FV) product family. As documented in ETRM 12.2.2, the view is used to retrieve purchase order details for display within a form, consolidating header, line, shipment, and release information into a single flat structure. Because Federal Financials is built upon the standard Oracle Purchasing tables, this view serves as a simplified read-access layer over the core purchasing data model, presenting the joined results of purchase order headers, lines, line locations, and releases without requiring the calling form or report to reconstruct those relationships.

Underlying Base Objects

The view is defined over the following documented base objects: PO_HEADERS, PO_LINES, PO_LINE_LOCATIONS, and PO_RELEASES (all synonyms), together with the PO_HEADERS_SV3 package, which is invoked through the GET_PO_STATUS function. The join conditions map the header to its lines via PO_HEADER_ID, attach line locations to lines through PO_LINE_ID using an outer join, and associate releases to line locations through PO_RELEASE_ID using an outer join. The outer joins allow lines and shipments to be returned even when release information does not exist. Headers whose TYPE_LOOKUP_CODE is 'CONTRACT' are excluded, so the view reflects standard purchase orders and releases rather than contracts.

Key Columns

The view exposes identifiers and descriptive attributes across the purchasing hierarchy. Key columns include ORG_ID, PO_HEADER_ID, PO_LINE_ID, LINE_LOCATION_ID, PO_RELEASE_ID, VENDOR_ID, VENDOR_SITE_ID, and AGENT_ID, which support joins to operational units, buyers, and supplier records. Descriptive fields include SEGMENT1 (the purchase order number), RELEASE_NUM, LINE_NUM, and SHIPMENT_NUM. Quantity and pricing columns comprise QUANTITY, QUANTITY_RECEIVED, QUANTITY_BILLED, UNIT_PRICE, and UNIT_MEAS_LOOKUP_CODE (aliased as UOM). Item-level attributes include ITEM_ID, CATEGORY_ID, and ITEM_DESCRIPTION. Status-related columns include the derived APPROVED_FLAG returned from PO_HEADERS_SV3.GET_PO_STATUS and CANCEL_FLAG from the line location. Notably, the column PO_DATE corresponds to the underlying CREATION_DATE of the purchase order header, which is the field most relevant to the user's search term "po_date."

Common Use Cases and Queries

The view is commonly used in Federal Financials forms and concurrent programs that require a consolidated view of purchase order activity, and it can be queried directly for reconciliation and reporting. A frequent scenario involves filtering purchase orders by date, status, or supplier. For example:

  • Retrieve purchase orders created within a date range: SELECT PO_NUM, PO_DATE, VENDOR_ID, QUANTITY, UNIT_PRICE FROM APPS.FV_PO_MASTER_V WHERE PO_DATE BETWEEN :START_DATE AND :END_DATE;
  • Identify orders by status and buyer: SELECT PO_NUM, PO_DATE, AGENT_ID, APPROVED_FLAG FROM APPS.FV_PO_MASTER_V WHERE APPROVED_FLAG = 'APPROVED' AND AGENT_ID = :BUYER_ID;
  • Compare ordered, received, and billed quantities for a line: SELECT PO_NUM, LINE_NUM, QUANTITY, QUANTITY_RECEIVED, QUANTITY_BILLED FROM APPS.FV_PO_MASTER_V WHERE PO_HEADER_ID = :HEADER_ID;
  • Join to supplier and item master data: SELECT V.PO_NUM, V.PO_DATE, V.ITEM_DESCRIPTION, V.UOM FROM APPS.FV_PO_MASTER_V V, APPS.PO_VENDORS PV WHERE V.VENDOR_ID = PV.VENDOR_ID;

Because the view draws on transactional purchasing tables, query performance benefits from filtering on ORG_ID and PO_DATE and from restricting results using indexed identifiers such as PO_HEADER_ID or VENDOR_ID.