Data from R/3 to MDM

Hello,
Our requirement is to transfer the data load in R/3 tables to MDM for data management etc..
Please suggest me about the ways to achieve this.
Please help its urgent!!
Brad

Hello Brad ,
To transfer the data from R/3 to MDM you can have a look at the following options:
MDMGX and MDM_CLNT_EXTR.
To have details about it have a look at the following links:
MDMGX Configurations
MDMGX
SRM-MDM Integration
MDMGX is to extract the generic data.basically as provided by the SAP for Vendor ,Customer,Employee,Product and Material type of objects for other you have to customize and write function modules.
In MDM_CLNT_EXTR u can extract data of any type through idocs
Hope this may help you.
Ankit

Similar Messages

Process to Extract the data from R/3 to MDM .

Hi
Can any one Explain the process of how the data is Extracted from the R/3 to MDM.
If any doc plz mail me to [email protected]
Thanking you in Advance.
Hari.

Hi,
To extract data from R/3 to MDM you would need to first set up a port to XI (if it is your integrator) and then establish an FTP to the MDM server.
R/3 has lookup data/check table data that can be extracted to MDM to do this you could run standard code provided by SAP extract the lookup data as an xml file & upload this data using hte standard maps in to the MDM repository
If you have any custom tables in R/3 you could extract that data using MDMGX transaction code .
Finally for the actual master data you could set up extraction variants using MDM_CLNT_EXTR and schedule jobs to run them/ MDMC to extract records.
Please find the IT Scenario config guide & other relevant documents at:
https://websmp204.sap-ag.de/nw04operation
Regards,
Anita

Replicate Non-standard lookup data from R3 to MDM

Hi MDM Experts,
I am having a scenario like i want to replicate the reference data(Lookup table data) from R3 System to MDM System.
For that i can use the transaction "MDMGX" but in this we can replicate for standard lookup table data which has been shipped by SAP in R3 on the basis of object types like article, product, catalog etc....
I want to replicate the look up table data which is not standard one.
I just want to know that what all the possible ways so that I can customize the same and would be able to replicate the lookup table data from R3 to MDM.
Any help would be highly appriciated.
Thanks,
Saurabh..

Hi Deepankar,
I'm sorry to correct you, but MDMGX does not send IDocs to MDM. MDMGX provides the customizing data in XML format. You can configure MDMGX either to send the XMLs directly to MDM's port folders via FTP or to download those files locally on your PC. MDMGX is only capable to extract customizing data for master data objects but not the object itsself.
The output of MDM_CLNT_EXTR depends on the system it is running in. R/3 (ERP) systems use IDocs for message distribution via the systems ALE layer. These can be DEMDM, CREMDM, MATMAS, and so on if you use the standard SAP content, or any other customer defined IDoc type. These IDocs have usually an XML format, but they are not really XML documents. The transformation from IDoc to XML usually happens on XI.
It' a bit different if you extract data from CRM or SRM systems. Those systems use an integrated Proxy implementation for message distribution. The messages sent to XI (or MDM) are already real XMLs.
Additionally pleas enote that MDM_CLNT_EXTR is intended to be used for the extraction of Master Data Objects and not the related customizing data!
BR Michael

Initial load from ECC/R3 to MDM

Hi,
Could any one tell me the process for one time intial load from R3 to MDM.
preferably without XI.
how to extract data from R3 ?
what format?
how to map source to MDM repository?
Farah

Hi Farah,
There are two transactions to extract the data from R/3
MDMGX - For Extracting Lookup data
MDM_CLNT_EXTR - For Extracting Main table data
MDMGX Steps:
1.Go to transaction MDMGX.
2. Define Object Types: There are some standard object defined in MDMGX, you can use from them as per your requirement and you can also create the new objects.
3. Define Repositories and associate it with the object created in the previous step.Also add the FTP Server details.
4. Maintain Ports and Check tables: Add the Codes of the ports and select the corresponding table from where you want to extract the data.
5. Generate XSD: to generate the XSD file to use in console while creating port.
6. Start Extraction: To Extract the data from the R3 to MDM via FTP Server.
MDM_CLNT_EXTR steps:
Refer the below link that contains the entire configuration needed to extract the Main table data.
[https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/50260ae5-5589-2910-4791-fc091d9bf797]
Regards,
Jitesh Talreja

