Data Migration Validation Approach

Dear all,
I am rather new to the SAP world so some patience and clear explanations might be required. Currently I have to find some approaches to validate migrated data (like for instance take random employee and check whether data is moved correctly), but in our company we have no common practices for that kind of things. Can I ask you to help me out and give me some tips (or maybe describe some practices from your experience) on different approaches to validate migrated data.
Thank you all in advance!

Hi,
There are a couple of resources you can use to audit employee master data. The quickest action for you is probably to use SAP standard reports, rather than using SAP Query / Ad Hoc query. You certainly could use either of the reporting tools but if you're really new to SAP and are working on a deadline to audit your master data, I think the learning curve might be too high.
Some helpful standard reports are:
PC00_M02_LINF0 - Robust infotype overview per employee, but requires some drill-down.
S_AHR_61016360 - You might need to play with the selection screen a bit but this can be useful. Canned Ad Hoc Query report.
You may have to resort to looking up your employees at the infotype table level using transaction SE16. This takes longer but it's also a good exercise for some one who is just starting out in SAP HR.
Honestly, if you're looking to perform an audit of multiple employees at once, then SAP Query or Ad Hoc Query are much more robust tools. If you're going to be working with master data in SAP beyond the go-live, then it would benefit you greatly to take the time to learn them both. Ad Hoc Query is a simpler but less powerful reporting tool that is useful if you want to slap together a data overview very quickly. Unfortunately I don't know of a good resource for Ad Hoc query off the top of my head. [Here|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/10eab7af-0e54-2c10-28a5-87b47adbe1a5?quicklink=index&overridelayout=true] is a fairly useful tutorial to SAP Query, which is a more robust - and more complicated - reporting tool.
I hope this helps!
-Matthew

Similar Messages

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 approach for Scheduling Agreements

Gurus,
Can anyone provide guidance on the data migration approach for Scheduling Agreements? How can we migrate the open delivery schedules and the respective cumulative quantities? The document type being used is "LZ".
Can correction deliveries (Doc type - LFKO) be used update the initial cumulative quantities?
Any help in this regard is higly appreciated.
Regards,
Gajendra

Hi Zenith
You might find useful information here: IS-U data export (extraction) for EMIGALL.
I've done numerous IS-U migrations in the last 10+ years, but never one from IS-U to IS-U.
One main questions to start with: Are the two systems on the same release level?
If they are not and it would be too much effort to get them onto the same release level I would think creating your own extract programs and using the Migration workbench (EMIGALL) is the way to go.
If they are on the same level, there might possible other ways to do it, dependent on the differences between the two systems (mainly around customising). Assuming there are significant differences - otherwise why would you bother migrating? - there's the high probability that using EMIGALL is the way to go as well.
Yep
Jürgen

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

URGENT - Data Migration - From Oracle BPEL 10.1.2.0 to current version

Anyone having any idea on the data migration appraoach to be followed from Oracle BPEL 10.1.2.0 to 10.1.3.3
If it supported?
I understand process migration is possible (I found it out in installation guide for 10.1.3.1) but there are no documents available for data migration approach (Or I am not able to get hold of any).
Regards
Ashutosh

To workaround the problem, from the DataModel project, right-clicked Project Properties, selected Business Components: Options, unchecked Validate Objects during Compile, and the project compiled successfuly, yet the issue is to have my xml files valid.

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

DMS Data Migration-Help required

Hi,
I don't have enough knowledge on DMS Data migration.
In our recent Implementation, we are implementing SAP DMS.
Our client has more legacy data which is in their server. So we have to upload all the data's into SAP DMS.
I gone through few SCN threads and understand that LSMW & BDC will be used for Data migration.
Which is the best method for Data migration?
We are having 50+ document types and it has different processes (status network), Classification & few Object links.
Please advice me and provide me some examples to upload legacy data in DMS.
Thanks in Advance,
Ravi

Hi Ravi,
There are few approach discussed in the thread https://scn.sap.com/thread/2119796
You may check feasibility on these approaches for your scenario.
We are having 50+ document types and it has different processes (status network), Classification & few Object links.
Creating these configurations into SAP is one time and should not be a problem.
I gone through few SCN threads and understand that LSMW & BDC will be used for Data migration.
Which is the best method for Data migration?
How much volume of data do you have in legacy system ?
Have a thought on whether do you really need to migrate all these data into SAP DMS ???
OR
You can configure the DMS system and start fresh leaving the document in legacy system as it is.
Hope this helps.
Regards,
Deepak Kori

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

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

Data Migration (FI/CO)

