MDM Data Migration

I have a current system where I load data from one R3 environement to another by extracting the data with an R3 DCOM connector via ASP pages, dump the data to SQL for manipulation, then submit back to SAP via the DCOM.
We are upgrading and implimenting MDM. I will need to move data into MDM and was wondering if I could migrate from SQL to MDM using the same or similar method and avoid XI and the Import manager. Is there a COM connector or API availeable to gain access into MDM?
Thanks in advance.
-Motley Drew

Hi Andrew,
In general, your engineering team is correct in that XI may not be suitable for mass loading of data into MDM. Of course, this also depends on the hardware (mainly cpu and memory) and the amount of data to load.
Aside from the hardware, there are 4 main factors in mass loading that can effect the appropriateness of using XI:
1. Timeframe required for the load.
2. Number of messages (or IDOCs in this case) to be loaded.
3. Size of each message.
4. Complexity of mapping requirement.
The size of the message (in XML format) and the mapping complexity will determine the J2EE memory requirement for each message. Especially, when the message is very large and the mapping is poorly developed, the memory requirement for each message can increase in size several times.
The number of messages and the time required to load will also determine memory requirement. If a limited time is required to mass load the messages, then data will have to be loaded concurrently. The amount of concurrency will determine memory requirement. Also, keep in mind there might be other messages being processed on the system.
Hundreds of thousands of message is definitely manageable by XI. In many mass loadings, the messages are usually in the hundreds of millions. In your case, I think it would be worth a look. The mass load processing can also be used for future incremental loading through XI. So, your work will not be in vain.
If timeframe is not critical, then it is possible the messages can be processed in sequence. This can avoid the memory requirement of processing multiple messages concurrently. Provided, of course, that there is enough time.
I would propose the following:
1. Design and configure the end-to-end processing of the message for the load.
IDOC -> XI (w/mapping) -> RFC/IDOC/ABAP Proxy
2. Measure the time required to execute 1 message. Do this several times; the 1st message will take longer due to initialization.
3. Calculate if this will meet your timeframe if processed sequentially. If so, then the problem is solved, and you can set up the message processing as EOIO (exactly once in order).
4. If not, then process the messages concurrently by sending as many as you can at one time. Make sure the J2EE, ABAP work dialog processes, XI queues, etc. are configured properly. Improperly tuned XI system can negatively affect performance. The XI basis person should be able to do this.
More likely, concurrent processing will be required. If a timeframe can be arranged to allocate XI exclusively for mass loading and the XI system is properly tuned, I think loading hundreds of thousands of messages will not be a problem.
The QuickSizer can help to give an "estimate" of the CPU and memory requirement of the hardware.
Regards,
Bill

Similar Messages

Data Migration techniques

Hi Experts,
I want to know about data migration techniques and how we can best use MDM while migrating old version of R/3 to new version of R/3....
I have implemented SAP MDM in cases where we have number of SAP R/3 instances across different region and we were taking data from different R/3 one by one and doing data stan'zation,consolidation, Harmonization and all... I am not talking about all this...
There was a good explanation from Markus Ganser about Duplicate data and identical data... I know all this..but my question is when I have only one SAP R/3 and I still want to implement MDM solution while migrating my old R/3 instance to new one, How can I proceed in this scenario? What is the data migration technique...
I know the common answer will be to use MDM as a middle ware..take Master data from old instance and after consolidation, send it back to new instance and at the same time send tran'data directly to new version... But is this worth doing this? Is there any other approach?
If there is any document on this or any one have idea about data migration techniques while implementing MDM solution than send me documents on [email protected].......
In short, I am looking for below 3 points while doing migration along with SAP MDM
Data Migration techniques
Prerequisites
Methodology in this kind of scenario
Step by step procedure
cheers,
R.n

hi..
here i am sending u the link for complete Data Migration Life Cycle
<a href="http://www.redwoodsystems.co.uk/dataMWhitePaper.html#links">http://www.redwoodsystems.co.uk/dataMWhitePaper.html#links</a>
hope it might be of any use to u
thank you & reward points if useful
Message was edited by:
Dasari Narendra

Data Migration from R3 to new ECC System

Hello,
We are doing a fresh implementation for SAP MDM. Currently we have 3 SAP R/3 systems and 1 non-R3 system (BPCS system). One of the project goals is to do data migration from all these 4 systems into a new SAP ECC system and to MDM for Vendor Master, Customer Master and Material Master. My manager says that we need Business Objects tool to Migrate these data. But, my question is that is it not possible to achive this through XI/PI itself ? Can anyone let me know the entire process in XI/PI as to how do I receive the Idocs from R/3, convert into XML and then send it to the new ECC system in Idoc format ?
Thks & Rgds,
Hema

