Results for “unmet_quantity”

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

Overview

MSC_ORDERS_V is a consolidated reporting view owned by the APPS schema in Oracle E-Business Suite, defined within the Advanced Supply Chain Planning (MSC) product family. Its documented purpose is to present, in a single unified result set, all supplies, demands, and sales orders relevant to the planning engine. In Oracle EBS 12.1.1 and 12.2.2 the view is shipped with a VALID status and is commonly used as a readable interface over the heavily normalized planning tables, allowing query tools, custom reports, and integration programs to retrieve planning order information without having to reconcile the supply and demand structures manually.

Because MSC_ORDERS_V unions records originating from more than one planning source and decorates them with descriptive attributes resolved through helper packages, it functions as a semantic layer rather than a simple projection. Analysts and developers use it to inspect how the Advanced Supply Chain Planning engine has classified each order — whether it is treated as a supply, a demand, or a sales order — and to read the action recommendations the planner has generated for that record.

Underlying Base Objects

The view text combines the MSC_SUPPLIES table (referenced in the definition as alias SUP) with MSC_DEMANDS, joining each to MSC_SYSTEM_ITEMS (MSI) for item and organization context. The resulting rows are enriched by several referenced objects documented in the ETRM metadata for 12.2.2:

• MSC_SUPPLIES (SYNONYM) and MSC_DEMANDS (SYNONYM) — the primary planning supply and demand records.
• MSC_SYSTEM_ITEMS (SYNONYM) — supplies inventory item identifiers, organization code, item name, and item attributes.
• MSC_ITEM_CATEGORIES (SYNONYM) — category information used by the naming helpers.
• MSC_PLANS (SYNONYM) — plan definition context for the rows returned.
• MSC_PROCESS_EFFECTIVITY (SYNONYM) and MSC_DMD_SCN_METRICS (SYNONYM) — additional planning and metrics context.
• MFG_LOOKUPS (VIEW) — resolves order type and disposition status meanings.
• MSC_GET_NAME (PACKAGE) — resolves action codes, department codes, and descriptive names.
• MSC_UTIL, MSC_DRP_UTIL, and MSC_REL_PLAN_PUB (PACKAGES) — supporting planning utilities referenced during resolution.

The two halves of the union are distinguished by a leading literal — 'MSC_SUPPLIES' for supply rows — which allows consumers to identify the source of each record.

Key Columns

The projection exposes a broad set of columns. Notable examples include:

• Source discriminator and identifiers: the leading type literal, ROWID, TRANSACTION_ID, SR_INSTANCE_ID, and PLAN_ID.
• Item and organization context: INVENTORY_ITEM_ID, ORGANIZATION_ID, ORGANIZATION_CODE, and ITEM_NAME.
• Action and status: the MSC_GET_NAME.ACTION result, DISPOSITION_STATUS_TYPE, IMPLEMENT_STATUS_CODE, and the MFG_LOOKUPS meaning.
• Dates: NEW_SCHEDULE_DATE, OLD_SCHEDULE_DATE, NEW_WIP_START_DATE, NEW_ORDER_PLACEMENT_DATE, FIRST_UNIT_START_DATE, LAST_UNIT_START_DATE, LAST_UNIT_COMPLETION_DATE, NEW_DOCK_DATE, FIRM_DATE, and IMPLEMENT_DATE.
• Quantities and rates: NEW_ORDER_QUANTITY, OLD_ORDER_QUANTITY, FIRM_QUANTITY, IMPLEMENTED_QUANTITY, QUANTITY_IN_PROCESS, DAILY_RATE, and their IMPLEMENT equivalents.
• Order attributes: ORDER_NUMBER (or TRANSACTION_ID when ORDER_TYPE is 5), ORDER_TYPE, LINE_ID, RESCHEDULE_FLAG, RESCHEDULE_DAYS, FIRM_PLANNED_TYPE, and RELEASE_STATUS.

Several columns are returned as TO_NUMBER(NULL), serving as placeholders that keep the union column list consistent between the supply and demand branches.

Common Use Cases and Queries

Typical scenarios include reviewing planning recommendations, comparing current versus proposed order dates and quantities, and auditing how the planning engine has classified individual orders. A simple extraction filtered by plan is:

• SELECT transaction_id, inventory_item_id, organization_code, order_type, disposition_status_type, new_schedule_date, new_order_quantity FROM apps.msc_orders_v WHERE plan_id = :plan_id;
• SELECT order_number, item_name, firm_quantity, firm_date, implement_quantity FROM apps.msc_orders_v WHERE disposition_status_type IS NOT NULL ORDER BY item_name;

Because the view depends on package calls such as MSC_GET_NAME.ACTION and MSC_GET_NAME.DEPARTMENT_CODE, performance is sensitive to row volume; qualifying queries by PLAN_ID, ORGANIZATION_ID, or a date range is recommended. The view is read-only and should be treated as a reporting and integration surface rather than a table targeted by DML.