Reg: Efficient Strategy of Data Migration

Hello all, can anybody please help me whether is there any efficient strategy for doing the data migration.
looking forward for lots of replies.........

looking forward for lots of replies......... We'll need a whole lot more information before we can offer a reply. What are you migrating from? What are you migrating to? What constraints are you working under? Is data cleansing involved? Is data ttransformation involved? etc.
You should have been around these forums long enough to know that these sorts of drive-by questions don't get sensible answers with further details, and are, in fact, likely to provoke bristly responses. After all, if you can't be bothered to invest some time in typing in the question properly why should we give up our time trying to guess what it is you want to know?
regards, APC

Similar Messages

Data Migration Reg.

Dear Experts,
What are the effective tools for Data Migration in SAP-ISU, if the data to be migrated is large, say 10lakhs. How this can be done effectively from a Legacy system.
Thanx in Advance

Hello,
Data Migration in SAP-ISU
EMIGALL :-
It is designed to upload huge mass data.
t.code:EMIGALL
the other sap supports are
LSMW
BDC

SAP HR Data Migration Strategy

Hello Guys,
I worked in Data migration in the areas like SD,MM,FI. But I am new to HR. Can anybody please give me the HR data migration stratagey like what data's (eg, Master ,transactional etc) we need to load and sequences and methods available for each type?
Thanks
Kal

Hi chakri,
Documentation we use is Data Convertion Bueprint which is simply customer's requirements accroding to what infotypes he needs, what data should be migrated and which org. elements will be imported.
Another one is Master Template which is actually prepared by us (technical team). We prepare LSMW for each infotype mentioed in former document, then we document it in this master template to provide to customer required flat files format. We prepare such becuase sometimes some filed may be fixed, some added and even are read-only so should be skipped. So this document differs a bit with previous one in regards to infotypes' used fields. Than we sent this document to our local functional team which is resposible for providing files with given format.
In first document there are also some Golden rules, which describes exact steps for one entire cycle (staring from deliveirng the file, ending with validation of loaded data for one infotype), which each involed party should follow.
The last but not least important document is what we call Loading sequence. I already described it previously. It is just the order of loading the data to infotypes which you should follow. It also contains such information as
- number of records in provided file
- number of errors, successfully loaded records
- files which we share with functional team (error logs)
- finally files which we sent as validation data (extracted from system after successful load of infotype)
Unfortunatelly I can't provide you any of them as these are company documents which are not to be distributed. Sorry I am not allowed to break this rule.
Anyhow I hope it will give you an overview of what kind of documentation you need. It is of course of your team how you organize your work and documentation.
All in all crucial thing is communication between teams, which from my experiaence sometimes fails.
One more thing:
Always remeber to give points to usefull answers, that's how the forum works. Of course it is not obligatory !
Rememebr if you get something, you appreciate it by assigning points:)
Cheers
Marcin

DATA Migration Strategy of Inventory from one SAP system to another

Hi,
We are migrating data from one sap system to another due to business split . I would like to know what are the considerations, dos and donts for inventory/stock balance migration.
Appreciate your responses on the same.
Kind regards,
Tanuja

Hi
Here are some of the links for Data migration in SAP which may be really helpful for you..Please have a look at them.
http://www.packtpub.com/article/data-migration-sap-business-one-part1
http://www.sap-press.de/download/dateien/1468/sappress_migrating_your_sap_data.pdf
http://sceisqaweb.sc.gov/documents/Agencies-Approach-and-Plan-for-Data-Conversion.pdf
Thanks.

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

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

SAP Data Migration from R/3 4.6C to ECC 6.0

Hey All
We are planning to upgrade SAP R/3 4.6C to ECC 6 in near future. I am aware that data migration is not an issue as upgrade takes care of it all. What we are concerned with is that if after a few days of upgrade when the system is functional and users have performed some quantum of transactions on it, in case if the system fails then and we have to revert back to R/3 4.6C how can we get back all the information that we processed on ECC back to R/3.
I would like to know if anyone who has performed an upgrade, had some kind of fail over strategy for such a situation. Is there some tool we can use for this purpose?
Regards
Bilal Nazir

> What we are concerned with is that if after a few days of upgrade when the system is functional and users have performed some quantum of transactions on it, in case if the system fails then and we have to revert back to R/3 4.6C how can we get back all the information that we processed on ECC back to R/3.
Simple answer: not possible.
> I would like to know if anyone who has performed an upgrade, had some kind of fail over strategy for such a situation. Is there some tool we can use for this purpose?
No - there is no tool.
Table structures change, update programs changed - it's not possible to "roll back" that to a date and re-do it on 4.6c again.
Do minimize the risk I would copy the production system to a sandbox, do the upgrade and let the (key-) users test their functionality intensively.
Markus

Data migration for Securities

