Results for “enabled_flag”

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

Overview

ENG_ECO_DEPARTMENTS_VIEW is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Engineering (ENG) product module. Its documented purpose is to expose all Engineering Change Order (ECO) departments that are maintained as organizations within Oracle Human Resources. In EBS Releases 12.1.1 and 12.2.2, ECO departments are not stored as a distinct entity; instead they are modeled as HR organizations and classified through the organization information framework. This view provides the filtered, denormalized projection that Oracle Engineering forms, concurrent programs, and reports rely on when resolving which departments may participate in an ECO workflow.

Because it abstracts the classification logic required to distinguish ECO departments from all other HR organization units, the view plays a supporting role in reporting and integration rather than serving as a transactional object. Customers routinely query it when building custom reports, validating setup data migrated between environments, or integrating ECO department lists into external systems.

Underlying Base Objects

The view is defined over two base objects, referenced in the ETRM metadata as synonyms resolving to their APPS base tables:

• HR_ALL_ORGANIZATION_UNITS (aliased OU) — the master table of HR organizations, supplying the organization identifier, business group, and organization name.
• HR_ORGANIZATION_INFORMATION (aliased OI) — the key-flexible descriptor table that stores classification and other organization attributes as context/information name/value triples.

The documented view text joins the two on ORGANIZATION_ID and restricts the result to rows where the concatenated ORG_INFORMATION_CONTEXT equals 'CLASS' and ORG_INFORMATION1 equals 'BOM_ECOD'. The BOM_ECOD classification is the internal identifier that marks an organization as an ECO department within the Bills of Material and Engineering classification scheme. Consequently, the view returns precisely those HR organizations that have been designated as ECO departments, and only that subset.

Key Columns

• ORGANIZATION_ID — Primary identifier of the ECO department organization, drawn from HR_ALL_ORGANIZATION_UNITS. This value is the foreign key used throughout Engineering tables that reference a department.
• BUSINESS_GROUP_ID — Identifier of the business group (the HR security and legislative grouping) to which the organization belongs. It is significant in multi-business-group implementations and in HR security profile enforcement.
• NAME — The user-visible name of the ECO department as defined on the HR organization.
• ENABLED_FLAG — Documented as an exposed column; it indicates whether the department organization is currently enabled and therefore selectable for ECO entry.
• The view text additionally selects OI.ORG_INFORMATION2 with no alias; this value is projected alongside the organization row and may be consumed by internal Engineering logic.

Common Use Cases and Queries

Typical scenarios include validating that required ECO departments exist before go-live, listing departments for a specific business group, and driving LOV-style customizations. A basic listing query is:

SELECT organization_id, business_group_id, name
FROM   apps.eng_eco_departments_view
ORDER BY name;

To restrict results to a single business group:

SELECT organization_id, name
FROM   apps.eng_eco_departments_view
WHERE  business_group_id = :p_business_group_id;

To resolve a department name from an ECO transaction, join the view to the Engineering change order tables on ORGANIZATION_ID. Because the view is a simple join over HR tables and contains no aggregation or complex logic, it performs efficiently and is safe for read-only reporting. It should not be used as a DML target; ECO departments must be created and classified through the HR organization setup and the Engineering classification, after which they automatically appear in the view.