Search Results engineering_date




Overview
Explore in AI Chat

Overview

APPS.EGO_MTL_SY_ITEMS_CHG_VL is a PL/SQL view owned by the APPS schema within the EGO (Advanced Product Catalog) product family of Oracle E-Business Suite. Its stated purpose is to store pending changes information for item operational attributes. In other words, it exposes the staged, not-yet-approved modifications that users make to item master operational fields — such as purchasing, inventory, order management, and shipping attributes — before those changes are released to the definitive item definitions in MTL_SYSTEM_ITEMS_B.

In the Oracle EBS 12.1.1 / 12.2.2 architecture, item attributes can be managed through a controlled approval workflow rather than being written directly to the base item table. When a user edits operational attributes for an item in a given organization, those edits are captured as pending changes. The _CHG tables hold this staging data, and the _VL view presents a joined, user-facing projection of it. The "VL" suffix conventionally denotes a view that combines a base (_B) and translation (_TL) table, providing descriptions alongside the attribute values.

For reporting and integration, this view is significant because it lets developers and analysts query in-flight item attribute changes without touching the underlying change tables directly. A search for shippable_item_flag returns this view because SHIPPABLE_ITEM_FLAG is one of the operational attributes projected, making the view the natural place to answer questions about which items have a pending change to their shippable status.

Underlying Base Objects

The ETRM documentation identifies two referenced base objects, both accessed through synonyms:

The view text shows the join pattern explicitly: table alias B (representing _CHG_B) supplies the operational attribute columns, while alias T (representing _CHG_TL) supplies the descriptive text. Columns are projected one-to-one from B, with T.DESCRIPTION and T.LONG_DESCRIPTION added from the translation side. The view therefore behaves as a consolidated, readable snapshot of pending item change records joined to their translated descriptions.

Key Columns

Common Use Cases and Queries

Typical scenarios include auditing pending item attribute changes, validating shippable status before release to order management, and building reconciliation reports that compare staged values against approved item master values.

To list items with a pending shippable-item change in a given organization:

SELECT inventory_item_id,
       organization_id,
       shippable_item_flag,
       customer_order_flag,
       description
FROM   apps.ego_mtl_sy_items_chg_vl
WHERE  organization_id = :org_id
AND    NVL(shippable_item_flag, 'N') = 'Y';

To trace all operational flag changes for a specific item:

SELECT inventory_item_id,
       shippable_item_flag,
       purchasing_item_flag,
       inventory_item_flag,
       last_updated_by,
       last_update_date
FROM   apps.ego_mtl_sy_items_chg_vl
WHERE  inventory_item_id = :item_id;

Integration programs frequently join the view to MTL_SYSTEM_ITEMS_B on INVENTORY_ITEM_ID and ORGANIZATION_ID to detect staged-versus-current differences prior to running the item change approval process. Because it is a view, no DML should be issued against it; changes are performed through the Advanced Product Catalog change-management APIs and concurrent programs.