SAP Master Data Governance on SAP S4HANA V18_Part8 PDF

UNIT 5 MDG Multiple Object Processing and Mass Changes Lesson 1 Exploring Multiple Object Processing 348 Exercise 11: Perform Multiple Material Record Processing...

UNIT 5 MDG Multiple Object Processing and Mass Changes Lesson 1 Exploring Multiple Object Processing 348 Exercise 11: Perform Multiple Material Record Processing 353 Lesson 2 Exploring Hierarchy Processing 367 Exercise 12: Perform SAP MDG-S - Hierarchy Maintenance 377 Lesson 3 Explaining Material Mass Changes and Multiple Object Processing 390 Exercise 13: Perform a Simple Material Mass Update for Dedicated Fields 393 UNIT OBJECTIVES Explore multiple object processing Explore hierarchy processing Explain material mass changes and multiple object processing © Copyright. All rights reserved. 347  Unit 5 Lesson 1 Exploring Multiple Object Processing LESSON OBJECTIVES After completing this lesson, you will be able to: Explore multiple object processing Mass Changes and Multiple Record Processing Common characteristics of Multi-record processing are: Well-defined governance process with multiple workflow steps for a limited number of Business Partners. Typically a collaboration of multiple processors. Governance processes exist for single and multiple objects. Examples: - An account manager wants to compare and harmonize sales data for all Customers belonging to the account. - A strategic buyer wants to update purchasing conditions of all relevant Suppliers based on a newly signed contract. Common characteristics of Mass Processing are: Interactive master data change process for a huge number of Business Partners. Typically ad-hoc / on-request / project-based processing by one data specialist. Examples: - Change dunning parameters for all C-Customers of a country based on a newly defined process. - After reorganization in purchasing, Suppliers are assigned to newly responsible purchasing groups. 348 © Copyright. All rights reserved.  Lesson: Exploring Multiple Object Processing Processing of Multiple Objects: Multi-Record Processing: Getting in Figure 315: Processing of Multiple Objects: Multi-Record Processing The process to change multiple Business Partners is with a spreadsheet-like UI. Start from the search result list: 1. Select multiple Business Partners. 2. Choose the Multi-Processing button. Pre-defined Change Request types are: Multi-Processing for Customer Sales. Multi-Processing for Customer Financials. Multi-Processing for Vendor Purchasing. Multi-Processing for Vendor Financials. Multi-Record Processing: Functionality Figure 316: Multi-Record Processing: Functionality Functions for rows are: © Copyright. All rights reserved. 349 Unit 5: MDG Multiple Object Processing and Mass Changes Add new rows. Copy rows. Delete rows. Functions for field values are: Edit single fields. Find and replace. Select rows with same value. Copy value to selected rows. Visualize/handle changes are: Highlight changes. Discard changes. Switch On or Off Highlight Changes Figure 317: Multi-Record Processing: Switch On or Off Highlight Changes The Highlight Changes button, delivered in some template UI configurations, allows the user to toggle the highlight changes function in multi-record processing. At startup, the highlighting of changes is always switched Off. This may enhance UI performance in certain cases. For more information, see SAP note 2547067 - MR Processing: Switch "Highlight Changes" and How To Guides on the SCN, such as Create User Interface for Multiple-Record Processing. 350 © Copyright. All rights reserved.  Lesson: Exploring Multiple Object Processing Change Request Types for Multiple Objects Figure 318: Change Request Types in Master Data Governance MDG Change Requests can be used for different tasks. Besides single object processing, they manage mass change processes, multiple object, and form-based workflows. Note: When a change request is approved, all object changes contained in it are approved. In other words, activities with one change request effect all contained objects. Change Request Types for Multiple Object Processing Figure 319: Change Request Types for Multiple Object Processing With Change Requests, it is possible to work with multiple objects in one transaction. Change Requests for multiple processing can contain multiple objects (as long as they are the same object type, for example, a material and a supplier in one multiple Change Request is not possible), and manage hierarchy processing and mass changes. © Copyright. All rights reserved. 351 Unit 5: MDG Multiple Object Processing and Mass Changes Change Request Workflow for Multiple Object Processing Figure 320: Change Request Workflow for Multiple Object Processing For mass changes or other multiple object management features, it is necessary to prepare an appropriate change request. After this, the end user can select the objects and assign them to the Change Request. The Change Request Type determines the workflow steps, agent determination, validations, and so on - in exactly the same manner as was for a single object Change Request. Change Request Type Definition Figure 321: Change Request Type Definition The determination of whether a change request is appropriate for multiple processing is defined in MDG customizing (the Implementation Guide). For an example of Business Partner Change Requests, see the figure, Change Request Type Definition. 352 © Copyright. All rights reserved.  Unit 5 Exercise 11 Perform Multiple Material Record Processing Simulation: Perform Multiple Material Record Processing For more information on Perform Multiple Material Record Processing, please view the simulation in the lesson Exploring Multiple Object Processing online in the SAP Learning Hub. Business Scenario You have the task to create and change data for different material master records using one single change request. In MDG you can work with the internet based NetWeaver Business Client (NWBC) or via the SAP Fiori launchpad. You can use Multiple-Record Processing to maintain several materials inside one Change Request, using a table-like UI. In this exercise, you learn how to use Multiple-Record Processing in SAP MDG-M. You can find a How-To Video for SAP Master Data Governance for Material (http:// scn.sap.com/docs/DOC-56797), which shows how to apply the copy materials feature in multi-records processing (available as of release MDG8.0). You can also find a How-To Guide: Create User Interface for Multiple-Record Processing (http://scn.sap.com/docs/ DOC-48895) to create new configurations for material. The delivered UI configurations can be used as template to build new tabular interfaces for customer needs. The buttons for add, copy, remove, and discard materials/sub-objects are included in these four delivered change request types for Multi-Record Processing MDG 1909: MATLMRP, MATLPUR, MATSAL, and MATUOM. Note: In this exercise, when the values include ##, replace the characters with the number that your instructor assigned you. In MDG you can work with the SAP NetWeaver Business Client (NWBC) or via the SAP Fiori launchpad. Task 1: Check Change Request Types for Multiple-Record Processing and Parameters In this exercise, you will check the existing Change Request Types in the Customizing for Material. You will also check the application parameters for highlighting the changes in the Multiple-Record Processing UI. 1. Customize settings. In the transaction MDGIMG, navigate to Master Data Governance → General Settings → Process Modeling → Change Requests → Create Change Request Type. © Copyright. All rights reserved. 353 Unit 5: MDG Multiple Object Processing and Mass Changes 2. Find the Change Request Types for Material. 3. Which Change Request Types are enabled for Multiple-Record Processing? Write down the change request types. Change Request Type Description Task 2: Multiple-Record Change Request (Basic Data and Planning Data Using Master- Detail Table Maintenance) In this exercise, you are a product manager and want to make changes to three different material master records using one change request. You can maintain the data using Multiple- Record Processing. 1. Search for Material T-FL1A*## in SAP Fiori launchpad. Under Material Governance → Manage Material, search for the material T-FL1A*## (e.g T-FL1A*01 for group 01). The system should show six material numbers in the results list. Select all of these materials and choose Multi-Processing. 2. In the pop-up select the Change Request Type Multi Pro. for Planning Data (select) and choose OK. 3. Adapt the column setting of table MATERIALS to change Lab/Office and Old Material Number. 4. To make the changes on these materials choose Edit. The system creates a Change Request. Enter a description for the Change Request, including your group number and close the Change Request UIBB to see more data. With this type of UI the content of the dependent tables depends on the lines you selected in the first table. For all materials with material type ROH change the old material number to “ABC”. 5. Make some changes on plant level. Mark all materials and close the Material Descriptions UIBB to see all plant dependent data in the table Planning. 6. Assign all materials to plant 1000. 7. Check your workflow inbox or open the My Change Request tile. Process the new Change Request. All changed fields are marked in yellow. Choose Activate to approve the changes. Task 3: Copy Multiple Materials from Search using Multiple-Record Change Request In this task, you are acting as a product manager. You want to copy three different material master records using one change request. You can create new materials using multi-record processing. 1. Use the Manage Material tile and search for material using search criteria T-FL1A*##. The system shows six material numbers in the result list. Select all of these materials besides T-FL1A## | Engine | HALBand choose Multi-Processing (Copy). 354 © Copyright. All rights reserved.  Lesson: Exploring Multiple Object Processing 2. In the pop-up select the Change Request Type Multi Pro. for Planning Data (select) and choose OK. 3. To create these new materials the system automatically creates a new Change Request. Enter a description for the Change Request, including your group number. Minimize the Change Request UIBB to see more data. With this type of UI the content of the second table depends on the lines you selected in the first table. Select all materials to see all the dependent data in UIBBs Material Description and Planning. Change the temporary © Copyright. All rights reserved. 355 Unit 5: MDG Multiple Object Processing and Mass Changes material numbers to T-FL1A6##, T-FL1A7##, and so on in the Materials UIBB. Check if all dependent tables also get the new material numbers. 4. Submit the Change Request and note your Change Request number. Close the window. 5. Open your workflow inbox or your My Change Request tile and check the new Change Request. 6. Click on your Change Request number. Then choose the Highlight Changes button. All new data lines have the create icon and all new fields are marked in yellow. 7. Choose Edit. Select all materials and open Material Descriptions. Choose Add. Add the language Croatian for all materials. 356 © Copyright. All rights reserved.  Lesson: Exploring Multiple Object Processing 8. Filter the lines with language key HR. Select all new lines. Change the description for all materials to Ekran. 9. Choose Save, then choose Activate to approve the changes. © Copyright. All rights reserved. 357  Unit 5 Solution 11 Perform Multiple Material Record Processing Simulation: Perform Multiple Material Record Processing For more information on Perform Multiple Material Record Processing, please view the simulation in the lesson Exploring Multiple Object Processing online in the SAP Learning Hub. Business Scenario You have the task to create and change data for different material master records using one single change request. In MDG you can work with the internet based NetWeaver Business Client (NWBC) or via the SAP Fiori launchpad. You can use Multiple-Record Processing to maintain several materials inside one Change Request, using a table-like UI. In this exercise, you learn how to use Multiple-Record Processing in SAP MDG-M. You can find a How-To Video for SAP Master Data Governance for Material (http:// scn.sap.com/docs/DOC-56797), which shows how to apply the copy materials feature in multi-records processing (available as of release MDG8.0). You can also find a How-To Guide: Create User Interface for Multiple-Record Processing (http://scn.sap.com/docs/ DOC-48895) to create new configurations for material. The delivered UI configurations can be used as template to build new tabular interfaces for customer needs. The buttons for add, copy, remove, and discard materials/sub-objects are included in these four delivered change request types for Multi-Record Processing MDG 1909: MATLMRP, MATLPUR, MATSAL, and MATUOM. Note: In this exercise, when the values include ##, replace the characters with the number that your instructor assigned you. In MDG you can work with the SAP NetWeaver Business Client (NWBC) or via the SAP Fiori launchpad. Task 1: Check Change Request Types for Multiple-Record Processing and Parameters In this exercise, you will check the existing Change Request Types in the Customizing for Material. You will also check the application parameters for highlighting the changes in the Multiple-Record Processing UI. 1. Customize settings. In the transaction MDGIMG, navigate to Master Data Governance → General Settings → Process Modeling → Change Requests → Create Change Request Type. 358 © Copyright. All rights reserved.  Lesson: Exploring Multiple Object Processing 2. Find the Change Request Types for Material. a) For more details, refer to exercise Perform Parallel Change Requests for a Single Material. From the menu choose Selection → By Contents... and use Data Model = MM to find the relevant change requests. To see if they are enabled for Multiple-Record Processing, select a Change Request and inspect its Business Activities via the dialog to the left. They should be assigned to the Business Activity MATM. 3. Which Change Request Types are enabled for Multiple-Record Processing? Write down the change request types. Change Request Type Description a) This is the result: Change Request Type Description MATLMRP Multi Pro. For Planning Data (select) MATLPUR Multi Pro. For Purchasing Data (select) MATLSAL Multi Pro. For Sales Data (select) MATLUOM Multi Pro. For Dimensions Data (select) MATMRP Multi Pro. For Planning Data (full) MATPUR Multi Pro. For Purchasing Data (full) MATSAL Multi Pro. For Sales Data (full) MATUOM Multi Pro. For Dimensions Data (full) Task 2: Multiple-Record Change Request (Basic Data and Planning Data Using Master- Detail Table Maintenance) In this exercise, you are a product manager and want to make changes to three different material master records using one change request. You can maintain the data using Multiple- Record Processing. 1. Search for Material T-FL1A*## in SAP Fiori launchpad. Under Material Governance → Manage Material, search for the material T-FL1A*## (e.g T-FL1A*01 for group 01). The system should show six material numbers in the results list. Select all of these materials and choose Multi-Processing. © Copyright. All rights reserved. 359 Unit 5: MDG Multiple Object Processing and Mass Changes a) 2. In the pop-up select the Change Request Type Multi Pro. for Planning Data (select) and choose OK. 3. Adapt the column setting of table MATERIALS to change Lab/Office and Old Material Number. a) Choose the Settings button on the top right corner of the table Materials. b) In the Personalization window, scroll down and select Lab/Office and Old Material Number. Then choose OK. 4. To make the changes on these materials choose Edit. The system creates a Change Request. Enter a description for the Change Request, including your group number and close the Change Request UIBB to see more data. With this type of UI the content of the dependent tables depends on the lines you selected in the first table. For all materials with material type ROH change the old material number to “ABC”. a) As Description for the change request, enter Change old material number for material type ROH - GR## b) Hover your mouse over one line, where Material Type is equal to ROH. Use the context menu (right-click) on value ROH and choose Select Rows with Identical Value. 360 © Copyright. All rights reserved.  Lesson: Exploring Multiple Object Processing c) Enter the new value ABC in field old material number of a selected material. Open the context menu and choose Copy Value to Selected Rows d) For two of the materials, enter G##in column Lab Office. e) Save the changes by choosing Save. Make sure that there are no more lines selected in the table. 5. Make some changes on plant level. Mark all materials and close the Material Descriptions UIBB to see all plant dependent data in the table Planning. a) Minimize Materials and Material Description and scroll down to the Planning area. b) Select all material data related to plant 1030 and enter the maximum lot size 20 for this plant data. Save your changes. 6. Assign all materials to plant 1000. a) In the Materials area select material T-FL1A1##. © Copyright. All rights reserved. 361 Unit 5: MDG Multiple Object Processing and Mass Changes b) Scroll down to the Planning area, where you will see the corresponding plants. Select the line for plant 1030 and choose Copy. c) In window Copy to New Data choose Copy Source Key for your selected material and change the value for plant to 1000. Then choose Copy. d) Mark all materials in UIBB Materials and restrict the data in UIBB Planning to plant 1000 (using the filter for column Plant) to see the new lines. e) Submit the Change Request and note your Change Request number. 7. Check your workflow inbox or open the My Change Request tile. Process the new Change Request. All changed fields are marked in yellow. Choose Activate to approve the changes. Task 3: Copy Multiple Materials from Search using Multiple-Record Change Request In this task, you are acting as a product manager. You want to copy three different material master records using one change request. You can create new materials using multi-record processing. 362 © Copyright. All rights reserved.  Lesson: Exploring Multiple Object Processing 1. Use the Manage Material tile and search for material using search criteria T-FL1A*##. The system shows six material numbers in the result list. Select all of these materials besides T-FL1A## | Engine | HALBand choose Multi-Processing (Copy). 2. In the pop-up select the Change Request Type Multi Pro. for Planning Data (select) and choose OK. 3. To create these new materials the system automatically creates a new Change Request. Enter a description for the Change Request, including your group number. Minimize the Change Request UIBB to see more data. With this type of UI the content of the second © Copyright. All rights reserved. 363 Unit 5: MDG Multiple Object Processing and Mass Changes table depends on the lines you selected in the first table. Select all materials to see all the dependent data in UIBBs Material Description and Planning. Change the temporary material numbers to T-FL1A6##, T-FL1A7##, and so on in the Materials UIBB. Check if all dependent tables also get the new material numbers. a) Enter Copy multiple materials - GR00 as Description for the change request and minimize the change request area. b) Select all materials to see the dependent data in the Material Description and Planning area. c) Change the temporary material numbers to T-FL1A6##, T-FL1A7##, etc. in the Materials UIBB. Check if all dependent tables also get the new material numbers. 4. Submit the Change Request and note your Change Request number. Close the window. 5. Open your workflow inbox or your My Change Request tile and check the new Change Request. 6. Click on your Change Request number. Then choose the Highlight Changes button. All new data lines have the create icon and all new fields are marked in yellow. 7. Choose Edit. Select all materials and open Material Descriptions. Choose Add. Add the language Croatian for all materials. 364 © Copyright. All rights reserved.  Lesson: Exploring Multiple Object Processing 8. Filter the lines with language key HR. Select all new lines. Change the description for all materials to Ekran. 9. Choose Save, then choose Activate to approve the changes. © Copyright. All rights reserved. 365 Unit 5: MDG Multiple Object Processing and Mass Changes LESSON SUMMARY You should now be able to: Explore multiple object processing 366 © Copyright. All rights reserved.  Unit 5 Lesson 2 Exploring Hierarchy Processing LESSON OBJECTIVES After completing this lesson, you will be able to: Explore hierarchy processing Hierarchy Management Figure 323: Hierarchy Management: Enabling Hierarchies in the Data Model Hierarchies are enabled for an entity type by changing the Hierarchies attribute to a value other than No hierarchy. The result is a hierarchy table that allows storing parent-child relations between entities of this entity type (and also between additional entity types if specified). A hierarchy can be defined as version, name, or edition dependent. Animation: Hierarchy Management: Enabling Hierarchies in the Data Model For more information on Hierarchy Management: Enabling Hierarchies in the Data Model, please view the animation in the lesson Exploring Hierarchy Processing, online in the SAP Learning Hub. © Copyright. All rights reserved. 367 Unit 5: MDG Multiple Object Processing and Mass Changes Additional Entity Types Figure 325: Additional Entity Types A hierarchy may contain entities of additional entity types as nodes. These entity types are specified under Entity Types for Hierarchies (in addition to the hierarchy name). By default, Use has the value No Special Use. You can also choose the value Ranges Permitted on End Nodes. This enables you to specify ranges of entities at the leaves of the hierarchy. In the example shown in the figure, Additional Entity Types, the entity type CCTR (Cost Center) has been specified as an allowed entity type within the Cost Center Group Hierarchy. Ranges on end nodes have been enabled. Another use case is to support text nodes. Data model settings are: Hierarchies can be switched on for entity types of usage and storage type 1. Hierarchies can be defined as edition dependent. Hierarchies can be defined as version dependent. - The hierarchy version is a fixed and predefined CHAR field of length 3. The hierarchy version cannot be modeled as an entity type. It is globally defined and valid across data models. Hierarchies can be defined as hierarchy name dependent: - Hierarchies always have a name that is modeled as an additional entity type regardless of whether the hierarchy is name dependent or not. - The hierarchy name can have leading relations (additional key fields). Additional entity types can be used as nodes within hierarchies. These types can be of usage and storage type 1, 2, or 3. - Example: Text nodes can be modeled as an entity type and entered as an additional entity type. - Constraint: Exactly one entity type must be of usage Hierarchy Name. Entity types used as hierarchy names must must have super-ordinate entity types. A hierarchy can have multiple key fields: - Constraint: key fields must also be key fields in the entity type for which the hierarchy is defined. Hierarchy relations can have additional attributes. 368 © Copyright. All rights reserved.  Lesson: Exploring Hierarchy Processing Additional Attributes in the Hierarchy Relation Figure 326: Additional Attributes in the Hierarchy Relation 1/2 Hierarchy relationships can have additional attributes. An attribute of the relationship can be specified by a data element or by a reference to an entity type. In this case the data element is optional and taken from the entity type. You can specify an alternative data element if necessary. The second example in the figure, Additional Attributes in the Hierarchy Relation, shows that if you want to add attributes to the relationship of the entity type for which the hierarchy has been defined, you must specify it again under Entity types for Hierarchies. Figure 327: Additional Attributes in the Hierarchy Relation 2/2 Attributes of the hierarchy relationship can be initially maintained during the insertion of an entity into the hierarchy. Later, the attributes can be changed by calling Change Hierarchy Attributes or Change Range from the context menu depending on whether a discrete entity value is specified or a range. © Copyright. All rights reserved. 369 Unit 5: MDG Multiple Object Processing and Mass Changes Collective Processing: Capabilities Figure 328: Collective Processing: Capabilities In general, hierarchies are maintained in the hierarchy view of the Collective Processing generic application. The main features are: You can insert new or existing nodes. You can insert several nodes in one step. You can move nodes (including sub-nodes) with arrow buttons. Drag-and-drop functionality is also supported. You can find nodes in the hierarchy. You can expand ranges to see which entities are currently assigned. At runtime: Like other master data hierarchies, they are maintained under the governance of change requests. The hierarchy can form nets (a node can have multiple higher-level nodes). Validations can be added in the rule service BAdI. For example, to enforce specific cardinalities like single higher-level nodes. A search for nodes in the hierarchy can be performed. Authorization can be granted on the level of arbitrary nodes of the hierarchy. Version-dependent hierarchies can be copied to new versions. Ranges can be expanded to see which entities are currently assigned. 370 © Copyright. All rights reserved.  Lesson: Exploring Hierarchy Processing Collective Processing: Layout Figure 329: Collective Processing: Layout The layout of the hierarchy view is derived automatically: Columns for descriptions are included according to the text settings of all entity types specified for the hierarchy. Columns for attributes of the leading entity type are included (unless disabled in the field property view by checking No Result List). Maintenance UI: Hierarchies are maintained in the hierarchy view of the collective processing application which is generic and works for all data models. The UI supports drag-and-drop functionality. Additional UI elements are available that can be added to the single item maintenance UI to maintain information on higher-level nodes and predecessors. Constraint: Currently these elements only support the entity type for which the hierarchy is defined. Pre-Delivered Models are: Table 15: Pre-Delivered Models Data Model Entity Type Version/Name Dependent Edition Dep. 0G CCTRG Not Version-dependent / Cross-name Yes 0G CELEMG Not Version-dependent / Cross-name Yes 0G CONSGRP Version-dependent / Not Cross-name Yes (name dependent) 0G FRSI Not Version-dependent / Cross-name Yes 0G FSI Version-dependent / Not Cross-name Yes (name dependent) 0G PCTRG Not Version-dependent / Cross-name Yes BP BP_HEADER Not Version-dependent / Not cross- No name (name dependent © Copyright. All rights reserved. 371 Unit 5: MDG Multiple Object Processing and Mass Changes Extensibility - Adding a Hierarchy to Model MM It is possible to extend the SAP hierarchy models or to create new hierarchy models within an SAP data model. The following model extension use cases explain this in more detail: Setting up a hierarchy in model MM (Material Domain) where no hierarchy is delivered by SAP. Setting up an alternative hierarchy in model BP (Business Partner Domain). Adding entity types as additional nodes in an SAP hierarchy. Figure 330: Extensibility - Adding a Hierarchy to Model MM, Overview 1/4 A hierarchy can be added to model MM (Material Domain) by creating additional entity types (with the reuse area MDG), one for the hierarchy and one for the name. In the following example, a work package hierarchy is set up where materials can be assigned. These work packages belong to design studies and depend on the year of the development. Therefore, another entity type for the year is created and maintained as a key field. Three entity types are created: One for the design study name (ZHRCHNAME) One for the work packages (ZWPHIER) One for the year (ZYEAR) The hierarchy name ZHRCHNAME (which identifies the design study) and the entity type MATERIAL are then specified under Entity Types for Hierarchies. Two relationships must be created to make the year a key field for the hierarchy. 372 © Copyright. All rights reserved.  Lesson: Exploring Hierarchy Processing Figure 331: Extensibility - Adding a Hierarchy to Model MM, Overview 2/4 Three entity types are created: One for the design study name (ZHRCHNAME), one for the work packages (ZWPHIER) and one for the year (ZYEAR). Figure 332: Extensibility - Adding a Hierarchy to Model MM, Overview 3/4 The hierarchy name ZHRCHNAME (which identifies the design study) and the entity type MATERIAL are then specified under Entity Types for Hierarchies. Figure 333: Extensibility - Adding a Hierarchy to Model MM, Overview 4/4 Two relationships have to be created to make the year a key field for the hierarchy. © Copyright. All rights reserved. 373 Unit 5: MDG Multiple Object Processing and Mass Changes Extensibility - Adding a Hierarchy to Model MM Figure 334: Extensibility - Adding a Hierarchy to Model MM In the hierarchy view of collective processing, you can maintain names for the design studies, create work package hierarchies below them, and assign materials to the work packages. Two design studies have been defined (CAR WING and REAR VIEW MIRROR). The first one contains three work packages and two materials at the leaf level. The second one contains two work packages. No materials are assigned so far. Using an Alternative Hierarchy in Model BP Figure 335: Extensibility - Using an Alternative Hierarchy in Model BP In the collective processing UI, you can maintain hierarchies in different versions and for different purchasing organizations. In this example, hierarchy version 001 has been created for purchasing organization 0001. 374 © Copyright. All rights reserved.  Lesson: Exploring Hierarchy Processing Adding an Entity Type to Hierarchy in Model BP Figure 336: Extensibility - Adding an Entity Type to Hierarchy in Model BP An additional customer-specific entity type can be added to the list of entity types for the hierarchy that is delivered for the entity type BP_HEADER. In the figure above, in the nr. 1, the new entity type ZTEXT serves as text node in the upper example. In nr. 2, the collective processing UI you can then insert text nodes (example above). Function in Detail: Hierarchies Figure 337: Function in Detail: Hierarchies You can now assign Business Partners to hierarchies during Single-Object Processing (the Creation or Change processes). The UI also offers a value help for the easy identification of the relevant parent node. © Copyright. All rights reserved. 375 Unit 5: MDG Multiple Object Processing and Mass Changes 376 © Copyright. All rights reserved.  Unit 5 Exercise 12 Perform SAP MDG-S - Hierarchy Maintenance Simulation: Perform SAP MDG-S - Hierarchy Maintenance For more information on Perform SAP MDG-S - Hierarchy Maintenance, please view the simulation in the lesson Exploring Hierarchy Processing online in the SAP Learning Hub. Business Scenario You are acting as a strategic buyer in the procurement department. You are supposed to create a new supplier hierarchy for reporting or other purposes. In SAP MDG you are able to work with the SAP NetWeaver Business Client (NWBC) or via the enterprise portal. Note: In this exercise, when the values include ##, replace the characters with the number that your instructor assigned you. In MDG you can work with the SAP NetWeaver Business Client (NWBC) or via the SAP Fiori launchpad. Task 1: Create a Hierarchy Change Request for Suppliers Hierarchy processing in MDG requires the preparation respective creation of a fitting Change Request. 1. Enter the supplier processing and create a Change Request for handling the supplier hierarchies. Hint: You need to apply a Change Request Type for processing multiple objects. Therefore, select Change Request Type BPHP1. Task 2: Create the Hierarchy Structure and Assign Suppliers / BPs to it Create a hierarchy structure from scratch for your suppliers, assigning the suppliers according to their headquarter location, for example, Europe for Germany, Americas for North America or Latin America, and so on. 1. For the root node you choose Create New Business Partner Hierarchy…. Give it a name containing your group number, for example, “SuppHier##”. 2. Create structure nodes for the continents, part of the continents, and some countries. © Copyright. All rights reserved. 377 Unit 5: MDG Multiple Object Processing and Mass Changes 3. Assign some BPs to one or two hierarchy nodes on the lowest level of the hierarchy structure. 4. Save your hierarchy work and assign the Change Request that you have prepared in Task 1. For managing of objects, single or multiple, MDG requires a Change Request. In the first steps of this exercise you prepared a Change Request that you have now assigned to the created/changed hierarchy structure. MDG asks via a pop-up for the specification of Change Request Type so that it can be used for hierarchy processing. Task 3: Process the Change Request When saved, the hierarchy is now bound to a Change Request. MDG determines the next agent in the Change Request workflow and puts the Change Request workflow step into the inbox of this end user. The training system is configured in a way so that every training attendee is allowed to execute the next step. In other words, in your inbox you should get an entry with “your” Change Request. 1. You can process the Change Request. Look up in your Change Request - Inbox and take the workflow item. The workflow has three steps. The first step was completed with the assignment of the hierarchy to the Change Request in task 2. You can execute the second step by choosing Finalize Processing. The third step is the approval, or rejection, of the Change Request. 2. After approving the Change Request, look it up in the database to see what the hierarchy looks like in the database tables. Note: The hierarchy structure and assignment information remains in the staging tables and is set to active. Because the underlying ERP system does not offer database tables for accepting and storing the hierarchy information, MDG cannot forward this data into ERP tables, it remains in the MDG area. The BP hierarchies are stored in the database tables that have been generated by MDG. Find them with execution of the report USMD_DATA_MODEL in the transaction for the ABAP editor: SE38. 378 © Copyright. All rights reserved.  Unit 5 Solution 12 Perform SAP MDG-S - Hierarchy Maintenance Simulation: Perform SAP MDG-S - Hierarchy Maintenance For more information on Perform SAP MDG-S - Hierarchy Maintenance, please view the simulation in the lesson Exploring Hierarchy Processing online in the SAP Learning Hub. Business Scenario You are acting as a strategic buyer in the procurement department. You are supposed to create a new supplier hierarchy for reporting or other purposes. In SAP MDG you are able to work with the SAP NetWeaver Business Client (NWBC) or via the enterprise portal. Note: In this exercise, when the values include ##, replace the characters with the number that your instructor assigned you. In MDG you can work with the SAP NetWeaver Business Client (NWBC) or via the SAP Fiori launchpad. Task 1: Create a Hierarchy Change Request for Suppliers Hierarchy processing in MDG requires the preparation respective creation of a fitting Change Request. 1. Enter the supplier processing and create a Change Request for handling the supplier hierarchies. Hint: You need to apply a Change Request Type for processing multiple objects. Therefore, select Change Request Type BPHP1. a) In the Supplier Governance tile group, choose the Manage Hierarchy app. © Copyright. All rights reserved. 379 Unit 5: MDG Multiple Object Processing and Mass Changes b) Enter a description Create Supplier Hierarchy - GR## and choose BPHP1 as the Change Request Type. c) Choose Next. d) In the Explanation area, enter -for example new regional supplier hierarchy. e) Choose Next. f) In the next step Changes, the system offers to you the specification of concrete objects to be taken into the Change Request governance, which is not necessary here. Choose Next and Submit. Close the window. The system creates the Change Request so it's ready to be filled with objects - hierarchy and suppliers. 380 © Copyright. All rights reserved.  Lesson: Exploring Hierarchy Processing Task 2: Create the Hierarchy Structure and Assign Suppliers / BPs to it Create a hierarchy structure from scratch for your suppliers, assigning the suppliers according to their headquarter location, for example, Europe for Germany, Americas for North America or Latin America, and so on. 1. For the root node you choose Create New Business Partner Hierarchy…. Give it a name containing your group number, for example, “SuppHier##”. a) In the category supplier governance, choose tile Process Hierarchy - Hierarchy Processing. On the following Selections screen, select Continue. b) On the next screen, choose Edit to start the hierarchy. c) To create a new Business Partner Hierarchy, choose Insert → New:BP Hierarchy... © Copyright. All rights reserved. 381 Unit 5: MDG Multiple Object Processing and Mass Changes d) Enter SuppHier## in the BPartner Hierarchy field and Group## in the Description (long text) field. Choose Transfer.. 2. Create structure nodes for the continents, part of the continents, and some countries. a) Create the supplier hierarchy structure with the insertion or – to be more exact – the creation of new nodes into the hierarchy. As before, open the Insert menu, but this time select New: Structure Node. Enter the following values and ensure, that you have selected Insert as Subnode: Field Name Value Structure Node Asia Description (long text) Suppliers in Asia b) Choose Transfer. c) In the same way, create the node for Europe and a sub-node for Germany. 382 © Copyright. All rights reserved.  Lesson: Exploring Hierarchy Processing Field Name Value Structure Node Europe Description (long text) Suppliers in Europe Structure Node Germany Description (long text) Suppliers in Germany d) You can move nodes within the same hierarchy level by using the up and down arrow buttons at the top of the table. e) You can lower the level of nodes in the hierarchy by using the left and right arrow buttons. f) You can add new nodes on the same level or below by creating new structure nodes as before. Then you can (optionally) move the nodes using the arrow buttons. 3. Assign some BPs to one or two hierarchy nodes on the lowest level of the hierarchy structure. a) Select one hierarchy node, for example Germany and choose Insert → Bus. Partner ID... to assign business partners to the selected hierarchy node. © Copyright. All rights reserved. 383 Unit 5: MDG Multiple Object Processing and Mass Changes b) Search for all the Suppliers with Name pattern S520*## and select the first two entries from the hit list and choose OK. c) In the next screen, choose both entries and choose Transfer to transfer the data to the hierarchy. 4. Save your hierarchy work and assign the Change Request that you have prepared in Task 1. For managing of objects, single or multiple, MDG requires a Change Request. In the first steps of this exercise you prepared a Change Request that you have now assigned to the 384 © Copyright. All rights reserved.  Lesson: Exploring Hierarchy Processing created/changed hierarchy structure. MDG asks via a pop-up for the specification of Change Request Type so that it can be used for hierarchy processing. a) Choose Save. In the pop-up select the previously created Change Request and choose Transfer. b) To verify your settings, choose Check in the header bar. c) Close the overview window. Task 3: Process the Change Request When saved, the hierarchy is now bound to a Change Request. MDG determines the next agent in the Change Request workflow and puts the Change Request workflow step into the inbox of this end user. The training system is configured in a way so that every training attendee is allowed to execute the next step. In other words, in your inbox you should get an entry with “your” Change Request. 1. You can process the Change Request. Look up in your Change Request - Inbox and take the workflow item. The workflow has three steps. The first step was completed with the assignment of the hierarchy to the Change Request in task 2. You can execute the second step by choosing Finalize Processing. The third step is the approval, or rejection, of the Change Request. a) Go to Supplier Governance tile group, and choose Change Request - Inbox application. b) Click on the number of your Change Request, to get an overview about this multiple object Change Request. © Copyright. All rights reserved. 385 Unit 5: MDG Multiple Object Processing and Mass Changes c) Choose Finalize Processing to continue with the Change Request and close the window. The next step in the workflow is sent to your inbox. d) Go to the Change Request - Inbox application and choose Refresh. The status of your change request has changed to To be Considered and Approved. e) Open your Change Request and the choose Approve. Close the window. 2. After approving the Change Request, look it up in the database to see what the hierarchy looks like in the database tables. Note: The hierarchy structure and assignment information remains in the staging tables and is set to active. Because the underlying ERP system does not offer database tables for accepting and storing the hierarchy information, MDG cannot forward this data into ERP tables, it remains in the MDG area. The BP hierarchies are stored in the database tables that have been generated by MDG. Find them with execution of the report USMD_DATA_MODEL in the transaction for the ABAP editor: SE38. a) Log on into the back-end system and start ransaction SE38. Enter report USMD_DATA_MODEL and execute the report. b) Specify the Data Model. Use the F4 input help and select BP. Then choose Copy. c) Choose Execute. 386 © Copyright. All rights reserved.  Lesson: Exploring Hierarchy Processing d) After execution scroll down and find the entry with these values: Field Name Value Entity Type BP_HEADER Subtype Hierarchy You can see how the table is named and where the BP hierarchy information is stored. See the example in the figure below: e) In column Physical Name double-click on the corresponding value, to be forwarded to the technical details of this generated table. f) In the Dictionary view, use the Contents button. g) Choose Execute to jump into the content view. h) Verify your table entries © Copyright. All rights reserved. 387 Unit 5: MDG Multiple Object Processing and Mass Changes 388 © Copyright. All rights reserved.  Lesson: Exploring Hierarchy Processing LESSON SUMMARY You should now be able to: Explore hierarchy processing © Copyright. All rights reserved. 389  Unit 5 Lesson 3 Explaining Material Mass Changes and Multiple Object Processing LESSON OBJECTIVES After completing this lesson, you will be able to: Explain material mass changes and multiple object processing Material Mass Changes and Multiple Object Processing Figure 339: Material Mass Changes and Multiple Object Processing Mass processing in MDG is used for the following tasks: Processing multiple selected objects of the same entity type in one step. During one transaction the same changes are applied to this selection. Performing multiple transactions (and selections) using the same change request. Before starting a mass process, an open change request of the right change request type (single object not checked in customizing) must exist and you need to be a valid processor. Multiple processors can work on the same change request. The mass change service enables you to replace the selected materials and their selected content with new values per field for all selected materials. 390 © Copyright. All rights reserved.  Lesson: Explaining Material Mass Changes and Multiple Object Processing Updating multiple materials is a two-step process. First, you create a change request for multiple materials using this service. Then, you use the Mass Change service to enter the details for the changes you want to make. How to create a change request is described in more detail in the generic learning units for MDG, but also in the previous services, for example, in the Create Material service. Here, we focus on the Mass Change service itself: 1. Create a change request. 2. Select the entities for mass change. 3. Replace or Initialize values for the fields with one dedicated value. 4. Review the results and execute the change. 5. Assign the mass change request. Multiple-Record Processing Figure 340: Multiple-Record Processing Multiple-Record Processing involves: Selection of relevant materials out of the search. Tabular maintenance of several materials at the same time. Find and Replace function. Animation: Multiple-Record Processing For more information on Multiple-Record Processing, please view the animation in the lesson Explaining Material Mass Changes and Multiple Object Processing, online in the SAP Learning Hub. © Copyright. All rights reserved. 391 Unit 5: MDG Multiple Object Processing and Mass Changes Material Mass Changes and Multiple Object Processing Figure 342: Material Mass Changes and Multiple Object Processing Multiple-Record processing features are: Example UI configurations and customizing delivered by business configuration sets. Combined maintenance of entity types Several operators available in context menu (For example: Select Rows with Identical Value) Highlighting changes with different colors: - Saved changes - Current changes 392 © Copyright. All rights reserved.  Unit 5 Exercise 13 Perform a Simple Material Mass Update for Dedicated Fields Simulation: Perform a Simple Material Mass Update for Dedicated Fields For more information on Perform a Simple Material Mass Update for Dedicated Fields, please view the simulation in the lesson Explaining Material Mass Changes and Multiple Object Processing online in the SAP Learning Hub. Business Scenario After completing this exercise, you will be able to perform the following tasks: Update a set of material objects with specific values. Run Mass Processes with MDG. Perform an Update of certain fields for a lot of material master data objects. You are an end user of your SAP MDG implementation. You need to perform changes for a bunch of material objects in a bulk mode. Note: In this exercise, when the values include ##, replace the characters with the number that your instructor assigned you. In MDG you can work with the SAP NetWeaver Business Client (NWBC) or via the SAP Fiori launchpad. Perform a Simple Material Mass Update for Dedicated Fields 1. Search material objects assigned to you by using search pattern T-FL4A*##. 2. Select all the materials and initiate a mass change. 3. In the navigation area, process the following changes: Reset the given Authorization Group assignments by initializing them For the X-Plant Material Status, enter E1 (Engineering in Work) For the Industry Standard Description , enter Group ## For the Field Lab/Office, enter the value G## from the value help list 4. Process your changes and specify the change request type for this task as Process Multiple Materials. © Copyright. All rights reserved. 393 Unit 5: MDG Multiple Object Processing and Mass Changes 5. Go back to the Material Governance tile group and select the Change Requests – Inbox application. Select your task and process the change request decision by completing the following tasks: Run a validation and verify the validation result. Activate the change request. Verify the new values for one of the materials. 394 © Copyright. All rights reserved.  Unit 5 Solution 13 Perform a Simple Material Mass Update for Dedicated Fields Simulation: Perform a Simple Material Mass Update for Dedicated Fields For more information on Perform a Simple Material Mass Update for Dedicated Fields, please view the simulation in the lesson Explaining Material Mass Changes and Multiple Object Processing online in the SAP Learning Hub. Business Scenario After completing this exercise, you will be able to perform the following tasks: Update a set of material objects with specific values. Run Mass Processes with MDG. Perform an Update of certain fields for a lot of material master data objects. You are an end user of your SAP MDG implementation. You need to perform changes for a bunch of material objects in a bulk mode. Note: In this exercise, when the values include ##, replace the characters with the number that your instructor assigned you. In MDG you can work with the SAP NetWeaver Business Client (NWBC) or via the SAP Fiori launchpad. Perform a Simple Material Mass Update for Dedicated Fields 1. Search material objects assigned to you by using search pattern T-FL4A*##. a) Open the SAP Fiori launchpad app and navigate to Material Governance → Manage Material. b) As search term for Material enter T-FL4A*## and choose Search. © Copyright. All rights reserved. 395 Unit 5: MDG Multiple Object Processing and Mass Changes 2. Select all the materials and initiate a mass change. a) In the result list, select all rows for the materials and choose Mass Change. b) Verify that you have picked only your materials, and choose Next. You also have the option to delete items and reselect data objects. 3. In the navigation area, process the following changes: Reset the given Authorization Group assignments by initializing them For the X-Plant Material Status, enter E1 (Engineering in Work) For the Industry Standard Description , enter Group ## For the Field Lab/Office, enter the value G## from the value help list a) Select the Initialize checkbox for the Authorization Group. 396 © Copyright. All rights reserved.  Lesson: Explaining Material Mass Changes and Multiple Object Processing b) Scroll down to following fields and enter the data provided in the table. Field Value X-plant matl status E1 Industry Std Desc Group ## c) In the Lab/Office field, enter G## and choose Next. © Copyright. All rights reserved. 397 Unit 5: MDG Multiple Object Processing and Mass Changes 4. Process your changes and specify the change request type for this task as Process Multiple Materials. a) Verify your changes and choose Execute Changes. Depending on the situation you may be requested to select or create a new change request. Always create a new one for your own exercise – otherwise you would add your changes into another existing change request. b) As Type, select Process Multiple Materials. As Description enter Mass Processing Material Group ## and choose OK to send the Mass Process Change Request for approval. If a warning pop-up appears, close the pop-up. c) To close the application, choose Close in the lower right corner of the screen. 398 © Copyright. All rights reserved.  Lesson: Explaining Material Mass Changes and Multiple Object Processing 5. Go back to the Material Governance tile group and select the Change Requests – Inbox application. Select your task and process the change request decision by completing the following tasks: Run a validation and verify the validation result. Activate the change request. Verify the new values for one of the materials. a) In Overview tab, view your changes. b) Navigate to the Changes view and check that all material objects are marked as Changed. c) Navigate to the Notes view and add a note to the Change Request, for example additional note group 00. To start a validation for the Change Request, choose Run Validation. © Copyright. All rights reserved. 399 Unit 5: MDG Multiple Object Processing and Mass Changes d) Check the validation log result. After that, close the window and navigate back to the Activate Change Request window. e) Choose Activate. f) Close the window. g) Go to the My Change Requests application in the same tile group to verify that the Change Request was successfully activated. 400 © Copyright. All rights reserved.  Lesson: Explaining Material Mass Changes and Multiple Object Processing h) Open the back end system and start transaction MM03 to verify the changes has been performed in the system also. Enter T-FL4A*## in the Material field and choose, for examle T-FL4A##. i) Choose Select View(s) and select Basic Data 1 and Basic Data 2. Then press Enter. j) Verify, that your changes were transferred to the back end system. © Copyright. All rights reserved. 401 Unit 5: MDG Multiple Object Processing and Mass Changes LESSON SUMMARY You should now be able to: Explain material mass changes and multiple object processing 402 © Copyright. All rights reserved.  Unit 5 Learning Assessment 1. Which statement is wrong? Choose the correct answers. X A Multi-record processing is typically an ad-hoc task for one business user. X B Multi-record processing never includes collaboration of multiple processors. X C Multi-record processing is a well-defined governance process with multiple workflow steps. 2. In which multiple object processes is “Highlight Changes” supported? Choose the correct answer. X A In multiple-record processing X B In the mass change process © Copyright. All rights reserved. 403 Unit 5: Learning Assessment 404 © Copyright. All rights reserved.