Search Results exp_cycle_start_day_code




Overview
Explore in AI Chat

Overview

The view PA_IMPLEMENTATIONS_ALL_MRC_V_O belongs to the Oracle Projects (PA) module and is documented as a single currency view. It is part of the Multiple Reporting Currencies (MRC) family of objects in Oracle E-Business Suite, a framework designed to allow an organization to report on transactional data in one or more reporting currencies in addition to the primary functional currency. In the 12.1.1 and 12.2.2 releases, MRC views such as this one exist to present a consolidated, single-currency perspective of the underlying Projects implementation setup data, which would otherwise be stored per set of books and per currency context.

The object exposes implementation-level configuration for Oracle Projects, including organization structures, billing and invoicing defaults, expenditure cycle configuration, cross-charging behavior, and tax determination hierarchies. Its principal role is to support reporting and integration scenarios in which downstream consumers require a stable, single-currency projection of the Project implementation parameters without joining directly to the full MRC-aware implementation table.

In the documentation metadata provided for ETRM 12.2.2, the view is noted as not implemented in the reference database, and no base objects are formally documented beyond the view text selector. This is a common characteristic of MRC-derived views, whose existence and availability depend on whether MRC is enabled and the corresponding set of books is configured in the instance.

Underlying Base Objects

Although the documented metadata lists no referenced base objects, the view text explicitly selects from PA_IMPLEMENTATIONS_ALL, the Projects implementation table that stores setup parameters for each business group and organization context. The defining query does not perform a currency conversion projection over multiple sets of books; instead, it presents a set of columns from PA_IMPLEMENTATIONS_ALL, with the SET_OF_BOOKS_ID value resolved at runtime through the USERENV('CLIENT_INFO') call:

  • NVL(TO_NUMBER(SUBSTR(USERENV('CLIENT_INFO'), 45, 10)), -99) — derives the current set of books identifier from the client information context, defaulting to -99 when unavailable.
  • All remaining columns are projected directly from PA_IMPLEMENTATIONS_ALL, including ORG_ID, the organization structure identifiers, and the cross-charging parameters.

Because the view is built on the "_ALL" implementation table, it is organization and business-group aware, and it is subject to the same multi-org and MRC access policies as the base table. The "_V_O" suffix conventionally indicates a view variant associated with MRC or currency-specific projections.

Key Columns

The view exposes a broad set of implementation parameters. The most significant, particularly in relation to the user search term default_rate_type, include:

Standard audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) are also exposed.

Common Use Cases and Queries

Typical scenarios include reporting on Projects implementation defaults per operating unit or ledger, verifying default rate type configuration after a migration or upgrade, and driving integrations that require the effective conversion defaults without joining the full MRC stack. A representative query to inspect default rate type configuration is:

SELECT org_id,
       business_group_id,
       default_rate_type,
       default_rate_date_code,
       cc_default_rate_type,
       cc_default_rate_date_code
FROM   pa_implementations_all_mrc_v_o
WHERE  default_rate_type IS NOT NULL;

A second common query audits billing and tax parameters for a given organization:

SELECT org_id,
       billing_cycle,
       billing_offset,
       output_tax_use_project_flag,
       output_tax_hier_project
FROM   pa_implementations_all_mrc_v_o
WHERE  org_id = :p_org_id;

Because the view is documented as not implemented in the reference database, administrators should confirm that MRC is enabled and that the underlying PA_IMPLEMENTATIONS_ALL table contains rows for the target organization context before relying on the view for production reporting.