Results for “include_target_demands”

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

Overview

MSC_PLAN_SCHEDULES is a table in the MSC schema belonging to the Advanced Supply Chain Planning (ASCP) module of Oracle E-Business Suite 12.1.1 and 12.2.2. It stores master production schedules and master demand schedules that participate in the planning process for a given organization and plan. In addition, the table is used to hold the input production schedule name for In-Line Vehicle Sequencing (ILVS) on Oracle Supply Chain Management, allowing ILVS to consume an externally maintained schedule definition as its sequencing input.

Because the table is keyed by a composite of plan and organization context plus a designator reference, its heuristic Data Vault classification is a link table. It connects planning organizations, plans, and designator records rather than holding standalone descriptive attributes. Modeling it as a link reflects its role as a contextual association between the plan/organization grain in MSC_PLAN_ORGANIZATIONS and the schedule definition in MSC_DESIGNATORS.

Key Information Stored

The table contains 40 documented columns, of which the following are the most significant for querying and integration:

• PLAN_ID — Identifies the ASCP plan to which the schedule belongs; part of the primary key and a foreign key to MSC_PLAN_ORGANIZATIONS.
• ORGANIZATION_ID — The inventory organization context for the schedule.
• SR_INSTANCE_ID — Source instance identifier, distinguishing records sourced from different EBS instances in a multi-instance or data-collection configuration.
• INPUT_SCHEDULE_ID — The schedule designator; a foreign key to MSC_DESIGNATORS and the pointer used by ILVS to resolve the input production schedule name.
• INPUT_TYPE — Classifies the schedule as a master production schedule or master demand schedule; appears in the unique index alongside the key columns.
• DESIGNATOR_TYPE — Categorizes the designator associated with the schedule.
• SCENARIO_SET and PROBABILITY — Support scenario-based planning and probabilistic demand modeling.
• DEMAND_VARIABILITY_TYPE and MAPE_VALUE — Capture demand variability classification and the associated Mean Absolute Percentage Error metric.
• SHIP_TO — Ship-to context for demand-driven schedules.
• INTERPLANT_DEMAND_FLAG — Indicates whether interplant demand is included.
• INCLUDE_TARGET_DEMANDS, INCLUDE_PO, INCLUDE_PLN_ORD — Flags controlling which demand and supply sources (target demands, purchase orders, planned orders) are incorporated.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — Standard concurrent program audit columns identifying the process that created or last updated the record.
• LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — The standard DFF flexfield block for client-specific extensions.

The surrogate primary key is MSC_PLAN_SCHEDULES_PK, composed of SR_INSTANCE_ID, ORGANIZATION_ID, PLAN_ID, and INPUT_SCHEDULE_ID. A unique business-key candidate is defined by MSC_PLAN_SCHEDULES_U1 over PLAN_ID, ORGANIZATION_ID, SR_INSTANCE_ID, INPUT_SCHEDULE_ID, and INPUT_TYPE, which prevents duplicate schedule definitions of the same type within a plan and organization.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include listing all schedules for a given plan, identifying the input schedule used by ILVS, and auditing which demand or supply inclusion flags are active per organization.

To list all production and demand schedules for a plan:

• SELECT organization_id, input_schedule_id, input_type, designator_type FROM msc_plan_schedules WHERE plan_id = :plan_id AND sr_instance_id = :instance_id;

To resolve the ILVS input schedule name, join to MSC_DESIGNATORS on INPUT_SCHEDULE_ID:

• SELECT d.designator, s.input_type FROM msc_plan_schedules s, msc_designators d WHERE s.input_schedule_id = d.designator_id AND s.plan_id = :plan_id;

To audit inclusion flags and demand variability for a plan:

• SELECT organization_id, include_po, include_pln_ord, include_target_demands, interplant_demand_flag, demand_variability_type, mape_value FROM msc_plan_schedules WHERE plan_id = :plan_id;

Because the table is populated and refreshed by the ASCP data collection and plan run, queries should generally filter on PLAN_ID and ORGANIZATION_ID to keep the result set bounded.

Related Objects

• MSC_PLAN_ORGANIZATIONS — Referenced via PLAN_ID, ORGANIZATION_ID, and SR_INSTANCE_ID; provides the plan and organization definition each schedule belongs to.
• MSC_DESIGNATORS — Referenced via INPUT_SCHEDULE_ID; supplies the designator record that resolves the schedule name used by ILVS.
• MSC_PLANS — The parent plan definition governing PLAN_ID values present here.
• MSC_SYSTEM_ITEMS — Item-level planning data joined to schedules through the organization and plan context.
• MSC_SUPPLIES and MSC_DEMANDS — Planning supply and demand records whose contents are shaped by the inclusion flags on this table.
• MSC_PLAN_SCHEDULES views and ASCP concurrent programs (plan launch, data collection, and ILVS sequencing) — the primary runtime consumers of these records.