HowTo MDGMaMaintenanceforMultiple Materials

7/24/2019 HowTo MDGMaMaintenanceforMultiple Materials

1/37

How To... Master Data Governance for Material:Maintenance for multiple Materials in oneChange Request

Applicable Releases:all

Version 1.2

December 2014


2/37

Document History

Document Version Description

1.00 First official release of this guide

1.10 Chapters 3.4 and 4.6

1.20 Update chapter 4.5: Update in Staging possible


3/37

3

TABLE OF CONTENTS

1. BUSINESS SCENARIO ......................................................................................................................................................... 4

2. PREREQUISITES ................................................................................................................................................................. 5

3. CREATION OF MULTIPLE MATERIAL................................................................................................................................... 6

3.1. CHANGE REQUEST WITH BUSINESS TYPE MATA(STAGING) ............................................................................................................... 6

3.2. FILE UPLOAD (STAGING) ............................................................................................................................................................. 9

3.3. DATA IMPORT FRAMEWORK (STAGING/ACTIVE AREA) .................................................................................................................... 12

3.4. ENTERPRISE SERVICE MATERIALERPBULKREPLICATEREQUEST (STAGING/ACTIVE AREA) ........................................................................ 14

3.5. BACKEND FUNCTIONS DIRECT INPUT/ALE(ACTIVE AREA) ............................................................................................................... 19

4. CHANGING MULTIPLE MATERIALS ................................................................................................................................... 20

4.1. CHANGE REQUEST WITH BUSINESS TYPE MATA(STAGING) ............................................................................................................. 20

4.2. FILE DOWNLOAD AND UPLOAD (STAGING) ................................................................................................................................... 21

4.3. MDG7.0MULTIPLE-RECORD PROCESSING (STAGING) ................................................................................................................... 25

4.4. MASS CHANGE (STAGING) ......................................................................................................................................................... 27

4.5. DATA IMPORT FRAMEWORK (STAGING/ACTIVE AREA) .................................................................................................................... 30

4.6. ENTERPRISE SERVICE MATERIALERPBULKREPLICATEREQUEST (STAGING/ACTIVE AREA) ........................................................................ 31

4.7. BACKEND MASS MAINTENANCE MM17(ACTIVE AREA) ................................................................................................................. 334.8. BACKEND FUNCTIONS DIRECT INPUT/ALE(ACTIVE AREA) ............................................................................................................... 36


4/37

4

1. BUSINESS SCENARIO

SAP Master Data Governance for Material (MDG-M) provides business processes to support the governance ofmaterial master data on a central hub and the subsequent distribution of material master data to connected operationaland business intelligence systems. This includes of course capabilities to search, create and change individualmaterials as well as options to work on many records at a time. The related processes are workflow-driven and caninclude several approval and revision phases, including collaboration between all users participating in master datamaintenance.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 usewhat. Moreover, this becomes important with a view to some restrictions originating from the intended purpose of thefeature in contemplation.

The following guide tries to provide some insights on the applicability of the individual features also with respect ofboundary conditions and possible limitations.


5/37

5

2. PREREQUISITES

Check if the following SAP Notes:

1517867 Functional restrictions in MDG-M in EhP51571467 Functional restrictions in MDG-M in EhP61701437 Functional restrictions in MDG-M in MDG6.11806108 Functional restrictions in MDG-M in MDG7


6/37

6

3. CREATION OF MULTIPLE MATERIAL

This chapter gives some insights about how to create multiple materials in the MDG Hub. You can create newmaterials using a Change Request in the staging area or by writing directly into the active area of the material masterbackend tables.

3.1. 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.


7/37

7

3.1.1. Create Change Request and Ass ign the new Materials

Create one Change Request and assign multiple materials to it.


8/37

8

3.1.2. 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 thesingle processing. The user can work material by material.


9/37

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 materialmaster data object usually spans several entities, which have to be uploaded separately. Dependencies are notcovered by the system. Therefore the user has to ensure that all the necessary entities are available as CSV file anduploaded 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. Itcould be used to create a small number of entities in staging. Flex Entities can also be created in this way.

3.2.1. Create Change Request

Create one change request and do not assign materials to it.


10/37

10

3.2.2. Uplo ad 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.


11/37

11


12/37

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 wantto do an initial load while operating MDG (importing data from new client systems into running MDG system).

Solution:You can use the Import Master Dataservice 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 yourapplication 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 Materialbusiness functions only support the import (DIF) andmonitoring of material master data and key mapping information. The export of material data can be done withother technologies for extraction (for example pure ALE technology using transaction BD10).

