Search Results edi_processed_flag




Overview
Explore in AI Chat

Overview

PO_HEADERS_ALL_MRC_V is a multiple reporting currency (MRC) view in the Oracle Purchasing (PO) module. It exposes purchasing document header information — requisitions converted to purchase orders, blanket agreements, contracts, and standard purchase orders — together with the currency conversion attributes maintained by the MRC architecture. In Oracle EBS 12.1.1 and 12.2.2, the _MRC_V suffix denotes a view that joins the operational (functional currency) record to its associated reporting-currency conversion rows, allowing transactions to be reported in currencies other than the ledger's functional currency.

The ETRM record for this object carries the annotation "Retrofitted" and an explicit implementation note stating "Not implemented in this database." This indicates that the view is a legacy or compatibility construct retained within the object library rather than a runtime object present in the delivered schema. Consequently, DBAs and developers should not assume its existence in a given environment; its columns and semantics nonetheless mirror the documented structure of the base purchasing header table.

Underlying Base Objects

The ETRM documentation lists no referenced base objects for this view. From the view text, the definition is anchored on the alias PO — corresponding to PO_HEADERS_ALL, the principal table storing purchasing document headers — joined to an MRC conversion source aliased MC, supplying RATE_TYPE, RATE_DATE, and RATE. The view therefore projects essentially every significant column of PO_HEADERS_ALL and appends the currency conversion descriptors. Because the object is documented as not implemented, no physical dependency chain is asserted; where a comparable MRC view does exist, the standard EBS pattern is a union or join across the reporting-currency set identified by ORG_ID and the MRC schema configuration.

Key Columns

The column list is extensive and closely tracks PO_HEADERS_ALL. Identification and control columns include PO_HEADER_ID, SEGMENT1 (the document number), TYPE_LOOKUP_CODE (document type), AUTHORIZATION_STATUS, APPROVED_FLAG, CANCEL_FLAG, CLOSED_CODE, and ORG_ID. Financial and vendor attributes include VENDOR_ID, VENDOR_SITE_ID, CURRENCY_CODE, TERMS_ID, BLANKET_TOTAL_AMOUNT, and AMOUNT_LIMIT. Agreement-specific fields include START_DATE_ACTIVE, END_DATE_ACTIVE, MIN_RELEASE_AMOUNT, QUOTE_TYPE_LOOKUP_CODE, and QUOTE_VENDOR_QUOTE_NUMBER.

For the searched term ACCEPTANCE_REQUIRED_FLAG, the view exposes this column directly from the purchasing header. It indicates whether formal acceptance of the goods or services is required before the document can be finally closed. It is paired with ACCEPTANCE_DUE_DATE, which records the deadline by which that acceptance must occur. Downstream, these fields drive the acceptance workflow and influence whether a purchase order can progress to closed status. Additional relevant indicators in the same record include CLOSED_DATE, USER_HOLD_FLAG, APPROVAL_REQUIRED_FLAG, FIRM_STATUS_LOOKUP_CODE, FROZEN_FLAG, and CONFIRMING_ORDER_FLAG. Descriptive columns NOTE_TO_AUTHORIZER, NOTE_TO_VENDOR, NOTE_TO_RECEIVER, and COMMENTS hold free-form text, while the fifteen ATTRIBUTE and five GLOBAL_ATTRIBUTE columns provide the standard EBS descriptive flexfield segments.

Common Use Cases and Queries

Typical applications include auditing which purchase orders require acceptance, reconciling reporting-currency amounts against functional-currency totals, and feeding header data into custom reporting or integration layers. A representative query targeting the searched column is:

  • SELECT ph.segment1, ph.type_lookup_code, ph.acceptance_required_flag, ph.acceptance_due_date, ph.authorization_status FROM po_headers_all_mrc_v ph WHERE ph.acceptance_required_flag = 'Y' AND ph.closed_code IS NULL;
  • SELECT ph.segment1, ph.currency_code, ph.rate_type, ph.rate, ph.rate_date, ph.blanket_total_amount FROM po_headers_all_mrc_v ph WHERE ph.org_id = :org_id;

Because the ETRM record documents the view as "Not implemented in this database," any query must first be validated against the target instance. Where the view is absent, equivalent results are obtained by joining PO_HEADERS_ALL to the appropriate MRC currency conversion table using PO_HEADER_ID and ORG_ID.