Search Results parent_value_pk




Overview
Explore in AI Chat

Overview

GMP_SR_OU_LE_V is a documented Oracle EBS view owned by the APPS schema within the GMP product family — Process Manufacturing Process Planning. It is registered as a VALID object in the ETRM metadata for both Oracle EBS 12.1.1 and 12.2.2. The view belongs to the family of "SR" (Setup/Reporting) views that expose a normalized, hierarchical column layout — a primary key column, a display value column, and the corresponding parent key/value pair. In Oracle EBS reporting and integration contexts, this shape is typically consumed by value-set-driven LOVs, flexfield hierarchies, and ETL extracts that need to walk a parent-child relationship between operating units (OU) and legal entities (LE).

The distinctive characteristic of GMP_SR_OU_LE_V, however, is that its documented view text resolves to a structural stub: a SELECT from SYS.DUAL with a WHERE 1 <> 1 predicate, projecting typed NULLs into every column. In other words, the view is defined but returns no rows in the base EBS installation. Reporting and integration objects that reference it therefore rely on customer-specific or product-specific override definitions supplied at implementation or patch time.

Underlying Base Objects

The documented ETRM metadata for this view lists a single referenced base object: DUAL (TABLE), owned by SYS. The full view text is:

Because the view is anchored on DUAL with a false predicate, its row-cardinality is defined as zero. The TO_NUMBER(NULL) casts on LEVEL_VALUE_PK and PARENT_VALUE_PK preserve the numeric datatype expected by downstream consumers, while the remaining columns are implicitly typed as VARCHAR2. The view is therefore best understood as a placeholder contract: it fixes the column names, order, and datatypes that Oracle EBS reporting components and third-party integrations expect, without committing to any particular underlying OU/LE resolution logic in the shipped code.

Key Columns

The column list defines a self-referencing hierarchy schema. It is the parent-key column that the user's search term — parent_value_pk — maps to:

  • LEVEL_VALUE_PK — numeric primary key of the current hierarchy node. Cast via TO_NUMBER(NULL) to enforce NUMBER typing.
  • LEVEL_VALUE — display value (typically the OU or LE name/identifier) associated with the current node.
  • PARENT_VALUE_PK — numeric foreign key that references the LEVEL_VALUE_PK of the parent node. This is the column searched for as "parent_value_pk" and is the pivot for recursive queries.
  • PARENT_VALUE — display value of the parent node, denormalized for convenient presentation in LOVs and reports.
  • ATTRIBUTE1 through ATTRIBUTE5 — five generic descriptive flexfield-style columns reserved for customer-specific extensions, segment qualifiers, or reporting attributes.

Common Use Cases and Queries

In standard Oracle EBS instances the view returns zero rows, so a direct query is primarily useful for verifying the view exists, is VALID, and exposes the expected column contract prior to a customer-specific override being applied. Typical diagnostic query:

  • SELECT level_value_pk, level_value, parent_value_pk, parent_value FROM apps.gmp_sr_ou_lev WHERE rownum <= 10;

Once an implementation replaces or overrides the DUAL stub with a real OU/LE hierarchy query, the view is consumed by reporting and integration logic that needs to resolve an operating unit to its owning legal entity, or vice versa. A recursive hierarchy walk using the parent link would resemble:

  • SELECT LEVEL, level_value, parent_value FROM apps.gmp_sr_ou_lev START WITH parent_value_pk IS NULL CONNECT BY PRIOR level_value_pk = parent_value_pk;

Common downstream scenarios include value-set LOV population for OU/LE prompts, ETL extraction for data warehouse dimensions, cross-validation of OU-to-LE mappings in Process Manufacturing planning reports, and integration payloads where a parent-child OU/LE structure must be transmitted to external systems.