Search Results order_type_text




Overview
Explore in AI Chat

Overview

APPS.MSC_EXC_DETAIL_RESOURCE_V is a reporting view in the Oracle EBS Advanced Supply Chain Planning (ASCP) schema, owned by APPS and defined under the FND Design Data object MSC.MSC_EXC_DETAIL_RESOURCE_V. It presents the resource-level detail records behind planning exceptions generated by the MSC engine — the same exception messages surfaced in the Planner Workbench, Exception Messages window, and related ASCP reports. Where MSC_EXCEPTION_DETAILS stores header-level exception rows, this view joins and flattens the resource, organization, item, and demand/supply attributes so that each row represents a single exception detail line attributed to a specific resource or department resource. It is read-only reference data maintained by the planning engine and is typically consumed for diagnostics, ad hoc reporting, and integration with downstream planning or exception-notification processes. The view status is VALID in both 12.1.1 and 12.2.2, and it is not referenced by any other database object, confirming its role as a leaf-level query object rather than a dependency of other schema components.

Underlying Base Objects

The view is defined over a combination of MSC planning tables and shared lookup objects, exposed through APPS synonyms:

These objects are joined within the view so that consumers do not need to reconstruct the exception-to-resource-to-item relationship manually.

Key Columns

Common Use Cases and Queries

The view is commonly queried to list exceptions by plan, organization, resource, or order type, and to reconcile required capacity against demand. The following sample retrieves resource-level exceptions for a plan, filtered by order type text:

  • SELECT plan_id, organization_code, resource_code, department_code, order_number, order_type_text, item_name, required_capacity, quantity, due_date FROM apps.msc_exc_detail_resource_v WHERE plan_id = :p_plan_id AND order_type_text = :p_order_type_text ORDER BY due_date;
  • Aggregate required capacity by resource: SELECT resource_code, SUM(required_capacity) FROM apps.msc_exc_detail_resource_v WHERE plan_id = :p_plan_id GROUP BY resource_code;
  • Exception exception roster: SELECT exception_type, exception_detail_id, order_number, buyer_name, planner_code FROM apps.msc_exc_detail_resource_v WHERE organization_id = :p_org_id;

Because the view joins multiple planning tables, queries should always be constrained by PLAN_ID or ORGANIZATION_ID to limit result sets on large ASCP instances.