Search Results eng_current_scheduled_dates




Overview
Explore in AI Chat

Overview

ENG_CURRENT_SCHEDULED_DATES is an Engineering (ENG) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores current and historical Engineering Change Order (ECO) scheduled implementation dates. Each row captures the planned date on which a revised item — an item revision produced or modified by an ECO — is scheduled to become effective in a given organization. Because ECO scheduling drives the timing of engineering changes across manufacturing and inventory, this table functions as the transactional record of when a change is intended to take effect and, through its historical rows, when that plan was subsequently altered.

From a dimensional modeling perspective, the documented foreign key structure supports a heuristic Data Vault classification of satellite-leaning. The table hangs off ENG_REVISED_ITEMS via REVISED_ITEM_SEQUENCE_ID and records descriptive, time-relevant attributes (scheduled dates, employee assignments, comments) rather than acting as a pure hub or link. Modelers should treat it as a satellite-like detail store keyed to the revised item, with additional references to employee data.

Key Information Stored

The table contains 20 documented columns. The most operationally significant include:

  • SCHEDULE_ID — Part of the composite primary key (ENG_CURRENT_SCHEDULED_DATES_PK) and part of the unique business-key index ENG_CURRENT_SCHEDULED_DATES_U1; identifies the scheduling record.
  • REVISED_ITEM_SEQUENCE_ID — The second component of the primary key and the leading column of the unique index; the foreign key to ENG_REVISED_ITEMS that ties a scheduled date to a specific revised item.
  • REVISED_ITEM_ID — The revised item identifier associated with the schedule.
  • SCHEDULED_DATE — The effective scheduled implementation date for the ECO change.
  • CHANGE_NOTICE — The ECO/change notice identifier the schedule pertains to.
  • CHANGE_ID — Internal identifier linking the row to the change record.
  • ORGANIZATION_ID — The inventory organization in which the scheduled implementation applies.
  • EMPLOYEE_ID — The employee responsible for or associated with the schedule; foreign key to PSB_EMPLOYEES.
  • OLD_EMPLOYEE_ID — Retains the prior assigned employee, supporting historical tracking of reassignment.
  • COMMENTS — Free-text notes explaining scheduling decisions or changes.

The surrogate-style primary key is the (SCHEDULE_ID, REVISED_ITEM_SEQUENCE_ID) pair, while ENG_CURRENT_SCHEDULED_DATES_U1 (REVISED_ITEM_SEQUENCE_ID, SCHEDULE_ID) represents the business-key candidate. Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and concurrent-program columns (REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE) are also present.

Common Use Cases and Queries

Engineering and manufacturing teams use this table to report on upcoming and historical ECO implementation plans, to audit schedule slippage, and to reconcile engineering changes against item revisions.

  • Reporting ECOs scheduled for a given date range or organization.
  • Comparing current versus historical scheduled dates for slippage analysis using OLD_EMPLOYEE_ID and creation/update timestamps.
  • Joining to ENG_REVISED_ITEMS to resolve revised item context.

A representative query pattern:

SELECT csd.CHANGE_NOTICE, csd.SCHEDULED_DATE, csd.ORGANIZATION_ID
FROM ENG.ENG_CURRENT_SCHEDULED_DATES csd
WHERE csd.SCHEDULED_DATE BETWEEN :from_date AND :to_date;

For employee lookups, join EMPLOYEE_ID to PSB_EMPLOYEES. Note that some date columns may carry a timestamp component; truncate as required for daily reporting.

Related Objects

  • ENG_REVISED_ITEMS — Referenced via ENG_CURRENT_SCHEDULED_DATES.REVISED_ITEM_SEQUENCE_ID; the principal parent for schedule records.
  • PSB_EMPLOYEES — Referenced via EMPLOYEE_ID, resolving the responsible employee.
  • ENG_ENGINEERING_CHANGES — Provides ECO/change notice context matched by CHANGE_NOTICE/CHANGE_ID.
  • MTL_SYSTEM_ITEMS_B — Resolves item detail for REVISED_ITEM_ID and ORGANIZATION_ID.
  • ENG_ECO_REVISED_ITEMS — Links ECOs to revised items for cross-referencing schedules.

These relationships make ENG_CURRENT_SCHEDULED_DATES a focal integration point between engineering change management and item/revision master data.