Results for “min_minmax_days”

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

Overview

MSC_ITEM_SUPPLIERS is a table in the MSC schema owned by the Advanced Supply Chain Planning (ASCP) module in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores item-supplier/site sourcing attributes—processing lead time, order modifiers, and delivery calendar information—for each combination of item and supplier/site. This data is consumed during supply chain planning runs to model how materials are procured or replenished from a given trading partner, functioning as the supplier-level planning attribute store for planned items.

From a Data Vault modeling perspective (heuristic, mined from FK structure), MSC_ITEM_SUPPLIERS is best classified as a link table. It associates business keys from MSC_SYSTEM_ITEMS (item), MSC_TRADING_PARTNERS (supplier), and MSC_TRADING_PARTNER_SITES (supplier site), while also carrying descriptive attributes such as lead time, MOQ, and replenishment method that behave satellite-like. The composite nature of the relationship confirms its role as a link between item and supplier dimensions within the planning data model.

Key Information Stored

MSC_ITEM_SUPPLIERS contains 68 columns. Its business-key candidate (unique index MSC_ITEM_SUPPLIERS_U1) is the composite of PLAN_ID, SR_INSTANCE_ID, ORGANIZATION_ID, INVENTORY_ITEM_ID, SUPPLIER_ID, SUPPLIER_SITE_ID, USING_ORGANIZATION_ID, SR_INSTANCE_ID2, NEW_PLAN_ID, and SIMULATION_SET_ID. The most important columns include:

• PLAN_ID, ORGANIZATION_ID, SR_INSTANCE_ID – planning context identifiers scoping the record.
• INVENTORY_ITEM_ID – FK to MSC_SYSTEM_ITEMS, the planned item.
• SUPPLIER_ID – FK to MSC_TRADING_PARTNERS, the sourcing supplier.
• SUPPLIER_SITE_ID – FK to MSC_TRADING_PARTNER_SITES, the supplier site.
• PROCESSING_LEAD_TIME – lead time applied to supply orders.
• MINIMUM_ORDER_QUANTITY / FIXED_LOT_MULTIPLIER / FIXED_ORDER_QUANTITY / MAXIMUM_ORDER_QUANTITY – order modifier rules.
• DELIVERY_CALENDAR_CODE – calendar governing delivery scheduling.
• REPLENISHMENT_METHOD, VMI_FLAG, ENABLE_VMI_AUTO_REPLENISH_FLAG – replenishment strategy and VMI configuration.
• ITEM_PRICE, SUPPLIER_ITEM_NAME, PURCHASING_UNIT_OF_MEASURE – commercial attributes.
• REFRESH_NUMBER, COLLECTED_FLAG, APPLIED – planning data refresh/collection control flags.

Surrogate key-like operational columns (LAST_UPDATE_DATE, CREATED_BY, REQUEST_ID, PROGRAM_ID) support audit and concurrent program tracing, while ATTRIBUTE1–15 provide DFF extensibility.

Common Use Cases and Queries

This table is queried to report item-source planning attributes, validate lead times and order modifiers feeding a plan, and extract supplier-level sourcing data for integration. A typical query joins the item, supplier, and site tables:

• Retrieve lead time and order modifiers for an item: SELECT supplier_id, supplier_site_id, processing_lead_time, minimum_order_quantity, fixed_lot_multiplier FROM msc_item_suppliers WHERE inventory_item_id = :item AND plan_id = :plan;
• List VMI-enabled item-supplier combinations: SELECT inventory_item_id, supplier_id FROM msc_item_suppliers WHERE vmi_flag = 'Y';
• Report replenishment methods per supplier site to analyze sourcing strategy.
• Reconcile collected vs. applied records using COLLECTED_FLAG and APPLIED during planning data refresh troubleshooting.

Because the table is populated by the collections/planning engine, reporting queries usually filter by PLAN_ID and SR_INSTANCE_ID to isolate a specific plan’s dataset.

Related Objects

MSC_ITEM_SUPPLIERS references several core planning dimension tables and is itself referenced through the planning engine. Significant related objects include:

• MSC_SYSTEM_ITEMS – joined on INVENTORY_ITEM_ID, PLAN_ID, SR_INSTANCE_ID, ORGANIZATION_ID for item master data.
• MSC_TRADING_PARTNERS – joined on SUPPLIER_ID for supplier details.
• MSC_TRADING_PARTNER_SITES – joined on SUPPLIER_SITE_ID for supplier site information.
• MSC_SUPPLIER_CAPACITIES – supplier capacity planning data commonly analyzed alongside.
• MSC_ITEM_SUPPLIERS can be related to sourcing-rule and approved supplier list tables (such as PO_APPROVED_SUPPLIER_LIST) for cross-referencing sourcing policies.
• Planning engine packages and concurrent programs (collections, plan generation) that populate and read this table during a planning run.

Together these objects provide the item-source context required for accurate supply generation, lead-time offsetting, and order-modifier application within ASCP.