Results for “cs_sr_inv_subcomponents_v”

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

Overview

CS_SR_INV_SUBCOMPONENTS_V is an APPS-owned database view within the Oracle E-Business Suite Service (CS) product family. Its documented purpose is to expose all inventory subcomponents derived from a bill of materials (BOM) structure. In the context of Oracle EBS 12.1.1 and 12.2.2, the view serves as a reporting and integration layer that flattens BOM hierarchy data into a denormalized, query-friendly result set for service-related processes.

The view is closely associated with the service request (SR) inventory component model, in which a top-level component may itself be an assembly composed of lower-level subcomponents. By resolving the BOM relationships for those assemblies, CS_SR_INV_SUBCOMPONENTS_V allows downstream logic — service billing, return material authorization, repair estimation, and depot repair — to enumerate every inventory item that participates in a serviced assembly. Because it is a view rather than a table, it introduces no stored redundancy; results are computed at query time, so any change to item, BOM, or component data is reflected immediately.

Underlying Base Objects

The documented base objects referenced by CS_SR_INV_SUBCOMPONENTS_V are BOM_BILL_OF_MATERIALS, BOM_INVENTORY_COMPONENTS, CS_SR_INV_COMPONENTS_V, FND_GLOBAL, and MTL_SYSTEM_ITEMS_VL. The view joins MTL_SYSTEM_ITEMS_VL (aliased KFV) as the master item source, BOM_INVENTORY_COMPONENTS (aliased BIC) for component lines, and BOM_BILL_OF_MATERIALS (aliased BOM) for the bill header. The EXISTS subquery against CS_SR_INV_COMPONENTS_V restricts the output to BOM assemblies that are already recognized as service-relevant components, anchoring the result set to the Service module. FND_GLOBAL supplies session context such as organization and user identifiers used by the underlying views for multi-org security.

The joins are constrained by ORGANIZATION_ID, BILL_SEQUENCE_ID to COMMON_BILL_SEQUENCE_ID, and COMPONENT_ITEM_ID to INVENTORY_ITEM_ID. Effectivity logic ensures only components whose EFFECTIVITY_DATE has passed and whose DISABLE_DATE has not yet been reached are returned, using current date truncation.

Key Columns

• ORGANIZATION_ID — Inventory organization that owns the assembly and its components; governs multi-org filtering.
• SUBCOMPONENT_ID — The inventory item identifier of the component item, aliased from KFV.INVENTORY_ITEM_ID. This is the column most often searched when resolving a specific subcomponent.
• DESCRIPTION — Item description sourced from MTL_SYSTEM_ITEMS_VL.
• CONCATENATED_SEGMENTS — The concatenated flexfield representation of the subcomponent item, useful for display and reporting.
• COMPONENT_ID — The assembly item identifier (BOM.ASSEMBLY_ITEM_ID) that the subcomponent belongs to, linking each row back to its parent component.

Common Use Cases and Queries

A typical scenario is identifying all subcomponents of a serviced assembly within a given organization. An example query follows:

• SELECT subcomponent_id, description, concatenated_segments, component_id FROM cs_sr_inv_subcomponents_v WHERE organization_id = :org_id AND component_id = :component_item_id;
• Exploding a repair or return order to enumerate every item that must be inspected, replaced, or credited.
• Joining to MTL_SYSTEM_ITEMS_VL to enrich reporting with additional item attributes, or to BOM structures to reconcile service and manufacturing BOM views.
• Feeding integration interfaces that publish subcomponent composition to external service or warranty systems.

Because effectivity is evaluated dynamically and alternate BOMs are excluded (ALTERNATE_BOM_DESIGNATOR IS NULL), results reflect only the current primary bill for each assembly, which is generally the correct basis for service processing.