Search Results xnc_item_summary_v




Overview

XNC_ITEM_SUMMARY_V is a reporting view delivered under the Oracle E-Business Suite module XNC — Sales for Communications. In release 12.1.1 and 12.2.2 this module is documented as obsolete, and the view is consequently catalogued as reference metadata rather than active product code. Its stated purpose is to provide consolidated information about a Product and its bill of materials context, presenting item master attributes alongside their decoded lookup meanings. The view serves as a read-only denormalization layer: rather than joining the item master, the manufacturing lookup set, the common lookup set, and catalog group definitions at query time, consumers can select from a single object and receive both coded values and their human-readable descriptions. Because it resolves keys through the Key Flexfield views (_KFV) of the underlying tables, the item number and catalog group are exposed as concatenated segment values rather than raw identifier columns, which makes the view convenient for ad hoc reporting, concurrent program data sources, and interface extract logic where descriptive output is preferred over normalized identifiers.

Underlying Base Objects

The documented definition joins four objects. MTL_SYSTEM_ITEMS_KFV is the primary source and supplies all item-level attributes; MTL_ITEM_CATALOG_GROUPS_KFV supplies the catalog group concatenated segments; MFG_LOOKUPS supplies the BOM item type meaning; and FND_COMMON_LOOKUPS supplies the item type meaning. Joins to MFG_LOOKUPS and FND_COMMON_LOOKUPS are constrained by lookup type, using 'BOM_ITEM_TYPE' and 'ITEM_TYPE' respectively. The relationship to FND_COMMON_LOOKUPS and to MTL_ITEM_CATALOG_GROUPS_KFV is expressed as an outer join, so items lacking an item type lookup value or a catalog group assignment are still returned, with those columns null. The join to MFG_LOOKUPS is an inner join, which means a row is only returned when the item's BOM_ITEM_TYPE value has a matching lookup code. The documented metadata records no owner and no referenced base objects, and the object is noted as not implemented in the reference database.

Key Columns

Common Use Cases and Queries

The view is typically used to report item composition in product structures, filter items by bill of materials classification, or feed downstream extracts with pre-decoded values. A representative query retrieves standard items for an organization:

SELECT item_number, item_description, bom_item_type_meaning, item_type_meaning, catalog_group FROM xnc_item_summary_v WHERE organization_id = :org_id AND bom_item_type = 'STANDARD';

Because BOM_ITEM_TYPE_MEANING is resolved through an inner join, filtering on the decoded meaning is equivalent to filtering the code and is safe for reporting. A second common pattern lists all model and option class items for configuration reporting:

SELECT item_number, bom_item_type_code, bom_item_type_meaning FROM xnc_item_summary_v WHERE organization_id = :org_id AND bom_item_type IN ('MODEL', 'OPTION CLASS') ORDER BY item_number;

A third pattern enumerates items grouped by catalog for merchandising or product hierarchy review:

SELECT catalog_group, COUNT(*) item_count FROM xnc_item_summary_v WHERE organization_id = :org_id GROUP BY catalog_group ORDER BY catalog_group;

Consumers should note the module's obsolete status and confirm the view exists in the target instance before incorporating it into new customizations.