Search Results planner_code_hidden




Overview
Explore in AI Chat

Overview

APPS.MSC_ACTION_SUMMARY_V is a supplementary database view in the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module, owned by the APPS schema. Its FND Design Data identifier is MSC.MSC_ACTION_SUMMARY_V, and its status is VALID in both 12.1.1 and 12.2.2. Oracle classifies this object as a supplementary view whose purpose is to simplify forms coding — specifically, it aggregates planning exception and action messages so that the Planner Workbench and related Action Summary forms can present consolidated exception information without directly joining the underlying planning tables. Oracle explicitly cautions that this view is not intended for direct customer query or update, and that its definition may change dramatically in subsequent minor or major releases. Consequently, any custom report or integration that consumes this view must be treated as version-sensitive and should be re-validated after patching or upgrades.

Underlying Base Objects

The documented reference metadata identifies three base dependencies: the synonym MSC_FORM_QUERY, the package MSC_GET_NAME, and the synonym MSC_PLANS. MSC_FORM_QUERY is the form-level query construct that supplies filtered exception rows for the Action Summary user interface, while MSC_PLANS anchors the plan context (PLAN_ID, COMPILE_DESIGNATOR) that scopes the rows returned. The MSC_GET_NAME package is invoked to resolve descriptive display values — for example, translating codes such as PLANNER_CODE, CATEGORY_ID, DEPARTMENT_ID, and RESOURCE_ID into human-readable names (PLANNER_CODE_HIDDEN, CATEGORY_NAME, PLANNING_GROUP, RESOURCE_CODE, and so on) used in the summary grids. The view therefore sits as a forms-supporting projection layer over the MSC planning exception tables, joining key, description, and hidden-sort columns into a single flattened structure.

Key Columns

In the context of the search term "department_line_code," the DEPARTMENT_LINE_CODE column (VARCHAR2(4000)) identifies the specific production line within a department against which a resource-related exception is raised, enabling line-level granularity in the Action Summary display.

Common Use Cases and Queries

The primary uses are Planner Workbench exception drill-down, Action Summary reporting, and diagnostic analysis of resource and department bottlenecks. A representative query groups exceptions by department line:

  • SELECT plan_id, organization_code, department_class, department_line_code, resource_code, exception_type_text, SUM(exception_count) FROM apps.msc_action_summary_v GROUP BY plan_id, organization_code, department_class, department_line_code, resource_code, exception_type_text;
  • Filter by a specific plan and organization to list open exceptions: SELECT * FROM apps.msc_action_summary_v WHERE plan_id = :plan_id AND organization_id = :org_id;
  • Join on DEPARTMENT_LINE_CODE to a resource/department view for line-capacity attribution in custom planning dashboards.

Because this is a forms-supporting view and Oracle discourages direct querying, custom usage should be limited to read-only reporting, wrapped behind a controlled interface, and validated against each target release (12.1.1 versus 12.2.2) before deployment.