Exporting data from R/3 system as IDOCs

As I am working with MDM and not familar with R/3 very much, is there any manual or baisic guidlines how to export master data as IDOCs from R/3 ?
Thank you in advance

Hi Vytas,
to send the data from R3 system to MDM System, you need to follow procedure as mentioned below:
1. you can use the transaction "MDMGX" in R3 system to extract the refrence data to the mdm system via FTP Server.generally this transaction is used to extract the lookup tables data into the repository.
for using this, you can use the option there in transaction MDMGX as "Define repositories and FTP Server" and configure all the required details and you have to install the ftp server on MDM server.then to extract the data, there is a option as "Start Extraction" and your data will be extracted from R3 to MDM inbound port via FTP Server.
for further details about MDMGX, you can refer SAP Note No-964991.
2. to extract the main table data from R3 to MDM, you can use the transaction "MDM_CLNT_EXTR".
for detail info about this transaction, just refer the SAP Note No.-836985, 1035601, 844558.
both transaction will be used for extracting the data from R3 to MDM as per your business requirement.
I hope, this will help you.
any further info, just let me know.
Regards,
Saurabh...
Reward with points if found helpful.

Help Required -- Can we use SQL Query to READ data from SAP MDM Tables

Hi All,
Please help.........
Can we use SQL Query to READ(No Creation/Updation/Deletion just Read) Data from SAP MDM tables directly, without using MDM Syndicator.
Or direct SQL access to SAP MDM tables is not possible. Only through MDM Syndicator can we export data.
Thanks in Advance
Regards

All the tables you create in Repository comes under A2i_CM_Tables in Database named as your repository name. So the tables names are fields of table A2i_CM_Tables. Now i tried it but cant make it.
Now, I dont think its possible to extract all fields in tables and there values using select query. May be pure sql guy can do that or not.
But there is no relation of data extraction and syndicator. Data is viewed in Data Manager. and you can also store data in a file from DM also.
BR,
Alok

Problem: Unable to retrieve workflow data from MDM repository

This is a new MDM installations scenario for version 5.5 SP05 (5.5.40.83).
After installing MS Visio, finding problems connecting it with the MDM Data Manager. After doing MDM workflow installations, able to initiate the MS Visio Workflow from MDM Data Manager and can see the Pane-MS Visio Workflow Stencil but not the able to see the Pane-MS Visio Workflow Stencil Details that appears below the Pane-MS Visio Workflow Stencil. Secondly geting a pop-up with the error message as - 'Unable to retrieve workflow data from MDM repository.'
I have added a parameter Mail Server=MailServerIPAddess (the existing IP addr), but it hasn't helped.
Can any one please help me in this !

Hi
As Felix mentioned, it might be a version compatibility problem.
You have also mentioned that mail server is not working for that do this
Mailserver = SMTP server.company.com ( ex. Mail.company(xxxxx).com)
MDM workflow notify task is working after rebooting the Machine. So the rule is after making changes to MDS.ini file reboot the machine ,to observe the consequence of configurable changes.
If u need anything this let me know.
Regards
Hari

Error while retrieving bulk data from mdm in staging server

I am getting an error while retrieving bulk data from MDM. The error goes like this "NiRawReadError: An error occured when reading data from socket.".
Could anyone please suggest me about the possible cause of this error. Please reply soon.
Moderator message: network error, relation to ABAP development unclear, please search for available answers, check with system administrators, consult SAP service marketplace.
Edited by: Thomas Zloch on Nov 22, 2010 5:16 PM