Hi,
Kindly let me know the process for data migration from legacy to SAP system.
The client wants us to migrate not only the open items but also all the line items (since there are not much transactions as the company was newly incorporated).
We are following the BDC approach, I need to know if there is a debit item then which account is to be credited.
If any document please send to my email [email protected]
Points would be awarded.
Thanks
SS

Hi SS,
I would recommend you to check the LSMW. You can achieve a lot with this tool to convert master data and transaction. Check also the modules you have. For example the asset module has special functions for conversion purpose.
Greetings,
S

Data Migration program for opportunity

Hi SAP Experts,
Please can one help with the Data Migration program for opportunity.
I want to know the approach.
These are few mandatory filed
1. Opportunity Name
2. Account
3. Contact
4. Opportunity Owner
5. Total Estimate/Curr* value_ currency
6. Project start date ---
7. Stage
8. Probability
9. Status
10. Product with Item category ZSOL
11. Service
12. Service Offering
Regards,
Jaya

Hi,
As suggested by Kai you can use LSMW. This will be better option as it is very easy to use and you can also write routines while mapping the fields. You can also use IDOCs for importing data from Legacy system.
If you want to write a report then you can use BAPI_BUSPROCESSND_CREATEMULTI. Please refer to the documentation of this BAPI. This BAPI internally calls CRM_ORDER_MAINTAIN. Do not forget to call BAPI_BUSPROCESSND_SAVE to commit your data.
Regards,
Sandeep

Data migration for re-organization

hello,
I have to delimit the existing org structure in SAP system.
the steps are as follows:
1) create new org structure
2) create new org structure to cost center mapping
3) delimit the old org and positions
4) assign new org to positions
5) assign cost center to some positions
Please can some one tell me which is the easiest transaction to do data migration for the step 3.
Regards
Meghana

hi,
You can delimit the positions llike,
Plan Version    HI Plan version
Object Type     S Position
Object ID       50018201     Director - Enterprise Bus
Object abbr.    S 50018201
Infotype        1001 Relationships
Subtype
Planning status 1    Active
Validity        06/11/2008 to     12/31/9999
Data sample
Then there is option called Delimit (shift+F1) where you can demilit the dates.
Try this.
Reward me if helps,
Thanks,
Vasu.
Edited by: VASU MALYAVANTHAM on Jun 12, 2008 1:05 AM

Upcoming SAP Best Practices Data Migration Training - Chicago

