Material Master of Super BoM (MM02)V

ari

ant

Con

figu

rati

on

Source: SAP

• Basic Data 2 Screen: Set ‘Material is Configurable’ Indicator• To determine item category TAC in sales order, maintain a suitable item category group such as 0002 • MRP 2 View: Procurement type ‘E: In house Production’ • MRP 3 View: Strategy Grp. ’25: Make-to-order for configurable’ used for demo

• MRP3 View: Availability Check ’02: Individual Requirement’ • Classification view: Attach the variant class

Bill of Materials (CS01 / CS02 / CS03)

Vari

ant

Con

figu

rati

on

Source: SAP

Object Dependency in BoM (CS02)

Vari

ant

Con

figu

rati

on

Source: SAP

Components in Production Order can be selected using Object Dependency type Selection Condition

Routings (CA02) V

ari

ant

Con

figu

rati

on

Source: SAP

Operations in Production Order can be selected using Object Dependency type Selection Condition

Configuration Profile: Process

Vari

ant

Con

figu

rati

on

Source: SAP

Planned/production Order; explosion indicator None (others Single level or Multiple level)The material has a BOM that is not relevant to the sales order. Only the characteristics that describe the variant are required. The components are determined later during material requirements planning or production, so there is no need to explode the BOM in the sales order.

Sales order (SET): See next slide alsoIn the sales order, sales-relevant components are shown as sub-items of the header material. Requirements are transferred and pricing is calculated at component level, not at header material level.

Order BOMYou create a sales order. In order BoM, you can insert extra items or delete items manually. The changed BOM is stored as a separate BOM for the sales order.

Configuration Profile: SETV

ari

ant

Con

figu

rati

on

Source: SAP

This processing form means that in the sales order you can only process sales-relevant BOM items. You can use the item category group like 0004 at configurable material level to define that requirements transfer and pricing are at component level.

For example, a PC is made up of the components monitor, CPU, keyboard, and printer. These components are all salable materials that are manufactured separately. In the sales order, you want to see the individual components that make up the computer as order items, as well as the whole computer. In the sales order, these products are grouped together in a SET. For this reason, this type of processing is also referred to as set processing.

Configuration Profile: Dependencies

Vari

ant

Con

figu

rati

on

Source: SAP

Dependencies like Actions and Procedure can be assigned to Configuration Profile.

Configuration Profile: Variant Table

Vari

ant

Con

figu

rati

on

Source: SAP

• Tables are used to store combinations of values for different characteristics

• A table HD_1300_COLOR_PR is created in CU62 transaction.

It has 2 fields: HD_COLOR (key field) and SURCHARGE.

The selected characteristic will be transferred to HD_COLOR and surcharge to SURCHARGE2.

• The table contents are given below (see transaction CU60)

VK30: Has description entries for the surcharge column listed above

VK12: Will pick up pricing value based on condition type VA00

PricingV

ari

ant

Con

figu

rati

on

Source: SAP

Check definition of characteristic SURCHARGE2 – Additional data tab -> reference table and field

Simple method to achieve Variant Pricing is given below:• Create multiple value characteristic SURCHARGE2 referring to SDCOM-VKOND.

• Put this characteristic in the class HD-000 which was used for the configurable material

• Now go to CT04 and change the Characteristic HD_COLOR Go to values tab and select Red. Go to Extras-> Object Dependencies->Editor and then select Procedure. In front of 000010 Enter $self.surcharge2='HD-003_03'. Similarly Select Black to enter $self.surcharge2='HD-003_02‘. Same way 'HD-003_01’ for Silver

• VK30: Has description entries for the surcharge column listed above

• VK12: Will pick up pricing value based on condition type VA00

PricingV

ari

ant

Con

figu

rati

on

Source: SAP

VK30: Maintain descriptions for variant price conditions

(optional step; done while creating dependencies for surcharges; maintains consistencies of configuration)

VK11 / VK12: Maintain actual condition record for variant price surcharges

Pricing FactorsV

ari

ant

Con

figu

rati

on

Source: SAP

Pricing factors can only be maintained on characteristic level.

The syntax of pricing factors is as follows:

$SET_PRICING_FACTOR ($SELF, <characteristic>, <variant key>, <factor>)

This expression contains the following information:

• The characteristic that refers to structure SDCOM, in which variant conditions are defined.

• The variant key used to infer the condition for a characteristic value.

• The factor by which the surcharge increases.

Material VariantV

ari

ant

Con

figu

rati

on

Source: SAP

