When we started the project we are debating about which is the best way to import material master data from SAP R/3 to SAM MDM. Now, before we got to the core material data, there is some data on which the material data is dependent on like Account groups, Item Category groups, Industries, Units etc etc. This data in MDM terminology is called the look up data. In this blog we will see how to extract data out of SAP R/3, use the standard maps provided by SAP and load this data. So, the first thing that you do is to unarchive the SAP MATERIAL repository (comes along with the MDM software). This step should be pretty easy. 1. Specify the DBMS where you want to unarchive the respository. 2. Specify the name of the repository and the name of the archive (.a2a) file. That’s all you need to do, you should be able to see the repository in your MDM console. Now if you see on the right hand side (in MDM), it gives you a complete list of tables that are a part of this repository. This data model is what is given by SAP as a standard. However, if you have different systems from where the data is coming and this data model, does not fit your requirements, you should be able to change the same according to your requirements. For now, I am assuming that we are going to go with the standard repository given by SAP. So, given that what do we need to do import the data? 1. Create Client systems / Agencies (SP01) in MDM. 2. Decide upon a format in which you are going to import data. MDM can accept data in multiple file formats – Excel, XML. For now we will concentrate on the XML format. 3. Extract data from SAP R/3 Check Tables / Look up tables Material Data Before we upload the material data, we will have to upload the data for the Check tables. Now the questions comes, how do we extract data for the check tables from SAP R/3. We have write some customer ABAP Programs to extract data in an Excel format or an XML format. However, SAP has been kind enough (Is it really??) to help us out in this context. We have note 830864. which when applied will create these extract programs for the check tables. • The extractors with the ending”_552″ are synchronized with the MDM 5.5 Support Package 2 and the extractors with the ending “_551” are synchronized with MDM 5.5 Support Package 1. • Enter the path under which you want the system to save the XML document as the first input parameter (p_fpath). • Do not select the second input parameter (p_indiv) because this option is not supported for Support Package 1 and Support Package 2 yet. When you execute the program, the output file will be a bunch of XML files, with the data for the check tables. These files can be directly used to import the data into SAP MDM. A sample XML file for UoM details will look like the below one. Now, you are ready to import the data. Login to the Import Manager and give this file as input. You should be able to preview the source data in the bottom of the screen. Now, select the source and target tables in the import manager (on the top). Now the next step to map the source and target fields. If it is not standard you can do the mapping manually and store the mappins as a .map file. In the current case as we are using standard data, SAP has gives the standard mapping file. Before mapping Now, open the map file – File –> Open Once you choose the right mapping file, you should be able see the mappings on the tab, in green colour. In the TAB – Match Records, specify which field or fields to be used to determine duplicates. Here you specify what is the action you want to perform. Default will set to Skip. Change that to create so that the data records are created. If you want to test the creation of the records, you can always set the CREATE status (Import Action) for specific records. (See the picture above). In the Import Status tab, you should be able see what is the next step to be done. In case you have missed anything it will ask you to do the specific step and will not let you proceed. Right now, we are all set to import the data Unit of Measurements. Now go ahead and click the Import (Exclamation mark) button on the top toolbar. If everything is good, message pops up informing how many records have been imported. Other wise a report is generated showing the errors. Closing In further blogs we will see how to import the actual material data, how to map data manually and lots of other features that MDM gives. You might be wondering, where does XI fit in this case. As we are dealing with standard data and SAP has provided the extractors to write XML files, here you might not need XI. I am talking only about standard data coming from SAP R/3. If your data is coming from other systems you might need XI to map and write an XML file to specific location. While loading the actual material data, an MATMAS 05 IDOC is sent to XI and XI will write the data into an XML file which can be picked up by MDM. The places where are dealing with non-SAP systems, its left to technical design team as to how to execute the process. One has to repeat this process for every table modeled in MDM (Painful isn’t it). Well that is the way it has be done because unlike SAP R/3, MDM does not deal at an object level rather it deals at table level. Note : The repository structure, mapping files might change for different releases.