Search Results msc_planned_resources_v




Overview
Explore in AI Chat

Overview

MSC_PLANNED_RESOURCES_V is a database view owned by the APPS schema in Oracle E-Business Suite, defined within the Advanced Supply Chain Planning (MSC) product family. As its description states, the view exposes all resources used in a plan, presenting the resource definitions, capacities, utilization factors, and planning attributes that the planning engine has resolved for a given plan run. In EBS 12.1.1 and 12.2.2 the object retains a VALID status and is treated as a reporting and integration surface rather than a transactional table, meaning it is read-only in practice and is populated implicitly by the planning data that resides in the MSC tables.

The view is most commonly consumed by custom reports, concurrent program extracts, and downstream integrations that need to enumerate the resources associated with a plan without navigating the more granular MSC base tables. It acts as a denormalized projection, joining resource, department, and plan context into a single row per planned resource.

Underlying Base Objects

The view is defined over several documented base objects, most of which are synonyms pointing to the underlying MSC tables. These are:

The SELECT text shows that RES is the driving row source, and the view calls MSC_GET_NAME.ORG_CODE, MSC_GET_NAME.DEPARTMENT_CODE, and MSC_GET_NAME.LOOKUP_MEANING to translate internal IDs into human-readable values. Several trailing columns are emitted as TO_NUMBER(NULL) or NULL placeholders, which preserves a fixed column contract for consumers while some underlying attributes are not materialized.

Key Columns

The view exposes a broad set of resource attributes. Significant columns include:

Common Use Cases and Queries

Typical scenarios include capacity review reports, resource utilization dashboards, and integrations that feed planning output into external scheduling or MES systems. A representative query filtering to a single plan is:

  • SELECT resource_code, department_code, resource_type, max_rate, utilization, efficiency FROM msc_planned_resources_v WHERE plan_id = :plan_id AND organization_id = :org_id;
  • SELECT resource_code, resource_cost, unit_of_measure FROM msc_planned_resources_v WHERE plan_id = :plan_id ORDER BY resource_code;
  • SELECT department_code, COUNT(*) FROM msc_planned_resources_v WHERE plan_id = :plan_id GROUP BY department_code;

Because the view calls MSC_GET_NAME functions per row, large extracts benefit from restrictive predicates on PLAN_ID and ORGANIZATION_ID to limit the function-call overhead. Joins back to MSC base tables should be performed on RESOURCE_ID and ORGANIZATION_ID to preserve plan context.