Can you elaborate the thing... I don't think /*+ APPEND */ this is working for me ,still I am getting same error.
If you have any other suggestion,I would like to hear.
Should i not put commit after some 500 records inserted ? As i am putting commit once after whole data gets inserted.

Transfer the data from MDM to SAP R/3

Hi,
I have to transfer the material master data from MDM to R/3.I have syndicated the data and put the file in the .xsd format in the ready folder of the repository.Now I have to transfer this file to R/3 , one way is through XI(XI will pick the file from the current location and an IDOC from there will pass this data to R/3. The other way I was thinking a UNIX script can do it. The UNIX script will run and pick the data from ready folder and pass it to R/3.If somebody of you has done similar thing kindly reply.
Regards,
Ashutosh

The best method of integrating MDM with R/3 is to use XI (PI). There are a couple of reasons for this, but most importantly you can use the IDoc adapter to turn your XML message into an IDoc and send it to R/3. This has a lot of advantages because IDocs are very easy to monitor, troubleshoot, and reprocess in the event of an error. IDocs are definitely the preferred method of integration with R/3, therefore using PI is a very good idea. A few years back I wrote a blog about how to configure XI for an interface between MDM and R/3, perhaps it will help you:
/people/harrison.holland5/blog/2006/12/20/xi-configuration-for-mdm-integration--sample-scenario
While it is possible to use a batch script, it's not recommended. You would still have to write a load program (LSMW or some other type of load program) on the R/3 side. Monitoring and troubleshooting is going to be more cumbersome, because you also have to monitor the message flow on the UNIX system. If PI is serving as the middleware it does the end-to-end monitoring for you.

Transferring Product Data from SRM 7.0 to SRM-MDM 3.0

Dear SRM-MDM experts,
We are running the program BBP_CCM_TRANSFER_CATALOG to transfer product data from SRM 7 to SRM-MDM 3.0 The question we have is after running the program, where do we find the file the XML file which the program has generated so we can see the results? SLG1 just shows how many products were processed. We need to see the list of the products generated.
Thanks and regards
Pedzi

Hi Pedzi,
You can find the generated XML file in MDM server. Here is the path to get the Product Data XML file.
C:/usr/sap/SRD\MDS00/mdm/distributions/MDD_ORCL/REPOSITORYNAME/Inbound/SRM/_MDMProductDataTransmission/Archive
Thanks,
Anshuk Saxena

Price Information data from SRm to MDM

Hello,
I m working on SRM-MDM Catalog 2 scenario.
I have imported lookup table data in MDM using MDMGX transaction.
But i couldnt get data for Price Lookup Qualified Table.
Can anybody please tell me how should i send Price Information data from SRM?
Thanks,
Maheshwari

Hi,
By MDMGX, you replicate only the lookup table data.if you want to see which kind of look uptable data it replicate, you can refer the FS Guide/Config Guide of SRM-MDM.
when you replicate the main table data from SRm to MDM via XI then you will get all those info related to price in the Qualified lookup table.
Hope this will help you.
TNR,
saurabh...

Posting Vendor data from MDM to R3

Hi,
We are trying to post vendor data from MDM to ECC via XI using CREMDM -> CREMAS + ADRMAS and using the standard mapping SAP has provided. I have serialized CREMAS + ADRMAS such that ADRMAS posts before CREMAS. ADRMAS works fine but CREMAS fails with error "Fill all required fields SAPMF02K 0111 ADDR1_DATA-NAME1". Standard mapping is mapping the no-data value "/" in CREMAS NAME1 field too as recommended.Still it throws this error.
If anyone has worked on similar scenario...Please help.
Thanks,

Hi Swapna,
we had faced the same error.
You will need to enter a value in the name1 field if you want your idoc to post successfully.
even though in the vendor creation transaction name1 is not a mandatory field but for the idoc posting, the name1 field is required.
We solved the error by entering a value in the name 1 field.
Hope this helps.
Jyotika
Pls reward for helpful answers

Contract data from ECC to MDM

HI all,
We have standard setup to push Contract data to catalog from ECC using MECCM transaction from ECC... and Via PI we use the standard way to FTP the file... we use standard mapping interface in PI - CatalogueUpdateNotification_Out... which in turn pushes the Data from PI to FTP server. Where the MDM picks it and upload it.
Everything works fine.... But I need to understand how the MDM recogize the File and how the PORT and XML schemas upload the FIle into MDM database???
Need to Identify whether it can be modified???
regards,
Prabhu

Hi Prabhu,
You can upload the xsd from PI into MDM. To get the schema go to your message type and click on xsd tab and copy and paste in notepad and save as .xsd and upload. Else you need to create the schema in external tools like altova xml spy or stylus studio etc.
There is option in MDM whether to load that file from the port automatically or manually. If automatic it will load immediate else you need to run manaully the file.
Need to Identify whether it can be modified???
I did not understand this. Do you mean to change something in the file once written from PI. If yes then try to go to MDM console and open the port and load it manually. So the file will be sitting there and you can modify and upload manually through Import Manager. But this is not advisable in production.
If PI is sending a csv or tab delimited file then you dont need to have a schme for that. You can load it manually.
Regards,
---Satish

Data from ecc to xi to mdm

Hello
would you please let me know how data data flow from ECC-XI-MDM
Thanking you

Hi
For vendor master use IDOc of type CRemas.
for customer master use idoc OILDEB,
Configuration for sendinf any master data from ECC to XI
1. create RFC destination of type 3 in ECC using SM59 and point to your XI system
2. Create Communication Port for IDoc Processing using Transaction WE21 select the RFC destination created in above step.
3. Create Logical System (LS) for IDoc Receiver System: Transaction BD54
4. Create Partner Profile with Outbound Parameter. Transaction WE20
-Deepak.

Read data from MDM For Lookup and Flat table using MDM ABAP API

Hi,
I have requriment to read data from MDM from FLAT and Lookup table using MDM ABAP API. My design is like this ,
I have one ITEMS (Main table in MDM) and inside that i have one Lookup flat table ITEM_TYPE , my requriment is to read Item number and its related Item type.
From ABAP.
Please help if any body has any idea.
Regards,
Shyam

HI Guys,
I found my solution by myself. Below is the solution , hope this will help others:-
Retrieve data from MDM using MDM ABAP API.
Step- 1. Create structure in SAP with the same name as that of MDM field code for MDM Main table.
Step-2. Create another structure in SAP having all lookup fields of MDM , fieldname in ECC must be same as that of MDM field
code.
Step-3.Create structure in SAP for individual lookup field(Single Field only)   with the same name as MDM Field code.
Step-4.
DATA: IT_QUERY            TYPE STANDARD TABLE OF MDM_QUERY, "MDM_QUERY_TABLE,
      WA_QUERY            TYPE MDM_QUERY,
      WA_CDT_TEXT         TYPE MDM_CDT_TEXT,
      IT_RESULT_SET_KEY   TYPE MDM_SEARCH_RESULT_TABLE,
      WA_RESULT_SET_KEY   TYPE MDM_SEARCH_RESULT,
      WA_STRING           TYPE STRING.
DATA:<Internal table> TYPE STANDARD TABLE OF <SAP Str Having all LOOKup Fields>
DATA: :<Internal table>TYPE STANDARD TABLE OF <SAP Str one LOOKup field>,
     <Workarea> LIKE LINE OF :<Internal table>.
*PASS LOGICAL OBJECT NAME.
V_LOG_OBJECT_NAME = 'Logical object name defined in Customization'.
Define logon language, country & region for server
WA_LANGUAGE-LANGUAGE = 'eng'.
WA_LANGUAGE-COUNTRY = 'US'.
WA_LANGUAGE-REGION = 'USA'.
TRY.
    CREATE OBJECT LR_API
      EXPORTING
        IV_LOG_OBJECT_NAME = V_LOG_OBJECT_NAME.
ENDTRY.
CONNECT to repository. Apply particular logon language info
CALL METHOD LR_API->MO_ACCESSOR->CONNECT
EXPORTING
    IS_REPOSITORY_LANGUAGE = WA_LANGUAGE.
*NOW PASS ITEM NO AND GET KEY FROM MDM.
CLEAR WA_QUERY.
WA_QUERY-PARAMETER_CODE = <MDM FIELD CODE>. "Field code
WA_QUERY-OPERATOR        = 'EQ'. "Contains
WA_QUERY-DIMENSION_TYPE = 1. "Field search
WA_QUERY-CONSTRAINT_TYPE = 8. "Text search
WA_STRING                = <Field Value>.
GET REFERENCE OF WA_STRING INTO WA_QUERY-VALUE_LOW.
APPEND WA_QUERY TO IT_QUERY.
CLEAR WA_QUERY.
*PASS ITEM NUMBER AND GET RELATED KEY FROM MDM.
TRY.
    CALL METHOD LR_API->MO_CORE_SERVICE->QUERY
      EXPORTING
        IV_OBJECT_TYPE_CODE = <MDM Main Table>
        IT_QUERY            = IT_QUERY
      IMPORTING
        ET_RESULT_SET       = IT_RESULT_SET_KEY.
CATCH CX_MDM_COMMUNICATION_FAILURE .
CATCH CX_MDM_KERNEL .
CATCH CX_MDM_NOT_SUPPORTED .
CATCH CX_MDM_USAGE_ERROR .
CATCH CX_MDM_PROVIDER .
CATCH CX_MDM_SERVER_RC_CODE .
ENDTRY.
Pass record id into keys.
LOOP AT IT_RESULT_SET_KEY INTO WA_RESULT_SET_KEY.
WA_KEYS = WA_RESULT_SET_KEY-RECORD_IDS.
ENDLOOP.
WA_RESULT_SET_DEFINITION-FIELD_NAME = <Look field name>.
APPEND WA_RESULT_SET_DEFINITION TO IT_RESULT_SET_DEFINITION.
CALL METHOD LR_API->MO_CORE_SERVICE->RETRIEVE
EXPORTING
    IV_OBJECT_TYPE_CODE      = <MDM Main Table>
    IT_RESULT_SET_DEFINITION = IT_RESULT_SET_DEFINITION
    IT_KEYS                  = WA_KEYS
IMPORTING
    ET_RESULT_SET            = IT_RESULT_SET.
LOOP AT IT_RESULT_SET INTO
        WA_RESULT_SET.
*PASS KEYS INTO MAIN TABLE TO GET Structure for FALT or Look up Table
TRY.
      CALL METHOD LR_API->MO_CORE_SERVICE->RETRIEVE_SIMPLE
        EXPORTING
          IV_OBJECT_TYPE_CODE = <MDM Main Table>
          IT_KEYS             = WA_KEYS
        IMPORTING
          ET_DDIC_STRUCTURE =<SAP Strct having all Look up fileds of MDM>
ENDTRY.
LOOP AT <SAP Strct having all Look up fileds of MDM> INTO <Work area>.
    CLEAR WA_KEYS.
    APPEND <Work area>-field name TO WA_KEYS.
    CALL METHOD LR_API->MO_CORE_SERVICE->RETRIEVE_SIMPLE
      EXPORTING
        IV_OBJECT_TYPE_CODE = <MDM Lookup table name>
        IT_KEYS             = WA_KEYS
      IMPORTING
        ET_DDIC_STRUCTURE   = <Single Structure in SAP For Lookup field>.
    READ TABLE <Single Structure in SAP For Lookup field>. INTO <Work Area> INDEX 1.
Here you can get the value of realted lookup fields associated with main table data.
ENDLOOP.
ENDLOOP.
LR_API->MO_ACCESSOR->DISCONNECT( ).
Edited by: Shyam Babu Sah on Nov 24, 2009 4:52 AM

Data from R/3 to MDM

Similar Messages

Maybe you are looking for