Purpose

Super BOMs are used in Variant Configuration and contain all the components that are required to manufacture
the material. This documentation will provide an overview on how to use Classes as BOM Items (Components)

Overview

You can use class items to control the selection of variant parts in a BOM, here it works same as selection condition
do in case of Super BOM.

Variant parts are classified in a class, and this class which is entered in the BOM as a class item. When you configure
the material, the class is replaced by a suitable variant part.

Class items can help you to simplify maintenance of BOMs for configurable materials: ( 1 )

• You only enter one item for the class, instead of several items for the individual variant parts.
• You do not need to create and assign selection conditions.
• You can classify additional objects in the class at any time, without having to change the BOM.

Lets take example of Super Bike, it have 3 parts which have 3 possible combinations.

If we create SUPER BOM for it we need to Create BOM with 9 items and write dependencies (Selection Condition ) for
each item position.

Below are the steps to Create Class BOM.

1)     Create characteristics that describe the objects

Transaction CT04

Characteristic Name: COLOUR , Allowed Values RED, BLUE, BLACK

 
( 2 )

CHARACTERSTIC ENGINE

( 2 )

CHARACTERISTIC EXHAUST

( 2 )

Create Class: COLOUR , Transaction CL01, Create Classes of type 200 & 300 with same name.




 

( 2 )

Input previously created Characteristic COLOUR in it.

In class type 200 maintaion Unit of measure, resultant item category and allowed in BOM indicator

( 2 )

Class: ENGINE
 
  ( 2 )

Input previously created Characteristic ENGINE in it

Class: EXHAUST

( 2 )

Input previously created Characteristic EXHAUST in it.

Create Material Master: SUPER BIKE, and Include these Classes in Classification View.

( 2 )

Create Configuration Profile for Super Bike , Transaction: CU41

 

  ( 2 )

Create BOM for Super Bike, Transaction: CS01

 

 ( 2 )

Go To Class Tab and add the classes as shown below

 

( 2 )

Create Material: Paint Red

( 2 )

And in Classification view, add class COLOUR with value 01(RED)

Repeat same to create other 8 materials tied up with other value combination ie Blue, Black, 1200 CC, 1500 CC, 1800 CC etc

To test this setup , Go To Transaction CU50

( 2 )

Assign values to characteristics

( 2 )

Select Result

Classes presented in BOM will be replaced by material number associated with characteristic values.

( 2 )

Advantages ( 1 )

For products with many variants, class items make the bill of material easier to maintain.

• The class item is used as a placeholder for an item, and has several objects allocated to it (for example, screws from
  different suppliers). Each object has a unique identifier in the class. Which object is replaced for the class item depends
  on the characteristic values that are required for a particular configuration of the material.
• If you enter all the possible objects for an item individually, you must allocate a selection condition to each item, so that
  only the component you require is selected when you configure the material.

If you use a class item, you no longer need to maintain these selection conditions. When you configure the material, the
system selects the component whose characteristic values in the class are identical to those required for this material.

Material requirements planning (MRP) is supported for class items.

 In Customizing functions for MRP, you can define that a check is made in MRP as to whether an order BOM exists. If an
order BOM does exist, requirements for a material selected from a class item are transferred to MRP.

Disadvantage ( 1 )

In a class item, the item quantity is always the same, regardless of which classified material is selected. For this reason,
only use class items in cases where you use the same quantity of different materials. As quantity modification is not supported.

Below are few enhancements Related to class nodes in variant configuration

Related Content

( 1 ) Text is copied from help.sap.com

( 2 ) Screens are captured from SAP IDES ( SAP ECC 6.0, release 7.8.01.014 ) , all master data is created by me

Appreciate if people who used it in their previous implementations can share their thoughts on this approach.

Related SAP Notes/KBAs

SAP Note 1302546: Incorrect aggregated quantities after deletion of subitems

SAP Note 177308: Class node: manual object search and changes

SAP Note 37484: CU50: Class node with action or procedure

SAP Note 1671129: Issue with Component Allocation

SAP Note 201647: @3Z@ class nodes: Collective note