• For variants that are required frequently, create material variants, which can be produced without a sales order and kept in stock.

• When a sales order is received, check whether the variant is in stock and deliver immediately.

• The material master record of a material variant is linked to the configurable material and configured using the characteristics of the configurable material.

Material Variant in Sales Order

Vari

ant

Con

figu

rati

on

Source: SAP

On the value assignment screen, you can check whether the values assigned match the

configuration of a material variant.

Material VariantV

ari

ant

Con

figu

rati

on

Source: SAP

Replacement of configurable material by a material variant

Material VariantV

ari

ant

Con

figu

rati

on

Source: SAP

Item category gets changed to TAN; Pricing will also change as per new MTS product.

Summary of day 1V

ari

ant

Con

figu

rati

on

Source: SAP

By now, you should be comfortable with the following topics:

• Explain what Variant Configuration is and its use in make to order scenario

• Using Variant Configuration during sales order processing

• Configuration details like item category and condition types

• Classification System - Characteristics and Classes

• Super BoM, Configuration Profile, Object Dependencies

• Pricing Surcharges in sales order processing

• Using Material Variants for make to stock scenario

• Day 2: Understanding Object Dependencies in detail

Dependency TypesV

ari

ant

Con

figu

rati

on

Source: SAP

Pre ConditionV

ari

ant

Con

figu

rati

on

Source: SAP

Only if the model specified is racing, the bicycle can have 21 gears.

1. Create a precondition with the following source code:

MODEL eq 'Racing' and Specified MODEL

2. Allocate the precondition to value 21 of characteristic GEARS

Selection ConditionV

ari

ant

Con

figu

rati

on

Source: SAP

A selection condition is allocated to each component and each operation. This selection condition determines which components and operations are selected for a variant.

Changing Master Data with Dependencies

Vari

ant

Con

figu

rati

on

Source: SAP

In variant configuration, you can use reference characteristics with dependencies to change field values of tables for bills of material (BOMs), task lists, and master recipes.

Table names and fields are given below for reference.

Table STPO field MENGE can be used to change component quantities of BoM.

Table PLPOD field VGW01 can be used to change setup time of Operation.

ProceduresV

ari

ant

Con

figu

rati

on

Source: SAP

Procedures can set default values for a characteristic (can be overwritten by the user)

ProceduresV

ari

ant

Con

figu

rati

on

Source: SAP

• Set default values:

$SET_DEFAULT ($SELF, <characteristic>, <term>)

For example: ( $SET_DEFAULT ($SELF, COLOR_CHAR, 'BLUE'), $SET_DEFAULT ($SELF, GLOSS_CHAR, 'NONE') ) IF $root.PC_CASING_CHAR = 'TOWER'

• Delete default values:

$DEL_DEFAULT ($SELF, <characteristic>, <term>)

Produce a sum of the values for a characteristic in a multi-level configuration:

$SUM_PARTS ($SELF, <characteristic>)

It can be used to calculate the weight of components and transfer the same to structure VCSD_UPDATE, gross weight field BRGEW

• Add the components of a BOM together:

$COUNT_PARTS (<$SELF>)

• Surcharge for variant conditions in Pricing:

$SET_PRICING_FACTOR ($SELF, <characteristic>, <variant key>, <factor>)

Constraints and Dependency Net

Vari

ant

Con

figu

rati

on

Source: SAP

The main purpose of a constraint is to monitor the consistency of a configuration.

There are four sections in a constraint.

1. OBJECTS: Declaration of all classes and objects used.

2. CONDITION: Pre requisite for processing the constraint.

3. RESTRICTIONS: For interdependencies and consistency check; check and set values.

4. INFERENCES: Enter the characteristics for which characteristic values are to be inferred.

Constraints are grouped together in dependency nets.

The dependency net can be allocated to a configuration profile.

Example: The hard disk can only have the value ‘1620’ for a tower, or ‘850’ for a mini tower.

OBJECTS: PC IS_A (300) PC

RESTRICTIONS:

PC.HARD_DISK = ‘1620’ if PC.CASING = ‘Tower’,

PC.HARD_DISK = ‘850’ if PC.CASING = ‘Mini tower’.

ActionsV

ari

ant

Con

figu

rati

on

Source: SAP

Actions can be used to infer values for characteristics.

Actions can also be used to change field values in BOM items or operations in routings.

Procedures can set default values for a characteristic, which can be overwritten by the user. The user cannot overwrite values that are set by an action.

For new developments, use Procedures rather than Actions (to become obsolete)