SAP NETWEAVER MDM WALKTHROUGH · 2019-11-12 · Step 8.0: Start Extraction Select “Start Extraction” option. Choose exactly the settings you see on the screen. Choose your own

DEMO SCRIPT

SAP NETWEAVER MDMWALKTHROUGHCONFIGURE A LANDSCAPE AND RUN COREPROCESSES

© COPYRIGHT 2009 SAP AG. ALL RIGHTS RESERVED.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the expresspermission of SAP AG. The information contained herein may be changed without prior notice. Some softwareproducts marketed by SAP AG and its distributors contain proprietary software components of other software vendors.Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10,System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400,S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5,POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect,RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner, WebSphere, Netfinity, Tivoli and Informixare trademarks or registered trademarks of IBM Corporation. Linux is the registered trademark of Linus Torvalds in theU.S. and other countries.Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of AdobeSystems Incorporated in the United States and/or other countries.Oracle is a registered trademark of Oracle Corporation.UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registeredtrademarks of Citrix Systems, Inc.HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium,Massachusetts Institute of Technology.Java is a registered trademark of Sun Microsystems, Inc.JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented andimplemented by Netscape.SAP, R/3, xApps, xApp, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAPproducts and services mentioned herein as well as their respective logos are trademarks or registered trademarks ofSAP AG in Germany and in several other countries all over the world. All other product and service names mentionedare 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 AG and its affiliatedcompanies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAPGroup shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Groupproducts and services are those that are set forth in the express warranty statements accompanying such products andservices, if any. Nothing herein should be construed as constituting an additional warranty.

3TABLE OF CONTENTS

1. Introduction.......................................................................................................................... 41.1 Demo Description................................................................................................................................ 4

1.2 Tips Before Running The Demo .......................................................................................................... 4

1.3 Storyflow Summary ............................................................................................................................. 4

1.4 Release Info For Used Components.................................................................................................... 4

2. Demo Script Step By Step................................................................................................... 52.1 Step By Step Explanation.................................................................................................................... 5

2.1.1 Set up CRM system to transfer customizing data into MDM..................................................... 5

2.1.2 Set up MDM repository and import configuration data............................................................ 12

2.1.3 Creation and Sending of Business Partner records from CRM system ................................... 17

2.1.4 Information regarding PI configuration data ........................................................................... 21

2.1.5 Importing of data into MDM ................................................................................................... 25

3 Summary............................................................................................................................. 30

41.INTRODUCTION

1.1 DEMO DESCRIPTION

This demo shows how to quickly consolidate master data e.g. business partners from an SAP CRM system via SAPNetWeaver Process Integration into SAP NetWeaver Master Data Management 5.5.Here standard delivered Business Content of SAP NW MDM 5.5 SP06 is used. This means that the repository, ImportMaps, PI Business Content and Customizing tables for the CRM system are used as delivered to set up an Initial Loadof business partner data from a CRM system into MDM.

1.2 TIPS BEFORE RUNNING THE DEMO

The demo script provides the complete picture with explanations of all steps involved in the overall process flow.Therefore we highly recommend reading the demo script before running the recorded demo. The recording is based ona comprehensive hands-on exercise for the given scenario. Please note that due to the original intent of the demo, therecording contains some steps that are only relevant for the original hands-on exercise (such as system log-in details),and can be neglected in this context.

1.3 STORYFLOW SUMMARY

The entire demo consists of the following steps:

Set up CRM system to transfer customizing data into MDMSet up MDM repository and import configuration dataCreation and Sending of Business Partner records from CRM systemShort information on PI configuration data (Highlights)Importing of data into MDM

1.4 RELEASE INFO FOR USED COMPONENTS

Software Component Release Support Pack

SAP NetWeaver MDM 5.5 6

SAP CRM 6.0 3

SAP NetWeaver PI 7.0 15

5

2.DEMO SCRIPT STEP BY STEP2.1 STEP BY STEP EXPLANATION

