Search Results bis_mrpgmall_v

Overview

BIS_MRPGMALL_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, registered under the Applications BIS product family. Within the ETRM documentation it is described as a retrofitted object, meaning it was carried forward and revalidated across releases rather than newly authored for a specific version. The view presents business plan target definitions associated with a single, hard-coded target level whose short name is 'MRPGMALL'. In practice, this makes BIS_MRPGMALL_V a specialized slice of the general target-value model, pre-filtered so that consumers receive only the targets belonging to the MRPGMALL target level.

The view belongs to the BIS (Business Intelligence System / Applications BIS) schema area, which supplies plan and target metadata used by enterprise planning and performance reporting. Rather than exposing raw transactional data, BIS_MRPGMALL_V denormalizes plan identifiers, time-level values, target amounts, tolerance ranges, and role assignments into a single read-only result set suited for downstream reporting, integration, and comparison against planning hierarchies.

Underlying Base Objects

The documented view text joins four base objects:

• BIS_TARGET_VALUES (VAL) — the fact-like source of target values, ranges, and role identifiers.
• BIS_BUSINESS_PLANS (PLAN) — the plan header providing plan ID, short name, version, and the current-plan indicator.
• BIS_TARGET_LEVELS (LVL) — the target-level definition supplying WF_PROCESS and the level short name.
• GL_PERIODS (GL) — included in the FROM clause to supply period context for the target values.

The joins are keyed on TARGET_LEVEL_ID between BIS_TARGET_VALUES and BIS_TARGET_LEVELS, and on PLAN_ID between BIS_TARGET_VALUES and BIS_BUSINESS_PLANS. The defining filter is LVL.SHORT_NAME = 'MRPGMALL', which restricts the output to the MRPGMALL target level. Note that ETRM 12.2.2 lists no separately documented referenced base objects for this view, so the join relationships must be inferred from the embedded view text rather than from a cataloged dependency list.

Key Columns

The view exposes the following columns:

• WF_PROCESS — the workflow process associated with the target level.
• PLAN_ID, PLAN_SHORT_NAME, VERSION_NO, CURRENT_PLAN_FLAG — plan identity and versioning context, with the flag identifying the active plan version.
• TOTAL_TIME (documented as TIME_LEVEL_VALUE in the view text) — the time-level value against which the target is expressed.
• TARGET — the primary target amount.
• RANGE1_LOW / RANGE1_HIGH, RANGE2_LOW / RANGE2_HIGH, RANGE3_LOW / RANGE3_HIGH — three configurable tolerance or variance bands around the target.
• ROLE1_ID / ROLE1, ROLE2_ID / ROLE2, ROLE3_ID / ROLE3 — up to three owner or responsibility designations, exposed both as IDs and as display values.

Common Use Cases and Queries

The view is typically consumed to retrieve MRPGMALL targets alongside their plan and role context, for scorecard reporting, plan-versus-actual comparisons, and integration into custom BI extracts. A representative query follows:

SELECT plan_short_name,
       version_no,
       current_plan_flag,
       total_time,
       target,
       range1_low,
       range1_high,
       role1,
       role2,
       role3
FROM   apps.bis_mrpgmall_v
WHERE  current_plan_flag = 'Y';

Because the view already applies the MRPGMALL restriction, no additional target-level predicate is required. Analysts generally restrict by CURRENT_PLAN_FLAG, PLAN_ID, or a TOTAL_TIME range to limit the result set to the plan and period of interest. Consumers should treat BIS_MRPGMALL_V as read-only and should not attempt DML against it, since it is a multi-table join view rather than an updatable entity.