Search Results availability_match_wt




Overview
Explore in AI Chat

Overview

The PA_IMPLEMENTATIONS_ALL_MRC_V2 view belongs to the Oracle Projects (PA) module and is described in the ETRM repository as a "single currency view." It exposes the implementation-level setup records maintained for Oracle Projects, presenting them in the context of a single reporting currency rather than the multiple reporting currencies (MRC) that the underlying implementation data may otherwise span. The _MRC_ naming convention and the trailing _V2 suffix indicate that this is a reporting-currency variant of the base implementation view, retained for backward compatibility with earlier Oracle Projects schema versions.

Because the view projects client-attribute context (via USERENV('CLIENT_INFO')) into the ORG_ID column, it is inherently multi-organization aware. The ETRM metadata records that the view is Not implemented in this database, meaning it exists in the data dictionary of the documented environment only as a definition; it may be a legacy or non-deployed object in Oracle EBS 12.1.1 and 12.2.2 installations. Its role is therefore primarily informational, supporting queries that need to read project implementation options in a currency-neutral manner, particularly when reconciling setups across reporting sets or when migrating configuration between operating units.

Underlying Base Objects

The ETRM metadata does not document any referenced base objects for this view. In Oracle Projects, implementation options are physically stored in PA_IMPLEMENTATIONS_ALL and, where MRC is enabled, in corresponding MRC tables keyed by a currency or set-of-books context. The single-currency "V2" wrapper typically selects from the MRC implementation data and filters or joins to return exactly one row per implementation context, removing the reporting-currency dimension. Because the ETRM record lists no base objects, the safest interpretation is that the view is a thin projection over the implementation tables — its columns mirror the underlying implementation attributes almost one-for-one.

Key Columns

Common Use Cases and Queries

This view supports configuration audits, multi-currency reconciliation, and migration validation. A representative query retrieves implementation options for the current operating unit:

SELECT org_id, multi_currency_billing_flag, default_rate_type,
       centralized_invoicing_flag, cc_ic_billing_prvdr_flag
FROM   pa_implementations_all_mrc_v2
WHERE  org_id = :org_id;

Administrators also use it to confirm which interface and cross-charging flags are active before running GL costing or intercompany invoicing. Because no base objects are documented, developers should treat the view as a convenience projection and confirm its exact definition in their environment with DBMS_METADATA.GET_DDL before building dependent logic.