Search Results atp_components_flag

Overview

MSC_SYSTEM_ITEMS_SC_V is a supply chain planning view owned by the APPS schema and validated under the MSC – Advanced Supply Chain Planning product in Oracle EBS 12.1.1 and 12.2.2. It exposes item-level planning attributes for every item known to the MSC planning engine, joining the master item definition (MTL_SYSTEM_ITEMS_B, surfaced through the MSC_SYSTEM_ITEMS synonym) to plan-specific context (MSC_PLANS) and category data (MSC_ITEM_CATEGORIES). The view is a flattened, denormalized reporting surface: rather than requiring report authors to resolve lookup codes, it invokes the MSC_GET_NAME package to translate coded columns into their meanings as part of the SELECT itself.

Because the query string surfaces a planning organization, a compile designator from MSC_PLANS, and category-set information, the view is typically used to enumerate items within the scope of a particular plan, along with the planning parameters that drive replenishment behavior. The "SC" in the object name aligns it with the supply chain planning schema family. The user's search term, planning_make_buy_code, is exposed directly as a raw code column and again translated through MSC_GET_NAME.LOOKUP_MEANING('MTL_PLANNING_MAKE_BUY', MSI.PLANNING_MAKE_BUY_CODE), making this view the standard reference point for reports that need to distinguish make versus buy items.

Underlying Base Objects

The view is defined over the following documented objects, all referenced through synonyms in the APPS schema:

• MSC_ITEMS — the core MSC item definition, providing the item master attributes used throughout the projection.
• MSC_ITEM_CATEGORIES — supplies category-set linkage: SR_CATEGORY_ID, CATEGORY_SET_ID, CATEGORY_NAME, and the category DESCRIPTION.
• MSC_PLANS — supplies plan context via ORGANIZATION_ID and COMPILE_DESIGNATOR, identifying which plan the row belongs to.
• MSC_SYSTEM_ITEMS — the synonym aliased as MSI, contributing the bulk of the planning columns (planning make/buy, lead times, order modifiers, planner, ABC class, and so on).
• MSC_GET_NAME — a PL/pgSQL-style package (in EBS, a PL/SQL package) invoked inline for name resolution.

Function calls to MSC_GET_NAME.ORG_CODE, MSC_GET_NAME.LOOKUP_MEANING are embedded in the projection. Note that the view text contains an independent call to MSC_GET_NAME.LOOKUP_MEANING for MRP_ATO_FORECAST_CONTROL (once with the raw column, once with a lookup type) and again for PLANNING_MAKE_BUY_CODE, WIP_SUPPLY_TYPE, MTL_EFFECTIVITY_CONTROL, BOM_ITEM_TYPE, MRP_HARD_PEGGING_LEVEL, MSC_END_ASSEMBLY_PEGGING, MRP_PLANNING_CODE, and MTL_PLANNING_MAKE_BUY. Any query against this view therefore inherits the performance characteristics of those package calls.

Key Columns

• INVENTORY_ITEM_ID, ITEM_NAME, ORGANIZATION_ID — item identity and owning inventory organization.
• PLANNING_MAKE_BUY_CODE — the raw make/buy indicator. The translated value, exposed via MSC_GET_NAME.LOOKUP_MEANING('MTL_PLANNING_MAKE_BUY', ...), resolves to the planning make/buy meaning; this is the column that satisfies the search term.
• MRP_PLANNING_CODE, REPETITIVE_TYPE, WIP_SUPPLY_TYPE, BOM_ITEM_TYPE, EFFECTIVITY_CONTROL, ATO_FORECAST_CONTROL — planning and manufacturing classification, each optionally translated through the lookup package.
• PREPROCESSING_LEAD_TIME, POSTPROCESSING_LEAD_TIME, FULL_LEAD_TIME, FIXED_LEAD_TIME, VARIABLE_LEAD_TIME — lead-time components used by the planning engine.
• STANDARD_COST, CARRYING_COST, LIST_PRICE, and the derived margin expression NVL(LIST_PRICE,0) - NVL(STANDARD_COST,0) — cost and pricing attributes.
• FIXED_DAYS_SUPPLY, FIXED_ORDER_QUANTITY, FIXED_LOT_MULTIPLIER, MINIMUM_ORDER_QUANTITY, MAXIMUM_ORDER_QUANTITY, SHRINKAGE_RATE — order modifiers and shrinkage.
• PLANNER_CODE, BUYER_NAME, ABC_CLASS, ABC_CLASS_NAME, PLANNING_EXCEPTION_SET — ownership and classification.
• SR_CATEGORY_ID, CATEGORY_SET_ID, CATEGORY_NAME — category dimensions.
• FULL_PEGGING, END_ASSEMBLY_PEGGING_FLAG, PLANNING_TIME_FENCE_DATE, PLANNING_TIME_FENCE_DAYS, INVENTORY_USE_UP_DATE — planning control and pegging attributes.

Common Use Cases and Queries

A typical application is a make-versus-buy item listing scoped by plan:

• Report the translated planning make/buy meaning along with item name and planner, filtered by plan designator and organization, to support sourcing decisions.
• Reconcile lead times and order modifiers for a set of items against the plan's compilation.
• Extract category membership and ABC classification for planner workload analysis.
• Feed downstream integration or analytics extracts where a single flat row per item/plan is required rather than the normalized base tables.

Illustrative query:

SELECT item_name,
       organization_id,
       compile_designator,
       planning_make_buy_code
FROM   apps.msc_system_items_sc_v
WHERE  compile_designator = :p_plan
AND    organization_id    = :p_org;

Because lookup resolution is performed in-line, filtering on the raw code column is generally preferred over filtering on the translated expression, both for index-friendliness and predictability. Where the plan designator or organization context is absent, the view may return rows spanning multiple plans, so scoping predicates should always be applied in production reporting.