You can use the Import Master Dataservice to import files containing material and classification data to the MasterData Governancesystem. You can also import key and value mapping information. The data from these files cancreate new data using the options available in the Import Master Dataservice.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). Aprerequisite is that you have prepared your file for import in IDoc-XML format.

See also How To Guide for DIF:https://scn.sap.com/docs/DOC-47519
https://scn.sap.com/docs/DOC-47519https://scn.sap.com/docs/DOC-47519https://scn.sap.com/docs/DOC-47519https://scn.sap.com/docs/DOC-47519


13/37

13


14/37

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 BPMBusiness Process Management) or any client system can create SOAmessages. You may need to create multiple materials on the MDG Staging/Active Area from your cross system orclient system.

Note: Services can also be used to make changes to Materials in the active/staging area. This is discussed in section4.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 theSDN Link.
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/e03cb2f0-3e03-3010-cca5-d4cd11592c28http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/e03cb2f0-3e03-3010-cca5-d4cd11592c28


15/37

15


16/37

16


17/37

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.


18/37

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.


19/37

19

3.5. Backend Functions Direct Input/ALE (Active Area)

Use case:You want todo an initial load or transfer material data from other systems and want to create the complete MaterialMaster 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 informationsheet on transferring material master data (Industry):http://help.sap.com/erp2005_ehp_07/helpdata/en/f6/ca0766a7a911d1950500a0c930e0da/content.htm?frameset=/en/f6/ca0766a7a911d1950500a0c930e0da/frameset.htm

Available BAPIS: 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:

BCALE Implementation and Administration

BCALE Introduction

Creating Material Master Data

Distributing Material Master Data

ALE Programming Guide

Master Data Distribution
http://help.sap.com/erp2005_ehp_07/helpdata/en/f6/ca0766a7a911d1950500a0c930e0da/content.htm?frameset=/en/f6/ca0766a7a911d1950500a0c930e0da/frameset.htmhttp://help.sap.com/erp2005_ehp_07/helpdata/en/f6/ca0766a7a911d1950500a0c930e0da/content.htm?frameset=/en/f6/ca0766a7a911d1950500a0c930e0da/frameset.htmhttp://help.sap.com/erp2005_ehp_07/helpdata/en/f6/ca0766a7a911d1950500a0c930e0da/content.htm?frameset=/en/f6/ca0766a7a911d1950500a0c930e0da/frameset.htmhttp://help.sap.com/saphelp_erp60_sp/helpdata/en/0b/2a6095507d11d18ee90000e8366fc2/frameset.htmhttp://help.sap.com/saphelp_erp60_sp/helpdata/en/0b/2a6095507d11d18ee90000e8366fc2/frameset.htmhttp://help.sap.com/saphelp_erp60_sp/helpdata/en/0b/2a6095507d11d18ee90000e8366fc2/frameset.htmhttp://help.sap.com/saphelp_erp60_sp/helpdata/en/0b/2a6095507d11d18ee90000e8366fc2/frameset.htmhttp://help.sap.com/saphelp_erp60_sp/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htmhttp://help.sap.com/saphelp_erp60_sp/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htmhttp://help.sap.com/saphelp_erp60_sp/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htmhttp://help.sap.com/saphelp_erp60_sp/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htmhttp://help.sap.com/saphelp_erp60_sp/helpdata/en/78/217e0f51ce11d189570000e829fbbd/frameset.htmhttp://help.sap.com/saphelp_erp60_sp/helpdata/en/78/217e0f51ce11d189570000e829fbbd/frameset.htmhttp://help.sap.com/saphelp_erp60_sp/helpdata/en/78/217e1c51ce11d189570000e829fbbd/frameset.htmhttp://help.sap.com/saphelp_erp60_sp/helpdata/en/78/217e1c51ce11d189570000e829fbbd/frameset.htmhttp://dwdf213/MDG_PROJECT/10%20Solution%20Management/70%20Roll%20Out/SDN/SDN_MDG%20for%20Material/01.%20Work/ALE%20Programming%20Guidehttp://help.sap.com/saphelp_erp60_sp/helpdata/en/78/2178b351ce11d189570000e829fbbd/frameset.htmhttp://help.sap.com/saphelp_erp60_sp/helpdata/en/78/2178b351ce11d189570000e829fbbd/frameset.htmhttp://help.sap.com/saphelp_erp60_sp/helpdata/en/78/2178b351ce11d189570000e829fbbd/frameset.htmhttp://dwdf213/MDG_PROJECT/10%20Solution%20Management/70%20Roll%20Out/SDN/SDN_MDG%20for%20Material/01.%20Work/ALE%20Programming%20Guidehttp://help.sap.com/saphelp_erp60_sp/helpdata/en/78/217e1c51ce11d189570000e829fbbd/frameset.htmhttp://help.sap.com/saphelp_erp60_sp/helpdata/en/78/217e0f51ce11d189570000e829fbbd/frameset.htmhttp://help.sap.com/saphelp_erp60_sp/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htmhttp://help.sap.com/saphelp_erp60_sp/helpdata/en/0b/2a6095507d11d18ee90000e8366fc2/frameset.htmhttp://help.sap.com/erp2005_ehp_07/helpdata/en/f6/ca0766a7a911d1950500a0c930e0da/content.htm?frameset=/en/f6/ca0766a7a911d1950500a0c930e0da/frameset.htmhttp://help.sap.com/erp2005_ehp_07/helpdata/en/f6/ca0766a7a911d1950500a0c930e0da/content.htm?frameset=/en/f6/ca0766a7a911d1950500a0c930e0da/frameset.htm


