Results for “exception_group”

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

Overview

MSC_ACTIONS_TREE_V is a reporting view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the MSC product family — Advanced Supply Chain Planning — and is documented as a VALID object whose stated purpose is to "show all the exceptions in the tree." In practice the view exposes the hierarchical set of planning exceptions and action recommendations presented to the planner in the Advanced Supply Chain Planning workbench, flattened into a single relational result set that can be queried directly for reporting, analytics, or integration purposes.

The view is a UNION ALL of two distinct data sources. The first selects directly from the MSC_ITEM_EXCEPTIONS table, retrieving item-level exceptions tied to a plan, version, exception group, and exception type. The second derives recommendation-type exceptions from planned supplies and system item attributes, applying the recommendation horizon configured by the user in MSC_WORKBENCH_DISPLAY_OPTIONS. This dual construction is what allows the view to represent both pre-existing exception records and dynamically calculated supply recommendations within a single tree.

Underlying Base Objects

The documented dependencies of MSC_ACTIONS_TREE_V are MSC_ITEM_EXCEPTIONS, MSC_PLANS, MSC_SUPPLIES, MSC_SYSTEM_ITEMS, and MSC_WORKBENCH_DISPLAY_OPTIONS (all referenced through APPS synonyms), together with the MSC_GET_NAME and FND_GLOBAL packages. MSC_ITEM_EXCEPTIONS supplies the exception rows in the first branch of the union. MSC_SUPPLIES and MSC_SYSTEM_ITEMS are joined in the second branch to identify planned orders and the make/buy attributes of the affected items, while MSC_PLANS constrains the query to the active plan and its planning horizon. MSC_WORKBENCH_DISPLAY_OPTIONS is the source of the user-specific recommendation window, and FND_GLOBAL.USER_ID is used to ensure each planner sees only their own display preferences.

Key Columns

• PLAN_ID — Identifier of the plan the exception or recommendation belongs to. In the supply-based branch it is taken directly from MSC_SUPPLIES.
• VERSION — Plan version for exception rows. For recommendation rows this column is populated with TO_NUMBER(NULL), reflecting that recommendations are not version-specific.
• EXCEPTION_GROUP — Grouping of the exception. In the supply branch it is hard-coded to 10.
• EXCEPTION_TYPE — Numeric type code. Where the exception is derived from a supply, a DECODE expression maps order type, make/buy flag, souring, and routing attributes to distinct codes such as 101, 102, 103, and 104.
• ORGANIZATION_ID — Inventory organization in which the exception or recommendation applies.
• SR_INSTANCE_ID — Source system instance identifier, supporting multi-instance or multi-organization planning configurations.

Common Use Cases and Queries

Because the view presents exceptions and recommendations in a uniform shape, it is frequently used as the data source for planner workbench extracts and dashboard reporting. A typical query filters by plan and organization:

SELECT plan_id, exception_group, exception_type, organization_id, sr_instance_id
FROM   apps.msc_actions_tree_v
WHERE  plan_id = :p_plan_id
AND    organization_id = :p_org_id
ORDER BY exception_group, exception_type;

A second common pattern aggregates exception volumes by type to identify recurring supply problems:

SELECT exception_type, COUNT(*)
FROM   apps.msc_actions_tree_v
WHERE  plan_id = :p_plan_id
GROUP BY exception_type
ORDER BY COUNT(*) DESC;

It should be noted that the second branch of the view depends on the runtime value of FND_GLOBAL.USER_ID, so result sets can differ between users based on their workbench display options, particularly the recommendation days horizon.