Search Results revised_date




Overview
Explore in AI Chat

Overview

The PO_HEADERS_MRC_V view belongs to the Oracle Purchasing (PO) module and exposes purchasing document header information in a multiple reporting currency (MRC) context. In Oracle EBS 12.1.1 and 12.2.2, MRC views allow transactions and documents originally entered in a functional currency to be reported in one or more additional reporting currencies. This view extends the standard purchasing document header with the conversion attributes required to express the document amounts in a reporting currency, specifically RATE_TYPE, RATE_DATE and RATE drawn from the currency conversion relationship.

The ETRM documentation classifies this object with the description "Retrofitted" and states that the corresponding implementation is not implemented in this database. This is significant: within the ETRM reference framework, MRC objects are frequently retrofitted rather than natively deployed, meaning the view may not exist as a physical database object in every environment and should be verified against the target instance before being referenced in custom code, reports or integrations.

Because it surfaces purchasing header data alongside reporting currency conversion data, the view is intended for cross-currency reporting, period-end analysis and integration scenarios where purchasing commitments and agreements must be presented in a currency other than the operating currency.

Underlying Base Objects

The documented metadata lists no explicit base objects for this view. However, the column list confirms that the view's primary source is the purchasing document header entity (PO_HEADERS_ALL), aliased as PRIMARY in the view text, which supplies all document attributes such as PO_HEADER_ID, SEGMENT1, VENDOR_ID, CURRENCY_CODE, AUTHORIZATION_STATUS, APPROVED_FLAG and the descriptive flexfield ATTRIBUTE1 through ATTRIBUTE15. The MRC conversion attributes are derived from a currency conversion source (aliased MC), which in standard MRC architecture is the reporting currency counterpart of the header, typically PO_HEADERS in a reporting currency set. The join between the two is established on PO_HEADER_ID.

The extensive column set — including GLOBAL_ATTRIBUTE_CATEGORY and GLOBAL_ATTRIBUTE1 onward — mirrors the full base header structure, ensuring that MRC reporting does not lose any descriptive or operational attribute present in the transactional record. The referenced base objects are therefore the purchasing header table and its reporting currency extension, though the ETRM metadata does not document them explicitly.

Key Columns

  • PO_HEADER_ID — Primary identifier linking the reporting currency row to the purchasing document header.
  • RATE_TYPE, RATE_DATE, RATE — The currency conversion attributes used to translate amounts from functional to reporting currency.
  • SEGMENT1 — The document number (purchase order, blanket agreement or contract number).
  • VENDOR_ID, VENDOR_SITE_ID, VENDOR_CONTACT_ID — Supplier identification for the document.
  • CURRENCY_CODE — The transaction currency of the document.
  • AUTHORIZATION_STATUS and NOTE_TO_AUTHORIZER — The approval workflow state and the note directed to the authorizer, the latter directly relevant to the user's search term.
  • APPROVED_FLAG, APPROVED_DATE, CANCEL_FLAG, FROZEN_FLAG — Document status and control indicators.
  • BLANKET_TOTAL_AMOUNT, AMOUNT_LIMIT, MIN_RELEASE_AMOUNT — Agreement and release financial thresholds.
  • ORG_ID — Operating unit identifier supporting multi-org reporting.
  • TYPE_LOOKUP_CODE — Distinguishes document types such as standard purchase orders, blanket agreements and contracts.

Common Use Cases and Queries

The primary use case is reporting purchasing documents in a reporting currency. A typical query retrieves approval status and the authorizer note alongside the conversion rate, which is directly relevant to the searched term:

SELECT po_header_id,
       segment1,
       authorization_status,
       note_to_authorizer,
       rate_type,
       rate_date,
       rate
  FROM po_headers_mrc_v
 WHERE approved_flag = 'Y'
   AND org_id = :p_org_id;

Another common scenario reconciles functional and reporting currency values for period-end close, or feeds downstream analytics where documents must be stated in a currency other than the operating currency. The view can also support approval audits by exposing AUTHORIZATION_STATUS, NOTE_TO_AUTHORIZER and APPROVED_DATE together. Because the ETRM metadata records that this view is not implemented in the reference database, developers should confirm its existence in the target instance prior to use.