Search Results change_template_id

Overview

ENG_CHANGE_TEMPLATES_VL is a read-only multilingual (VL) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is part of the ENG (Engineering) product family and presents engineering change templates in a language-aware, report-ready format. Engineering change templates define reusable defaults and workflow patterns applied when engineering change orders (ECOs) are created, such as approval routing, status defaults, and standard descriptive text. The view gives reporting tools, concurrent programs, and integration layers a single denormalized source that joins the base transaction table to its translation table without exposing the join logic or requiring callers to know the underlying schema.

The "VL" suffix denotes a view that combines a "_B" (base) table with a "_TL" (translation) table and filters translations to the session language. The record returned therefore always carries the template name and description in the language of the current user, as determined by USERENV('LANG'). This makes the view the standard access point for both Forms-based UI logic and external integrations that need to retrieve or reference a change template by its identifier.

Underlying Base Objects

Per the documented ETRM metadata, ENG_CHANGE_TEMPLATES_VL is defined over two synonyms: ENG_CHANGE_TEMPLATES_B and ENG_CHANGE_TEMPLATES_TL. The base table ENG_CHANGE_TEMPLATES_B holds language-independent attributes, including the primary key CHANGE_TEMPLATE_ID, ORGANIZATION_ID, and the effective dating columns START_DATE and END_DATE, along with standard WHO audit columns. The translation table ENG_CHANGE_TEMPLATES_TL holds the TEMPLATE_NAME and DESCRIPTION, keyed by CHANGE_TEMPLATE_ID and LANGUAGE.

The view text joins the two tables on CHANGE_TEMPLATE_ID and restricts rows with T.LANGUAGE = USERENV('LANG'), returning exactly one translated row per template for the session's language. Because it is a view rather than a table, no DML is possible against ENG_CHANGE_TEMPLATES_VL; inserts and updates must target the underlying base and translation tables.

Key Columns

• CHANGE_TEMPLATE_ID — Primary identifier of the engineering change template; the column most frequently used in joins and lookups.
• ORGANIZATION_ID — Owning inventory organization, enabling multi-organization filtering of templates.
• TEMPLATE_NAME — Translated template name, sourced from ENG_CHANGE_TEMPLATES_TL.
• DESCRIPTION — Translated descriptive text, also from the TL table.
• START_DATE / END_DATE — Effective date range defining when the template is active.
• ROW_ID — ROWID of the base table row, useful for direct row identification.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns from the base table.

Common Use Cases and Queries

Because the search term "change_template_id" targets the primary key, the most common pattern is a lookup by identifier to resolve the name and description for display or validation.

SELECT change_template_id, organization_id,
       template_name, description,
       start_date, end_date
FROM   apps.eng_change_templates_vl
WHERE  change_template_id = :p_template_id;

A second scenario lists all currently effective templates for an organization, typically to populate a selection list in a custom form or report:

SELECT change_template_id, template_name
FROM   apps.eng_change_templates_vl
WHERE  organization_id = :p_org_id
AND    TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, TRUNC(SYSDATE)+1);

Integrations that map external change requests to EBS templates commonly join this view to engineering change order headers to verify which template governed a given ECO, filtering by CHANGE_TEMPLATE_ID. Reporting extracts frequently select TEMPLATE_NAME and DESCRIPTION for localized output, relying on the view's USERENV('LANG') filter to guarantee translation correctness. When the required language is not the session language, query ENG_CHANGE_TEMPLATES_TL directly with an explicit LANGUAGE predicate, since the VL view will not return rows for other languages.