Search Results requestor_name

Overview

ENGFV_ENGINEERING_CHNG_ORDERS is a read-only Oracle EBS view owned by the APPS schema within the Engineering (ENG) product family. It consolidates Engineering Change Order (ECO) header information with descriptive attributes drawn from multiple master and transactional tables, presenting a denormalized, user-friendly result set suited to reporting and integration. In 12.1.1 and 12.2.2 the view remains VALID and is defined with the WITH READ ONLY clause, confirming it is intended strictly for query access rather than DML.

The view exposes the engineering change order name, status descriptions, approval workflow details, project and task context, responsible organizations, and the requestor's full name. Because it translates coded lookup values into meanings via the '_LA:' directives and resolves the requestor through HZ_PARTIES and PER_PEOPLE_F, it shields report authors from the joins required against the base transactional tables. The presence of the '_SEC:EN.ORGANIZATION_ID' predicate indicates that row-level organization security is enforced, so results are filtered according to the querying user's organization access.

Underlying Base Objects

The view is constructed over the following documented base objects: ENG_ENGINEERING_CHANGES (the ECO header, aliased EN), ENG_CHANGE_ORDER_TYPES_TL (change type translations), ENG_ECN_APPROVAL_LISTS (approval list definitions), HR_ALL_ORGANIZATION_UNITS (organization name and responsible organization, aliased AL1 and AL2), MTL_PARAMETERS (organization code), PA_PROJECTS_ALL and PA_TASKS (project and task context), HZ_PARTIES and PER_PEOPLE_F (requestor identity), plus the HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY packages.

Joins to HZ_PARTIES and PER_PEOPLE_F are outer joins, ensuring ECOs without a resolvable requestor still appear. The PER_PEOPLE_F join uses an effective-date filter so that only the currently effective person record is matched. ENG_CHANGE_ORDER_TYPES_TL is joined without an outer join and filtered by USERENV('LANG'), guaranteeing that change type names are returned in the session language. Project, task, approval list, and responsible organization joins are all outer joins, allowing ECOs that lack those associations to be reported.

Key Columns

• ECO_NAME — the engineering change order identifier (EN.CHANGE_NOTICE).
• REQUESTOR_NAME — the full name of the requestor (P.FULL_NAME), the column most directly related to the user's search.
• ORGANIZATION_CODE / ORGANIZATION_NAME — the organization code from MTL_PARAMETERS and the organization name from HR_ALL_ORGANIZATION_UNITS.
• ECO_CREATION_DATE, IMPLEMENTATION_DATE, CANCELLATION_DATE, APPROVAL_DATE, APPROVAL_REQUEST_DATE — key lifecycle dates for the change order.
• PRIORITY_CODE, REASON_CODE, CHANGE_TYPE_CODE — classification attributes.
• ENG_IMPLEMENTATION_COSTS, MFG_IMPLEMENTAION_COSTS — estimated engineering and manufacturing costs.
• PROJECT_NAME, TASK_NAME — project and task associations (PA_PROJECTS_ALL, PA_TASKS).
• APPROVAL_LIST_NAME — the approval list (EC.APPROVAL_LIST_NAME).
• ECO_RESPONSIBLE_ORGANIZATION — the responsible organization name (AL2.NAME).
• ORGANIZATION_ID, REQUESTOR_ID, APPROVAL_LIST_ID, CHANGE_ORDER_TYPE_ID, RESPONSIBLE_ORGANIZATION_ID, PROJECT_ID, TASK_ID — foreign key identifiers retained for drill-down.
• CREATED_ON, CREATED_BY, UPDATED_ON, UPDATED_BY — audit columns.

Common Use Cases and Queries

The view is typically used to produce ECO status reports, approval tracking extract files, and integration feeds that require the requestor's name. The following query returns ECOs requested by a given person:

• SELECT eco_name, requestor_name, organization_name, approval_date FROM apps.engfv_engineering_chng_orders WHERE requestor_name = 'SMITH, JOHN';

To list open ECOs by organization and creation date:

• SELECT eco_name, requestor_name, eco_creation_date, project_name FROM apps.engfv_engineering_chng_orders WHERE organization_code = 'M1' AND cancellation_date IS NULL ORDER BY eco_creation_date DESC;

Because the view applies organization security through HR_SECURITY, results are automatically restricted to the organizations the user is authorized to access. Reporting tools such as Oracle Reports, BI Publisher, and OBIEE commonly query this view when a joined, presentation-ready ECO dataset including REQUESTOR_NAME is required.