Results for “minimum_quantity”

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

Overview

MSC_PROCESS_EFFECTIVITY_V is an APPS-owned reporting view within the MSC (Advanced Supply Chain Planning) product of Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the process effectivity definitions used by Oracle Advanced Supply Chain Planning (ASCP) when modeling process manufacturing routings, production lines, and resource consumption. The view consolidates data from the MSC_PROCESS_EFFECTIVITY planning table together with descriptive attributes from the MSC_SYSTEM_ITEMS, MSC_ROUTINGS, MSC_BOMS, and MSC_DEPARTMENT_RESOURCES tables, presenting a denormalized, plan-scoped record that is convenient for reporting, extract, and integration purposes.

Rather than requiring a report author to join multiple planning tables manually, the view returns a single row per process effectivity record, enriched with organization code, item name, alternate routing and BOM designators, department or line code, and production line rate. This makes it suitable for both ad hoc queries and downstream interfaces that need to understand which item, at which organization, on which routing and BOM, is valid over a given date range and within defined quantity boundaries.

Underlying Base Objects

The view is defined over five synonym-referenced base objects in the APPS schema: MSC_PROCESS_EFFECTIVITY (the driving table, aliased MPE), MSC_SYSTEM_ITEMS (MSI), MSC_ROUTINGS (MR), MSC_BOMS (BOM), and MSC_DEPARTMENT_RESOURCES (DEPT). All are synonyms over the corresponding MSC planning tables.

The join keys reflect the plan-scoped, multi-instance nature of ASCP data. MSC_SYSTEM_ITEMS is joined on PLAN_ID, SR_INSTANCE_ID, ORGANIZATION_ID, and INVENTORY_ITEM_ID = MPE.ITEM_ID. MSC_DEPARTMENT_RESOURCES, MSC_BOMS, and MSC_ROUTINGS are outer-joined (denoted by the (+) operator) on LINE_ID, BILL_SEQUENCE_ID, and ROUTING_SEQUENCE_ID respectively, along with the common PLAN_ID, SR_INSTANCE_ID, and ORGANIZATION_ID keys. The department join is further constrained to LINE_FLAG = 1, indicating that the resource record represents a production line. Because three of the five joins are outer joins, process effectivity rows are preserved even when no matching BOM, routing, or department resource exists.

Key Columns

• PLAN_ID, SR_INSTANCE_ID, ORGANIZATION_ID — the composite planning context; every query should constrain on these to avoid cross-plan or cross-instance data.
• ORGANIZATION_CODE, ITEM_ID, ITEM_NAME — descriptive identifiers for the organization and item sourced from MSC_SYSTEM_ITEMS.
• PROCESS_SEQUENCE_ID, EFFECTIVITY_DATE, DISABLE_DATE — the process identifier and the effective date range during which the effectivity record applies.
• MINIMUM_QUANTITY, MAXIMUM_QUANTITY — the lower and upper quantity bounds for which the process effectivity is valid; these are central to the "maximum_quantity" search context.
• PREFERENCE — the priority used to select among competing effectivity records.
• ROUTING_SEQUENCE_ID, ALTERNATE_ROUTING_DESIGNATOR, BILL_SEQUENCE_ID, ALTERNATE_BOM_DESIGNATOR — routing and BOM context, including alternate designators.
• TOTAL_PRODUCT_CYCLE_TIME, ITEM_PROCESS_COST — planning cost and lead-time attributes.
• LINE_ID, LINE_CODE, PRIMARY_LINE_FLAG, PRODUCTION_LINE_RATE — production line identification and throughput rate.

Common Use Cases and Queries

Typical scenarios include validating effectivity date and quantity ranges for a process item, investigating why ASCP selected a particular routing or line, and sourcing process cost and cycle-time data for reporting. The following query returns effectivity records for a given plan and organization.

SELECT item_name, process_sequence_id, effectivity_date, disable_date,
  minimum_quantity, maximum_quantity, preference,
  organization_code, line_code, production_line_rate
FROM apps.msc_process_effectivity_v
WHERE plan_id = :p_plan_id
  AND sr_instance_id = :p_sr_instance_id
  AND organization_id = :p_org_id
  AND maximum_quantity >= :p_order_qty
  AND effectivity_date <= SYSDATE
  AND NVL(disable_date, SYSDATE + 1) > SYSDATE
ORDER BY item_name, preference;

A second common pattern filters to primary lines only, using the PRIMARY_LINE_FLAG and LINE_CODE columns for line-level capacity analysis. Because the view resolves all descriptive attributes, it is equally well suited to data extraction routines feeding external planning or MES systems.