Search Results pa_implementations_all_mrc_v




Overview
Explore in AI Chat

Overview

APPS.PA_IMPLEMENTATIONS_ALL_MRC_V is a Projects (PA) module view in Oracle EBS 12.1.1 and 12.2.2 that exposes implementation-level configuration settings for Oracle Projects. Its name carries the _MRC_V suffix, denoting a Multi-Reporting Currency (MRC) view, which in the E-Business Suite conventionally presents multiples of a base entity keyed by reporting set of books or ledger context via the USERENV('CLIENT_INFO') mechanism. The view returns a single row of system-wide Projects implementation setup for the active organization/operating unit context, mirroring the columns of the underlying PA_IMPLEMENTATIONS_ALL synonym. It serves reporting, diagnostic, and integration consumers that need a read-only projection of Projects option flags and defaults without directly querying the base implementation table.

Underlying Base Objects

The documented view metadata lists a single referenced base object: PA_IMPLEMENTATIONS_ALL (SYNONYM). The view definition selects a column list directly from this synonym and synthesizes one MRC key column:

  • NVL(TO_NUMBER(SUBSTR(USERENV('CLIENT_INFO'), 45, 10)), -99) — the reporting/ledger context derived from the client session environment, exposed alongside the project implementation attributes.
  • Because PA_IMPLEMENTATIONS_ALL is resolved in the APPS schema as a synonym, the view inherits the security and grants applied to that base object. The _MRC_V naming implies the view is intended to surface currency-context variants of implementation setup.

Key Columns

The view exposes the full PA implementation configuration surface. Notable columns include:

Common Use Cases and Queries

Typical scenarios include verifying implementation flags after setup, auditing GL interface and cross-charge configuration, and feeding downstream integrations the current option values. A representative query follows:

  • Review GL interface flags:
    SELECT org_id, interface_labor_to_gl_flag, interface_usage_to_gl_flag, interface_revenue_to_gl_flag FROM pa_implementations_all_mrc_v;
  • Inspect billing and numbering defaults:
    SELECT billing_cycle, billing_offset, manual_invoice_num_type, next_automatic_invoice_number FROM pa_implementations_all_mrc_v;
  • Check cross-charge configuration:
    SELECT cc_process_io_code, cc_allow_iu_flag, cc_ic_billing_prvdr_flag FROM pa_implementations_all_mrc_v;
  • Diagnose MRC context:
    SELECT org_id, fte_day, period_set_name, same_pa_gl_period FROM pa_implementations_all_mrc_v;

Because the view returns a compact, implementation-wide result set and derives the MRC key from CLIENT_INFO, queries should be executed within a properly initialized EBS session to obtain meaningful reporting-context values; otherwise the synthesized key defaults to -99.