How To... Master Data Governance for Material: Maintenance for multiple Materials in one Change Request. Applicable Releases: all

Transcription

1 How To... Master Data Governance for Material: Maintenance for multiple Materials in one Change Request Applicable Releases: all Version 1.2 December 2014

2 Document History Document Version Description 1.00 First official release of this guide 1.10 Chapters 3.4 and Update chapter 4.5: Update in Staging possible

3 TABLE OF CONTENTS 1. BUSINESS SCENARIO PREREQUISITES CREATION OF MULTIPLE MATERIAL CHANGE REQUEST WITH BUSINESS TYPE MATA (STAGING) FILE UPLOAD (STAGING) DATA IMPORT FRAMEWORK (STAGING/ACTIVE AREA) ENTERPRISE SERVICE MATERIALERPBULKREPLICATEREQUEST (STAGING/ACTIVE AREA) BACKEND FUNCTIONS DIRECT INPUT/ALE (ACTIVE AREA) CHANGING MULTIPLE MATERIALS CHANGE REQUEST WITH BUSINESS TYPE MATA (STAGING) FILE DOWNLOAD AND UPLOAD (STAGING) MDG7.0 MULTIPLE-RECORD PROCESSING (STAGING) MASS CHANGE (STAGING) DATA IMPORT FRAMEWORK (STAGING/ACTIVE AREA) ENTERPRISE SERVICE MATERIALERPBULKREPLICATEREQUEST (STAGING/ACTIVE AREA) BACKEND MASS MAINTENANCE MM17 (ACTIVE AREA) BACKEND FUNCTIONS DIRECT INPUT/ALE (ACTIVE AREA)

4 1. BUSINESS SCENARIO SAP Master Data Governance for Material (MDG-M) provides business processes to support the governance of material master data on a central hub and the subsequent distribution of material master data to connected operational and business intelligence systems. This includes of course capabilities to search, create and change individual materials as well as options to work on many records at a time. The related processes are workflow-driven and can include several approval and revision phases, including collaboration between all users participating in master data maintenance. Now, with the delivery of MDG 7.0 MDG-M supports in addition the maintenance of multiple material master data records at a time within the framework of Multi-Record Processing. Taking the offered variety of functions at a glance it does not really surprise that frequently question arises when to use what. Moreover, this becomes important with a view to some restrictions originating from the intended purpose of the feature in contemplation. The following guide tries to provide some insights on the applicability of the individual features also with respect of boundary conditions and possible limitations. 4

5 2. PREREQUISITES Check if the following SAP Notes: Functional restrictions in MDG-M in EhP Functional restrictions in MDG-M in EhP Functional restrictions in MDG-M in MDG Functional restrictions in MDG-M in MDG7 5

6 3. CREATION OF MULTIPLE MATERIAL This chapter gives some insights about how to create multiple materials in the MDG Hub. You can create new materials using a Change Request in the staging area or by writing directly into the active area of the material master backend tables Change Request with Business Type MATA (Staging) Use case: You want to create more than one material master using one change request. Solution: You can use a change request type with the business activity MATA. 6

7 Create Change Request and Assign the new Materials Create one Change Request and assign multiple materials to it. 7

8 Enrich the Materials in the Change Request The next processor can find the submitted change request in the worklist. The processor can enrich the data with the single processing. The user can work material by material. 8

9 3.2. File Upload (Staging) Use case: You want to create data for one entity (for example, the entity Material). Solution: You can use the File Down- and Upload function. Flex Entities can also be created in this way. CSV*-based transfer of data (entities) could be used for load scenarios into staging area. Be aware that a material master data object usually spans several entities, which have to be uploaded separately. Dependencies are not covered by the system. Therefore the user has to ensure that all the necessary entities are available as CSV file and uploaded into the same change request. You can NOT upload a complete Material Master (all views at once). Each single view is mapped more or less as a single MDG entity type. This needs to be selected upfront and can be uploaded one by one for different entity types. It could be used to create a small number of entities in staging. Flex Entities can also be created in this way Create Change Request Create one change request and do not assign materials to it. 9

10 Upload the CSV file Upload your CSV file with the File Upload function. You can use a variant which you created before. Load your CSV file from your PC. 10

11 11

12 3.3. Data Import Framework (Staging/Active Area) Use Cases: You want to do an initial load in the MDG implementation phase (importing data into a new MDG system) or you want to do an initial load while operating MDG (importing data from new client systems into running MDG system). Solution: You can use the Import Master Data service to import files. Data transfer represents a collection of functions and features you can use to move master data and mapping information between systems and clients. Examples of these systems include existing ERP systems and your Master Data Governance hub system. To transfer master data and mapping information, perform the following steps: 1. Export the master data and mapping information from the source system to an XML file. This file rests on your application server. 2. Copy the XML file from the application server of the source system to the application server of your target system. 3. Import the master data and mapping information to the target system using the Data Import Framework. Note: The Master Data Governance for Material business functions only support the import (DIF) and monitoring of material master data and key mapping information. The export of material data can be done with other technologies for extraction (for example pure ALE technology using transaction BD10). You can use the Import Master Data service to import files containing material and classification data to the Master Data Governance system. You can also import key and value mapping information. The data from these files can create new data using the options available in the Import Master Data service. You can import the data in Active area (do not flag the field Governance) and in Staging area (flag field Governance and define a Change Request Type). A prerequisite is that you have prepared your file for import in IDoc-XML format. See also How To Guide for DIF: 12

