Search Results change_log_id




Overview
Explore in AI Chat

Overview

ENG_CHANGE_LOGS_VL is a seeded, valid view in the APPS schema within the Oracle E-Business Suite Engineering (ENG) module. It presents the audit and change-log history recorded against engineering change orders (ECOs) and their associated change lines, combining the transactional change-log records with their language-specific descriptive text. The "_VL" suffix denotes a "view with a language" — that is, a view that joins a base table (_B) with its translation table (_TL) and filters the translation rows to the session's current language via USERENV('LANG'). This design enables multi-language support without requiring callers to perform the join themselves. The view is the primary reporting and integration interface for the LOG_CLASSIFICATION_CODE attribute that users frequently search for, since classification of change-log entries (for example, revision, approval, or attribute-level change events) is a core data point in change-history reporting.

Underlying Base Objects

The view is defined over two synonyms, both resolving to tables owned by the APPS schema:

  • ENG_CHANGE_LOGS_B — the base table holding non-translated, structural columns such as identifiers, codes, dates, and who-columns.
  • ENG_CHANGE_LOGS_TL — the translation table holding language-specific text (LOG_TEXT).

The join predicate is B.CHANGE_LOG_ID = T.CHANGE_LOG_ID combined with T.LANGUAGE = USERENV('LANG'). The view also exposes B.ROWID as ROW_ID, making the underlying base-table row address available to callers. Both underlying objects are documented as synonyms in the ETRM 12.2.2 metadata, and the structure is consistent between 12.1.1 and 12.2.2.

Key Columns

Common Use Cases and Queries

Typical use cases include ECO change-history reports, audit trails for revision and approval events, and integration extracts that feed downstream systems. Because the view resolves LOG_TEXT automatically, callers avoid an explicit translation join. A representative query filtering on classification is:

  • SELECT change_log_id, change_id, change_line_id, log_classification_code, log_type_code, log_text, creation_date FROM apps.eng_change_logs_vl WHERE log_classification_code = :p_classification AND change_id = :p_change_id ORDER BY creation_date;
  • Reporting all log entries for a given ECO line: SELECT * FROM apps.eng_change_logs_vl WHERE change_line_id = :p_change_line_id;
  • Audit extract by date window: SELECT change_id, log_classification_code, creation_date, created_by FROM apps.eng_change_logs_vl WHERE creation_date BETWEEN :p_from AND :p_to;

Queries should reference the view through the APPS schema or a granted synonym, and callers should be aware that LOG_TEXT depends on the session NLS language setting.