Results for “eng_current_scheduled_dates_v”

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

Overview

The ENG_CURRENT_SCHEDULED_DATES_V view is an Oracle E-Business Suite (EBS) dictionary object owned by the APPS schema and registered under the Engineering (ENG) product module. Its documented purpose is to expose current and historical ECO scheduled implementation dates. Engineering Change Orders (ECOs) drive controlled modifications to items, bills of material, and routings, and each ECO passes through a scheduled implementation milestone. This view surfaces the scheduled date together with the employee responsible for the schedule entry, allowing implementers, planners, and reporting layers to determine when a change notice is expected to take effect and which revision of which item is affected.

Because the object is a view rather than a table, it carries no storage of its own and does not perform transactional work. Its role in EBS is strictly presentational and integration-oriented: it supplies a denormalized, ready-to-join row set for concurrent programs, Oracle Forms LOVs, OBIEE/BI Publisher reports, and interface extracts. The view status is recorded as VALID in the APPS schema, and the design is consistent between release 12.1.1 and 12.2.2, since the view text and column list are unchanged across the documented metadata.

It is worth noting that the user search term mtl_employees_view corresponds directly to one of the referenced base objects of this view, since employee names are resolved through that view rather than through a direct HR table join.

Underlying Base Objects

The documented referenced base objects for this view are:

• ENG_CURRENT_SCHEDULED_DATES (recorded as a SYNONYM resolving to the underlying ENG base table) — supplies all schedules, dates, and audit columns.
• MTL_EMPLOYEES_VIEW (VIEW) — supplies the employee full name for the responsible employee.
• HR_GENERAL (PACKAGE) — HR utility package supporting employee/assignment logic.
• HR_PERSON_NAME (PACKAGE) — name formatting logic used to derive the employee full name.
• HR_SECURITY (PACKAGE) — applies HR security (organization/assignment) restrictions.

The join itself is an outer join driven by the schedule table: ECSD.EMPLOYEE_ID = MEV.EMPLOYEE_ID(+) and ECSD.ORGANIZATION_ID = MEV.ORGANIZATION_ID(+). Both the employee identifier and the organization identifier must match, which means the schedule row and employee assignment must be in the same organization to resolve a name. When no matching employee row exists, the view still returns the schedule but with a null employee name — a critical detail for reports that must not lose ECO rows.

Key Columns

• ROW_ID — the ROWID of the underlying schedule row, used for identified updates and Forms block row identification.
• CHANGE_NOTICE — the ECO/change notice number identifying the engineering change.
• ORGANIZATION_ID — the inventory organization context for the scheduled date.
• REVISED_ITEM_ID and REVISED_ITEM_SEQUENCE_ID — the item and revision sequence affected by the change.
• SCHEDULED_DATE — the planned ECO implementation date, the primary business attribute.
• SCHEDULE_ID, EMPLOYEE_ID, EMPLOYEE_FULL_NAME — the schedule identifier, the responsible employee, and the resolved name from MTL_EMPLOYEES_VIEW.
• COMMENTS — free-text notes attached to the schedule entry.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard audit columns.
• REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE — concurrent request and program audit trail.

Common Use Cases and Queries

Typical uses include ECO implementation dashboards, schedule slippage analysis, and integration extracts feeding MES or PLM systems. All queries should be prefixed with the APPS schema or a synonym and should honor organization access, since HR_SECURITY influences the employee name resolution.

List scheduled dates for a change notice:

SELECT change_notice, revised_item_id, scheduled_date,
       employee_full_name, comments
FROM   apps.eng_current_scheduled_dates_v
WHERE  change_notice = :p_eco
ORDER  BY scheduled_date;

Identify ECOs due within a window for a given organization:

SELECT change_notice, revised_item_id, scheduled_date,
       employee_full_name
FROM   apps.eng_current_scheduled_dates_v
WHERE  organization_id = :p_org
AND    scheduled_date BETWEEN :p_from AND :p_to
ORDER  BY scheduled_date;

Because the employee join is an outer join, reports should treat EMPLOYEE_FULL_NAME as optional and never use it as a filter for mandatory rows. Where a schedule has no matching employee in the organization, the ECO is still valid and must be reported.

Finally, verify privileges against MTL_EMPLOYEES_VIEW, HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY when granting access, as the view inherits security behavior from these objects.