13 13

14 3.4. Enterprise service MaterialERPBulkReplicateRequest (Staging/Active Area) Overview: An A2A inbound service interface to group the operations to request the replication of materials Supports single and bulk replication of materials Possibility to create/replicate directly to MDG Active or Staging Area Use case: Your source system (for example BPM Business Process Management) or any client system can create SOA messages. You may need to create multiple materials on the MDG Staging/Active Area from your cross system or client system. Note: Services can also be used to make changes to Materials in the active/staging area. This is discussed in section 4.6. Solution: Settings: 1. Ensure all the Service configuration and customizing settings are maintained (Logical Port, End-point settings) in the SOA Manager. 2. Ensure the business function ERP_Material_SOA is switched on. 3. The appropriate Key Mapping and Value Mapping customizing settings have been made if applicable. Steps: 1. The inbound service supports the following views of ERP Material Master (for most of the standard ECC fields): Basic, Classification, Purchasing, Sales, MRP, and Accounting. 2. Download the WSDL corresponding to this inbound service from SOA Manager as an XML file. 3. Prepare the payload for the service by maintaining data under respective nodes using any XML editor. 4. The screen shots provided below indicate how the views of backend are mapped to corresponding Nodes of the Service; for more details regarding mapping of Service fields and ECC backend fields, refer to the SDN Link. 14

15 15

16 16

17 5. In order to create material in multiple plants, sales areas, or valuation types you must maintain multiple entries in the corresponding nodes (by clicking on + button next to the node). In order to create/change multiple materials, maintain multiple entries in the Material node and org data under the respective nodes. 6. Use WS Navigator to import the XML file and test it. Alternatively, you can create a proxy instance and execute the Service by passing the data from source system 7. Check the log using transaction SXMB_MONI and go to the detailed log to see the details of the material/change request created. 17

18 If the material is created in Active Area -> try to display material using MM03 If the material is created in Staging -> try to display the corresponding Change Request using MDG UI. 18

19 3.5. Backend Functions Direct Input/ALE (Active Area) Use case: You want to do an initial load or transfer material data from other systems and want to create the complete Material Master in the active area. Solution: Use a custom program for Direct Input or BAPI or use ALE. You can transfer materials: Using direct input The preferred way is to use direct input method or a user-created program with a BAPI. See this information sheet on transferring material master data (Industry): =/en/f6/ca0766a7a911d a0c930e0da/frameset.htm Available BAPI S: BAPI_MATERIAL_SAVEDATA Create and Change Material Master Data BAPI_MATERIAL_SAVEREPLICA BAPI for Mass Maintenance of Material Data Using Application Link Enabling (ALE) You can find a detailed description of ALE, including supported functions and the procedure, under the following components: BC ALE Implementation and Administration BC ALE Introduction Creating Material Master Data Distributing Material Master Data ALE Programming Guide Master Data Distribution 19

20 4. CHANGING MULTIPLE MATERIALS This chapter gives some insights on changing multiple existing materials in the MDG Hub. The change is possible with a Change Request in Staging or directly into the active area of the material master backend tables Change Request with Business Type MATA (Staging) Use case: You want to change more than one material master in one change request. You can use a change request type with business activity MATA to do this. Select existing materials in the change request. See chapter 3.1 Change Request with Business Type MATA (Staging) 20

21 4.2. File Download and Upload (Staging) Use case: You want to change data for one entity (for example, entity Material). Solution: You can use the File Download and Upload function. Flex Entities can also be changed in this way. Data to be changed must reside in only one entity and selected materials are not in other change requests. The File Download and Upload functionality provides the possibility to download existing data and upload the changed data for one entity with an Excel file. This could be sufficient for changing specific values which are on one entity but not for maintaining the complete material master. In this scenario several entities must be updated which requires several Excel files. This can be very inconvenient for the end user. If you want to change data in one entity you can use the File Download and Upload function. Flex Entities can also be changed in this way Create Change Request Create one change request and do not assign materials to it. 21

22 Execute File Download Download data for one entity with the Download function. You can use a variant which you created before. 22

23 Store the file as CSV if you want to maintain it with Microsoft Excel Maintain Data in file Execute File Upload Upload the changed data using the Change Request, which was created before. 23

24 24

25 4.3. MDG7.0 Multiple-Record Processing (Staging) Use case: You want to change various data with governance for some materials. Solution: You can use Multiple-Record Processing. This service enables you to edit (and mark for deletion) a number of master data records at the same time. The service is recommended for small numbers of records and should not be considered a replacement for the Mass Change service. You cannot use this service to create new materials. 25