In the following, all steps of the recording are explained in detail. Please note that the recording is based on an end-to-end hands-on exercise.Therefore, some of the described steps contain information that was only relevant for the purpose of the exercise (for example, system log-in steps).2.1.1 Set up CRM system to transfer customizing data into MDM

Steps What You See What To Say

Step 1.0: Logon to CRM System

Call SAP-Logon .Select CRM system.

Step 2.0: Call transaction MDMGX

6


Call transaction MDMGX.

After calling the transaction, you get theshown screen provided.

Once you are logged on, This calls the“Generic extractor”, the transaction tosetup, extract and transfer customizingdata either to an ftp-server or a filesystem. From there MDM can access thedata.Before we can extract the data, we haveto setup the structure of the customizingdata to be transferred. The transaction isvery powerful however we’ll do here onlysome basic customizing setting to do aninitial transfer.We will not be able to configureeverything in class, since users wouldlock each other during working. For thispurpose the instructors already createdsome entries for you.

7


Step 3.0: Define Object Types

Select option “Define Object Types”.

After you had a view on the differentobject types you press the “Back-button” in the toolbar to navigate tothe main selection screen of thetransaction.

As you can see, entries have alreadybeen created for each of the participantsgroups.We’ve done this for you, since here userswould lock each other while working inthis table.The purpose of entries here is simply todefine new object types for dataextraction later on.

Step 4.0: Define Repositories and FTP Servers

Select option “Define Repositories andFTP servers”.

Mark the Logical repository name,which belongs to your group.

Select the display button to get animpression, which parameters havebeen defined here (we did only thenecessary ones for our scenario).

Press the “Back-button” in thetoolbar to navigate to the main selectionscreen

We’ll define now what kind of data needto be extracted for these object types(e.g. regions, languages, BusinessPartner types etc).

Here the SAP team created as wellentries for you, since users would lockeach other while working in this table. Inthis screen an ftp-server addresses canbe maintained (in case you use them –we don’t), the type of the client system,and languages for the customizing data.

8


Step 5.0: Upload ports and check tables

