<p>about your learning experience to help us improve.</p>

You've completed

cleanFiles/bookmap_Configuring_Classification_in_SAP_S_4HANA__en-US_learning-sap-com_lsc-prod.zip (MMCP-DROPZONE) - 2024-12-16T07:43:55.000Z

Using Classification in Variant Configuration

<div id="content"><div class="parentsection"><div class="section"><div tabindex="0"><h3>Variant Configuration: Class Type 300</h3></div><p tabindex="0">The following video explains the following class types:</p><ul style="list-style-type:disc"><li tabindex="0"><strong>300</strong>, for variant configuration for configurable materials, general maintenance task lists, and standard networks for project management.</li><li tabindex="0"><strong>301</strong>, for configurable model service specifications.</li></ul><div class="kalturaVideoLessonWrapper"><div aria-label="The following video explains the following class types: 300 for variant configuration for configurable materials, general maintenance task lists, and standard networks for project management. Class type 301 for configurable model service specifications." class="kalturaVideoLessonContainer" data-testid="video" id="1_mtdsf9pc"></div></div><p tabindex="0">You assign a configurable material to a variant class in material master maintenance or the configuration profile for the material.</p></div></div></div>

Variant Configuration: Class Type 300

<div id="content"><div class="section"><p tabindex="0">In the following demonstration, we will show an example from the variant configuration. We explain which model data is assigned to a variant configuration model. We show how to use the variant configuration in the sales order, for example.</p><div class="kalturaVideoLessonWrapper"><div aria-label="This video shows an example from the variant configuration. It explains which model data is assigned to a variant configuration model. It also shows how to use the variant configuration in the sales order." class="kalturaVideoLessonContainer" data-testid="video" id="1_x9p9hlad"></div></div><p tabindex="0">For more information on variant configuration or using classes in BOMs, check the SAP Library.</p><p tabindex="0"></p></div></div>

How to Use Classification in Variant Configuration

Implementing Classification in SAP S/4HANA Cloud Private Edition

ZMigrated_mmcpLearningContent_12_Image_05_Ani.mp4

For variant configuration, you need a class type that has the variant configuration indicator in customizing. In the standard system, class type 300 is defined for variant configuration for configurable materials, general maintenance task lists, and standard networks for project management. Class type 301 is for configurable model service specifications. To assign a configurable material to a variant class, you can use the characteristics of the class to describe a variant.

Demo_S41420_Unit_2_Slide_8_Variant_Configuration.mp4

