Search Results ecg_material_disposition




Overview

The view APPS.ENG_REVISED_ITEMS_API_V is a denormalized reporting and integration view that exposes revised item records from the Oracle E-Business Suite engineering change management module. It surfaces the data stored in ENG_REVISED_ITEMS alongside descriptive flexfield and lookup translations, allowing revised items to be reported and consumed through public APIs and interfaces without requiring joins to be repeated in every client query. In the context of ETRM 12.1.1 and 12.2.2, the view plays a central role in engineering change order (ECO) processing, since each revised item identifies an item affected by a change notice, the disposition applied to it, the new revision or use-up strategy, and the associated bill of materials reference.

The view is particularly relevant to searches such as ecg_material_disposition, since it directly joins to the MFG_LOOKUPS view on the lookup type ECG_MATERIAL_DISPOSITION and exposes the decoded meaning in the DISPOSITION column. This makes the view the natural starting point for any query that needs to translate a stored disposition code into a user-readable description.

Underlying Base Objects

According to the documented ETRM 12.2.2 metadata, the view is defined over the following base objects:

  • ENG_REVISED_ITEMS (synonym over the base revised-items table) — the driving table, aliased ERI, supplying change notice, organization, revised item, status, disposition, revision, and scheduling attributes.
  • MTL_ITEM_FLEXFIELDS (view) — joined twice as MIF1 and MIF2 to resolve the revised item number/description and the use-up item number/description respectively.
  • MFG_LOOKUPS (view) — joined twice as ML1 and ML2: ML1 decodes STATUS_TYPE against lookup type ECG_ECN_STATUS, and ML2 decodes DISPOSITION_TYPE against lookup type ECG_MATERIAL_DISPOSITION.
  • BOM_BILL_OF_MATERIALS (view) — outer-joined on BILL_SEQUENCE_ID to provide the alternate BOM designator and assembly type.
  • FND_GLOBAL (package) — referenced for session and application context used in the API layer.

The outer joins to the BOM and use-up item sources mean revised items without an associated bill or use-up item are still returned, preserving the full set of ECO revision lines.

Key Columns

Common Use Cases and Queries

The view is commonly used to report ECO impact by organization, to validate disposition values before submission to the revised-items API, and to drive downstream integration extracts. A typical query resolving material disposition is:

SELECT change_notice, revised_item, new_item_revision, disposition, revised_item_status
FROM apps.eng_revised_items_api_v
WHERE organization_id = :org_id
AND disposition_type = 'USE_UP';

A second common pattern retrieves the ECO history of a single item:

SELECT change_notice, disposition, implementation_date, auto_implement_date
FROM apps.eng_revised_items_api_v
WHERE revised_item_id = :inventory_item_id
ORDER BY creation_date DESC;

Because the view already resolves the ECG_MATERIAL_DISPOSITION and ECG_ECN_STATUS lookups, queries against it avoid repetitive joins to MFG_LOOKUPS and return user-facing meanings directly, making it suitable for concurrent programs, OAF pages, and external integration extracts.