Hello
I have been going the suggestions on the thread below,
Data Migration Strategy for Securities
I would like to clarify at which price do i book securities on cut off date, here is an example
my cut off date is 31/12/2009 and i have the following deals
1 . Purchase of R207 bond (04I) nominal 10million on 06/06/2009 price 98%
2. Sale of R207 bond 5million on 11/11/2009 price 97%
My balance nominal as at cut off on R207 bond is 5Million so on the 31/12/2009 i will book on TS01 5 MILLION on what price, currently on QA we booked all deals at original prices including all sales. Note that we do MTM on 04I and amortisation on 04X bonds.
Thank you in advance
Regards
Victor
Data Migration Strategy for Securities

Hi Victor,
looking into your example, it seems you have outstanding balance of 5 mio of certain bond and result (P&L) of difference between purchase (10 mio) and sales (5mio) should be booked in Y2009 and is already included in financial figures in Legacy system. If you say that you use plain Mart-to-Market Valuation for this particular type bond, so the Balance value is dependant on Market price on last date of the Y2009.
Rgds,
Renatas

Data Migration of Excise Duty payables at initial upload

Hi!
Can any one tell me, how to upload initial Excise Duty payable in data migration procedure.
for example if different excise duty payables like ED, CESS, SEC.CESS for normal goods and capital goods.
thanks in advances.
regs,
ramesh b

Hi Ramesh,
From my exposure with indian company codes these are just another GL account to be migrated since there are
no dependies you can do the mapping from legacy to the new sap system the GL account.
Just my view
regards
pbb

SAP Accelarated Data migration

Hi All,
Could someone kindly provide more info about SAP ADM. I am uanble to get any info about the same. I would like to understand as to how exactly the tool works. I have the 4 page PDF that is posted on the site but its not clear on the actual tool. Can someone kindly provide me with some document or screen shots or any more info about it. My mail id is [email protected] Could someone kindly reply at the earliest.
Thanks
Prahlad

Hi Prahlad,
Go through this hope u can understand.
With SAP Accelerated Data Migration, you can reduce migration
costs by as much as 50% and avoid interruption of business
processes. Moreover, shutting down the source system after
migration reduces system administration costs and total cost
of operations. In short, you realize the following benefits:
Significantly reduced cost and time to complete migration
projects
Accurate, cost-effective data transfer applicable for any kind
of source system
Better data quality because of preconfigured business objects
that ensure data consistency
Improved end-user productivity and acceptance thanks to
migration of historical data
Effective migration that avoids interruption of business
processes
Full support services to avoid risks and ensure the optimum
performance of your new business applications
Faster return on investment
In short, a smoother, more cost-effective migration to a new
technology solution ultimately positions your organization
to lower your total cost of ownership, maintain competitive
advantage, and pursue new business opportunities.
Expertise in Action
SAP Accelerated Data Migration applies a business objectoriented,
two-step approach that uses a neutral interface as a staging area
and predefined migration content for the conversion and upload
of data. The neutral interface enables the SAP tool to generate
predefined migration content and prevents all potential legal
issues regarding the intellectual property of any source-system
vendor. The whole data migration process from the source to
the target system consists of just two steps, as follows:
1. Data is extracted from the source system into the standard
interface as XML files.
2. Data migrates from the interface into the mySAP Business
Suite database. The migration is based on a new migration
workbench engine developed by SAP based on the SAP
NetWeaver® platform. All requirements for mapping structures
and fields and developing complex conversion rules are solved
within this engine (see Figure 1).
Once the migration is complete, business-unit end users have
access to all the legacy data in the new applications as if it had
originated there. They can continue to work on the existing
business process items in the new applications and benefit from
improved functionality.
Lifting the Limitations
Much of the cost and effort involved in classical data migrations
are generated by migration content development, as follows:
Identifying business objects for migration to properly support
the business
Defining the structure and field mapping for the relevant
business objects
Developing conversion rules for all necessary value mapping
Readily available migration content can simplify this effort.
SAP Accelerated Data Migration provides preconfigured business
content, helping you migrate it to your new system more efficiently
and rapidly. The tool allows the migration of all types of
data, independent of its current state within a business process.
This includes master and dynamic data, as well as partially
processed and historical data, to minimize data loss. Business
processes are uninterrupted and normal operation procedures
can be retained.
By providing a standard, neutral interface and reading data as an
XML file, SAP Accelerated Data Migration is applicable for any
kind of source system. Preconfigured data migration objects built
specifically for SAP applications significantly simplify the conversion
from non-SAP software data into SAP software data objects,
yielding far-reaching benefits. Besides reducing related IT costs,
you can be certain of consistency across business-object boundaries.
Through a direct insert into the database, you avoid the
performance limitations of classical data migration.
Reward points if helpful.
Thanks

Transaction Data Migration