Hi Gandhi,
You have SAP MDM, BPC and R/3 systems in your landscape, when you are migrating data to new ECC system, what is the role of mdm, did you moving the same data to MDM to avoid duplicate/redundant data??is there any data migration from R/3 to MDM(any integration required)or MDM to R/3,
You have to develop different interfaces to transfer data from MDM to ECC, BPC to ECC.definelty you required one middleware, the option definitely SAP PI. it offers very easy of integration between MDM and R/3 system, you can use MDM-PI adapter to connect to directly MDM syndicator file port from there you can pull the XML file and convert it in to IDoc format use Receiver IDoc adapter in PI, the same way we can integrate BPC system with R/3.
Search in sdn, there are some scenarios integration of R/3 and MDM using PI, refer those links, if still you have any doubts let me know,
Regards,
Raj

MDM Data Export

Hi All,
I am working on MDM 7.1 SP07. I am looking for a solution how we can transport Datas from QAS to PRD Server.
Does there any options similar like Export/Import Repository schema for Data.
Please help
Regards
Ponnusamy

Hi Ponnusamy,
1. Archive and Unarchive is the data migration procedure available between any servers. If u are really concerned about doing this for the first time, you can try doing it between Sandbox and Dev servers if you have them in the landscape. If not, try doing it between two different, unimportant repositories in lower level envronments.
2. As Shamir rightly said, u can refer to the Console reference guide for Archive procedure. The number of repositories can be depending upon your DB size. However the less the number of repositories more will be the performance. Also the number of records in the repositories and the number of tables in the repository plays a vital role in the performance.
Post us your further queries:)
Kind Regards,
Thamizharasi N

Challenges - Data Migration

Hi, could someone tell me the challenges that are commonly encountered during data migration?

Hi Ananth,
We can foresee numerous challenges in Data Migration. Few of the most important ones as below:
1) Ensure that we download/extract precise data from Source system( eg.ECC). We must configure fool proof extract mechanism to download it to right format.
2) Precise Import maps -
a) Lookup tables - Look up tables have to be refreshed with live data from source systems with valid remote keys. This is required for making auto value mapping happen during import.
b) Main table import map - Accurate import map for main table ;identify the right matching field 9 primary key)
c) Maps for Qualified /Hierarchy tables - Import maps Involves compound fields and field partioning, Right display fields to be decided and configured accordingy.
Ensuring table joins, splitting, partitioning are done accurately is very important.
3) Volume of imports - Bulk imports hinder import performance. Perform batch imports of smaller chunk size to speed up the process.
4) Data validation - Formulating a process/template to validate data in MDM with source system data. This is a complex process when validation is required for every field in data model.
Regards,
Vinay M.S

What are the corresponding Data Types of some MDM Data Types

Hi Guys,
The MDM ABAP API involves creation of a DDIC structure in SRM. This structure should have the same fields with the MDM table fields. We would like to ask the corresponding ABAP Data Types for the following MDM Data Types.
MDM SRM
1. Look up (flat)
2. Look up (taxonomy)
3. Look up (heirarchy)
4. Look up (qualified flat look up)
Any significant inputs on this?
Thanks and regards,
RE

Hi,
Refer the below link. This is from the MDM Reference guide and contains the sample source code as well for almost all the things like creating repository, creating tables and fields etc. It would be helpful to you.
http://help.sap.com/saphelp_mdm550/helpdata/en/47/5fd3f7cbd75518e10000000a421138/frameset.htm
Regards,
Jitesh Talreja

Can not Upload PDF in MDM data repository

Hi, expert,
when I upload the PDF in MDM data manager, the system error log is :
Unable to open Adobe Acrobat.
See your administrator about installing Adobe Acrobat.
But, when I upload the image, the status is success..
I do not know if it is Adobe Acrobat installing problem or I miss some configuration or it can not upload the PDF into MDM repository..
Your help would be really appreciated.
thanks & Best Regards,

Hi,
Can you open the PDF without any error? Is Adobe Acrobat installed on the server where the repository is loaded?
Regards,
jason

Fixed Asset Data Migration Wizard

Hi All,
I tried to use Fixed Asset Data Migration Wizard to migration my fixed asset data from 8.82 to 9 in the development server. The server only accessible by myself.
When I start the migration run, system prompt me " To Continue with the fixed asset data migration, you must be the only user logged on to this company data".
In fact I'm the only user in the company data and system not allow me to execute the migration.
What are the causes that system recognise there is another user in the system?
Please advise.
Thanks in advance.
Best Regards,
Foong Yee

Hi,
If you're using SQL Server, try Detach (close existing connections) and re-Attach the database again then re-login and try executing again the wizard.
Regards,
Donald

Data Migration for Open Purchase Order

