<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

Controlling Class Customization

<div id="content"><div class="parentsection"><div class="section"><div tabindex="0"><h3>Settings for Classes</h3></div><p tabindex="0">The following video introduces the settings you can customize.</p><div class="kalturaVideoLessonWrapper"><div aria-label="This video contains the topics of customizing of Classifiable Object Types , Class Types and Class Groups." class="kalturaVideoLessonContainer" data-testid="video" id="1_r662rjkq"></div></div></div></div></div>

Settings for Classes

<div id="content"><div class="section"><p tabindex="0">The following video shows how to control customization for classes.</p><div class="kalturaVideoLessonWrapper"><div aria-label="This video shows how to control customization for classes.." class="kalturaVideoLessonContainer" data-testid="video" id="1_mljhkjc5"></div></div></div></div>

How to Control Customizing for Classes

Implementing Classification in SAP S/4HANA Cloud Private Edition

ZMigrated_mmcpLearningContent_11_Image_02_Ani.mp4

For each class type, you define class statuses, organizational areas, text types for classes, classification statuses, and functions and filters for finding objects. The standard system has predefined class statuses and classification statuses. You can check the statuses and change them if required. You can define groups for classes, as you can for characteristics, to help you find classes. Class groups are for all class types.

Demo_S41420_Unit_1_Slide_2_Setting_for_Classes.mp4

What could a possible business example for this customizing chapter look like? We check the standard customizing and consider whether adjustments are necessary. Now let's go to the customizing of the classes. In the SAP GUI, we are in the SAP menu, Tools, Customizing, IMG, Execute Project Equals Transaction SPRO. Here in the SAP Reference IMG, in the Implementation Guide, Cross Application Components, Classification System, and here's the second entry classes. This entry contains four subitems. The first two subitems are discussed in detail here. We do not have to look at the third subitem, the class groups, again, as it behaves exactly as with the characteristic groups. The last and therefore fourth sub-item, the user profiles, we will look at in detail later. Let's start with the first point, the object keys. Twice caution. Once you have done this, this customizing activity is cross-client. The second is that not only settings for the classification system are made here, but also for other applications such as document management. Each object type, that is, every database table whose entries we want to classify, must be contained here. However, this has already been achieved in the standard system in the delivery version. For example, material master equals database table MARA. The following is of interest for classification. First, if the material master is to be displayed from the search result, this is done using transaction MM03. As the name of the material master is to be displayed in an object list, such as in the search result, this name is found in the field maktx of table MAKT. The entry in the middle right is still of interest for the object dependency in the variant configuration. The material number is queried in the object dependency with the syntax  scenario. Back. And we start the same for example for documents equals database table DRAW. The following is also of interest for classification. First, if the document is to be displayed from the search result, this is done using transaction CV03N. If the name of the document is to be displayed in an object list, this name is found in the table DRAT in the field DKTXT. The entry in the middle right is still of interest for the object dependency in the variant configuration. Here, the syntax type and nr inversion in part stands for the four key fields. Return to the customizing menu. If an entry is made in the first subitem, you can start with the second subitem. Maintain object types and class types. This customizing starts with the object type. Here are the object tables. Again, there is a detail screen for the object table MARA. What are we setting here? On the left-hand side of the detail screen, we find subscreens for object-specific views in classification transactions. What is meant by that? Here we see a screen Module 100 for Transaction CL20N. Let's check that in a second session. Here we can find in the menu of the classification system. Under assignment. Here this Transaction CL20N. This is screen number 100. You can control that. We go to, menu option, system, status, and here is the control of the screen number 100. Back. The top right is the maximum tab pages of classes for this object type. You can also control that. Let's look at a material class. There are exactly the five tab pages that are selected on the left. In addition, there is a first tab called Basic Data. Since they cannot be deselected, this has not been included in customizing. Attention, we will get to know another 7th tab page right away. Back. At the bottom right, the entry material is also important for object dependencies and variant configuration. Back and we look at these details for documents for table draw. We have other screen building blocks. For example, in transaction CL20N, we need four fields to enter the entire key of documents. We also have fewer tabs here as we can control. For example, document class CL0001. We have the basis data and three other tab pages here. Back. At the bottom right, the entry document is again important for object dependencies and variant configuration. Back. The class type now follows on the left in the tree structure of the hierarchical customizing. These are the four class types that exist here for Material Masters. Again, there is a detail screen. This can be started from the menu, using a button, or by double-clicking. On the left, you can further restrict the tab pages for the classes of this class type. On the bottom left, you can specify whether engineering change management and change documents are also possible for classification. For characteristic maintenance and for class maintenance, both are always possible and therefore cannot be set here. On the right, there are other class type specific settings. A class type is the standard class type for each object type. This is preferably proposed. Multiple classification, that is, you can assign a material master to several material classes of class type 001. The next flag would only allow you to classify material masters using material master maintenance. The indicator is not set that is, you also classify a material master using transactions CL20N and CL24N. In another session, check that this is not allowed for all class types. For example, transaction CL24N. For example, class type 018 for task lists. Any class of this class type. Only new assignments. The system issues an error message in the footer. Back to customizing. The next two flags are also not set here. Therefore, we go back and go to class type 300. Both indicators are set on the detail screen of class type 300. The first means that this is a variant class type. This means that you can select such classes in the configuration profile of the variant configuration. In this way, valuation interfaces are created there. The second flag is also set here. Multiple objects allowed, or rather multiple object types allowed. In this way, you can assign objects of different object types to such a class. Which object types are these? This is defined here on the left under Objects. Here we find a lot of entries. Why are these so many? These are all configurable and all configured object types. Return to class type 001. The next flag is called class node and it is not set here. This flag is set in class type 200. Here. This flag generates a 7th tab page in class maintenance. Let's control that. Class type 200. Any class of this class type. And we have this 7th tab. You can use this tab page to allow classes as items and BOMs. This can only be used in configurable BOMs. Back. The next flag is used for ALE to collect material numbers that are to be distributed together. The penultimate flag allows class hierarchies. The last flag allows you to create tables for the search and the classification system for each class. All subitems on the left below the class type are class type specific. sub-item is empty. Since the class type does not have multiple objects allowed, you must not enter anything here. The second sub-item is the class status. The class status is class type specific and has a detail view for each status. What does released mean? Double click. What does locked mean? Double click. What does in preparation mean double click. No adjustment is necessary here. However, you can change settings freely. The third sub item here is the organizational areas. The fourth sub item here is the types of long texts. The fifth sub item here is the classification status. In contrast to the class status, there are no further details here. The setting for automatic release was of interest here. See status In the last sub-item, we find the filter report for the search in classes. This is not a standard. And we find transactions that can be jumped from the search result. Transaction MM02 is not a standard here. This is class customizing.