Results for “msc_flp_supply_v”

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

Overview

MSC_FLP_SUPPLY_V is an APPS-owned database view within the Oracle Advanced Supply Chain Planning (MSC) product, delivered under Oracle E-Business Suite 12.1.1 and 12.2.2. As its description states, it presents a denormalized "view of supply information" drawn from the planning supply repository. The view is defined over MSC_SUPPLIES (aliased MR) joined to MSC_ITEMS (aliased MIF) on INVENTORY_ITEM_ID, and enriched through calls to the MSC_GET_NAME package. Because it consolidates supply transactions with descriptive item, organization, project, and task attributes, the view functions primarily as a reporting and integration layer rather than as a transactional object. Report authors, discoverer workbooks, and custom interfaces targeting planned supply frequently select from it to avoid re-implementing the decoding logic embedded in MSC_GET_NAME. The object is documented as VALID in the APPS schema.

Underlying Base Objects

The documented referenced base objects are MSC_GET_NAME (a package), MSC_PLANS, MSC_SUPPLIES, and MSC_SYSTEM_ITEMS, exposed as synonyms. In the view text, MSC_SUPPLIES supplies the supply rows (transaction, item, organization, plan, order, and date columns), while MSC_ITEMS supplies the item master context used for ITEM_NAME. MSC_GET_NAME is invoked repeatedly to resolve foreign-key style identifiers into readable values: lookup meaning for MRP_ORDER_TYPE, project and task names, organization code, item description, and supplier. MSC_PLANS and MSC_SYSTEM_ITEMS are referenced indirectly through these package calls and the planning data model, providing plan and item-instance resolution across source instances (SR_INSTANCE_ID). The equality join MIF.INVENTORY_ITEM_ID = MR.INVENTORY_ITEM_ID restricts output to items that exist in the item master, and the query returns no aggregation or filtering predicate beyond that join.

Key Columns

• TRANSACTION_ID — Identifier of the underlying supply transaction; also used as the order name for order type 5.
• INVENTORY_ITEM_ID, ORGANIZATION_ID, PLAN_ID, SR_INSTANCE_ID — Planning keys identifying item, organization, plan, and source instance.
• ORDER_TYPE — Numeric supply type, decoded to text via MSC_GET_NAME.LOOKUP_MEANING('MRP_ORDER_TYPE', ...).
• ORDER_NAME — DECODE of ORDER_TYPE; returns TO_CHAR(TRANSACTION_ID) for type 5, otherwise ORDER_NUMBER.
• NEW_SCHEDULE_DATE / ORDER_DATE, NEW_ORDER_QUANTITY / SUPPLY_QUANTITY — Scheduled date and quantity of the planned supply.
• NEW_PROCESSING_DAYS — The user's search term; the revised processing (lead) time in days applied to the supply.
• NEED_BY_DATE — Demand need-by date associated with the supply.
• ITEM_ORG, DESCRIPTION, UNIT_NUMBER — Derived item name concatenated with organization code, truncated item description, and unit number.
• PROJECT_NUMBER, TASK_NUMBER, SOURCE_ORG_SUPPLIER, DISPOSITION_ID, BY_PRODUCT_USING_ASSY_ID — Project/task context, source organization or supplier, disposition, and by-product assembly reference.

Common Use Cases and Queries

Typical scenarios include reviewing planned supply by plan and organization, reconciling processing lead times, tracing project or task supply, and identifying source organization versus supplier. A representative query filtered on the searched column is shown below.

• Supply review: SELECT ITEM_ORG, ORDER_NAME, ORDER_TYPE, NEW_SCHEDULE_DATE, NEW_ORDER_QUANTITY FROM MSC_FLP_SUPPLY_V WHERE PLAN_ID = :plan_id ORDER BY NEW_SCHEDULE_DATE;
• Processing days focus: SELECT INVENTORY_ITEM_ID, ORGANIZATION_ID, ORDER_TYPE, NEW_PROCESSING_DAYS FROM MSC_FLP_SUPPLY_V WHERE NEW_PROCESSING_DAYS IS NOT NULL;
• Source analysis: SELECT ORDER_NAME, SOURCE_ORG_SUPPLIER, PROJECT_NUMBER, TASK_NUMBER FROM MSC_FLP_SUPPLY_V WHERE SR_INSTANCE_ID = :instance_id;

Because MSC_GET_NAME performs per-row lookups, large unfiltered extracts should be constrained by PLAN_ID, ORGANIZATION_ID, or date range to control execution cost.