Search Results eng_change_statuses_vl




Overview
Explore in AI Chat

Overview

ENG_CHANGE_STATUSES_VL is a seeded, valid database view owned by the APPS schema within the Oracle E-Business Suite Engineering (ENG) module. It exposes the set of change status codes used by Oracle Engineering Change Management (ECM) and related engineering change order (ECO) workflows in release 12.1.1 and 12.2.2. In EBS, a large class of reference and lookup data is exposed to the applications and to reporting tools through "_VL" (value-list) views. These views join a base-language table with its corresponding translation ("_TL") table, filtering by the runtime session language, so that consumers see the localized status name and description without having to code the join themselves. For a technical consultant, ENG_CHANGE_STATUSES_VL is the canonical, application-supported entry point for querying engineering change statuses. It is the object referenced in lookup and validation logic, in Discoverer or BI Publisher reports, and in custom integrations that need to resolve a status code to its displayed status name. Because the view is a database object rather than a pure lookup (as in FND_LOOKUPS), it also carries engineering-specific attributes such as the object to which a status applies and whether the status is seeded or user-defined.

Underlying Base Objects

The view is defined over two base objects, both referenced through APPS synonyms:

  • ENG_CHANGE_STATUSES — the base table that stores the language-independent attributes of each change status, including the status code, sort order, disable date, and the seeded flag.
  • ENG_CHANGE_STATUSES_TL — the translation table that stores the language-dependent status name and description, keyed by status code and language.

The view text joins the two on ECS.STATUS_CODE = ECSTL.STATUS_CODE and restricts the translation rows to ECSTL.LANGUAGE = USERENV('LANG'). The join is performed so that each base status appears exactly once, with the translation matching the language of the current session. The _VL suffix therefore signals a value-list view: a view that combines a "non-TL" base with its "_TL" companion and presents the translated attributes as ordinary columns.

Key Columns

The view exposes the following columns:

  • ROW_ID — the physical row identifier of the base ENG_CHANGE_STATUSES row.
  • STATUS_CODE — the language-independent code that uniquely identifies a change status and is the primary reference used by the application.
  • STATUS_NAME — the translated display name of the status, drawn from the _TL table.
  • DESCRIPTION — the translated, longer description of the status.
  • STATUS_TYPE — a classification of the status, distinguishing the category of engineering change status.
  • OBJECT_NAME — the engineering object to which the status applies, scoping the status to a specific entity used by the engineering change process.
  • SORT_SEQUENCE_NUM — the ordering sequence used when presenting statuses in a list of values or report.
  • DISABLE_DATE — the date on which the status became (or becomes) inactive, if applicable.
  • SEEDED_FLAG — indicates whether the row is Oracle-seeded or user-defined, useful for distinguishing standard statuses from custom ones.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include resolving a stored STATUS_CODE to a human-readable name in reports; driving a list of values for an ECO status parameter; identifying which statuses are still active; and separating seeded from custom statuses. The following examples illustrate typical access patterns.

List all active change statuses in sort order:

SELECT STATUS_CODE, STATUS_NAME, STATUS_TYPE
FROM   APPS.ENG_CHANGE_STATUSES_VL
WHERE  DISABLE_DATE IS NULL
ORDER  BY SORT_SEQUENCE_NUM;

Resolve a specific code to its display name:

SELECT STATUS_CODE, STATUS_NAME, DESCRIPTION
FROM   APPS.ENG_CHANGE_STATUSES_VL
WHERE  STATUS_CODE = :p_status_code;

Restrict to Oracle-seeded statuses for a given object:

SELECT STATUS_CODE, STATUS_NAME
FROM   APPS.ENG_CHANGE_STATUSES_VL
WHERE  SEEDED_FLAG = 'Y'
AND    OBJECT_NAME = :p_object_name;

Because the view uses USERENV('LANG'), results are automatically returned in the language of the connected session. Consultants should query the view rather than joining the base and translation tables directly, thereby relying on the same join and language filtering the application itself uses.