Results for “safety_stock_code”

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

Overview

MSC_SAFETY_STOCKS_V is an APPS-owned reporting view within the Oracle Advanced Supply Chain Planning (MSC) module, valid in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents time-phased safety stock definitions maintained against planned items, joining the safety stock fact records in MSC_SAFETY_STOCKS to the corresponding item attribute records in MSC_SYSTEM_ITEMS. The view exposes the safety stock quantity—the column users most commonly search for as SAFETY_STOCK_QUANTITY—together with item descriptive attributes, organizational context, plan identifier, effectivity dating, and the internal identifiers for the source instance and planning run.

Because MSC is the planning product family, this view is primarily consumed by planning data extracts, custom reports, and reconciliation queries rather than by the transactional planning engine itself. It provides a flattened, human-readable projection of safety stock settings, including decoded text for the safety stock code and resolved project and task names, which makes it suitable for reporting layers and for integration interfaces that must publish supply chain planning parameters to external systems or downstream data warehouses.

Underlying Base Objects

The documented base objects referenced by this view are:

• MSC_SAFETY_STOCKS (synonym) — the driving table supplying organization, source instance, plan, item, effectivity date, safety stock code, safety stock quantity, and the standard WHO columns plus request, program, project, task, and planning group context.
• MSC_SYSTEM_ITEMS (synonym) — the item master source for planning, providing item name, description, unit of measure, and the safety stock code used in the decode, plus the SR inventory item identifier.
• MSC_GET_NAME (package) — a utility package whose TASK and PROJECT functions resolve internal project and task identifiers into descriptive names.

The join is performed on four key columns: SR_INSTANCE_ID, INVENTORY_ITEM_ID, ORGANIZATION_ID, and PLAN_ID. This composite key ensures that safety stock rows are matched only to item records belonging to the same planning source instance, organization, item, and plan, which is essential where the same item is planned across multiple organizations or in multiple plans.

Key Columns

• SAFETY_STOCK_QUANTITY — the safety stock value defined for the item, organization, and plan at the effectivity date.
• SAFETY_STOCK_CODE — the numeric indicator of the safety stock method; SAFETY_STOCK_CODE_TEXT decodes 1 as "NON-MRP PLANNED PERCENT," 2 as "MRP PLANNED PERCENT," and NULL otherwise.
• INVENTORY_ITEM_ID, SR_INVENTORY_ITEM_ID, ITEM_NAME, DESCRIPTION, UOM_CODE — item identification and descriptive attributes.
• ORGANIZATION_ID, SR_INSTANCE_ID, PLAN_ID — the planning context identifying source system, organization, and plan.
• EFFECTIVITY_DATE — aliased from PERIOD_START_DATE, indicating the period from which the safety stock quantity applies.
• PROJECT_ID, PROJECT_NAME, TASK_ID, TASK_NAME, PLANNING_GROUP — project and task accounting context, with names resolved by MSC_GET_NAME.
• ROW_ID — the row identifier derived from MSC_SAFETY_STOCKS.ROWID.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, and PROGRAM_UPDATE_DATE.

Common Use Cases and Queries

Typical scenarios include auditing safety stock levels by organization and plan, comparing safety stock against effectivity periods, and extracting item planning parameters for supply chain analytics. A common query filters by item and organization:

• SELECT inventory_item_id, organization_id, plan_id, effectivity_date, safety_stock_quantity, safety_stock_code_text FROM apps.msc_safety_stocks_v WHERE item_name = :item AND organization_id = :org ORDER BY effectivity_date;
• SELECT plan_id, COUNT(*), SUM(safety_stock_quantity) FROM apps.msc_safety_stocks_v GROUP BY plan_id;
• SELECT item_name, project_name, task_name, safety_stock_quantity FROM apps.msc_safety_stocks_v WHERE project_id IS NOT NULL;

Because the view resolves concatenated segments and names, it is well suited for ad hoc reporting without additional lookups.