Is there a "best practice" for transaction data conversions from a legacy system into R/3? I am in a project where I have to create a strategy for SCM transaction data (PO's, Inventory, Vendor Invoices, and so on). I would like to know the pros and cons of migrating a PO in their various stages (Open, G/R but not yet invoiced, Partial G/R). Basically a strategy to propose to my client regarding their SCM transaction data.
Thanks for your help!!!!

hi,
For uploading the GLs :-->
Use FB50 entry Dr GL a/c Credit Data migration a/c or controlling a/c
For uploading the Vendor balances : -->
Use FB60 entry Dr Data migration a/c or controlling a/c and credit Vendor a/c (individually)
For uploading the Customers balances :-->
Use FB70 entry Dr Customers a/c (individually) Cr Data migration a/c or controlling a/c
For uploading the Assets-->
AS91 -> for uploading assets in AA
OSAV --> for uploading assets in GL entry Dr Asset (invidiually) Cr Data Migration account or controlling account
You can use LSMW for uploading all these things
After uploading all, your data migration account will become zero.
For posting the transactional data use LSMW for relevant TCODES
Radha

Data migration for PO Release startegy,PO cnditions

Hi All,
is it possible to data migartion for PO release strategy, PO Conditions(pricing), PO History ?
If yes, please advice how i can achive this.
Thanks

PO Release strategy
You can not do the Migration of release strategy. You need to configure separately.It is better to follow the SAP notes to avoid inconsistancy.
For transportation of release strategy from one client to another client please follow the SAP notes
SAP Note 86900 & 45951
PO Conditions
You can do the data migration of condition records by using LSMW or BDC program. Please explain your requirement clearly
PO History
Do you want to migrate all the GR & IR? What is your requirment? Are you migrating Legacy to SAP.
Only open POs can be migrated.
Explain your requirement in detail.

Hr master data migration

Hi
I am working in a sap hr master data migration project.The client is having sap hr system in one location ,they want to migrate the datas of other 3 locations into sap hr system.(2 diffrent countries ).I have prepared a business blue print for 3 locations,now client want a Functional Design Document for 3 locations .
Can any one help me to prepare a design document.Is there any standard format ?
Payroll ,time managementand benefits are in third party system.In this project only hr master data migration

hai sony joseph,
as per the thread you need to prepare data migration strategy document for each module,if yes i will give some guidance overthat.
Regards,
Chiran Reddy.

Validation rules applied to data migration templates at import

Hi everyone!
First post here for me, so please bear with me if I missed something.
My company has just started the initial implementation of ByDesign. We come from a set of disparate and partially home-grown systems that we outgrew a few years ago.
As part of this initial phase, we are basically re-creating the data on customers, suppliers, etc. since none of our existing systems makes a good source, unfortunately. We will be using the XML templates provided by ByDesign itself to import the relevant data.
It has become clear that ByDesign applies validation rules on fields like postal codes (zip codes), states (for some countries), and other fields.
It would be really helpful if we could get access to the rules that are applied at import time, so that we can format the data correctly in advance, rather than having to play "trial and error" at import time. For example, if you import address data, the first time it finds a postal code in the Netherlands which is formatted as "1234AB", it will tell you that "there needs to a space in the 5th position, because it expects the format to be "1234 AB". At that point, you stop the import, go back to the template to fix all the Dutch postal codes, and try the import again, only to run into the next validation issue.
We work with a couple of very experienced German consultants to help us implement ByDesign, and I have put this question to them, but they are unaware of a documented set of validation rules for ByDesign. Which is why I ask the question here.
So just to be very celar on what we are looking for: the data validation/formatting rules that ByDesign enforces at the time the XML data migration templates are imported.
Any help would be appreciated!
Best regards,
Eelco

Hello Eelco,
welcome to the SAP ByDesign Community Network!
The checks performed on postal codes are country specific, and represent pretty much the information that you would find in places like e.g. the "Postal Codes" page in Wikipedia.
I recommend to start with small files of 50-100 records that are assembled of a representative set of different records, in order to collect the validation rules that need reactions based on your data in an efficient way. Only once you have caught these generic data issues, I would proceed to larger files.
Personnaly I prefer to capture such generic work items on my list, then fix the small sample file immediately by editing, and do an immediate resimulation of the entire file, so that I can drill deeper and collect more generic issues of my data sample. Only after a while when I have harvested all learnings that were in my sample file, I would then apply the collected learnings to my actual data and create a new file - still not too large, in order to use my time efficiently.
Best regards
Michael

ALE/IDOC for Data Migration of some master data

Are ALE/IDOC available for data migration of the following master data:?
1)General Tasklists in PM
2)Equipment Tasklists in PM
3)Single Cycle plans in PM
4)Strategy plans in PM
5)Equipments
6)Functional locations
7)Measuring points
8)Work Centers
9)Equipment BOMS
10)QM Info Records
11)Sampling procedure
12)Certificate Profiles QM
13)Inspection Plans
14)Material master-QM View
15)PP Recipes
16)Equipment BOM
If anyone has worked worked on ALE/IDOC for data migration, please guide

Hi Dirk ,
Thanks for your reply . Can we use matmas03 for loading. What will be the differences between these two IDOCS.

Reg: Efficient Strategy of Data Migration

Similar Messages

Maybe you are looking for