Results for “component_yield_factor”

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

Overview

WSM_COMPONENTS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, registered under the WSM — Shop Floor Management product family. Its documented purpose is to expose coproduct components associated with a bill of materials, providing a denormalized projection that joins assembly, component, and inventory item attributes into a single queryable structure.

The view is valid in both Oracle EBS 12.1.1 and 12.2.2 and is intended primarily for shop floor and manufacturing reporting contexts where component-level detail is required without navigating the underlying BOM entity model directly. Because it is a view rather than a base table, no direct DML should be performed against it; it serves strictly as a read-only access path. Users searching for component_yield_factor will find that this column is one of the principal outputs of the view and carries a defensive DECODE transformation to prevent null or zero propagation.

Underlying Base Objects

The view text is defined over the following documented base objects:

• BOM_BILL_OF_MATERIALS (VIEW) — referenced twice in the view definition as BOM1 and BOM2. BOM1 supplies the assembly item, organization, and alternate BOM designator; BOM2 links the bill sequence identifier used to resolve the common bill sequence relationship.
• BOM_INVENTORY_COMPONENTS (VIEW) — referenced as BIC, supplying the component item identifier, component quantity, component yield factor, implementation date, and bill sequence identifier.
• MTL_SYSTEM_ITEMS (SYNONYM) — joined to restrict results to items where BUILD_IN_WIP_FLAG equals 'Y' and PICK_COMPONENTS_FLAG equals 'N', ensuring the view returns only buildable assemblies with components that are not pick-to-order.
• BOM_SUBSTITUTE_COMPONENTS (SYNONYM) and FND_GLOBAL (PACKAGE) — documented as referenced base objects in ETRM metadata, supporting substitute component handling and session context resolution respectively.

The join between BIC.BILL_SEQUENCE_ID and BOM2.BILL_SEQUENCE_ID, and between BOM1.COMMON_BILL_SEQUENCE_ID and BOM2.BILL_SEQUENCE_ID, establishes the common bill of materials linkage that allows the view to surface shared BOM definitions across organizations.

Key Columns

• ASSEMBLY_ITEM_ID — the inventory item identifier of the parent assembly in the BOM structure.
• COMPONENT_ITEM_ID — the inventory item identifier of the component consumed by the assembly.
• ORGANIZATION_ID — the inventory organization in which the assembly and its components are defined.
• COMPONENT_QUANTITY — the required quantity of the component per assembly, expressed in the component's primary unit of measure.
• COMPONENT_YIELD_FACTOR — the yield factor applied to the component. The view applies DECODE(BIC.COMPONENT_YIELD_FACTOR, 0, 1, BIC.COMPONENT_YIELD_FACTOR), substituting a value of 1 where the stored yield factor is zero or null, thereby avoiding division-by-zero or zero-quantity behavior in downstream calculations.
• ALTERNATE_BOM_DESIGNATOR — the alternate BOM label associated with the assembly, used to distinguish between multiple BOM versions.

Common Use Cases and Queries

Typical usage includes shop floor reporting, component requirement analysis, and integration extracts that feed external planning systems. A representative query retrieving coproduct components for a specific organization is shown below:

SELECT assembly_item_id, component_item_id, component_quantity, component_yield_factor, alternate_bom_designator FROM apps.wsm_components_v WHERE organization_id = :org_id;

To isolate components with a non-default yield factor, filtering on the transformed column is effective:

SELECT component_item_id, component_yield_factor FROM apps.wsm_components_v WHERE component_yield_factor <> 1;

Because the view text disables the effectivity date predicates in the commented section, callers requiring date-effective component filtering must apply their own effective date logic against the underlying BOM_INVENTORY_COMPONENTS records rather than relying on the view.