on ‎2010 Aug 31 10:34 AM
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!
Request clarification before answering.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi again,
In my honest opinion, you'll probably want to create a set of SAP Query reports for auditing your master data. SAP Query is a really indispensable tool for an analyst. Danielle Larocca has a pretty good book on the subject titled SAP Query Reporting that you may want to check out. There's also some useful guides available here on SDN. Ad Hoc query might work for you as well, just keep in mind it's a little simpler and definitely less robust than SAP Query reporting. Otherwise, you're going to be stuck pulling your data from infotype tables manually and dumping it into Excel for vlookups and comparisons.
I hope this helps - sorry there are no silver bullets here.
-Matthew
To "migrate data", a template is usually built. For example, the personal information on an employee exists in your Legacy System, and that information will need to migrate to IT0002, IT0006, IT0009, etc...
Check it the employee's name, address, birth date, sex, marital status, bank info, etc... was correctly transfered from your Legacy System to SAP.
Then do the same about all the information you had in your old system (Union affiliation, e-mail address, benefits, pay scale/level, etc...) . Did you plan to transfer it and has it been transfered correctly?
There may also be some information that was not in your Legacy System but that was transfered in SAP through "conversion spreadsheets". What new information did you plan to transfer into SAP and has it been transfered correctly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Rémi,
First of all thank you for the response. Few additional questions though: I was under the impression that "migration template" was mostly used to categorize all the steps that are needed for data migration, but it does not really explain what actions should be taken to actually test transferred data.
I think in my case, most of the data that will be migrated is personnel data, so if there are other ways to test the correctness of migration some other way then reports, please let me know.
Thank you!
lmsw - is an sap legacy migration system? workbench.
you configure it based on the input files you are going to provide. you provide the files, it loads the data, it gives you reporting per record as to what happen per the load.
you can easily find plenty of materials searching LMSW in google or on this forum.
best regards
michael
We used a custom program to transfer the data from the Legacy Systems into SAP's Conversion Spreadsheets (included in our Accelerated HR Data Transfer Toolbox).
The information in these spreadsheets were compared with the Legacy System's information and with SAP's specifications. In other words, was the information required from the Legacy System transfered to the appropriate spreadsheet and in the appropriate format. Sometimes, additional information is added to the spreadsheets, and the spreadsheets are usually transfered into text files for the upload program.
For Unit Tests, Integration Tests, Parallel Tests and the "Go-Live", these Conversion Spreadsheets were uploaded into SAP using program ZHRDXPA0. A reconcilliation was then done between the data in the uploaded spreadsheets and the information contained in SAP to make sure everything was transferred correctly.
As mentioned by Michael, the LSMW can also be used to upload the information into SAP, but the process is basically the same: Dowload from Legacy to Spreadsheet, Check and Complete Spreadsheet, Upload Spreadsheet into SAP, Reconcile Data between SAP and Spreadsheet.
| User | Count |
|---|---|
| 57 | |
| 29 | |
| 21 | |
| 11 | |
| 4 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.