Search Results pattern_id




Overview
Explore in AI Chat

Overview

The HR_COMPONENTLESS_PATTERNS_V view is an Oracle E-Business Suite database object owned by the APPS schema and classified under the PER (Human Resources) product module. It holds a status of VALID and is documented as being primarily used to support the user interface. In the context of Oracle EBS 12.1.1 and 12.2.2, this view does not store data of its own; instead, it presents a filtered perspective derived from the underlying pattern definition tables used by the HR pattern construction framework.

The view isolates a specific subset of pattern records — those patterns that are not themselves components of a larger pattern structure. Because the underlying HR_PATTERN_CONSTRUCTIONS table describes hierarchical relationships among patterns (that is, which pattern acts as a component of another), the view surfaces only those patterns with no corresponding row in that relationship table. In ETRM reporting and integration terms, it functions as a convenience query surface that eliminates the need for application code or reports to reproduce the external-join filtering logic embedded in its definition.

Underlying Base Objects

The documented metadata identifies two referenced base objects, both resolved through synonyms in the APPS schema:

  • HR_PATTERNS (SYNONYM) — the primary master table of HR pattern definitions, aliased as PAT in the view text. This supplies both the pattern identifier and the pattern name.
  • HR_PATTERN_CONSTRUCTIONS (SYNONYM) — the construction table, aliased as CON, which records component relationships between patterns.

As shown in the view definition, the two objects are joined on the pattern identifier: PAT.PATTERN_ID = CON.COMPONENT_PATTERN_ID (+). The (+) symbol denotes an Oracle outer join, and the additional predicate CON.COMPONENT_PATTERN_ID IS NULL restricts output to rows where no matching construction record exists. This composes an anti-join pattern that yields only componentless patterns.

Key Columns

The view exposes exactly two documented columns:

  • PATTERN_ID — the unique identifier of the pattern, sourced from HR_PATTERNS. This is the value users typically search for when they enter pattern_id in a query, and it corresponds to the join key used against HR_PATTERN_CONSTRUCTIONS.
  • PATTERN_NAME — the descriptive name of the pattern, also sourced from HR_PATTERNS, used for display and reference in the user interface.

Because the projection is deliberately narrow, the view carries no construction or component attributes; only the identity and label of the surviving pattern records are returned.

Common Use Cases and Queries

The view is typically used to enumerate patterns that can serve as top-level or standalone definitions within the HR pattern framework, such as when populating list-of-values elements or validating that a candidate pattern is not already consumed as a component elsewhere.

A straightforward listing of all componentless patterns:

  • SELECT pattern_id, pattern_name FROM apps.hr_componentless_patterns_v ORDER BY pattern_name;

Retrieving a single pattern by its identifier, which matches the common “pattern_id” search:

  • SELECT pattern_name FROM apps.hr_componentless_patterns_v WHERE pattern_id = :p_pattern_id;

Joining the view back to HR_PATTERN_CONSTRUCTIONS to confirm the anti-join behavior:

  • SELECT v.pattern_id, v.pattern_name FROM apps.hr_componentless_patterns_v v WHERE NOT EXISTS (SELECT 1 FROM apps.hr_pattern_constructions c WHERE c.component_pattern_id = v.pattern_id);

These queries reflect the view's intended role: a read-only, interface-supporting object that simplifies identification of patterns which are not components of any other pattern.