Hi, All,
Is there anyone know how to Count the volume for Open Purchase Order. What's the normal strategy for the Data Migration and Cut-over stage?
My client want to know how many Open Purchase Order in the legacy system and then determine manual or automatic data migration. If manual, how to do? If automatic, how to do? Because all materials and vendors, plants are different number. How to track? How to find out to match between new and old?
Thank you very much

JC,
Sounds a bit early to be making decisions about the realization phase. It doesn't sound like you have finished the Blueprinting phase yet, much less the testing phase.
Anyhow, in my experience I typically use LSMW (Legacy system migration workbench) to load MM master data (material masters), Inventory (WIP, RM, FG, etc) Purchasing Master data (Vendors, Purchase Info Records, Source Lists, Quota Arrangements), and Purchasing transactional documents (POs, PurReqs, Scheduling Agreements, etc). Depending on the complexity and volume of data, it may be necessary to write custom programs to load the data. You will find this out during your requirements gathering.
It is uncommon but possible to load all of these data manually. I have never run across a client that wants to pay a consultant's hourly rate to sit at a terminal to peck away loading master data, so if the client intends to have his own users enter the data manually, the project manager should make provision that there will be qualified TRAINED client employees available for this data entry. I did help with a portion of a conversion once manually; of Sales Credits, but there were only about 30 SD docs to load. I did this the evening before go-live day, while I was waiting for some of my LSMW projects to complete in the background.
A good opportunity to 'practice' your data loads is right after you have completed your development and customization, and you have gotten the approval from the client to proceed from the pilot build to the full test environment. Once you have moved your workbench and customization into the client's test environment, but before integration testing, you can mass load all, or a substantial portion of your conversion data into the qual system. You can treat it like a dry run for go-live, and fine tune your processes, as well as your LSMW projects.
Yes, it is good practice to generate comparisons between legacy and SAP even if the client doesn't ask for it. For Purchase orders on the SAP side, you could use any of the standard SAP Purchasing reports, such as ME2W, ME2M, ME2C, ME2L, ME2N. If these reports do not meet the requirements of the client, you could write a query to display the loaded data, or have an ABAPer write a custom report.
You didn't ask, but you should also do comparisons of ALL loaded data - including master data.
It sounds like you are implying that the client wants YOU to extract the legacy data. For an SAP consultant, this is not very realistic (unless the legacy system is another SAP system). Most of us do not understand the workings of the myriad legacy systems. The client is usually expected to produce one or more legacy system technical experts for you to liase with. You normally negotiate with the technical expert about every facet of of the data migration. In addition, you will liase with business users, who will help you and the implementation team to logically validate that the final solution (turnkey SAP production system, fully loaded with data) will meet the client's business needs.
Finally, you mentioned how do you track the mapping of master data between legacy and SAP. There are many ways to do this. I normally try to get the legacy person do the conversion on his end, eg, when he gives you the load file, you would like to have already translated the master data and inserted the SAP relevant values into the file. If this is not possible, I usually use MS Access databases to maintain a master map, and I perform the mapping on a PC. If your data package is small, you can probably get by using MS Excel or similar.
Good Luck,
DB49

Data migration of open production order

Hello SAP gurus,
Please advise me about the steps that should be followed for data migration of open production order from legacy to SAP.
Regards,
Anand

Hello SAP gurus,
Please advise me about the steps that should be followed for data migration of open production order from legacy to SAP.
Regards,
Anand

Data migration

Dear all my friends,
please help to share me about data migration before go-live FI system.
i plan to migrate GL acct balance, AP/AR open item and last 3 months historical data.
please help to show me : how should i do ?
thanks !

1. Normal GL Accounts: In this case line items are not required and totals are to be updated in SAP. This can be done using GL fast entry if the number is not too high.
2. Open Item Managed GL Accounts: All the open line items are required to be uploaded in SAP from Legacy in order to clear them. Hence, a LSMW / BDC program has to be developed to upload the line items.
BAPI_ACC_DOCUMENT_POST - for GL/AP/AR
BAPI_ACC_INVOICE_RECEIPT_POST - for AP
BAPI_ACC_GL_POSTING_POST - for GL
GL Balance
F-02 or RFBIBL00 or BAPI
Dr GL a/c Credit Data migration Account or Clearing Account
3. Customer & Vendor Open Items: All open line items in Customer and Vendor Accounts have to be brought in into SAP. For this also a LSMW / BDC program needs to be developed and upload the line items.
Vendor Balances
F-02 or RFBIBL00 or BAPI
Credit Vendor a/c (individually) and Dr Data migration Account or Clearing Account
Customer balances
F-02 or RFBIBL00 or BAPI
Dr Customers a/c (individually) and Dr Data migration Account or Clearing Account
4. Asset Accounting: In case asset accounting is implemented the individual balances of each asset (Gross Value and Accumulated Depreciation) have to be uploaded using transaction AS91. For this also you need to develop a LSMW / BDC program. Further, you also need to update the GL Accounts related to Asset Accounts with totals for each asset class T.Code OASV.
For uploading the Assets
AS91 -> for uploading assets in AA
OSAV --> for uploading assets in GL entry Dr Asset (individually) Cr Data migration Account or Clearing Account
You can use LSMW for uploading all these things
After uploading all, your data migration account will become zero

