Search Results level_value_pk




Overview
Explore in AI Chat

Overview

GMP_SR_BG_ALL_V is a view in the APPS schema belonging to the GMP (Process Manufacturing Process Planning) product family within Oracle E-Business Suite 12.1.1 and 12.2.2. The view is registered as VALID in the EBS data dictionary, but its definition is notable in that it does not select from any operational Process Manufacturing table. Instead, it is defined entirely over SYS.DUAL and carries a predicate of WHERE 1 <> 1, which guarantees that the view always returns zero rows.

Because it is defined as an empty structure, GMP_SR_BG_ALL_V functions as a placeholder or "stub" object rather than a reporting or integration source. It exposes a fixed column projection of level/hierarchy attributes — LEVEL_VALUE_PK, LEVEL_VALUE, PARENT_VALUE_PK, PARENT_VALUE, and ATTRIBUTE1 through ATTRIBUTE5 — all of which are cast to NULL. The view therefore serves as a schema-compatible template for a hierarchical (parent/child level) data structure that is not populated in the delivered product.

Underlying Base Objects

The only documented base object referenced by GMP_SR_BG_ALL_V is SYS.DUAL. Each column in the SELECT list is a literal NULL, explicitly typed using TO_NUMBER(NULL) for the primary-key columns (LEVEL_VALUE_PK, PARENT_VALUE_PK) and untyped NULL for the remaining character-oriented columns. The DUAL reference supplies a single-row result set that is eliminated by the WHERE 1 <> 1 predicate, so the view materializes no data.

This construction pattern is commonly used in EBS when a view must exist for form, concurrent program, or interface compilation purposes but the delivered implementation does not require source data. In such cases, the view preserves the expected column names, data types, and ordering so that dependent code compiles and executes without error, while returning an empty result set at runtime.

Key Columns

  • LEVEL_VALUE_PK — Numeric primary key of a hierarchy level, cast via TO_NUMBER(NULL). This is the column most frequently associated with the "level_value_pk" search term. It is intended to uniquely identify a level node within a parent/child structure.
  • LEVEL_VALUE — The descriptive or code value of the hierarchy level associated with LEVEL_VALUE_PK.
  • PARENT_VALUE_PK — Numeric primary key of the parent node, establishing the self-referencing relationship required for hierarchical (tree) traversal.
  • PARENT_VALUE — The descriptive or code value of the parent node.
  • ATTRIBUTE1 – ATTRIBUTE5 — Five generic descriptive flexfield-style columns reserved for client-specific or implementation-specific extensions of the level record.

All columns are projected as NULL, confirming that no hierarchy data is stored or derived by the view in the standard installation.

Common Use Cases and Queries

Because the view is always empty, its practical uses are limited to structural validation, dependency checking, and placeholder substitution. Typical scenarios include confirming that the object exists and is VALID in a given environment, verifying column availability before building an interface, and providing a compile-safe definition for dependent PL/SQL or form logic.

A basic structural query confirms the view resolves and returns no rows:

  • SELECT level_value_pk, level_value, parent_value_pk, parent_value FROM apps.gmp_sr_bg_all_v;

To inspect the delivered definition and confirm the DUAL-based, always-false predicate:

  • SELECT text FROM all_views WHERE view_name = 'GMP_SR_BG_ALL_V';

To verify object status and column metadata in the data dictionary:

  • SELECT object_name, status FROM all_objects WHERE object_name = 'GMP_SR_BG_ALL_V';
  • SELECT column_name, data_type FROM all_tab_columns WHERE table_name = 'GMP_SR_BG_ALL_V';

Customers requiring a populated hierarchy view typically extend or replace this stub with a custom view selecting from their actual level/background tables, preserving the documented column interface so that existing dependent objects continue to function. Any such replacement should retain the column names and numeric typing of the primary-key columns to avoid breaking downstream references to LEVEL_VALUE_PK and PARENT_VALUE_PK.