Results for “eng_item_flag”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

EGO_ITEMS_V is an APPS-owned view in the Oracle E-Business Suite Advanced Product Catalog (EGO) module. It presents a denormalized, integration-oriented projection of item attributes used for UCCNet product synchronization, the standardized data-pool exchange mechanism through which suppliers publish item content to trading partners. The view consolidates item master, cross-reference, unit-of-measure, weight, and GTIN (Global Trade Item Number) attributes into a single flattened result set, avoiding the joins that a consumer would otherwise have to perform against the underlying inventory and catalog tables.

Because UCCNet publication requires an unambiguous GTIN per item and a reliable indicator of whether publication has been attempted and succeeded, EGO_ITEMS_V is primarily used by outbound interfaces, integration extracts, and validation reports operating at the master organization level. The view is documented as VALID under schema APPS and is available in both 12.1.1 and 12.2.2, with no differences in its documented definition relevant to the columns described here.

Underlying Base Objects

The view is defined over one view and a mixture of synonyms resolving to base tables: EGO_ITEM_GTN_ATTRS_B, EGO_UCCNET_EVENTS, FND_FLEX_VALUES_VL, FND_FLEX_VALUE_SETS, MTL_CROSS_REFERENCES_B, MTL_CROSS_REFERENCES_TL, MTL_PARAMETERS, MTL_SYSTEM_ITEMS_B, MTL_SYSTEM_ITEMS_B_KFV, and MTL_UNITS_OF_MEASURE_TL. The principal driving objects are MTL_SYSTEM_ITEMS_B_KFV (concatenated key flexfield segments) and MTL_SYSTEM_ITEMS_B, joined on inventory_item_id and linked to MTL_PARAMETERS on organization_id to obtain the master_organization_id. GTIN values are sourced through MTL_CROSS_REFERENCES_B, with the descriptive text taken from MTL_CROSS_REFERENCES_TL filtered by the session language. GTIN and trade-item attributes such as top_gtin, gross_weight, and consumer-unit flags come from EGO_ITEM_GTN_ATTRS_B. Publication status is derived from EGO_UCCNET_EVENTS, and trade item descriptor meanings are resolved from FND_FLEX_VALUE_SETS and FND_FLEX_VALUES_VL using the TRADEITEMDESCVS value set.

Key Columns

The view exposes inventory_item_id, organization_id, and concatenated_segments as its item identifiers, alongside master_organization_id from MTL_PARAMETERS. GTIN is aliased from MTL_CROSS_REFERENCES_B.cross_reference, with cross_reference_type and a language-specific description. UOM data is represented by primary_uom_code and its description.

Trade item content includes trade_item_descriptor and trade_item_descriptor_desc (resolved through the Trade Item Descriptor value set), is_trade_item_a_consumer_unit, unit_weight, gross_weight, and top_gtin. Publication status is a computed CASE expression returning 'Y' when EGO_UCCNET_EVENTS contains a publication event with action NEW_ITEM, INITIAL_LOAD, DATA_CHANGE, or CORRECTION and where the disposition_code is either null or not equal to 'FAILED'. This makes disposition_code the pivot on which the publication_status column depends. Orderability and engineering flags are exposed through customer_order_enabled_flag and eng_item_flag.

Common Use Cases and Queries

Typical uses include identifying publishable items, auditing failed or missing publication events, and extracting GTIN-level content for data-pool feeds. A representative query listing successfully published items is:

• SELECT inventory_item_id, organization_id, concatenated_segments, gtin, primary_uom_code, publication_status FROM ego_items_v WHERE publication_status = 'Y';
• SELECT concatenated_segments, gtin, top_gtin, gross_weight FROM ego_items_v WHERE is_trade_item_a_consumer_unit = 'Y';
• SELECT ie.inventory_item_id, ie.disposition_code FROM ego_uccnet_events ie WHERE ie.disposition_code = 'FAILED';

Because publication_status is filtered on disposition_code internally, users troubleshooting synchronization failures can compare view output against EGO_UCCNET_EVENTS directly. Note that the view is filtered to the master organization context and should be joined to organization-specific queries only where the underlying joins support it.