Search Results network_scheduling_method

Overview

MSC_PARAMETERS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, belonging to the MSC (Advanced Supply Chain Planning) product family. It exposes the planning parameter configuration defined at the organization level, one row per inventory organization that participates in Advanced Supply Chain Planning. In EBS 12.1.1 and 12.2.2 the view is registered as VALID and is treated as a read-only presentation layer over the base planning parameters table.

Functionally, the view provides a denormalized, query-friendly projection of the plan option setup that planners maintain through the Plan Options and Organization Parameters windows. Because it is a view rather than a table, it cannot be updated directly; all maintenance flows through the underlying MSC_PARAMETERS table and the standard MSC planning setup forms. The user search term repetitive_anchor_date corresponds directly to a column exposed by this view, REPETITIVE_ANCHOR_DATE, which is the anchor date used to align repetitive manufacturing scheduling buckets.

Underlying Base Objects

The documented base object for this view is MSC_PARAMETERS, referenced through a synonym. The view definition selects from that single table, aliased as M, and performs no joins, unions, or aggregations. It is therefore a pure column-projection view.

• APPS.MSC_PARAMETERS — the sole documented base table; the synonym resolves to the MSC schema table that stores organization-level planning parameters.
• M.ROWID is exposed as ROW_ID, preserving row identity for tooling that requires a unique handle.
• One expression is derived rather than passed through: NULL is selected into the ABC_ASSIGNMENT_GROUP_NAME column, so no lookup is performed against the ABC assignment group definition.

Because the relationship is one-to-one with the base table, row cardinality and filtering behaviour are identical to querying MSC_PARAMETERS directly; the view adds no implicit WHERE clause.

Key Columns

• ORGANIZATION_ID — inventory organization the parameter set applies to; the principal filter key.
• SR_INSTANCE_ID — source instance identifier linking the record to the originating application instance.
• REPETITIVE_ANCHOR_DATE — anchor date that fixes the start of the repetitive scheduling horizon and bucket alignment.
• REPETITIVE_HORIZON1 / REPETITIVE_HORIZON2 — day ranges defining the repetitive planning horizons.
• REPETITIVE_BUCKET_SIZE1 / 2 / 3 — bucket sizes applied across the repetitive horizons.
• DEMAND_TIME_FENCE_FLAG / PLANNING_TIME_FENCE_FLAG — flags controlling demand and planning time fences.
• OPERATION_SCHEDULE_TYPE — scheduling mode applied to operations.
• CONSIDER_WIP, CONSIDER_PO, CONSIDER_RESERVATIONS — supply and reservation inclusion switches.
• SNAPSHOT_LOCK, PLAN_SAFETY_STOCK, PART_INCLUDE_TYPE — planning behaviour controls.
• NETWORK_SCHEDULING_METHOD, INCLUDE_REP_SUPPLY_DAYS, INCLUDE_MDS_DAYS, INCLUDE_PAST_DUE_FORECAST — horizon and scheduling scope settings.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — descriptive flexfield storage.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — concurrent program audit trail of the last update.

Common Use Cases and Queries

The view is typically used to audit planning configuration, compare setups across organizations, and supply repetitive scheduling parameters to custom reports. A basic extraction for a specific organization:

• SELECT organization_id, repetitive_anchor_date, repetitive_horizon1, repetitive_horizon2 FROM msc_parameters_v WHERE organization_id = :org_id;
• SELECT organization_id, planning_time_fence_flag, demand_time_fence_flag, operation_schedule_type FROM msc_parameters_v;
• SELECT organization_id, consider_wip, consider_po, consider_reservations FROM msc_parameters_v ORDER BY organization_id;
• SELECT organization_id, last_update_date, last_updated_by, request_id FROM msc_parameters_v;

Note that ABC_ASSIGNMENT_GROUP_NAME always returns NULL and should not be used for lookups.