Results for “curr_reservation_level”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MSC_PDR_PLAN_DETAILS_V1 is an APPS-owned database view within the Oracle Advanced Supply Chain Planning (MSC) product family. It is a presentation-layer object that exposes the planning parameter configuration for one or more supply chain plans in a form suitable for reporting, integration, and diagnostic review. The view does not store data; it derives its content at runtime from the underlying plan parameter and plan definition tables and translates coded flag values into human-readable text.

The object is valid in both Oracle EBS 12.1.1 and 12.2.2. Its principal role is to flatten the many enumerated columns held in the plan parameter tables into descriptive literals, so that report writers and integration developers can present plan settings without embedding the decode logic themselves. It is also commonly used during implementation and tuning work, where a planner needs to confirm which resource, item, routing, and constraint options were selected when a plan was compiled.

The view additionally supports the "assignment_set" concept through the CURR_SR_ASSIGNMENT_SET column, which carries the assignment set associated with the currently active plan revision. This is the element most frequently searched by users looking to identify which sourcing assignment set is tied to a given plan.

Underlying Base Objects

The documented base objects referenced by the view are:

• FND_GLOBAL (PACKAGE) — supplies session context such as the current user and responsibility.
• MSC_GET_NAME (PACKAGE) — provides name resolution utilities used when converting identifiers to display values.
• MSC_PDR_PARAMETERS_NEW (SYNONYM) — the primary parameter source, aliased as PP in the view text.
• MSC_PLANS (SYNONYM) — the plan definition source, providing plan identity and compile designator.
• MSC_PLAN_PARAMETERS_V (VIEW) — a supporting parameter view used in the join chain.

In the view text, the alias PP (referencing MSC_PDR_PARAMETERS_NEW) supplies nearly every projected column, including CURR_PLANNED_RESOURCES, CURR_PART_INCLUDE_TYPE, CURR_SR_ASSIGNMENT_SET, CURR_DEM_PRIORITY_RULE, CURR_OPERATION_SCHEDULE_TYPE, the time fence and pegging flags, the optimize and constraint enforcement flags, the objective weights, the supplier/resource/transport over-utilization costs, the demand lateness penalty cost, and the daily and weekly bucket aggregation parameters. MSC_PLANS contributes the compile designator and plan identity. Because the view is built on synonyms and views rather than directly on base tables, it remains insulated from physical table changes and is safe for read-only consumption.

Key Columns

• CURR_PLANNED_RESOURCES — decoded to 'ALL RESOURCES' or 'BOTTLENECK RESOURCES'.
• CURR_PART_INCLUDE_TYPE — decoded to 'ALL PLANNED ITEMS', 'DEMAND SCHEDULE ITEMS ONLY', 'SUPPLY SCHEDULE ITEMS ONLY', or 'DEMAND AND SUPPLY SCHEDULE ITEMS'.
• CURR_SR_ASSIGNMENT_SET — the sourcing assignment set for the current plan revision, defaulted to a space when null.
• CURR_DEM_PRIORITY_RULE — the demand priority rule name.
• CURR_OPERATION_SCHEDULE_TYPE — 'OPERATION START DATE' or 'ORDER START DATE'.
• CURR_APPEND_PLANNED_ORDERS, CURR_FULL_PEGGING, CURR_DEMAND_TIME_FENCE_FLAG, CURR_PLANNING_TIME_FENCE_FLAG, LOT_FOR_LOT, OPTIMIZE_FLAG, CURR_ENFORCE_CAP_CONSTRAINTS, CURR_ENFORCE_DEM_DUE_DATES — decoded to 'YES' or 'NO'.
• COMPILE_DESIGNATOR — identifies the plan compiled.
• CURR_CUTOFF_DATE — the plan cutoff date as a character string.
• OBJECTIVE_WEIGHT_1, OBJECTIVE_WEIGHT_2, OBJECTIVE_WEIGHT_4 — optimization objective weights, defaulted to zero.
• SUPPLIER_CAP_OVER_UTIL_COST, RESOURCE_OVER_UTIL_COST, TRANSPORT_CAP_OVER_UTIL_COST, DMD_LATENESS_PENALTY_COST — penalty cost values, defaulted to zero.
• DAILY_CUTOFF_BUCKET and WEEKLY_CUTOFF_BUCKET — bucket counts.
• DAILY_ITEM_AGGREGATION_LEVEL, WEEKLY_ITEM_AGGREGATION_LEVEL — 'ITEMS' or 'PRODUCT FAMILY'.
• DAILY_RES_AGGREGATION_LEVEL, WEEKLY_RES_AGGREGATION_LEVEL — 'INDIVIDUAL' or 'AGGREGATE'.
• DAILY_RTG_AGGREGATION_LEVEL, WEEKLY_RTG_AGGREGATION_LEVEL — 'ROUTINGS' or 'BOR'.
• DAILY_RESOURCE_CONSTRAINTS, DAILY_MATERIAL_CONSTRAINTS — 'YES' or 'NO'.

The first two projected columns in the SELECT list are TO_CHAR(NULL) placeholders, so consumers should select columns by name rather than by position.

Common Use Cases and Queries

The view is typically used to audit plan settings, compare parameter configurations between plans, and feed downstream reporting that requires decoded values. A simple query to inspect the assignment set and core options for a plan is:

• SELECT compile_designator, curr_sr_assignment_set, curr_planned_resources, curr_part_include_type FROM apps.msc_pdr_plan_details_v1;
• SELECT compile_designator, curr_enforce_cap_constraints, curr_enforce_dem_due_dates, optimize_flag, curr_cutoff_date FROM apps.msc_pdr_plan_details_v1 WHERE compile_designator = :plan;
• SELECT compile_designator, objective_weight_1, objective_weight_2, objective_weight_4, resource_over_util_cost, dmd_lateness_penalty_cost FROM apps.msc_pdr_plan_details_v1;
• SELECT compile_designator, daily_item_aggregation_level, weekly_item_aggregation_level, daily_res_aggregation_level FROM apps.msc_pdr_plan_details_v1 ORDER BY compile_designator;

Because the view presents decoded text, it is well suited to BI Publisher reports and to integration extracts where the consumer expects descriptive labels rather than internal coded values. When very large plans are involved, filtering by COMPILE_DESIGNATOR is advisable, since the view inherits its cost profile from the joined parameter objects.