Search Results top_product_description

Overview

CS_CONFIG_RG_V is a read-only Oracle EBS database view owned by the APPS schema and registered against the CS (Service) product family. It presents configuration relationships for a customer product and its subcomponents, resolving a customer product record (CP1) together with the configuration root record (CP2) that governs it. Because the view joins both records to the item key flexfield view, it exposes fully concatenated product identifiers and descriptions for two levels of the configuration hierarchy: the immediate parent and the top-level configuration root.

In the context of a search for top_lot_number, the relevant column is TOP_LOT_NUMBER, which returns the lot number of the configuration root record. This allows service, depot repair, and field service reporting to identify the controlling lot for an installed configuration without having to traverse CS_CUSTOMER_PRODUCTS_ALL recursively. The view is primarily used for reporting and integration extracts rather than transactional processing; it performs no DML and carries no package-level validation logic of its own beyond the lookup helper referenced in its predicate.

Underlying Base Objects

The documented base objects for this view are:

• CS_CUSTOMER_PRODUCTS_ALL (synonym; joined twice, aliased CP1 and CP2) — the installed base table holding customer product instances, including lot, serial, reference number, inventory item, and the CONFIG_ROOT_ID link. CP1 supplies the parent record, CP2 supplies the top record via CP2.CUSTOMER_PRODUCT_ID = CP1.CONFIG_ROOT_ID.
• MTL_SYSTEM_ITEMS_KFV (synonym; joined twice, aliased KFV1 and KFV2) — the item key flexfield view supplying CONCATENATED_SEGMENTS and DESCRIPTION for each product. Both joins are constrained by KFV.ORGANIZATION_ID = CS_STD.GET_ITEM_VALDN_ORGZN_ID, restricting items to the validation organization.
• CS_STD (package) — invoked in the join predicate to return the item validation organization identifier.
• CSICUMPI_PUB (package) — a documented referenced object associated with the view; it provides the public packaging for configuration instance and component processing in the CS module.

The relationship between view and base objects is a straight equi-join on INVENTORY_ITEM_ID (to both item flexfield aliases) and a self-join on CS_CUSTOMER_PRODUCTS_ALL through CONFIG_ROOT_ID. No outer joins are used, so a row is returned only when both the parent and root customer product records exist and both resolve to a valid item in the validation organization.

Key Columns

• PARENT_CP_ID — CUSTOMER_PRODUCT_ID of the parent and subcomponent record (CP1).
• PARENT_REFERENCE_NUMBER — reference number of the parent customer product instance.
• PARENT_PRODUCT / PARENT_PRODUCT_DESCRIPTION — concatenated flexfield segments and description of the parent item.
• PARENT_LOT_NUMBER / PARENT_SERIAL_NUMBER — lot and current serial number of the parent instance.
• TOP_REFERENCE_NUMBER — reference number of the configuration root (CP2).
• TOP_PRODUCT / TOP_PRODUCT_DESCRIPTION — concatenated segments and description of the root item.
• TOP_LOT_NUMBER — lot number of the configuration root instance; the column targeted by the top_lot_number search.
• TOP_SERIAL_NUMBER — current serial number of the configuration root instance.

Common Use Cases and Queries

Typical scenarios include installed-base reporting that must show the top-level lot alongside each configured component, service entitlement checks keyed on the root lot, and extracts feeding depot repair or warranty systems. A representative query lists configuration rows for a given top lot number:

• SELECT parent_cp_id, parent_reference_number, parent_product, parent_lot_number, top_reference_number, top_product, top_lot_number FROM apps.cs_config_rg_v WHERE top_lot_number = :p_lot_number;
• SELECT parent_product, parent_serial_number, top_product, top_lot_number FROM apps.cs_config_rg_v WHERE top_reference_number = :p_ref_num ORDER BY parent_product;
• SELECT DISTINCT top_product, top_lot_number, top_serial_number FROM apps.cs_config_rg_v WHERE parent_lot_number = :p_lot_number;

Queries should bind the item validation organization consistently with CS_STD.GET_ITEM_VALDN_ORGZN_ID to avoid missing rows, and callers should filter on the parent or top keys rather than performing full scans, since the view resolves two item flexfield lookups per returned row. Oracle proprietary and confidential; refer to the ETRM 12.2.2 entry for the authoritative definition before reuse in custom code.