Results for “engbv_engineering_change_types”

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

Overview

The ENGBV_ENGINEERING_CHANGE_TYPES view is a read-only reporting object in the Oracle E-Business Suite Engineering (ENG) module, owned by the APPS schema. It is classified in ETRM documentation as "Retrofitted," indicating that it is not an original base-table replacement but a compatibility or presentation layer built over the underlying Engineering change-order type data. The view exposes engineering change order (ECO) type definitions — the classification codes that control how an engineering change is processed, including whether it revises the bill of materials and what assembly or component selection rules apply. Because the view is defined WITH READ ONLY, it serves purely as a query surface for reports, concurrent programs, and integrations rather than as an update path. This makes it a stable, safe access point for referencing change type codes without risking DML against the protected base table.

Underlying Base Objects

The view is defined over a single referenced base object: ENG_CHANGE_ORDER_TYPES, reached through a SYNONYM. The defining SQL selects directly from ENG_CHANGE_ORDER_TYPES (aliased CH) and is constrained WITH READ ONLY. This one-to-one relationship means the view is a lightweight projection: every row in ENGBV_ENGINEERING_CHANGE_TYPES corresponds to one row in ENG_CHANGE_ORDER_TYPES, subject only to column renaming and recalculation. The base table stores the canonical definitions of Engineering change order types, while the view re-presents those definitions using column aliases that align with a different naming convention — most notably through the CHANGE_TYPE_CODE alias discussed below. No joins, unions, or aggregations are present in the documented view text, so performance characteristics closely track those of a direct query against the synonym.

Key Columns

• CHANGE_TYPE_CODE — Aliased from CH.CHANGE_ORDER_TYPE. This is the business-facing identifier for the change order type and is the column users most often search for. It supplies the code used to classify and filter engineering changes.
• DESCRIPTION — The descriptive text for the change order type.
• INACTIVE_DATE — Aliased from CH.DISABLE_DATE. Indicates the date on which the change type was disabled; a null value typically means the type remains active.
• "_LA:REVISE_ENG_BILL_FLAG" — A column whose name derives from an entity-attribute mapping expression. It encodes whether the change type revises the engineering bill of materials. Note the mixed-case, quoted identifier, which requires care in SQL.
• CHANGE_ORDER_TYPE_ID — The internal primary key linking back to the base table.
• CREATED_ON / CREATED_BY — Audit columns populated from CH.CREATION_DATE and CH.CREATED_BY.
• UPDATED_ON / UPDATED_BY — Audit columns populated from CH.LAST_UPDATE_DATE and CH.LAST_UPDATED_BY.

An additional positional expression referencing CH.ASSEMBLY_TYPE and MFG_LOOKUPS appears in the view text; its physical column name is not enumerated in the documented column list.

Common Use Cases and Queries

Typical usage centers on listing and filtering valid engineering change types. To retrieve all active types, filter on a null inactive date:

• SELECT change_type_code, description FROM apps.engbv_engineering_change_types WHERE inactive_date IS NULL;
• SELECT change_type_code, description, inactive_date FROM apps.engbv_engineering_change_types ORDER BY change_type_code;
• SELECT change_order_type_id, change_type_code FROM apps.engbv_engineering_change_types WHERE change_type_code = :p_code;

These patterns support value-set validation, reporting on change order classifications, and integration lookups keyed by change_type_code. Because the view is read-only, all maintenance must be performed against the base table via supported Engineering forms or APIs.