Search Results reqs_in_pool_flag




Overview
Explore in AI Chat

Overview

PO_REQUISITION_LINES_ALL_MRC_V is a Purchasing (PO) module view in Oracle EBS 12.1.1 and 12.2.2 that exposes requisition line information in the reporting (MRC) currency context. The "_MRC_V" suffix identifies it as a Multiple Reporting Currencies view, meaning its purpose is to present requisition line amounts converted from the ledger's functional currency into a reporting currency using the standard currency conversion packages. This view is part of the set of MRC shadow views Oracle provides so that multi-currency reporting and subledger drill-down can be performed without triggering a manual re-derivation of exchange rates.

The ETRM metadata lists the object as "Retrofitted" and states "Not implemented in this database." This indicates the view is a legacy MRC-era artifact whose behavior is emulated (retrofitted) through the MRC currency packages rather than through physically maintained MRC shadow tables in the current 12.2.2 installation. Where MRC functionality is not enabled, the view may exist in the data dictionary but return no rows or simply pivot functional-currency values.

Underlying Base Objects

No base objects are formally documented in the ETRM metadata, but the view text shows it selects directly from the PO_REQUISITION_LINES_ALL table (aliased PO), with currency conversion applied on top. The critical dependency is the PO_MC_CURRENCY_PKG package, invoked two ways:

The view is the line-level companion to the requisition header MRC views and mirrors PO_REQUISITION_LINES_ALL in structure, layering converted amount expressions on top of the base table's columns.

Key Columns

Common Use Cases and Queries

The view is typically used for multi-currency requisition reporting, subledger reconciliation to the general ledger, and drill-down from MRC reports to requisition detail. A representative query retrieving reporting-currency unit price and amount follows:

SELECT requisition_header_id,
       line_num,
       currency_code,
       currency_unit_price,
       request
FROM   po_requisition_lines_all_mrc_v
WHERE  org_id = :p_org_id
AND    nvl(cancel_flag,'N') = 'N'
ORDER BY requisition_header_id, line_num;

Because conversions depend on NVL(RATE_DATE, SYSDATE), results can vary if RATE_DATE is null; queries should therefore constrain by RATE_DATE or ORG_ID where deterministic results are required. For requisitions with no document currency (CURRENCY_CODE null), the DECODE expressions return NULL for the converted price, so consumers should handle these as functional-currency-only records. Finally, since the object is documented as not implemented in a standard 12.2.2 database, availability should be verified with ALL_VIEWS before relying on it in production reports.