Search Results msc_action_orders_tree_v




Overview
Explore in AI Chat

Overview

MSC_ACTION_ORDERS_TREE_V is an Oracle E-Business Suite 12.1.1 / 12.2.2 database view owned by the APPS schema and flagged as VALID. It belongs to the MSC — Advanced Supply Chain Planning product family and is designed to present the recommendations (action orders) generated by the planning engine in a hierarchical, tree-oriented form. The view's stated purpose in the ETRM documentation is: "This view shows the recommendations in the tree." In practice, it functions as the data source behind the Planner Workbench Action Orders / recommendations tree, exposing a uniform row set that the application can format into parent-child nodes so planners can drill from a plan down into individual order recommendations.

Because it is a view rather than a table, it performs no storage of its own; it is a read-only projection assembled at query time. It plays a reporting and integration role: external reports, custom concurrent programs, and personalizations can query the view to retrieve recommendation details without duplicating the planning engine's internal extraction logic. The view is composed from two principal segments joined by UNION ALL: the first selects exception-driven recommendations from MSC_EXCEPTION_DETAILS_V, and subsequent segments derive new order placement recommendations from MSC_SUPPLIES, MSC_SYSTEM_ITEMS, MSC_PLANS, and MSC_WORKBENCH_DISPLAY_OPTIONS.

Underlying Base Objects

The documented base objects referenced by the view are:

  • FND_GLOBAL (PACKAGE) — supplies the runtime USER_ID used to filter display options to the current user.
  • MSC_EXCEPTION_DETAILS_V (VIEW) — source of plan exceptions and their associated item, project, task, resource, and department attributes.
  • MSC_GET_NAME (PACKAGE) — used for name resolution during view evaluation.
  • MSC_PLANS (SYNONYM) — provides PLAN_ID and PLAN_START_DATE for date-window filtering.
  • MSC_ROUTINGS (SYNONYM) — routing information referenced for resource-related recommendations.
  • MSC_SUPPLIES (SYNONYM) — the primary supply/order records from which new order placement recommendations are derived.
  • MSC_SYSTEM_ITEMS (SYNONYM) — item master attributes such as PURCHASING_ENABLED_FLAG, PLANNING_MAKE_BUY_CODE, organization code, and item name.
  • MSC_WORKBENCH_DISPLAY_OPTIONS (SYNONYM) — user-level display preferences, notably RECOMMENDATION_DAYS, which bounds the recommendation horizon.

The view is not a simple join; it assembles rows from multiple planners' internal structures, which is why it depends on a relatively large set of MSC synonyms and the FND_GLOBAL session context.

Key Columns

The column list is the union of the projected attributes across both segments. Notable columns include:

Collectively these columns let consumers reconstruct the tree hierarchy and identify each recommendation's planning context.

Common Use Cases and Queries

Typical uses include building custom Action Orders reports, feeding recommendations into downstream scheduling systems, and supporting Workbench-style drill-downs outside the standard form. A representative query retrieving buy recommendations for a specific plan is:

  • SELECT plan_id, organization_code, item_name, exception_type, resource_code, batchable_flag FROM msc_action_orders_tree_v WHERE plan_id = :p_plan_id AND sr_instance_id = :p_sr_instance ORDER BY organization_code, item_name;
  • SELECT exception_type, COUNT(*) FROM msc_action_orders_tree_v WHERE plan_id = :p_plan_id GROUP BY exception_type; — useful for validating the mix of recommendation types (including the 101 and 102 constants).
  • SELECT * FROM msc_action_orders_tree_v WHERE inventory_item_id = :p_item AND organization_id = :p_org; — to inspect all action orders for a single item/organization.

Because the view applies FND_GLOBAL.USER_ID-based filtering through MSC_WORKBENCH_DISPLAY_OPTIONS and a date window tied to RECOMMENDATION_DAYS, results depend on the connected user's display options; queries executed as a different user may return differing recommendation sets. Consumers should therefore supply plan and item predicates and be aware that the view reflects the planning engine's extraction, not live transaction data.