Results for “planner_code_hidden”

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

Overview

The view MSC_ACTION_SUMMARY_V is an Advanced Supply Chain Planning (MSC) dictionary object owned by the APPS schema. Its documented purpose is to present exception group counts organized within the planning exception tree. In Oracle EBS 12.1.1 and 12.2.2, this view serves as the reporting and integration layer that feeds the Planning Exception Messages workbench, the horizontal/vertical exception summary region, and the tree-based navigation that planners use to drill from an exception group into the individual exception messages that generated it.

Rather than storing data itself, MSC_ACTION_SUMMARY_V is a decoding and aggregation view. It reads a single base query row from MSC_FORM_QUERY, translates internal numeric identifiers (exception codes, exception types, organization, resource, and department identifiers) into human-readable values, and exposes a consistent column list that the MSC planning UI and external report writers can consume directly. The view does not contain DML logic; it is read-only, and any customization should be performed by creating a separate wrapper view rather than modifying the APPS-owned definition.

Underlying Base Objects

The documented referenced base objects are:

• MSC_FORM_QUERY (SYNONYM) — the primary driver table supplying all NUMBER, CHAR, and QUERY_ID columns from which the view derives exception counts, group identity, and hierarchical ordering.
• MSC_GET_NAME (PACKAGE) — a utility package whose functions (LOOKUP_MEANING, ITEM_NAME, ORG_CODE, PROJECT, TASK, DEPARTMENT_CODE, RESOURCE_CODE, SUPPLIER) resolve internal keys into display names.
• MSC_PLANS (SYNONYM) — supplies the plan and COMPILE_DESIGNATOR context that ties each exception summary row to a specific plan compilation.

The relationship is effectively one row of MSC_FORM_QUERY binding to one plan in MSC_PLANS, with MSC_GET_NAME applied column-by-column to enrich the output.

Key Columns

The view exposes audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY), plan context via COMPILE_DESIGNATOR and QUERY_ID, and a set of decoded descriptive columns:

• Exception group identifier and its decoded type via MSC_GET_NAME.LOOKUP_MEANING('MRP_EXCEPTION_CODE_TYPE', NUMBER2) and the exception version label.
• Item identity resolved by ITEM_NAME, and organization resolved by ORG_CODE.
• Project and task context from PROJECT and TASK.
• Department line code — produced by MSC_GET_NAME.DEPARTMENT_CODE(2, MFQ.NUMBER9, MFQ.NUMBER4, MFQ.NUMBER14, MFQ.NUMBER15) using NVL(MFQ.CHAR7, ...), which is the column users reach when searching for department_line_code. It identifies the routing department associated with the exception.
• Resource code and supplier name from RESOURCE_CODE and SUPPLIER.

Two trailing DECODE expressions compute the sort order of the exception tree, mapping raw exception codes to display sequence numbers.

Common Use Cases and Queries

Typical uses include validating exception group counts per plan, building custom exception dashboards, and reconciling the Planning Exception Messages form against extracted data. For example:

• Listing all exception groups for a plan: SELECT COMPILE_DESIGNATOR, QUERY_ID, NUMBER2 FROM MSC_ACTION_SUMMARY_V WHERE COMPILE_DESIGNATOR = :plan;
• Filtering department-level exceptions: SELECT QUERY_ID, DEPARTMENT_LINE_CODE FROM MSC_ACTION_SUMMARY_V WHERE DEPARTMENT_LINE_CODE = :dept;
• Joining to the base query table for drill-down counts: SELECT v.QUERY_ID, f.NUMBER2 FROM MSC_ACTION_SUMMARY_V v, MSC_FORM_QUERY f WHERE v.QUERY_ID = f.QUERY_ID;

Because COUNT columns are pre-aggregated in MSC_FORM_QUERY, queries against the view are inexpensive, making it suitable for concurrent programs and BI Publisher extracts in both 12.1.1 and 12.2.2.