Search Results cancellation_date




Overview
Explore in AI Chat

Overview

The APPS.ENG_ENGINEERING_CHANGES_VAL_V view is a validation-oriented reporting object within the Oracle E-Business Suite Engineering (ENG) module. Its documented purpose is to expose non-cancelled engineering change orders. In practice, the view functions as a filtered, denormalized projection of the master engineering change order table, returning only those engineering change (ECO) records whose cancellation date has not yet effectively removed them from the active working set.

The critical filter embedded in the view definition is WHERE TRUNC(NVL(CANCELLATION_DATE, SYSDATE + 1)) > TRUNC(SYSDATE). This predicate evaluates true for any engineering change order that either has no cancellation date at all (defaulted to a future date of SYSDATE + 1) or has a cancellation date in the future. Consequently, ECOs whose cancellation date is on or before the current system date are excluded from the result set. This view is therefore useful for reports, integrations, and validation logic that must operate exclusively against engineering change orders still considered active by the application.

Underlying Base Objects

The view is owned by the APPS schema and is defined over a single documented base object: ENG_ENGINEERING_CHANGES, accessed through a synonym. The view text aliases this table as EEC. No joins to secondary tables are present in the documented definition, so the view performs a one-to-one filtered projection of the base engineering change order records without aggregating or combining rows across tables.

Because the view is defined directly over the base table with only a row-level filter, the columns exposed mirror those of the underlying table. This means column semantics, data types, and value domains correspond exactly to the base engineering change order entity. The view name suffix _VAL_V is consistent with Oracle EBS conventions denoting a validation view, commonly referenced by descriptive flexfield and value-set validation logic.

Key Columns

The most relevant columns exposed by the view include:

Common Use Cases and Queries

The view is typically used to retrieve active engineering change orders for reporting, validation lists, and integration payloads. A representative query filtering by organization and status follows:

  • SELECT change_notice, description, status_type, implementation_date FROM eng_engineering_changes_val_v WHERE organization_id = :org_id AND status_type = :status ORDER BY change_notice;

Because the view already excludes records with a past cancellation date, there is no need to re-apply the cancellation predicate at the call site. A simple listing of all active change orders requires only:

  • SELECT change_notice, approval_status_type, approval_date FROM eng_engineering_changes_val_v;

Consumers should be aware that the filter depends on the database server date via SYSDATE, so results are time-sensitive. Any integration that caches or replicates results from this view must account for the fact that a change order may drop out of the result set once its cancellation date is reached. Queries driven by the CANCELLATION_DATE column itself will return only future or null cancellation dates, since past cancellation values are filtered out by the view definition.