The file has the following structure(double-click on the file and view the fileeither with notepad or WordPad.As you can see, the file describes theobject type “BusinessPartner”.You need to replace the object typewith your individual object type in theCRM customizing, e.gIM271_BP_GRP01.This can be done with the replacefunction in notepad.

We’ll define now what kind of data needto be extracted for these object types(e.g. languages, Partner titles, Partnerfunctions etc).Via the option “Upload ports and checktables” – since our repository is astandard repository, we simply have toupload the standard provided Businesscontent. This is what we’ll do. In theBusiness Content for the MDM Businesspartner delivery there’s one file“MDMGX_BuPa_Org.txt” describing thestructure of the customizing tables. It isstored in the folder C:\session\IM271\.Before we can upload the file, we have tomake some changes (these changes arerequired due to the character of theexercise that each group has its specialrepository name assigned).

IM271_BP_GRPXX

9


Step 6.0: Upload ports and check tables

Switch back to the CRM system andselect “Upload Ports and Check-Tables”.Select your object type from the dropdown box or via the F4-Help (be carefulhere, not that you use someone else’s)and enter the complete path includingfilename, where your file is stored.After successful upload you receive theconfirmation: Upload OK!Press two times the “Back-button” .Select “Maintain Ports and Check-Tables”, select your object-type and hitexecute => you’ll see a list with allcustomizing tables imported for yourobject type.

Now we’re ready to upload thesedefinitions into the CRM system.

Step 7.0: Generate XSD

Select “Generate XSD”.

Select your repository from the drop-down list.

For the File directory field, enter thefilename (including path), where theXSD-file should be stored. This was thelast step for the customizing dataconfiguration in the CRM system.

Now that we defined the structure of ourcustomizing data to be extracted, we’llgenerate an XSD-File. This XSD-Fileafterwards needs to be imported into ourrepository.

10


Step 8.0: Start Extraction

Select “Start Extraction” option.Choose exactly the settings you see onthe screen.Choose your own Repository with yourGroup number.For the File directory field, choose yourlocal download (to get to the C:directory, go to Windows Explorer >NetWeaver 7.0 EhP1 SP0 >Win2003(C:)). Go to C:\ProgramFiles\SAPMDM5.5\Server\Distributions\Localhost_MSQL.This is the directory, where the MDMImport Server reads data files forautomated Import.Select the checkbox to download inMDM Port structure.Uncheck the checkbox for Upload viaFTP!Afterwards press .

After generating the XSD file, wecontinue now to download the actualcustomizing table entries to our locallaptop.

11


Step 9.0: Check Import Server directory

Please verify in the Import Serverdirectory, that you’re data arrived atthere. You can do this via the WindowsExplorer.

We’re now finished with the definition andextraction of the customizing data fromCRM.

122.1.2 Set up MDM repository and import configuration data


Step 10.0: Mount Server

Start MDM Console via Start / AllPrograms/ SAP MDM/ MDM ConsoleMount your local MDM Server via “MDMServers” -> “Mount MDM Server”Or by using the context menu in the left-hand side “Console Hierarchy” pane.Use “localhost” as MDM Server name.

NOTE, the MDM server localhost mayalready be running.

Step 11.0: Unarchive Repository

Place the mouse on your MDM Serverand from the Context Menu select“Unarchive Repository”.

13


Step 12.0: Create your OWN Repository

For the DB login enter the requiredlogin informationAfterwards press the “Next”-button.Select appropriate Archive (last box inthe dialog screen)Type appropriate repository nameAfterwards press the “Finish” button.Wait for the dialog box to tell you thatyour archive has completedsuccessfully.

Please be very careful here!Your repository name needs to match(and be case sensitive) the repositoryname you defined in the CRM system.Otherwise the Import Server will later onsearch in a different directory for thecustomizing data, you already extractedfrom CRM.Please stick to this convention; otherwisewe’ll have some issues later, when itcomes to configuration later

Step 13.0: Connect to Repository

Select the repository in the “ConsoleHierarchy” pane.Enter login data

IM271_BP_GroupXX

14


Step 14.0: Ports

We navigate to the “Admin node” in the“Console Hierarchy” and expand thenode.We select then the “Ports” node

Before we load the repository, we’ll havea look at the port-structure. The Portdefinition is done under the Admin node.You can see all of the different ports,which come predefined for the repository.We’ll focus on the ports for the CRMsystem. We can see a port for MDMBusiness Partner object Inbound itselfand numerous ports for customizing data.

Step 15.0: XSD Structure/XML Schema

Select the XML schema forReferenceData CRM.You’ll see then the filename and path,where the original xsd-file in therepository, came from.Replace this xsd file with the xsd file,that was generated from our CRMsystem(C:\session\IM271\CRM_Customizing.xsd\IM271_BP_GRPXX_M27800.xsd)Select the XML-schema for SAP MDMBusiness Partner 5.5.5.You’ll see then the filename and path,where the original xsd file in therepository, came from. Replace thisxsd file with this xsd file(C:\session\IM271\MDMBusinessPartner_556.xsd).Afterwards press “Shift-Return” to saveyour work.

We also have to bring in the XSD-structure (containing the structure of ourcustomizing data), we generatedpreviously from the CRM system. TheXSD-structure is used by the ImportManager and the Import Server (optionxml-schema). The advantage of usingXML-schema is that each file to beimported is validated against the xml-schema. This way files with a wrongstructure can be recognized easily and asa consequence they won’t be imported.

15


Step 16.0: Load Repository

Select the repository in the “ConsoleHierarchy” pane and load it via theContext Menu. Load RepositoryImmediate.

Now we’re ready to load the repository.We select the repository in the “ConsoleHierarchy” pane and load it via theContext Menu. Load RepositoryImmediate.

Step 17.0: Start Import Server

The Import Server is started via “Start –Settings – Control Panel -Administrative tools – Services”.In the Services-list, select the “MDMImport Server 5.5” and start it via theContext Menu.

After the successful load of the repository,we’ll start the Import Server toautomatically import the previouslyextracted customizing data from our CRMsystem into MDM.This step can be done manually via theImport manager, however due to the fact,that we generated and have to populatenumerous lookup-tables with values, wedecided to do this automatically. TheImport server should pick up now the filesfrom the different directories and importsthem into the repository

16


Step 18.0: Check Directory

Go to C:\Program Files\SAP MDM5.5\Server\Distributions\LOCALHOST_MSQL\IM271_BP_GroupXX\Inbound\CRM\LT_AcademicTitles, where XX isyour group number.

You can check, on what’s happening inthe different port structures, by looking inthe directories under each port directory.Archive : After successful processing of asource file it’s moved into this directoryLog: a log file is written into this directoryfur further analysis.Ready: From this directory Import Serverpicks up the files to import. As long as afile hasn’t been processed completely, itstays in this folderException: If a problem occurred duringprocessing, the source-file is moved intothis directory.

Step 19.0: Check tables

When all ports have been processedsuccessfully, you can also start theMDM Data Manager via the Start menu(Start > Programs > SAP MDM > MDMData Manager).

Once in the Data Manager, check thedifferent lookup tables, whether the dataarrived there. An example for loadedConfig-Values for the different languagescan you see in the screenshot below.

172.1.3 Creation and Sending of Business Partner records from CRM system


Step 20.0: Create new Business Partner

Start transaction BP (Maintenance ofBusiness Partners).To create a new Business Partner(Organization), press first the“Organization” button.Then populate the other fields as shownin the below screenshot.Enter your CRM User ID here for eachrecord you create. This is onlynecessary so that you later on findamong all the files PI created the oneswhich belong to you.Save your BP at the end.

Sending Business Partner Data fromCRM system. We branch again into theCRM system to create some BusinessPartner records.

Make sure, that when you create aBusiness Partner, address data aremaintained complete. The reason for thisis that the standard PI content forBusiness Partner is defined that way thataddress data are mandatory. (If your BPhas missing address-fields, it won’t gothrough PI, and PI would deliver anexception). If you would have businesspartners without address data, you wouldhave to either maintain the dummyaddress data or make changes in the xsddefinition of the PI content.

18


Step 21.0: Create new Business Partner

Call transaction mdm_clnt_extr.You may need to re-size your screen tosee all of the fields as displayed in thescreenshot.

After creating the Business Partners wewould like to extract and send the newlycreated Business Partners from CRM toMDM.

Step 22.0: Create your own variant

Create your own extraction variant.For field “Variant”, enterTECHED_BUPA_XX, where XX is yourgroup number.Extraction object: BUPA_EXTRACT2Target System:INTEGRATION_SERVER_NWXDistribution Mode: I(ensure this is capital letter “I” as inInvoice, not lowercase l as in “land”.Block Size : 1Afterwards press “return” and you’llbranch to the detail screen to do furthersettings.Make a double click on the BUT000field group => your screen on the right

PI will use this info as well, so that youhave later on no problems with finding theXML-File, containing your data – but moreinfo about this is given in the PI-Configuration

19


hand side will be updated.For the field BU_SORT2, enter yourUser-ID (this field definition refers to theSearch term2 – remember: youmaintained this field for all the businesspartners you created). The extractionlater on will select all records, whichhave this field value in the Searchterm2 field.Save your settings by pressing thebutton.

Step 23.0: Start Extraction

Therefore press the -button.Afterwards press the -button. This brings you to the overview screen,showing all extraction jobs which havebeen launched.The instructors will now show you yourXML messages in the PI monitor.

Your screen is updated – we can use thisvariant now to extract our BusinessPartner data.

20


Step 24.0: Monitoring

Once in PI, call transaction sxmb_moni.Execute the Menu option “Monitor forprocessed XML Messages”.Afterwards press the -button in thetoolbar. You’ll see a display of allmessages for the selections you did.If we would like to see more detailedinfo on our message, we can mark itand press the -button in thetoolbar.This displays then the completemessage information includingmessage content, receiver info and soon.

We can see, that all of our messageswere processed successfully (Status-Flag).If you look at the message detailinformation and look at the payload-information, you should be able to findyour business partner data, you sent out.

PI is configured that way, that it writes theoutgoing message via file adapter on afile share. Below picture is just a sample,cause of security restrictions the trainingparticipants have no access to this fileshare. Via a background copy programthe files from this share will be copied toanother location, from where you canaccess them. The instructors will tell youthe exact location from where you canaccess the files.

212.1.4 Information regarding PI configuration data

(Proceed to Step 2.1.5)


Step 25.0:

Log on to PI system.Start Integration Builder.Start transaction sxmb_ifr.In the Integration Builder call theIntegration Directory.It can be, that you’re requested asecond time to logon.Again enter username and password.Once you’re in the Integration Directory,select the scenarioMDM55_Teched2008 and expand it.

We decided to provide you an alreadypreconfigured PI-scenario, which is readyto use for our Data-Transfer. The pre-delivered PI content for MDM has beendeployed and it’s ready to use forconfiguration. In the next steps, we wouldlike to explain the highlights of the PIconfiguration, so that you could do similarconfiguration on your own at home.Again, we only have a look at theconfigurations; we won’t do any changesor configure something on our own.You can see that the following objectshave been configured.Communication Channel FileReceiver Determination|M27_800|ABABusinessPartnerOutInterface Determination|M27_800|ABABusinessPartnerOut|XI_INTEGRATION_SERVER_FileadapterReceiver Agreement |M41_800|XI_INTEGRATION_SERVER_Fileadapter|MDMBusinessPartnerIn

In the SLD (System Landscape directory)there are two systems configured (notdisplayed here)M27_800 (this is our CRM system)XI_INTEGRATION_SERVER_Fileadapter(a directory on the XI-Server).

22

What You See What To Say

Step 26.0: Receiver Determination

Some more info about the ReceiverDetermination. In a ReceiverDetermination you define one or morereceivers to a sender /outbound interfacepair. In our case there’s only one receiverdefined, and that’s the file adapter. TheCRM system M27_800 sends out it’s databy using the message typeABABusinessPartnerOut. The fileadapterXI_INTEGRATION_SERVER_Fileadapteruses the message typeMDMBusinessPartnerIn. For supportpackage SP06 new business content isdelivered, which has been used here.

Step 27.0: Interface determination

Some more info about the Interfacedetermination.You use an interface determination tospecify for a sender and a receiver whichinbound interface is to be used for theinbound processing of a message.In an interface determination you definefor the outbound interface of a sender aninbound interfaceAn interface mapping between theinbound and the outbound interface hasbeen done.

23


Step 28.0: Receiver Agreement

The system M27_800 sends out theBusiness Partner data by using theinterface ABABusinessPartnerOut.MDM (in our case the file adapter)receives the data via the messageinterface MDMBusinessPartnerIn.The definition, how a field from themessage type ABABusinessPartnerOut isgetting mapped toMDMBusinessPartnerIn is done via theInterface Mapping.With the MDM Business content therecomes a predefined Interface mapping forexactly these two message interfaces(ABABUPa_700ToMDMBuPa555In).There are several of these interfacemappings delivered, depending on theWAS Version the sending system isrunning on.Some more info about the ReceiverAgreement. In the Receiver Agreementyou define which communication channelto use to process for a particularcombination of senders and receivers.The receiver agreement is used for theoutbound processing on the IntegrationServer (the XI system).

24


Step 29.0: Communication channel

Some more info about theCommunication Channel.In the Communication Channel definitionit’s defined e.g. what adapter type (in ourcase file adapter) and what targetdirectory is used to store the files. Inaddition you can configure e.g. how thefilename is composed or in what formatthe files are written. In the following screenshots we showsome highlights of the communication.In the processing tab there’s defined inmore detail how the filename iscomposed. In our case a counter is usedto make sure, that files aren’t beingoverwritten. Possible filenames createdby the system are e.g.01_xi_output_00001.xmlThe last parameter for the filenamecomposition is the calculation definition ofthe variable var01. The calculationformula looks in the message payload(the actual Business partner information,you’re sending over) and assigns thevalue of the field SearchTerm2 to thevariable var1. Var1 is used as a prefix forthe filename generation, that way eachgroup can recognize their files on the fileshare pretty easy (Remember you weretold to add your group name into the fieldSearchTerm2 when creating yourbusiness partners.

252.1.5 Importing of data into MDM


Step 30.0: Start Import Manager and Connect to Repository

Start the MDM Import Manager via StartPrograms ->SAP MDM-> ImportManager.Select the repository and logon.

Importing a file into MDM. Now that we’veseen, how XI is configured and that ourfiles arrive on the provided share, we’llcontinue and import a file into ourrepository:


For the type of data we’re reading, weselect XML Schema.This type has the advantage that thesystem makes a structural comparisonbetween the XML-schema definition andthe XML-Data File to be read in.For the remote system we select MDCCRM, since our source file comes froma CRM system.For the XML Schema, select SAP MDMBusiness Partner 5.5.5, which is theBusiness partner structure.And finally select the file with the sourcedata

If the structures don’t match, the programdisplays an error-message, telling, thatthere’s a structural mismatch.


26


To load this Import Map, press thebutton,A popup with all the different ImportMaps is displayed hereSelect the MDMBusinessPartner map.Theoretically we could change here themapping, but in our case everything isfine and we simply continue.

After reading the data, you should seethis screen. It shows the source datastructure (of your xml-file) and the targetdata structure (your repository).We’ve to perform the mapping of thefields from source to target structure.With the delivery of the Business Partnerrepository, there comes also a ready-to-use Import Map for the Business Partnerobject (_MDMBusinessPartner).This map contains all mappings fromsource to target fields for these structuraltypes.

Step 33.0: Map Fields/Values Tab

Select the Map Fields/Values tab. Once you opened the map, the systemautomatically performs the field mappingbetween source and target fields. Youcan see this by clicking on the MapFields/Values tab. Each field, which hasan icon in the Mapped column, ismapped to another field. A single field canalways be mapped only to one targetfield, not to several.

27

What To Do What You See What To Say

Step 34.0: Match Records Tab

Select the Match Records tab. Here again we can see, what was alreadystored in the map and can be reused.These are the Matching fields and theDefault Import actions. Whatever hasbeen stored here duringcreation/changing of the map, will bereused.

Step 35.0: Start Import

Select the Import Status tab.Now we start the import by pressing the

button.A popup window appears, displayingthe different import steps performed at atime.After a successful import you shouldsee the popup “Finished importingrecords”.

Now we see that we’re ready to importthe data(=> All mapping steps, matching fieldassignments and Import actions are ok).

28


Step 36.0: MDM Data Manager

Start the MDM Data Manager via theshortcut on the desktop or via the Startmenu.Select the repository and logon (withuser Admin, no password)In the Data Manager screen, you’ll seenow all of your imported records.Check the Search Terms for your Groupnumber.

We finished now the import of the dataand for verification we’ll go into the MDMData Manager to check whether ourrecords really arrived in the system.

Step 37.0: Edit Key Mappings

Select a record in the Records paneand with right mouse click select theContext menu option Edit Keymappings.

If you need additional verification, you cancheck also for the key mapping of arecord.

29

What To Do What You See What To Say

Step 38.0: Display Record

The key mapping dialog for the record isdisplayed.

You can see that the record came fromthe CRM system and in addition you cansee the key the record has in the remotesystem.

This is the end of our exercise aboutconfiguration of a system landscape torun MDM Core processes.

30

©SAP AG 2008 / I NTERNAL / SCENARIO ID:

3 SUMMARYThe demo is a recording of an end-to-end hands-on exercise about extracting, and importing master data from an SAPCRM system to SAP NetWeaver MDM for subsequent consolidation and harmonization purposes. Using thepredefined MDM business content for such a scenario helps customers to:

Lower the TCO due to short configuration and implementation times using standard business content for MDM Enable the composition of cross-application processes with consistent master data

Documents

SAP NETWEAVER MDM WALKTHROUGH · 2019-11-12 · Step 8.0: Start Extraction Select “Start Extraction” option. Choose exactly the settings you see on the screen. Choose your own