<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

Classifying Object Types

<div id="content"><div class="parentsection"><div class="section"><div tabindex="0"><h3>Defining New Object Types as Classifiable</h3></div><p tabindex="0">You can classify objects that are not predefined as classifiable in the standard system by defining their object type as classifiable. To do this, follow these steps:</p><ol><li tabindex="0"><strong>Create Custom Programs and Configure Settings</strong>: Identify the master data table containing the objects and its key fields. Enter this information in the "Maintain Object Keys" section.</li><li tabindex="0"><strong>Specify Screens for New Objects</strong>: Navigate to "Maintain Object Types and Class Types" to define the screens that will be used for classifying the new objects. These screens must be created using the Screen Painter within the namespace 9000-9999 and will be available within Function Group CBCM.</li><li tabindex="0"><strong>Update Structure Entries</strong>: Add a new entry to either structure RMCLY or RMCLX, corresponding to the key field of the table.</li><li tabindex="0"><strong>Ensure Function Module Exists</strong>: Before using the new objects, ensure that the function module OBJECT_CHECK_XXXX (where XXXX is the name of the object file) exists. This module, created in the ABAP Workbench, checks the validity of the objects you wish to classify.</li></ol><p tabindex="0">Watch the following video to learn more about this process.</p><div class="kalturaVideoLessonWrapper"><div aria-label="This video shows you how to create a new Classifiable Object Type in Customizing. It explains the preconditions and steps in customizing." class="kalturaVideoLessonContainer" data-testid="video" id="1_al0oqmr6"></div></div><p tabindex="0">For detailed instructions, refer to the Implementation Guide (IMG) for classification.</p></div></div></div>

Definition of New Object Types to Enable Classification

<div id="content"><div class="section"><p tabindex="0">The following video shows how to classify objects that are not predefined as classifiable in the standard system, by defining their object type as classifiable. In this example, material masters are classified on a plant-specific basis.</p><div class="kalturaVideoLessonWrapper"><div aria-label="This video shows how to classify objects that are not predefined as classifiable in the standard system, by defining their object type as classifiable." class="kalturaVideoLessonContainer" data-testid="video" id="1_q9hv75pf"></div></div></div></div>

How to Classify Object Types and Create New Class Types

Implementing Classification in SAP S/4HANA Cloud Private Edition

Learn how to classify objects not defined in the standard system using custom programs and settings. Create screens, function modules, and key fields for object classification in SAP ABAP.<br><br># This description was auto-generated #

ZMigrated_mmcpLearningContent_11_Screenshot_01_Ani.mp4

You can also classify objects, that are not defined as classifiable, in the standard system. To do this, you must define the object type, as classifiable. You need to write your own programs, as well as, define settings in customizing. First, find out which file, that is, master data table, contains the objects, and which are the key fields of this table. Enter this data, under maintain object keys. To maintain object types and class types, enter the screens that are called for classifying the new objects. You must create these screens in the screen painter using namespace 9000 to 9999. All these screens are available in function group CBCM. You need a new entry in structure RMCLY or RMCLX. The new entry is the key field of the table. Before you can work with the new objects, function module, object, underscore, check, underscore, xxxx, that is, with xxxx, equals, name of object file, must exist. This must be created, in the ABAP workbench. This function module checks, whether, the objects you want to classify are valid.

Demo_S41420_Unit_1_Slide_4_new_object_type_MARC.mp4

Work scheduling in our company requires classes in which you can include material masters and classify them differently for different plants. This means that we want to classify material masters on a plant-specific basis. This is not possible in the standard system. We can classify everything. Then we must also be able to classify material masters on a plant-specific basis. This would be a classification of database table MARC. We need more master data before we can start customizing. We need screen building blocks. In the SAP GUI, we are in the SAP menu, Tools, ABAP Workbench, Overview, Object Navigator. This is transaction SE80. These subscreens must be created and assigned here in function group CBCM. Screens here. In the last demonstration, for example, we used screen 100. Double-click here, and we go to the menu, Screen, Test. In this dialog box, choose Enter. We see the screen. This is the field of the material number for transaction CL20N. We use the same in the last demonstration for documents. Back, screen 104, double click here, and we go the same way as before. We see the screen. These are the four fields of the document key for transaction CL20N. The same was created here in preparation for the plant specific material master. We scroll into the customer language room, i.e. to the numbers from 9000. screen 9114. Double click here. And we go the same way as before. We see the screen. These are the two fields of the key of mark for transaction CL20N. Here, we have copied screen 114 for work centers and changed it accordingly. The other three screens in the area of 9000 are also new and are also required immediately. In addition to the screens, we require a function module that checks that the plant-specific material master exists. This means whether an entry exists in the database table mark. Here under ABAP Workbench, Development, ABAP Editor. This is Transaction SE38. The name is generally object_Check_Name of the database table. The name here is object_check_MARC. display. This is the required function module. A copy template was also used here. Here, the function module for the database table Mara was copied and changed. So, these were the prerequisites outside of customizing. We will go to the customizing of the classes again. In the SAP GUI, we are in the SAP menu. Tools Customizing IMG Execute Project This is the transaction SPRO. Here in the SAP Reference IMG, cross application components, classification system. And here's the second entry classes. Here we have to start with the first entry. Define object keys. Attention twice here. The table is cross client. And the table is not only used by the classification system. Let's look at the mark entry. Here. Why does the entry exist? This is because it is used elsewhere. It is required in variant configuration. Details. That looks the same as for MARA. Only the key field for the plant is additional here. Back. Class type is maintained and also created here in the second entry. The initial screen is the object table. Let's look at the MARC entry. This is missing. Here he should have been between MARA and MCHA. Correct, MARC cannot be classified yet. That's why we choose New Entry. Table MARC, table text dor example, Material Master Plant. Here are the four screens from before with the numbers in the Customer Language Area 9000. Which views should classes for MARC have? For example, these three. Save Request Now, we want to create a class type. Here, Class Types, everything is empty here. We can select a new entry here. However, we can simply copy and adjust class type 001. Back, Table MARA, Class type 001. Copy. As the key, we choose a value from the customer language area. For example, ZZ1. The table is now marked. Do we want to change more? Perhaps fewer views in the master record of the class? Enter. 16 entries have been copied, that is, all class type specific entries here in the customizing hierarchy. To access the detail screen of the new class type, we must switch to the object table MARC again. Here is the detail view. Let's take a look at the five subitems for the new class type. No objects, because only one object type is allowed. Class status, organizational areas, text types, classification status, functions and filters for finding objects. Well so, and we save. Finally, we check the result by creating a class with this class type. Any name. For example, test again. Class type is ZZ1. Create. A description. We include any characteristic whose use in classes has not been restricted. For example, the color. Save. Finally, we check the result by classifying with this class and thus with this class type. Our new class. Only new assignments. Plant specific material numbers. Any material number, but also a plant. We assume that it has been checked in advance that this material number exists in this plant. The function module from initially also controls this. Any color, for example, red. The same material number in a different plant. Any color, for example, blue. The same material number in a different plant. Any color, for example, green. The same material number in a different plant. Any color, for example, yellow. Save. Finally, we check the result by searching for objects with this class and therefore with this class type. Our new class. Enter. With any color, that is, white card. And one of the two search buttons. We find both objects. Here also with the three character abbreviation for the object type. We can view the material. Select the line with the material number and select this here. The view of the classification. But now comes the great limitation. The view of the material master is not automatically enhanced with this plant-specific classification. The view of the material master remains unchanged. That is, we only see a classification at client level. We don't see our new class types easy one. and we are at the end of this demonstration.