20/37

20

4. CHANGING MULTIPLE MATERIALS

This chapter gives some insights on changing multiple existing materials in the MDG Hub. The change is possible witha Change Request in Staging or directly into the active area of the material master backend tables.

4.1. 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 chapter3.1 Change Request with Business Type MATA (Staging)


21/37

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 bechanged 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 changeddata for one entity with an Excel file. This could be sufficient for changing specific values which are on one entity butnot for maintaining the complete material master. In this scenario several entities must be updated which requiresseveral 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.




22/37

22

4.2.2. Execute File Download

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


23/37

23

Store the file as CSV if you want to maintain it with Microsoft Excel.

4.2.3. Maint ain Data in file

4.2.4. Execu te File Uplo ad

Upload the changed data using the Change Request, which was created before.


24/37

24


25/37

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 useMultiple-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 Changeservice. You cannot use this service to create new materials.


26/37

26

The Multiple-Record Processingfunction enables you to use the following features:

Streamlined ProcessingMultiple records can be updated without creating a separate mass change request before beginningprocessing. The service can be accessed directly from the material search function.

Entity Pre-SelectionA Multiple-Record Processingchange 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 areavailable with pre-configured scenarios for Material.

UI OptionsThe Multiple-Record ProcessingUI enables you to use a Find and Replacefeature, to copy data to selectedrows, and to highlight rows with identical values.

Color CodingThe Multiple-Record ProcessingUI offers color coding to facilitate easy identification of material fields andvalues changed in the current change request.

For details see How To Guide on SDN:https://scn.sap.com/docs/DOC-48895
https://scn.sap.com/docs/DOC-48895https://scn.sap.com/docs/DOC-48895https://scn.sap.com/docs/DOC-48895


27/37

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 datato 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 onentity 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.



4.4.2. Mass Chan ge

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.


28/37

28


29/37

29


30/37

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 Governancesystem. The data

from these files should update existing master data records using the Import Master Dataservice.

Solution:You can use the Import Master Dataservice to import files.

It is possible to update into the Active Area with DIF. With MDG 7.0 and SAP notes 2045848 and 2035892 it is alsopossible to update into Staging Area.


31/37

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 (Forexample, a NW MDM or GDS system) on MDG Staging Area by calling the MaterialERPBulkReplicateRequest_Inasynchronous 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 eachview/node under material sub node. This flag indicates how the data of that node is to be processed in accordance withits action code value.

Example:Consider the Description node.

Go to the node MaterialERPBulkReplicateRequest MaterialERPReplicateRequestMessage

MaterialERPReplicateRequestMessage Material. Click on the button next to the Description node to add thedetails of Description.

If the CTI flag (corresponding to description at Material node level) is False:

Material descriptions not passed remain unchanged.Check the is Nullcheckbox for the field descriptionListCompleteTransmissionIndicator in the materialnode.

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 Nullcheckbox for the field descriptionListCompleteTransmissionIndicator in thematerial node and check the True indicator.

The behaviour of the different action codes are as given below:


32/37

32

04-Save:

Create if new data is passed.

If the material already exists, updates the material with the new data passed and deletes theexisting data.

05-Remove:

Delete if the data exists

If no data exists, then no action

.


33/37

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 materialmasters.

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 mightoverwrite changes done by the MM17 (due to the snapshot comparison).


34/37

34


35/37

