Search Results msc_end_assembly_pegging

Overview

APPS.MSC_SYSTEM_ITEMS_SC_V is a supply chain planning view in Oracle E-Business Suite that exposes item master attributes required by the Advanced Supply Chain Planning (ASCP) and related MSC schemas. The suffix "_SC_V" indicates a supply chain–oriented, security-enabled view. It flattens the planning-relevant columns of MTL_SYSTEM_ITEMS_B (exposed through the MSC_SYSTEM_ITEMS synonym owned by the MSC schema) together with organizational context from MSC_PLANS and category information from MSC_ITEM_CATEGORIES. The view's purpose is to present a planning-ready item record without requiring callers to join the base inventory tables themselves, and to translate coded values into descriptive meanings through the MSC_GET_NAME package.

The object is widely used in ASCP data extraction, custom reports, and integration interfaces where a denormalized, decoded item view is more convenient than querying MTL_SYSTEM_ITEMS_B directly. In Oracle EBS 12.1.1 and 12.2.2 the definition is functionally consistent; the metadata is documented for 12.2.2.

Underlying Base Objects

The documented referenced base objects are:

• MSC_GET_NAME (PACKAGE) — provides the org_code and lookup_meaning functions used for decoding organization identifiers and lookup codes.
• MSC_ITEMS (SYNONYM) — synonym to the item master, supplying inventory item attributes.
• MSC_ITEM_CATEGORIES (SYNONYM) — synonym to category assignments, providing category set, category id, and category name.
• MSC_PLANS (SYNONYM) — synonym to the plan definitions, supplying plan organization id and compile designator.
• MSC_SYSTEM_ITEMS (SYNONYM) — synonym to MTL_SYSTEM_ITEMS_B, the primary source of item attributes.

These synonyms map to the corresponding MSC or MTL base objects in the APPS schema. The view therefore sits on top of the standard item master and planning plan definition, with MSC_GET_NAME performing runtime lookup decoding on the fly.

Key Columns

The view exposes a broad set of planning attributes. Notable columns include:

• inventory_item_id, item_name, organization_id — item and organization identifiers; organization is decoded via msc_get_name.org_code.
• planning_make_buy_code — decoded using the MTL_PLANNING_MAKE_BUY lookup.
• mrP_planning_code — decoded using the MRP_PLANNING_CODE lookup.
• end_assembly_pegging_flag — a planning control that determines how end-assembly pegging is applied; this is the column directly associated with the user's search term.
• full_pegging — decoded via MRP_HARD_PEGGING_LEVEL, controlling the hard pegging level.
• Lead-time columns — preprocessing, postprocessing, full, fixed, and variable lead times.
• Cost columns — standard_cost, carrying_cost, list_price, and the derived margin (list_price − standard_cost).
• Safety stock and order modifiers — safety_stock_bucket_days, safety_stock_percent, fixed_safety_stock_qty, fixed_days_supply, fixed_order_quantity, fixed_lot_multiplier, minimum_order_quantity, maximum_order_quantity, shrinkage_rate.
• Category columns — sr_category_id, category_set_id, category_name, description from MSC_ITEM_CATEGORIES.

The end_assembly_pegging_flag is decoded by msc_get_name.lookup_meaning('MSC_END_ASSEMBLY_PEGGING', ...), where the DECODE maps values N, A, Y, B, I, X to numeric lookup codes before resolving the meaning — this directly supports pegging behaviour used in ASCP planning.

Common Use Cases and Queries

A frequent requirement is retrieving end-assembly pegging configuration for a set of items so planners can audit or tune pegging behaviour.

SELECT inventory_item_id,
       item_name,
       organization_id,
       msc_get_name.lookup_meaning('MSC_END_ASSEMBLY_PEGGING',
         DECODE(end_assembly_pegging_flag,'N',1,'A',2,'Y',3,'B',4,'I',5,'X',6,1)) pegging_meaning,
       full_pegging
  FROM apps.msc_system_items_sc_v
 WHERE organization_id = :org_id;

Another common use is joining the view to planning results in MSC_SYSTEM_ITEMS or MSC_ITEMS for exception reporting, or extracting the decoded make/buy and planning code descriptions for interface files. Because lead-time, safety-stock, and order-modifier columns are already present, the view is also used to populate planning parameter snapshots without re-joining MTL_SYSTEM_ITEMS_B.

When querying, restrict by organization_id and inventory_item_id whenever possible, as the view joins multiple synonyms and invokes MSC_GET_NAME functions per row, which can affect performance on large item sets.