Example: Selection in a Multi-Level BOM (SAP Library - Working with Parameter Effectivity)

Example: Selection in a Multi-Level BOM

You have created an item containing material M1, in the BOM for material FL01, using change number KD01. KD01 has the CUSTOMER effectivity type. You have assigned the value "Smith" to the CUSTOMER effectivity parameter, in change master record KD01.

You created component 2 without a change number valid from July 1 1999. You do not make an y changes to this component. Therefore M2 is alw ays valid and effective after 1 June 1999.

Single-Level BOM

This graphic is explained in the accompanying text

M1 is an assembly whose items you also create with reference to change master records with parameter effectivity. However, these items have the SERNR (serial number) effectivity type.

Multi-Level BOM

This graphic is explained in the accompanying text

The system only checks the effectivity of items P1 and P2 if the product is assembled for customer "Smith":

If product FL01 is assembled for customer "Smith" the system selects the valid component M1 (highlighted in yellow in the first evaluation list in the trace log). The system then checks the effectivity of the components in M1 (P1 or P2).

You enter the following values:

Effectivity Parameter	Value
CUSTOMER	Smith
MATNR	FL01
SERNR	1500

BOM for Customer Smith

This graphic is explained in the accompanying text

On the other hand, if product FL01 is assembled for a different customer, component M1 is invalid (highlighted in red in the evaluation list in the trace log). In this case, items P1 and P2 are not checked.

You enter the following values:

Effectivity Parameter	Value
CUSTOMER	Jones
MATNR	FL01
SERNR	1500

BOM for a Different Customer

This graphic is explained in the accompanying text