The classification tools in variant configuration. In batch classification and variant configuration, we have class types that allow multiple object types. In the classification of batches and in variant configuration, we have so-called object hierarchies. We have the material master as the superior object of the hierarchy. This material master is classified manually. The sub-objects of the hierarchy automatically classified or configured. When you do this, the characteristics in the material master behave in the same way as for a class hierarchy. That is, only a value restriction takes place here and no classification takes place. Let's take a closer look. First, let's look at the configurable material. In the back-end system here in the SAP menu, production, master data, material master, material, change, immediately. This is transaction MM02 with this material number. We select Basic Data 2 and classification as views. In Basic Data 2, we see the flag that makes the material master configurable. And in the classification, but with class type 300, we see the Variant Class. In the standard system, we do not have a valuation here. A valuation would be a value restriction. We want to make value restrictions, for example, for shelter width. You can enter an interval here. You can use the F1 key to go to the characteristic display and see that the characteristic is single value and does not allow intervals as a valuation. However, these restrictions do not apply to value restrictions. and save the material master. In a second session, let's have a look at the behavior of this material in a sales order. SAP menu, Logistics, Sales and Distribution, Sales, Order, Create. This is transaction VA01, order type, sales organization, distribution channel, enter, sold to party, delivery data, customer reference. With this material number from the left window, enter. The variant configuration valuation UI is displayed automatically. Let's look at the first characteristic. This characteristic allows 3 values. Let's look at the second characteristic. This characteristic allows 5 values. If you select gas for the first characteristic, only 3 values are allowed for the second characteristic. This is a value restriction using object dependencies, more precisely, using a constraint that we will still look at. If you select electric for the first characteristic, only three values are allowed for the second characteristic, but three other values are allowed. The third characteristic is calculated automatically using object dependencies. Let's evaluate the characteristics on the second tab. It is interesting to see shelter width and shelter length. The value restriction from the material master has an effect here. And interval values are not allowed. Now we are still evaluating features of the third tab. The last two characteristics were calculated using object dependencies. However, the third and fourth characteristics were also evaluated using object dependencies. In the case of net value, you could control how the variant configuration influences pricing. Let's go further to the overview screen of the sales order. And save it. Let's look at more master data of the variant configuration model. For example, the bill of material. For example, in the Fiori Launchpad. For example, using transaction CS03, our material number from the left screen. You can use the F4 help here to find the only existing BOM. This is a configurable super BOM. Configurable, that is, object dependencies exist here. Here there is the column OD for object dependency. The last three BOM items have object dependencies. For example, here the road equipment. Double click to view the syntax. This is a selection condition. This means that this BOM item is required in planning and production if the value, 1, was entered for characteristic  T_FC008 in the configuration. Back. There are many assemblies here, as you can see in this column. Double click and continue. Again, a configurable super-BOM with the column OD. Back. Let's have a look at more variant configuration master data. A nice transaction for this is this Variant Configuration Modeling Environment app. This is Transaction PMEVC, with our material number, class type 300, plant 1010, and the BOM application PP01  Enter. In the tree structure on the left, you can see the following five entries. The material master, the configuration profile, the variant class, the bill of material, and the routing. Let's drill down the BOM. Here is again our BOM item with the road equipment. If you expand this BOM item, you also see the object dependency again, and the material number above. Double click the object dependency to display the details on the right. This is the change mode. The syntax is also displayed here in the editor. How do you write such syntax for the road equipment? On the left, you select the characteristic and characteristic value on which you want to make it dependent. For example, characteristic  T_FC008 = road equipment.  For example, from the value 1 equals with. Drag and drop this value into the editor, done. Or here with the second button. This is the value help. This is the F4 help, keyword $Parent, "dot", symbolic characteristic T_FC008,  operator equal, symbolic value 1, done. This can be controlled using this first button. According to the footer, we have error-free syntax. Here we have the configuration profile. Double click. Here's a lot of object dependencies. You can also see the object dependency here on the left. For example, a constrain net with a constraint and with a variant table. click. Due to this dependency with this variant table, you could not combine each of the three types of drive with each of the five engine performance values. Here are the two characteristics with their three or five values in the variant class. You can also have the system create object dependencies. This means that you do not have to enter syntax manually. For example, we do not want the second characteristic engine performance to be allowed to be assigned values until the first characteristic type of drive has been assigned a value. To do this, go to the context menu of the second characteristic engine performance and select this wizard. The dependency wizard starts. Continue. We want to control when we can. This is already selected correctly. Continue. We want to make it dependent on this characteristic. This is already selected correctly. Continue. We don't want any specific value. We want any value. Continue. Any description here. Continue. Here yes, reusable. Then we need a name for the object dependency, continue, and done. The dependency wizard created everything automatically. Save. You can test the complete model in the simulation. This is possible here, or in a separate app. This is the material configuration simulation modeling app. This is Transaction CU50. You can use this button to load an existing configuration. For example, our sales order from earlier. This is our sales order. Enter and this first button opens the value assignment screen. This sixth button opens the BOM. This is the configured BOM. These first BOM items have no object dependencies and are therefore in the configured BOM for each configuration. See last and empty column. Here, as the last BOM item, we see the road equipment. Here, we can also see in the last column that object dependencies exist. Now let's test that the road equipment disappears if we don't want to have it. This is why you can return to the characteristics here. Here 0 equals without road equipment, and back to the configured BOM. The road equipment has disappeared. If you select All Components under View then Scope, here you can also see the road equipment again. The red Minus sign indicates that the BOM item has been removed. We are at the end of this demonstration.