Results for “engbv_eng_change_approvers”

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

Overview

The APPS.ENGBV_ENG_CHANGE_APPROVERS view is a reporting and integration object within the Oracle E-Business Suite Engineering (ENG) module. It is documented in the ETRM reference set for both 12.1.1 and 12.2.2 with a status of VALID and carries the descriptive marker "Retrofitted," indicating that it was re-implemented to preserve the column interface relied upon by existing customizations, reports, and interfaces after an underlying schema transformation. The view presents a flattened, human-readable roster of approvers assigned to Engineering Change Order (ECO) approval lists, joining approval-list membership records directly to employee personal data. Its principal purpose is to decouple downstream consumers from the normalized storage in ENG_ECN_APPROVERS and ENG_ECN_APPROVAL_LISTS, and to resolve the surrogate EMPLOYEE_ID into a displayable EMPLOYEE_NAME via the HR employee and person-name infrastructure. The view is defined with the WITH READ ONLY clause, so it can only be queried, never used as the target of DML, which is appropriate for a reporting construct.

Underlying Base Objects

The documented view text defines three directly referenced synonyms and their parent base tables: ENG_ECN_APPROVAL_LISTS (aliased LI), which supplies the approval-list name; ENG_ECN_APPROVERS (aliased AP), which supplies sequence, description, disable date, approver identity, and audit columns; and HR_EMPLOYEES (aliased EM), which supplies the resolved FULL_NAME projected as EMPLOYEE_NAME. The join predicates link AP.APPROVAL_LIST_ID = LI.APPROVAL_LIST_ID and AP.EMPLOYEE_ID = EM.EMPLOYEE_ID. The ETRM dependency list additionally records FND_PROFILE, HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY as referenced by the underlying HR_EMPLOYEES view and its supporting packages, which are responsible for name formatting and security-based row filtering.

Key Columns

• APPROVAL_LIST_NAME — Business-facing name of the ECO approval list to which the approver belongs.
• EMPLOYEE_NAME — Resolved full name of the approver, derived from HR_EMPLOYEES.FULL_NAME. This is the column most commonly surfaced when users search by employee name.
• SEQUENCE_NUMBER — The ordering position of the approver within the approval list (ENG_ECN_APPROVERS.SEQUENCE1).
• DESCRIPTION — Descriptive text associated with the approver record.
• INACTIVE_DATE — The date the approver entry is disabled (DISABLE_DATE).
• APPROVAL_LIST_ID and EMPLOYEE_ID — Surrogate identifiers for joining back to base tables and for programmatic processing.
• UPDATED_ON, UPDATED_BY, CREATED_ON, CREATED_BY — Audit columns mirroring the base record's creation and last-update metadata.

Common Use Cases and Queries

Typical uses include ECO approval-list reporting, approver maintenance validation, and integration feeds that require a readable approver name. A common lookup is to locate all approval lists to which a given employee name belongs:

• SELECT APPROVAL_LIST_NAME, EMPLOYEE_NAME, SEQUENCE_NUMBER FROM APPS.ENGBV_ENG_CHANGE_APPROVERS WHERE EMPLOYEE_NAME LIKE :name ORDER BY APPROVAL_LIST_NAME, SEQUENCE_NUMBER;
• SELECT APPROVAL_LIST_NAME, EMPLOYEE_NAME, SEQUENCE_NUMBER, INACTIVE_DATE FROM APPS.ENGBV_ENG_CHANGE_APPROVERS WHERE APPROVAL_LIST_ID = :list_id AND (INACTIVE_DATE IS NULL OR INACTIVE_DATE > SYSDATE);

Because the view is read-only and dependent on HR security, results are filtered by the querying user's HR access, and effective-dated name resolution applies. This makes it well suited to self-service-style reporting but unsuitable as a transactional interface.