YOU ARE INVITED TO ATTEND HANDS-ON TRAINING
SAP America, Downers Grove in Chicago, IL:
November 3 u2013 5, 2010     `
Installation and Deployment of SAP Best Practices for Data Migration & SAP BusinessObjects Data Services
Install and learn how to use the latest SAP Best Practices for Data Migration package. This new package combines the familiar IDoc technology together with the SAP BusinessObjects (SBOP) Data Services to load your customeru2019s legacy data to SAP ERP and SAP CRM (New!).
Agenda
At the end of this unique hands-on session, participants will depart with the SBOP Data Services and SAP Best Practices for Data Migration installed on their own laptops. The three-day training course will cover all aspects of the data migration package including:
1.     Offering Overview u2013 Introduction to the new SAP Best Practices for Data Migration package and data migration content designed for SAP BAiO / SAP ERP and SAP CRM
2.     Data Services fundamentals u2013 Architecture, source and target metadata definition. Process of creating batch Jobs, validating, tracing, debugging, and data assessment.
3.     Installation and configuration of the SBOP Data Servicesu2013 Installation and deployment of the Data Services and content from SAP Best Practices. Configuration of your target SAP environment and deploying the Migration Services application.
4.     Customer Master example u2013 Demonstrations and hands-on exercises on migrating an object from a legacy source application through to the target SAP application.
5.     Overview of Data Quality within the Data Migration process A demonstration of the Data Quality functionality available to partners using the full Data Services toolset as an extension to the Data Services license.
Logistics & How to Register
Nov. 3 u2013 5: SAP America, Downers Grove, IL
                 Wednesday 10AM u2013 5PM
                 Thursday 9AM u2013 5PM
                 Friday 8AM u2013 3PM
                 Address:
                 SAP America u2013Buckingham Room
                 3010 Highland Parkway
                 Downers Grove, IL USA 60515
Partner Requirements: All participants must bring their own laptop to install SAP Business Objects Data Services on it. Please see attached laptop specifications and ensure your laptop meets these requirements.
Cost: Partner registration is free of charge
Who should attend: Partner team members responsible for customer data migration activities, or for delivery of implementation tools for SAP Business All-in-One solutions. Ideal candidates are:
u2022         Data Migration consultant and IDoc experts involved in data migration and integration projects
u2022         Functional experts that perform mapping activities for data migration
u2022         ABAP developers who write load programs for data migration
Trainers
Oren Shatil u2013 SAP Business All-in-One Development
Frank Densborn u2013 SAP Business All-in-One Development
To register please use the hyperlink below.
http://service.sap.com/~sapidb/011000358700000917382010E

Hello,
The link does not work. This training is still available ?
Regards,
Romuald

Upcoming SAP Best Practices Data Migration Training - Berlin

YOU ARE INVITED TO ATTEND HANDS-ON TRAINING
Berlin, Germany: October 06 u2013 08, 2010     `
Installation and Deployment of SAP Best Practices for Data Migration & SAP BusinessObjects Data Integrator
Install and learn how to use the latest SAP Best Practices for Data Migration package. This new package combines the familiar IDoc technology together with the SAP BusinessObjects (SBOP) Data Integrator to load your customeru2019s legacy data to SAP ERP and SAP CRM (New!).
Agenda
At the end of this unique hands-on session, participants will depart with the SBOP Data Integrator and SAP Best Practices for Data Migration installed on their own laptops. The three-day training course will cover all aspects of the data migration package including:
1.     Offering Overview u2013 Introduction to the new SAP Best Practices for Data Migration package and data migration content designed for SAP BAiO / SAP ERP and SAP CRM
2.     Data Integrator fundamentals u2013 Architecture, source and target metadata definition. Process of creating batch Jobs, validating, tracing, debugging, and data assessment.
3.     Installation and configuration of the SBOP Data Integratoru2013 Installation and deployment of the Data Integrator and content from SAP Best Practices. Configuration of your target SAP environment and deploying the Migration Services application.
4.     Customer Master example u2013 Demonstrations and hands-on exercises on migrating an object from a legacy source application through to the target SAP application.
Logistics & How to Register
October 06 u2013 08: Berlin, Germany
                 Wednesday 10AM u2013 5PM
                 Thursday 9AM u2013 5PM
                 Friday 9AM u2013 4PM
                 SAP Deutschland AG & Co. KG
                 Rosenthaler Strasse 30
                 D-10178 Berlin, Germany
                 Training room S5 (1st floor)
Partner Requirements: All participants must bring their own laptop to install SAP Business Objects Data Integrator on it. Please see attached laptop specifications and ensure your laptop meets these requirements.
Cost: Partner registration is free of charge
Who should attend: Partner team members responsible for customer data migration activities, or for delivery of implementation tools for SAP Business All-in-One solutions. Ideal candidates are:
u2022         Data Migration consultant and IDoc experts involved in data migration and integration projects
u2022         Functional experts that perform mapping activities for data migration
u2022         ABAP developers who write load programs for data migration
Trainers
Oren Shatil u2013 SAP Business All-in-One Development
Frank Densborn u2013 SAP Business All-in-One Development
To register please follow the hyperlink below
http://intranet.sap.com/~sapidb/011000358700000940832010E

Hello,
The link does not work. This training is still available ?
Regards,
Romuald

Data Migration of Contracts with periodic billing and revenue recognition

Hello Experts,
I am trying to develop a legacy data migration plan for Contracts with periodic billing plan and revenue recognition.
Example of the scenario is given below:
Customer signed a contract for one year starting 01/01/2009.
Customer is billed quartely, billed in advance.
SAP going live on 04/01/2009
Customer is billed for 3 months and also for initial set up fees.
Revenue recognition is done monthly.
We have to migrate this contract to SAP.
Billing document posting may be necessay as it affects revenue recognition which spans across the total contract period.
Any ideas how to do this?
Thanks A Lot
Anil
Edited by: Anil Jose on Sep 17, 2008 9:38 PM

Hi Anil
How did you manage this? We also had the same problem in one of our contracts and what we did was that we copied the contracts from the legacy with the full value. That is suppose SAP went live on 1st April, 2009 and the contract was created on 1st January 2009 for a value of suppose 100 USD, with the first billing being done on 1st Jan for 33.33 USD for 4 months. We first created the contract with a validity from 1st Jan 2009 in the new system. We billed it with a billing type that we created that did not actually create new accounting entries as the accounting entries had already been created in the legacy system. In the new system then we recognised the revenue till the go live, so that the actual value remaining of the contract reduced. Then we started the billing plan of the contract from 1st of April 2009 for the remaining amount. So next invoice was created on 1st april for 33.33 USD. Can you share your solution.
Regards
Indranill

Data Migration Validation Approach

Similar Messages

Maybe you are looking for