Results for “tree_node”

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

Overview

MSC_TREE_SELECTION_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the MSC – Advanced Supply Chain Planning product. It exposes selection criteria used to drive tree-based selection logic within Advanced Supply Chain Planning (ASCP) and related planning engines. In EBS 12.1.1 and 12.2.2 the object carries a VALID status and is defined solely as a view, meaning it stores no data of its own and instead presents a denormalized, joined projection of two underlying criteria tables. Its principal value lies in flattening the relationship between a selection criterion record and the associated field definition, thereby supplying consumers with both the field prompt and the criteria values in a single row.

Because the view surfaces criteria at a granular level, it is typically consumed by reporting tools, custom concurrent programs, and integration routines that need to understand how planning selections were configured without navigating the normalized source tables directly.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through synonyms:

• MSC_SELECTION_CRITERIA — aliased as S, this is the primary driver table holding the actual criteria rows, including field names, conditions, and from/to values.
• MSC_CRITERIA — aliased as C, this table provides the field metadata, notably the field prompt.

The join is performed on two matching columns: C.FOLDER_OBJECT = S.FOLDER_OBJECT and C.FIELD_NAME = S.FIELD_NAME. This restricts output to criteria whose folder object and field name have a corresponding definition in MSC_CRITERIA. The relationship is therefore effectively an inner join; criteria rows lacking a matching field definition in MSC_CRITERIA are excluded from the result set.

Key Columns

The view projects the following columns, combining identifying keys from the selection criteria with descriptive metadata from the criteria definition:

• SEARCH_QUERY_ID — identifier of the parent search query to which the criterion belongs.
• FIELD_PROMPT — the user-facing prompt for the field, sourced from MSC_CRITERIA.
• FIELD_NAME — the internal name of the field being constrained.
• FIELD_TYPE — the data type or category of the field.
• CONDITION — the operator applied to the criterion (for example, equals, between, or similar).
• FROM_FIELD and FROM_FIELD_VALUE — the source field and its value representing the lower or starting bound of the criterion.
• TO_FIELD — the source field representing the upper or ending bound; this is the column most closely associated with the user search term "to_field".
• TO_FIELD_VALUE — the value applied to the TO_FIELD, completing range-style criteria.
• TREE_NODE — identifies the tree node context in which the criterion applies.

The catalog metadata also documents simplified column aliases (FIELD, FROM_VALUE, TO_VALUE), which correspond to the prompt and value columns above.

Common Use Cases and Queries

Typical usage centers on auditing or replicating planning selection definitions. A common pattern retrieves all criteria for a given search query:

• Reporting on configured selection criteria for a search query, joining FIELD_PROMPT for readability.
• Extracting range criteria by filtering on TO_FIELD IS NOT NULL to isolate bounded selections.
• Integration scenarios that reconstruct planning selections in external systems.

A representative query is:

SELECT SEARCH_QUERY_ID, FIELD_PROMPT, FIELD_NAME, CONDITION, FROM_FIELD_VALUE, TO_FIELD, TO_FIELD_VALUE, TREE_NODE FROM APPS.MSC_TREE_SELECTION_V WHERE SEARCH_QUERY_ID = :p_query_id;

Because the view is read-only and joins only two criteria tables, it performs efficiently as a reporting source, though consumers should account for the inner-join behavior that omits orphaned criteria rows.