35


36/37

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 theactive 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 informationsheet on transferring material master data (Industry):http://help.sap.com/erp2005_ehp_07/helpdata/en/f6/ca0766a7a911d1950500a0c930e0da/content.htm?frameset=/en/f6/ca0766a7a911d1950500a0c930e0da/frameset.htm

Available BAPIS: 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:

BCALE Implementation and Administration

BCALE Introduction

Creating Material Master Data

Distributing Material Master Data

ALE Programming Guide

Master Data Distribution
http://help.sap.com/erp2005_ehp_07/helpdata/en/f6/ca0766a7a911d1950500a0c930e0da/content.htm?frameset=/en/f6/ca0766a7a911d1950500a0c930e0da/frameset.htmhttp://help.sap.com/erp2005_ehp_07/helpdata/en/f6/ca0766a7a911d1950500a0c930e0da/content.htm?frameset=/en/f6/ca0766a7a911d1950500a0c930e0da/frameset.htmhttp://help.sap.com/erp2005_ehp_07/helpdata/en/f6/ca0766a7a911d1950500a0c930e0da/content.htm?frameset=/en/f6/ca0766a7a911d1950500a0c930e0da/frameset.htmhttp://help.sap.com/saphelp_erp60_sp/helpdata/en/0b/2a6095507d11d18ee90000e8366fc2/frameset.htmhttp://help.sap.com/saphelp_erp60_sp/helpdata/en/0b/2a6095507d11d18ee90000e8366fc2/frameset.htmhttp://help.sap.com/saphelp_erp60_sp/helpdata/en/0b/2a6095507d11d18ee90000e8366fc2/frameset.htmhttp://help.sap.com/saphelp_erp60_sp/helpdata/en/0b/2a6095507d11d18ee90000e8366fc2/frameset.htmhttp://help.sap.com/saphelp_erp60_sp/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htmhttp://help.sap.com/saphelp_erp60_sp/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htmhttp://help.sap.com/saphelp_erp60_sp/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htmhttp://help.sap.com/saphelp_erp60_sp/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htmhttp://help.sap.com/saphelp_erp60_sp/helpdata/en/78/217e0f51ce11d189570000e829fbbd/frameset.htmhttp://help.sap.com/saphelp_erp60_sp/helpdata/en/78/217e0f51ce11d189570000e829fbbd/frameset.htmhttp://help.sap.com/saphelp_erp60_sp/helpdata/en/78/217e1c51ce11d189570000e829fbbd/frameset.htmhttp://help.sap.com/saphelp_erp60_sp/helpdata/en/78/217e1c51ce11d189570000e829fbbd/frameset.htmhttp://dwdf213/MDG_PROJECT/10%20Solution%20Management/70%20Roll%20Out/SDN/SDN_MDG%20for%20Material/01.%20Work/ALE%20Programming%20Guidehttp://help.sap.com/saphelp_erp60_sp/helpdata/en/78/2178b351ce11d189570000e829fbbd/frameset.htmhttp://help.sap.com/saphelp_erp60_sp/helpdata/en/78/2178b351ce11d189570000e829fbbd/frameset.htmhttp://dwdf213/MDG_PROJECT/10%20Solution%20Management/70%20Roll%20Out/SDN/SDN_MDG%20for%20Material/01.%20Work/ALE%20Programming%20Guidehttp://help.sap.com/saphelp_erp60_sp/helpdata/en/78/217e1c51ce11d189570000e829fbbd/frameset.htmhttp://help.sap.com/saphelp_erp60_sp/helpdata/en/78/217e0f51ce11d189570000e829fbbd/frameset.htmhttp://help.sap.com/saphelp_erp60_sp/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htmhttp://help.sap.com/saphelp_erp60_sp/helpdata/en/0b/2a6095507d11d18ee90000e8366fc2/frameset.htmhttp://help.sap.com/erp2005_ehp_07/helpdata/en/f6/ca0766a7a911d1950500a0c930e0da/content.htm?frameset=/en/f6/ca0766a7a911d1950500a0c930e0da/frameset.htmhttp://help.sap.com/erp2005_ehp_07/helpdata/en/f6/ca0766a7a911d1950500a0c930e0da/content.htm?frameset=/en/f6/ca0766a7a911d1950500a0c930e0da/frameset.htm


37/37

2014 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 Germanyand 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, m@gic 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

www.sap.com

HowTo MDGMaMaintenanceforMultiple Materials

Documents

Transcript of HowTo MDGMaMaintenanceforMultiple Materials