Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

HR data upload using LSMW

abdulazeez12
Active Contributor
0 Likes
993

Hi All

I am using LSMW to upload the HR master data. The infotype data that is loaded include the basic infotypes like 0000, 0001, 0002, 0007, 0014 and 0019 (monitoring of tasks). I am using recording method. I can record all infotypes till 0014 in single shot and the recording gets saved at the end of 0014 and gets back to LSMW step. I need 0019 infotype recording also. For this what should I do? How should I record it? Can I record this individually and attach to the above recording? Please help.

Thanks

Shakir

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
847

u can record individually but u can not attach to the existing lsmw recording ,

have a look is there any configuration setting so that it can solve ur problem or try it another way

All the best

3 REPLIES 3
Read only

Former Member
0 Likes
848

u can record individually but u can not attach to the existing lsmw recording ,

have a look is there any configuration setting so that it can solve ur problem or try it another way

All the best

Read only

0 Likes
847

Thanks for your reply.

I can record individually but I will not be knowing the personnel number which got created earlier as it will be an internal number. So, if I create a HR record with initial set of infotypes, an internal personnel numbre gets created which is not known to us, then if I want to extend that personnel number for other infotypes, how can I do that without knowing the personnel number?

I am using LSMW, recording by PA30..any clues??

Read only

0 Likes
847

Hi,

What we do during data convertion is creating each recording separately. I don't think the customer will provide you one data file with all ITs information. Providing he/she has to extract data from his/her system it is likely that you get separeted files. Pelase ensure it won't be this way.

Moreover this approach is less error-prone. Image that you are missing some configuration for one of the infotype, which is in the middle (lets say 4th in the row out of 10). Everything would load correctly till it reaches this "unlucky" infotype. Then the record has status of not loaded. The rest would be skipped and you have missing data. Now you need to start reloading from this wrong infotype to the end. But how about these already loaded? Would you delete the records to avoid duplicating?

That's why I am really encouraging you to take each IT separately approach. It is better to spend some time preparing data files then loosing your nerves when investingating what's in and what's not yet in the system, in case an error occurs.

Regards

Marcin