Results for “planned_instance_id”

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

Overview

MSC_SEARCH_ACTIONS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the MSC (Advanced Supply Chain Planning) product family. In EBS 12.1.1 and 12.2.2 it retains a VALID status and is defined against the planning schema objects that support the Planner Workbench and exception messaging framework. The view presents the complete set of search criteria governing exception actions across one or more plans, exposing plan-level context together with exception grouping and exception type attributes so that callers can enumerate the filters that qualify a plan exception.

Conceptually, the view materializes the "search action" definition used when the planning engine reconciles exceptions and the messages generated against them. It does not store transactional planning data itself; instead it joins the plan tree hierarchy with the action tree hierarchy and the MFG_LOOKUPS translation table to yield human-readable meanings for stored lookup codes. Because the column list is padded with numerous NULL and TO_NUMBER(NULL) placeholders, the view conforms to a fixed positional contract expected by downstream consumers, even where a given UNION ALL branch does not populate every attribute. This makes it a predictable source for reports, concurrent programs, and integration extracts that must not vary in shape by branch.

Underlying Base Objects

The documented base objects for this view are FND_GLOBAL (PACKAGE), MFG_LOOKUPS (VIEW), MSC_ACTIONS_TREE_V (VIEW), MSC_ACTION_ORDERS_TREE_V (VIEW), MSC_GET_NAME (PACKAGE), and MSC_PLANS_TREE_V (VIEW). The view text builds its UNION ALL branches primarily from MSC_PLANS_TREE_V joined to MSC_ACTIONS_TREE_V and MFG_LOOKUPS.

• MSC_PLANS_TREE_V — supplies plan identity and execution context (PLAN_ID, COMPILE_DESIGNATOR, PLAN_TYPE, PLANNED_INSTANCE_ID, PLANNED_ORGANIZATION); only plans with a non-null PLAN_COMPLETION_DATE and DATA_COMPLETION_DATE are included.
• MSC_ACTIONS_TREE_V — provides the exception action attributes (EXCEPTION_GROUP, EXCEPTION_TYPE) linked on PLAN_ID.
• MFG_LOOKUPS — resolves lookup codes to MEANING for LOOKUP_TYPE values such as MSC_EXCEPTION_GROUP.
• MSC_ACTION_ORDERS_TREE_V, MSC_GET_NAME, FND_GLOBAL — supporting/utility objects referenced by the broader exception-action model.

Key Columns

• PLAN_ID — identifier of the plan the exception search rule belongs to.
• COMPILE_DESIGNATOR — the plan compile/designator name used to distinguish plan versions.
• PLAN_TYPE — classification of the plan.
• PLANNED_INSTANCE_ID — instance context of the planned organization.
• PLANNED_ORGANIZATION — organization code targeted by the plan.
• EXCEPTION_GROUP / derived group meaning — the exception group code and its MFG_LOOKUPS MEANING.
• EXCEPTION_TYPE / derived type meaning — the specific exception type and its translated meaning.
• Numerous NULL / TO_NUMBER(NULL) placeholder columns preserve positional alignment across UNION ALL branches.

Common Use Cases and Queries

Typical applications include exception reporting, validating exception-filter configuration per plan, and supplying integration extracts that must reconcile planner messages. A representative query lists the exception groups and types active for a given plan:

• SELECT plan_id, compile_designator, exception_group, exception_type FROM msc_search_actions_v WHERE plan_id = :p_plan_id ORDER BY 3, 4;
• SELECT DISTINCT compile_designator, exception_group FROM msc_search_actions_v WHERE planned_organization = :org;