Results for “curr_sr_assignment_set”
12 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
MRP_PLAN_PARAMETERS_V is an APPS-owned view in the Oracle E-Business Suite Master Scheduling/MRP product (MRP). It is described in the ETRM metadata as the "MRP or MPS Plan Options View". Its purpose is to present, in a single denormalized row, the effective set of planning parameters that govern a given plan or schedule designator — that is, the parameters actually in force when a plan is compiled or executed, rather than the raw stored values alone.
The view reconciles two sources of configuration: the current working values held in the plan/parameter records and the default values carried on the designator definition. It is heavily used by Oracle's planning concurrent programs, by the Plan Options user interface, and by customer reporting and integration layers that need to interrogate plan configuration without navigating the many underlying tables individually. The search term "schedule_designator" is directly relevant, because the view exposes both CURR_SCHEDULE_DESIGNATOR (the working designator) and SCHEDULE_DESIGNATOR (the scheduled designator), along with their descriptions and the associated schedule and operation schedule types.
Underlying Base Objects
The documented base objects referenced by the view are:
- MRP_PLANS (synonym) — the plan header and its current parameter values.
- MRP_PARAMETERS (synonym) — organization-level default planning parameters.
- MRP_DESIGNATORS_VIEW (view) — the designator definitions, including DESCRIPTION, DESIGNATOR_TYPE, ORGANIZATION_SELECTION, and DISABLE_DATE.
- MRP_SCHEDULE_DESIGNATORS (synonym) — schedule designator descriptions (aliased S1 and S2 in the view text).
- MRP_ASSIGNMENT_SETS (synonym) — assignment set name and description for the plan.
- MRP_ORGANIZATIONS_V (view) — the planned organization, resolved through NVL(MPO.PLANNED_ORGANIZATION, D.ORGANIZATION_ID).
- MRP_GET_PROJECT (package) — supplies LOOKUP_MEANING calls that translate coded values into descriptive meanings.
The view text aliases MRP_PLANS as M, MRP_DESIGNATORS_VIEW as D, and MRP_PARAMETERS as P. Values are resolved with NVL(M.<current value>, P.<default>), so that a stored plan-level value takes precedence over the organization default. Status is documented as VALID.
Key Columns
- ORGANIZATION_ID — the planned organization for the row.
- DESIGNATOR and CURR_SCHEDULE_DESIGNATOR / SCHEDULE_DESIGNATOR — the designator identifiers, with descriptions sourced from MRP_SCHEDULE_DESIGNATORS (S1, S2).
- DESIGNATOR_TYPE / PLAN_TYPE — decoded so that type 2 maps to 2 and type 3 maps to 1, then translated through MRP_GET_PROJECT.LOOKUP_MEANING('MRP_PLAN_TYPE', ...).
- CURR_SCHEDULE_TYPE and SCHEDULE_TYPE — interpreted via LOOKUP_MEANING('MRP_DESIGNATOR_TYPE_SHORT', ...).
- CURR_OVERWRITE_OPTION and CURR_APPEND_PLANNED_ORDERS — overwrite/append behaviour for regenerated plans.
- CURR_CUTOFF_DATE, CURR_PART_INCLUDE_TYPE, CURR_PLANNING_TIME_FENCE_FLAG, CURR_DEMAND_TIME_FENCE_FLAG, CURR_CONSIDER_RESERVATIONS, CURR_PLAN_SAFETY_STOCK, CURR_CONSIDER_WIP, CURR_CONSIDER_PO, CURR_SNAPSHOT_LOCK, CURR_FULL_PEGGING — the core planning behaviour flags and dates.
- CURR_OPERATION_SCHEDULE_TYPE / OPERATION_SCHEDULE_TYPE, REPETITIVE_ANCHOR_DATE — scheduling controls.
- CURR_ASSIGNMENT_SET_ID, ASSIGNMENT_SET_NAME, DESCRIPTION — assignment set context.
- LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, COMPILE_DEFINITION_DATE — audit and compile metadata, defaulted with SYSDATE where null.
Common Use Cases and Queries
Typical uses include auditing plan configuration before a plan run, comparing stored plan values against organization defaults, and reporting which schedule designator is active for a plan. A representative query retrieving the designator and key planning flags is:
SELECT organization_id,
designator,
schedule_designator,
plan_type,
schedule_type,
curr_cutoff_date,
curr_consider_wip,
curr_consider_po
FROM apps.mrp_plan_parameters_v
WHERE schedule_designator = :p_designator;
To report assignment-set and overwrite behaviour across organizations:
SELECT organization_id,
designator,
assignment_set_name,
curr_overwrite_option,
curr_append_planned_orders
FROM apps.mrp_plan_parameters_v
ORDER BY organization_id, designator;
-
View: MRP_PLAN_PARAMETERS_V 12.1.1
MRP or MPS Plan Options View
APPS.MRP_PLAN_PARAMETERS_V·↳ MRP_ASSIGNMENT_SETS·↳ MRP_DESIGNATORS_VIEW·↳ MRP_GET_PROJECT·Explore MRP module →
-
View: MSC_PLAN_PARAMETERS_V 12.1.1
APPS.MSC_PLAN_PARAMETERS_V·↳ MFG_LOOKUPS·↳ MSC_ASSIGNMENT_SETS·↳ MSC_CATEGORY_SETS·Explore MSC module →
-
View: MRP_PLAN_PARAMETERS_V 12.2.2
MRP or MPS Plan Options View
APPS.MRP_PLAN_PARAMETERS_V·↳ MRP_ASSIGNMENT_SETS·↳ MRP_DESIGNATORS_VIEW·↳ MRP_GET_PROJECT·Explore MRP module →
-
View: MSC_PLAN_PARAMETERS_V 12.2.2
APPS.MSC_PLAN_PARAMETERS_V·↳ MFG_LOOKUPS·↳ MSC_ASSIGNMENT_SETS·↳ MSC_CATEGORY_SETS·Explore MSC module →
-
eTRM - MRP Tables and Views 12.2.2
Recommendations based on user criteria selected in MRP Planner WorkBench
-
eTRM - MRP Tables and Views 12.1.1
Recommendations based on user criteria selected in MRP Planner WorkBench
-
eTRM - MSC Tables and Views 12.1.1
This table contains the mapping between user-defined zone and included regions
-
eTRM - MSC Tables and Views 12.2.2
This table contains the mapping between user-defined zone and included regions