Confuse on PR & PO data migration approach new to MM module

Hi All,
I'm pretty confuse with the PO data migration approach when it comes to PO is GR or partial GR or GR&IR. I'm hoping that someone can enlighten me. i understand that we typically don't migrate PO when it is GR & IR, FI team usually will bring over to the new system as an vendor open item in AP. How about the PR or PO which have gone through or half release strategy? What is the follow up process? I have created a criteria table below. How Could someone point me in the right direction? Thanks in advance.
PR
Criteria
Data migration required
Notes
Open and Released
Y
Open and not Released
Y
Flag for Deletion
N
Flag for Block
Y
PO
Criteria
Data migration required
Notes
Open and Released
Y
Open and not Released
Y
GR but no IR
GR & IR
N
AP will bring over as open item
Flag for Deletion
N
Flag for Block
Y
Partial
Y
For partial GR to recreate PO only with missing GR quantity
Regards,
John

Hi John,
The approach that i have followed recently is that we have considered PO as the base document and converted other documents based on the PO condition. This means you first need to see if the PO is to be converted or not. Then you can proceed to convert the related documents like PR, Agreement, Info record, Source list, etc.
Also open qty for PO should be considered for Material and Service line items both.
Once a GR/SES is created, it gets updated in the PO history table EKBE with its related transaction/event type.i.e. EKBE-VGABE = 1 for GR and 9 for SES. Quantity and value also gets updated in case of material and services. You can compare this consumed quantities with PO quantity.
Please see below from SCN and let me know if you need more info on PR or PO conversion.
Purchase Requisition Conversion Strategy
Thanks,
Akash

Data Migration of FI-CA Cleared Items

Hi,
Currently I am working on a Data Migration project to migrate data from our FI-CA module on ERP 4.7 to ECC 6.0.
THere has been a request from the business to migrate historical data (e.g. Cleared items).
Is there a SAP recommended approach or tools to load this data into the target environment?
Currently all documentation around SAP data migrations talks about stategies for open item data migration however I have seen nothing arouund migrating historical financial data.
Is this because it is not recommended or technically impossible?
Regards
Adam Gunn

That BAPI is used typically for straight out vanilla GL, AR, AP postings, however you still have to create the other side of the entry and then clear it.
I need to be able to migrate full history, which means from an FI-CA viewpoint:
1. Migrate FI-CA posting of liability against BP/contract account.
2. Migrate associated payments.
3. And then clearing documents.
Basically the requirement is to represent the historical data in the new system as if it was posted and matched off.
Is there a technical way to do this?
OR,
Do you migrate the FI-CA liabilties, then the associated payments and then run clearing on the target system?
I suspect this is almost an impossible data migration requirement as development of the extraction and load process would be extremely complex and testing would take months to cover all posting scenarios in FI-CA. However, I would be interested if anyone has attempted to do this before.
Adam

Data Migration from SAP r/3 to SAP R/3

Hi all,
What is the best method to migrate data from one verison of SAP to another verison of SAP ECC say from SAP 3.1 to SAP ECC 6.0?
This is for all SAP modules including sd, mm, pp, fi, co master and transaction data. I know there are number of technologies to load the data such as LSMW, IDOC, ALE, DI, etc but what is the best way to extract all data feeds to be loaded back into SAP.
Thanks in advace.

Take a look to the following link, may be useful for you
SAP NetWeaver - Data Migration (CA-DMI) [original link is broken]
if helpful reward points are appreciated

Data migration from legacy system to SAP

hi all,
could you please post some docs on migration from legacy system to SAP system., also the problems faced while migration and best practices in data migration
regards
sridharan

Hi ,
I require few details from you.
1. What ETL tool you are using, If Informatica, it already have PowerConnect to connect to SAP. So you can create source and Target Structure and also you can use RFC's to send data to R/3. Else, for other ETL tools, can you prepare RFC's or any other way to send data to R/3. let me know the tool.
2. Does R/3 contains the master data tables? If yes, then try to use LSMW for Mass upload of data to tables.
If your client don't want to use either of these options please elaborate, what is the case.
Regards
Aashish Sinha

MDM Data Migration

Similar Messages

Maybe you are looking for