Results for “cz_rpobjecttypes_lkv”

50+ results




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

Overview

CZ_RPOBJECTTYPES_LKV is a filtered reporting view owned by the APPS schema within the Oracle E-Business Suite Configurator (CZ) module. It is documented as a VALID object in ETRM 12.1.1 and 12.2.2. The view exposes the set of lookup values that describe the object types available to the Configurator runtime and rule-processing engine, specifically the lookup list identified internally as RP_OBJECT_TYPES.

The trailing "_LKV" suffix denotes a "list of values" view — a presentation-layer construct that restricts a general lookup repository to a single, purpose-specific list. Rather than querying the broad lookup tables directly, application code and reports consume this view to obtain a stable, named enumeration of Configurator object types. This makes the view a convenient dependency for validation logic, integration extracts, and operational reporting where a controlled vocabulary of object types is required without risk of pulling unrelated lookup entries.

The view is read-only by nature. It carries no DML logic and is intended solely as a SELECT-accessible interface into the Configurator lookups. Because the object is documented only through its view text and column list, no additional programmatic dependencies are declared.

Underlying Base Objects

ETRM documents a single referenced base object: CZ_LOOKUP_VALUES_VL, itself a view. The relationship is a direct, restrictive filter: CZ_RPOBJECTTYPES_LKV selects all rows from the base view where LIST_NAME = 'RP_OBJECT_TYPES'. No joins, unions, or aggregations are applied, so the column set of CZ_RPOBJECTTYPES_LKV is a one-to-one projection of the source view's columns.

The _VL suffix on the base object indicates a language-enabled view, typically exposing translated and untranslated segments of lookup data. The presence of both LANGUAGE and SOURCE_LANG columns in CZ_RPOBJECTTYPES_LKV confirms this multilingual lineage and means row counts can vary by session language.

Key Columns

  • LIST_NAME — The lookup list identifier; always RP_OBJECT_TYPES for this view, serving as the constant filter predicate.
  • DATA_VALUE — The internal code value for the object type, used as the authoritative key in Configurator processing.
  • NUMERIC_ID_VALUE — A numeric surrogate for the object type, useful for integration targets requiring numeric identifiers.
  • VALUE_SEQ — Display or processing sequence for ordering entries.
  • DATA_TYPE_ID — Identifier of the data type associated with the lookup value.
  • NULL_VALUE_FLAG — Indicates whether a null/empty value is a permitted member of the list.
  • VALUE_LABEL — Translated display label presented to end users.
  • VALUE_DESCRIPTION — Longer descriptive text for the object type.
  • VALUE_NOTES — Supplementary administrative notes.
  • LANGUAGE, SOURCE_LANG — Language context columns governing translated versus source-language values.

Common Use Cases and Queries

Typical scenarios include populating report parameters, validating object-type values in integration payloads, and extracting the controlled vocabulary for downstream systems.

Retrieve all object types in display order:

SELECT DATA_VALUE, VALUE_LABEL, VALUE_SEQ
FROM   APPS.CZ_RPOBJECTTYPES_LKV
ORDER  BY VALUE_SEQ;

Resolve a label for a known object type code:

SELECT VALUE_LABEL
FROM   APPS.CZ_RPOBJECTTYPES_LKV
WHERE  DATA_VALUE = :p_object_type;

Identify whether null values are permitted:

SELECT DATA_VALUE, NULL_VALUE_FLAG
FROM   APPS.CZ_RPOBJECTTYPES_LKV
WHERE  NULL_VALUE_FLAG = 'Y';

Enforce language context explicitly where session defaults are insufficient:

SELECT DATA_VALUE, VALUE_LABEL, LANGUAGE
FROM   APPS.CZ_RPOBJECTTYPES_LKV
WHERE  LANGUAGE = USERENV('LANG');

Because the view is unfiltered beyond the list-name predicate, results reflect the current content of the Configurator lookup definitions, including any values added or changed by administrators. Queries should therefore always qualify the schema as APPS and avoid assuming any fixed row count.