Search Results earliest_effective_date

Overview

ENGFV_ECO_REVISED_ITEMS is a read-only Oracle EBS view owned by the APPS schema within the Engineering (ENG) product family. It presents revised item information associated with Engineering Change Orders (ECOs), exposing the scheduling, implementation, cancellation, and disposition attributes that describe how a given item revision is introduced into production. The view is a foundation-layer reporting object used by Engineering and Manufacturing modules to surface ECO-driven item revisions without requiring direct joins against the normalized base tables.

The user search term "earliest_effective_date" maps directly to the view column EARLIEST_EFFECTIVE_DATE, which is sourced from ENG_REVISED_ITEMS.EARLY_SCHEDULE_DATE. This column is central to ECO scheduling analysis, as it represents the earliest date on which a revised item may take effect, distinct from the scheduled and implementation dates.

Underlying Base Objects

The ETRM metadata documents the following referenced base objects, all accessed via synonyms in the APPS schema:

• ENG_REVISED_ITEMS (RE) — The primary driving table containing revised item records linked to ECOs.
• MTL_SYSTEM_ITEMS_B (SY1) — The revised item master, joined on REVISED_ITEM_ID and ORGANIZATION_ID.
• MTL_SYSTEM_ITEMS_B (SY2) — The use-up item master, outer-joined on USE_UP_ITEM_ID and ORGANIZATION_ID.
• BOM_STRUCTURES_B (BI) — Outer-joined to resolve the alternate BOM designator.
• MTL_PARAMETERS (PA) — Provides organization context and the organization code.
• HR_ALL_ORGANIZATION_UNITS (AL) — Supplies the organization name.

The join structure is driven from ENG_REVISED_ITEMS and enforces organization-level security through the predicate on RE.ORGANIZATION_ID, ensuring only authorized organizations are returned. The view is defined WITH READ ONLY, preventing DML through the view layer.

Key Columns

• EARLIEST_EFFECTIVE_DATE — Sourced from EARLY_SCHEDULE_DATE; the earliest date the revision can take effect.
• START_EFFECTIVE_DATE — Sourced from SCHEDULED_DATE; the planned effective date.
• IMPLEMENTATION_DATE — Actual implementation date of the revision.
• CANCELLATION_DATE / CANCELLATION_COMMENTS — Cancellation details where applicable.
• CHANGE_DESCRIPTION — Descriptive text from the revised item record.
• ECO_NAME — The associated Engineering Change Order notice.
• NEW_ITEM_REVISION — The revision identifier being introduced.
• STATUS_TYPE, DISPOSITION_TYPE, MRP_ACTIVE, UPDATE_WIP, USE_UP — Lookup-derived meaning columns resolved via MFG_LOOKUPS.
• USE_UP_PLAN_NAME / USE_UP_ITEM_NAME — Use-up planning metadata.
• ORGANIZATION_CODE / ORGANIZATION_NAME — Organization identification.
• BOM_ALTERNATE_CODE — Alternate BOM designator.

Common Use Cases and Queries

Typical usage includes ECO impact reporting, revision scheduling, and organization-level release tracking. Because EARLIEST_EFFECTIVE_DATE answers queries around when a revision can first become active, it is frequently filtered or sorted in these scenarios.

• Identifying ECO revisions with upcoming earliest effective dates.
• Comparing scheduled versus earliest effective dates to assess scheduling variance.
• Reporting on use-up plans and dispositions tied to a revision.

Sample query:

SELECT eco_name,
      NEW_ITEM_REVISION,
      START_EFFECTIVE_DATE,
      EARLIEST_EFFECTIVE_DATE,
      IMPLEMENTATION_DATE,
      STATUS_TYPE,
      ORGANIZATION_CODE
FROM  APPS.ENGFV_ECO_REVISED_ITEMS
WHERE EARLIEST_EFFECTIVE_DATE >= SYSDATE - 30
ORDER BY EARLIEST_EFFECTIVE_DATE;

The view is restricted to read-only access and should be used in place of ad hoc joins against ENG_REVISED_ITEMS where the standard ECO revision reporting shape is required.