Search Results create_bom_in_local_org




Overview
Explore in AI Chat

Overview

ENG_CHANGE_ORDER_TYPES_V is an APPS-owned reporting view within the Oracle E-Business Suite Engineering (ENG) module. It is documented in ETRM with a status of VALID and provides a consolidated, read-only presentation of engineering change order type definitions. The object is described as "Engineering change order types - all records," indicating that the view exposes the complete set of change order type records rather than a filtered subset scoped to a single organization or operating unit.

In the context of Oracle EBS 12.1.1 and 12.2.2, engineering change order (ECO) types drive the behavior of the change management workflow, including numbering, assignee defaults, and item/BOM creation rules. This view serves as the primary reference surface for reporting, integration, and extensions that need to enumerate ECO types without directly querying the underlying transactional or setup tables. Because it is a view rather than a table, it carries no storage of its own and inherits its data entirely from its base objects.

Underlying Base Objects

The documented base objects referenced by this view are ENG_CHANGE_ORDER_TYPES_VL (VIEW) and FND_PROFILE (PACKAGE). The view text confirms that ENG_CHANGE_ORDER_TYPES_V is defined over ENG_CHANGE_ORDER_TYPES_VL, aliased as ECOT, with a straightforward SELECT list that projects every column from the VL (view layer) object. The VL object is the standard Oracle EBS multilingual view layer construct, which combines the base (language-independent) table with the translation (_TL) table so that descriptive and user-enterprise columns appear in the session language.

The reference to FND_PROFILE indicates that profile option values are resolved in the derivation of certain columns or in the runtime behavior of the view layer, consistent with EBS conventions where seeded or organization-scoped profile settings influence the effective values returned. Together, these dependencies mean the view reflects change order type configurations maintained through the Engineering setup and change management windows, reconciled through the VL and profile layers rather than a direct single-table projection.

Key Columns

Common Use Cases and Queries

Typical usage includes validating configured ECO types during implementation, populating LOVs or integration mappings, auditing seeded versus custom types, and identifying active types for a given organization.

SELECT change_order_type_id,
       change_order_type,
       type_name,
       change_order_organization_id,
       auto_numbering_method,
       seeded_flag
FROM   apps.eng_change_order_types_v
WHERE  disable_date IS NULL
ORDER  BY change_order_type;

To isolate seeded entries:

SELECT change_order_type_id, change_order_type, type_name
FROM   apps.eng_change_order_types_v
WHERE  seeded_flag = 'Y';

Because the view is read-only and defined over VL/profile constructs, it is appropriate for inquiry and reporting only; INSERT or UPDATE operations must target the underlying base tables through supported APIs.