Search Results display_column1_name




Overview

ENG_CHANGE_RULE_ATTRIBUTES_VL is a multilingual (VL) view owned by the APPS schema in Oracle E-Business Suite, belonging to the Engineering (ENG) product module. It exposes the translated and untranslated definitions of the attributes that may be referenced by Engineering Change Order (ECO) rule conditions. In Oracle EBS, change management rules determine which ECOs are automatically approved, routed, or flagged based on values carried on the change object and its related items, bills, and revisions. Each such rule condition is expressed in terms of an attribute, and this view provides the definitive, language-aware list of those attributes together with the metadata needed to build list-of-values (LOV) pickers and dynamic SQL fragments.

The view is declared VALID in the ETRM 12.2.2 dictionary. It functions as a reporting and integration surface: rather than querying the base tables directly, custom reports, extensions, and interfaces read the view so that attribute descriptions resolve to the session language and so that the join between the base and translation tables is applied consistently.

Underlying Base Objects

As documented in the ETRM metadata, the view is defined over two base objects, both referenced through APPS synonyms:

The two are joined on ATTRIBUTE_OBJECT_NAME and ATTRIBUTE_CODE, with the translation filtered by T.LANGUAGE = USERENV('LANG'). This is the standard EBS MLS join pattern: the _B table supplies the technical definition, the _TL table supplies the user-facing label in the language of the current session. All descriptive columns are projected from the translation row; all structural columns are projected from the base row.

Key Columns

  • ATTRIBUTE_OBJECT_NAME — identifies the object (for example, the change header, change line, or item) to which the attribute belongs. Part of the composite join key.
  • ATTRIBUTE_CODE — the internal code of the attribute. Part of the composite join key and the principal lookup column.
  • ATTRIBUTE_NAME — the translated, user-visible label for the attribute, sourced from the _TL table.
  • ATTRIBUTE_COLUMN_TYPE — the data type or column category used when rendering the attribute in rule definition screens.
  • LOV_SQL — a stored SQL fragment used to populate the list of valid values for the attribute.
  • DISPLAY_COLUMN1_NAME / DISPLAY_COLUMN2_NAME — the columns used to display the value in rule listings.
  • ATTRIBUTE_CLASS_CODE — classifies the attribute into a logical grouping.
  • LANGUAGE — the language code of the returned translation row.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — the standard EBS WHO audit columns.

Common Use Cases and Queries

Typical uses include building custom rule-validation reports, verifying which attributes are available for a given object before configuring ECO rules, and driving dynamic LOVs in extensions that mimic the standard change-rule setup forms.

  • Enumerate every attribute defined for a specific change object:
    SELECT attribute_code, attribute_name, attribute_column_type, attribute_class_code
    FROM   apps.eng_change_rule_attributes_vl
    WHERE  attribute_object_name = :object_name
    ORDER  BY attribute_name;
  • Retrieve the LOV SQL for a specific attribute so it can be executed or audited:
    SELECT attribute_name, lov_sql
    FROM   apps.eng_change_rule_attributes_vl
    WHERE  attribute_object_name = :object_name
    AND    attribute_code        = :attribute_code;
  • Confirm the session language in which translations are being returned:
    SELECT DISTINCT language
    FROM   apps.eng_change_rule_attributes_vl;

Because the view filters on USERENV('LANG'), results are always returned in the language of the connecting session, and only rows having a translation in that language are visible.