26 The Multiple-Record Processing function enables you to use the following features: Streamlined Processing Multiple records can be updated without creating a separate mass change request before beginning processing. The service can be accessed directly from the material search function. Entity Pre-Selection A Multiple-Record Processing change request automatically includes entities from the related data model, thereby speeding up the creating process. Depending on the MDG application you are using, BC sets are available with pre-configured scenarios for Material. UI Options The Multiple-Record Processing UI enables you to use a Find and Replace feature, to copy data to selected rows, and to highlight rows with identical values. Color Coding The Multiple-Record Processing UI offers color coding to facilitate easy identification of material fields and values changed in the current change request. For details see How To Guide on SDN: 26

27 4.4. Mass Change (Staging) Use case: You want to change data from one value to another for many material master records in one change request. The data to be changed is on entity type 1 Material. Solution: You can use a change request type with business activity MATA and Mass Change in MDG. The data must be on entity type 1 Material and selected materials must not be in other in-process change requests. The Mass Change function enables you to change attributes of the entity type 1 Material Create Change Request Create one change request and do not assign materials to it Mass Change Start the mass change and select your relevant materials using Define and Refine Selection. Then replace one or more fields with one dedicated value. You can review the results and then execute the change. 27

28 28

29 29

30 4.5. Data Import Framework (Staging/Active Area) Use case: You want to import files containing material and classification data to the Master Data Governance system. The data from these files should update existing master data records using the Import Master Data service. Solution: You can use the Import Master Data service to import files. It is possible to update into the Active Area with DIF. With MDG 7.0 and SAP notes and it is also possible to update into Staging Area. 30

31 4.6. Enterprise service MaterialERPBulkReplicateRequest (Staging/Active Area) Use case: Change an existing material or material(s) (with various material view relevant attributes) from an external system (For example, a NW MDM or GDS system) on MDG Staging Area by calling the MaterialERPBulkReplicateRequest_In asynchronous inbound web service. Solution: The sequence of steps for mass change using the Service remains the same as creating materials (as explained in Section 3.4), except for some points regarding preparation of the XML file (payload). Under the material node, there is a flag called Complete Transmission Indicator (CTI flag) corresponding to each view/node under material sub node. This flag indicates how the data of that node is to be processed in accordance with its action code value. Example: Consider the Description node. Go to the node MaterialERPBulkReplicateRequest MaterialERPReplicateRequestMessage MaterialERPReplicateRequestMessage Material. Click on the button details of Description. next to the Description node to add the If the CTI flag (corresponding to description at Material node level) is False: Material descriptions not passed remain unchanged. Check the is Null checkbox for the field descriptionlistcompletetransmissionindicator in the material node. The behaviour of different action codes are given below: 04-Save: Create if new data is passed. Update the material with the new data entered if the material already exists. 05-Remove: Delete if the data already exists. If no data exists, then no action. If the CTI flag is True: All material descriptions are passed and based on action code description are created/updated/deleted. Uncheck the is Null checkbox for the field descriptionlistcompletetransmissionindicator in the material node and check the True indicator. The behaviour of the different action codes are as given below: 31

32 . 04-Save: Create if new data is passed. If the material already exists, updates the material with the new data passed and deletes the existing data. 05-Remove: Delete if the data exists If no data exists, then no action 32

33 4.7. Backend Mass Maintenance MM17 (Active Area) Use case: You want to change data without governance. You want to change data from one value to another for many material masters. Solution: You can use backend transaction MM17. Note: Materials changed by this transaction should not be locked in change requests, as activation of a change request might overwrite changes done by the MM17 (due to the snapshot comparison). 33

34 34

35 35

36 4.8. Backend Functions Direct Input/ALE (Active Area) Use case: You want to transfer material changes from other systems and want to change the complete Material Master in the active area. Solution: Use a custom program for Direct Input or BAPI or use ALE. You can transfer materials: Using direct input The preferred way is to use direct input method or a user-created program with a BAPI. See this information sheet on transferring material master data (Industry): =/en/f6/ca0766a7a911d a0c930e0da/frameset.htm Available BAPI S: BAPI_MATERIAL_SAVEDATA Create and Change Material Master Data BAPI_MATERIAL_SAVEREPLICA BAPI for Mass Maintenance of Material Data Using Application Link Enabling (ALE) You can find a detailed description of ALE, including supported functions and the procedure, under the following components: BC ALE Implementation and Administration BC ALE Introduction Creating Material Master Data Distributing Material Master Data ALE Programming Guide Master Data Distribution 36

37 SAP SE. All rights reserved. SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer, StreamWork, SAP HANA, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other countries. Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. Business Objects is an SAP company. Sybase and Adaptive Server, ianywhere, Sybase 365, SQL Anywhere, and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase Inc. Sybase is an SAP company. Crossgate, EDDY, B2B 360, and B2B 360 Services are registered trademarks of Crossgate AG in Germany and other countries. Crossgate is an SAP company. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary. These materials are subject to change without notice. These materials are provided by SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.