Results for “gr_property_val_v”

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

Overview

GR_PROPERTY_VAL_V is a valid Oracle EBS view owned by the APPS schema and delivered as part of the GR - Process Manufacturing Regulatory Management product family. In Oracle EBS 12.1.1 and 12.2.2 it serves as the reporting and integration surface for the regulated property values that drive Process Manufacturing Regulatory Management calculations, label content, and compliance reporting. The view exposes the rows of the property values table, joining the translatable value records to the language definitions so that each row carries a human-readable language description. The searched term "lang_desc" corresponds directly to a column added by this view: LANG_DESC is not a column of the underlying table but is derived from FND_LANGUAGES_VL. Its presence makes the view particularly convenient for multilingual reporting, since consumers do not need to perform their own join to resolve a language code into a descriptive name.

Underlying Base Objects

The view is defined over two referenced base objects documented in the ETRM metadata: GR_PROPERTY_VALUES_TL, exposed in the APPS schema through a synonym, and FND_LANGUAGES_VL, which is itself a view over the Oracle Applications language definitions. GR_PROPERTY_VALUES_TL is the translation (TL) table that stores property values per language, and it is the primary driver of the view. The join condition is LANGUAGE = LANGUAGE_CODE, linking the LANGUAGE column of the property values table to the LANGUAGE_CODE of the FND_LANGUAGES_VL row. The view text additionally qualifies the row identifier and audit columns through the VAL alias (VAL.ROWID as ROW_ID, VAL.CREATED_BY, VAL.CREATION_DATE, VAL.LAST_UPDATED_BY, VAL.LAST_UPDATE_DATE, VAL.LAST_UPDATE_LOGIN), while DISPLAY_ORDER, VALUE, MEANING, SOURCE_LANG, PROPERTY_ID, and LANGUAGE are projected unqualified from the property values table. Because the join is an inner join on a single equality between LANGUAGE and LANGUAGE_CODE, only property value rows whose LANGUAGE has a matching row in FND_LANGUAGES_VL are returned.

Key Columns

• ROW_ID — the ROWID of the underlying property values row, useful for direct row addressing and debugging.
• PROPERTY_ID — identifier of the property to which the value belongs, the principal foreign key for joining to property definition tables.
• LANGUAGE — the language code of the translated value row; equal to LANGUAGE_CODE of the joined language definition.
• DISPLAY_ORDER — sequence used to order values when presented to users or printed on labels.
• VALUE — the stored property value itself.
• MEANING — the descriptive meaning associated with the value row.
• SOURCE_LANG — the language from which the row was originally derived, relevant for translation tracking.
• LANG_DESC — the description of the language, taken from FND_LANGUAGES_VL, and the column most often used to render readable language names in reports.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN for standard EBS auditing.

Common Use Cases and Queries

The view is used wherever property values must be listed with their language description, for example in regulatory reporting, property validation listings, and inbound/outbound interfaces that require a normalized language label. A typical query filters by property and sorts by display order:

SELECT property_id, language, lang_desc, display_order, value, meaning
FROM apps.gr_property_val_v
WHERE property_id = :p_property_id
ORDER BY display_order, language;

Because LANG_DESC is already resolved, a multilingual listing requires no additional join:

SELECT property_id, lang_desc, value
FROM apps.gr_property_val_v
WHERE language IN ('US', 'DE', 'FR');

For translation completeness checks, the view can be aggregated to confirm that all expected languages are present per property:

SELECT property_id, COUNT(DISTINCT language) lang_count
FROM apps.gr_property_val_v
GROUP BY property_id;

When integrating, consumers should account for the inner join behavior: a property value row whose LANGUAGE lacks a matching FND_LANGUAGES_VL entry will not appear. Queries intended to detect such orphaned rows should therefore read GR_PROPERTY_VALUES_TL directly rather than this view.