Results for “fv_requisition_master_v”

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

Overview

FV_REQUISITION_MASTER_V is a view owned by the APPS schema and classified under the Oracle Federal Financials (FV) product family. Its documented purpose is to retrieve requisition details for use in the "Document Cross-Reference" form, which allows users to trace the relationship between a purchase requisition and its downstream purchasing documents. In Oracle EBS 12.1.1 and 12.2.2, this view serves as a convenience layer over the core Purchasing requisition and purchasing tables, presenting approved requisition header, line, shipment, and purchase order attributes in a single denormalized result set. Because it is a view rather than a table, it stores no data of its own; it derives all values at runtime from its underlying base objects, which means query results always reflect the current transactional state of Purchasing. This makes it well suited to reporting, cross-reference inquiry, and lightweight integration where a flattened requisition-to-order picture is required without navigating multiple base tables directly. A key behavioral constraint documented in the view text is the filter PRH.AUTHORIZATION_STATUS = 'APPROVED', so only approved requisitions are returned through this interface. When a user searches for requisition_num, this view is the relevant source, since it exposes the requisition number through the REQUISITION_NUM column.

Underlying Base Objects

The view is defined over four documented base objects, all referenced through APPS synonyms: PO_REQUISITION_HEADERS, PO_REQUISITION_LINES_ALL, PO_LINE_LOCATIONS_ALL, and PO_HEADERS_ALL. The joins are structured as follows: the header table is joined to the lines table on REQUISITION_HEADER_ID, the lines table is outer-joined to line locations on LINE_LOCATION_ID, and line locations are outer-joined to purchase order headers on PO_HEADER_ID. The outer joins on the shipment and order tables are significant: they allow approved requisition lines that have not yet been placed on a purchase order, or that have no shipment record, to still appear in the result set. In practice this means PO_HEADER_ID, VENDOR_ID, and VENDOR_SITE_ID may be null for requisitions that have not progressed to the ordering stage, whereas header and line attributes remain populated.

Key Columns

• REQUISITION_NUM — the requisition number (derived from PRH.SEGMENT1), the primary business identifier users search on.
• REQUISITION_HEADER_ID, REQUISITION_LINE_ID, LINE_LOCATION_ID — surrogate keys for the header, line, and shipment respectively.
• ORG_ID — the operating unit, supporting multi-org reporting.
• AUTHORIZATION_STATUS — approval state; restricted to APPROVED by the view definition.
• PREPARER_ID (mapped to REQUESTER_ID) — the individual who prepared the requisition.
• LINE_NUM, ITEM_ID, CATEGORY_ID, ITEM_DESCRIPTION, QUANTITY, UNIT_MEAS_LOOKUP_CODE, UNIT_PRICE — line-level item and pricing detail.
• NEED_BY_DATE, CREATION_DATE, REQUISITION_DATE — key dates for aging and scheduling analysis.
• PO_HEADER_ID, VENDOR_ID, VENDOR_SITE_ID, SUGGESTED_VENDOR_NAME, SUGGESTED_VENDOR_LOCATION — downstream purchasing and sourcing information.

Common Use Cases and Queries

Typical uses include document cross-reference inquiry, requisition-to-PO traceability reporting, and Federal Financials audit extracts. The following sample retrieves approved requisitions by number:

• SELECT requisition_num, requisition_date, authorization_status, po_header_id, vendor_id FROM fv_requisition_master_v WHERE requisition_num = :p_req_num;
• SELECT requisition_num, line_num, item_description, quantity, unit_price FROM fv_requisition_master_v WHERE org_id = :p_org AND need_by_date < SYSDATE;
• SELECT r.requisition_num, r.line_num, r.suggested_vendor_name, p.segment1 po_number FROM fv_requisition_master_v r, po_headers_all p WHERE r.po_header_id = p.po_header_id(+);

Because the view already restricts results to approved requisitions and outer-joins shipment and order data, it is generally preferable to querying the base Purchasing tables directly for cross-reference and audit purposes.