Results for “level_value_pk”

50+ results




Overview
Explore in AI Chat

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

Overview

GMP_SR_LE_BG_V is a view owned by the APPS schema in Oracle E-Business Suite, registered under the GMP product family, Process Manufacturing Process Planning. In the EBS object registry it is recorded with a status of VALID and is classified as a view (Object Type: VIEW). The name suggests a role in the Standard Report (SR) lineage of the GMP module — specifically a structure that exposes level/level-value definitions used by a background (BG) reporting engine — but the documented definition does not carry any real business logic: the view text resolves to a single SELECT from SYS.DUAL with the predicate WHERE 1 <> 1.

This is the defining characteristic of the object. It is a placeholder or stub view: it is a syntactically valid view that defines a fixed column list (LEVEL_VALUE_PK, LEVEL_VALUE, PARENT_VALUE_PK, PARENT_VALUE, and ATTRIBUTE1 through ATTRIBUTE5) but yields zero rows under all circumstances. It exists to declare an interface — a column contract — for reporting or integration code that expects a hierarchy/level result set, without binding that code to a specific physical query. Because it returns no data, it plays no role in operational reporting and is normally encountered only during metadata inspection, dependency analysis, or as a compile-time reference in the APPS schema.

Underlying Base Objects

The only documented base object referenced by GMP_SR_LE_BG_V is SYS.DUAL, the standard Oracle one-row/one-column dummy table. DUAL is present in every Oracle database and is used here purely to make the view definition legal — a SELECT requires a FROM clause, and DUAL satisfies that requirement without touching any application data.

The ETRM metadata records no dependency on any GMP or other application table. There is therefore no join path, no foreign key relationship, and no row source that could populate the view. Practically, this means the view is independent of the Process Manufacturing data model: it will not change state as planning, batch, or level data changes, because it never reads such data. Any expectation that GMP_SR_LE_BG_V exposes live level or hierarchy records is not supported by the documented definition. Where the view is used as a base for other objects, those dependent objects would themselves inherit the empty result set unless they reference the view only for its column shape.

Key Columns

All nine columns are NULL-constant projections in the view text, so each returns a SQL NULL for every (non-existent) row. Their names, however, convey the intended shape of the interface:

  • LEVEL_VALUE_PK — the primary-key surrogate for a level value. As defined here, it is cast to NUMBER via TO_NUMBER(NULL), establishing that callers should expect a numeric identifier.
  • LEVEL_VALUE — the descriptive or display value associated with the level; typed as a generic NULL (character semantics).
  • PARENT_VALUE_PK — the numeric primary key of the parent node in the level hierarchy, mirroring LEVEL_VALUE_PK.
  • PARENT_VALUE — the parent node's display or descriptive value.
  • ATTRIBUTE1 through ATTRIBUTE5 — five generic global attributes declared as undefined NULLs, following the standard EBS extensibility convention for user- or implementation-defined values.

The consistent pairing of a *_PK column with a corresponding value column indicates a parent-child hierarchy contract: a row would represent one level value and point to its parent. Users searching for "level_value_pk" will find that this view uses the column, but cannot obtain data from it.

Common Use Cases and Queries

Because the view is a deliberately empty stub, its practical uses are limited to metadata and compatibility scenarios rather than reporting. Typical cases include:

  • Verifying the existence and validity of the object in an upgraded environment (12.1.1 or 12.2.2) during ETRM-style dependency reviews.
  • Serving as a compile-time interface so that dependent views, packages, or report definitions resolve against a known column list.
  • Documenting the intended hierarchy output for the Standard Report / background engine without committing to a source query.

A simple inspection query confirms both the schema and the empty behavior:

SELECT LEVEL_VALUE_PK, LEVEL_VALUE, PARENT_VALUE_PK, PARENT_VALUE, ATTRIBUTE1
FROM APPS.GMP_SR_LE_BG_V;
-- Returns no rows.

A column-shape check is equally straightforward:

SELECT column_name, data_type
FROM all_tab_columns
WHERE owner = 'APPS' AND table_name = 'GMP_SR_LE_BG_V';

Because no application table feeds the view, no query can be rewritten to retrieve production hierarchy data from it. For actual level-value content, the underlying Process Manufacturing tables and their associated reporting views must be used instead.