Duplicate records with HR

[Former Member]

I'm loading HR master data and get a lot of errors because of overlapping time-dependant data. This happens a lot with the Org Structure and Person. I found an OSS for Org struc that seems to have helped, but I've found no fix for Person. I'm trying to understand whether its because the customer has used time types in HR incorrectly or whether its something else.

[Former Member · Accepted solution]

Hi Anthony,

did you try loading to 'only PSA' in your infopackage and after successful load schedule the next package for updating the infoobject from PSA. We had a similar problem and this solved it.

regards

Siggi

[Former Member · Accepted solution]

Siggi, yes, I did try loading to the PSA then the object (I also tried skipping the PSA) not so much because of the duplicates problem but more because I also had some timeouts in R3 in SM58. Effectively I think doing that did also help with the duplicates. It would be interesting to know why that makes a difference.

I also used the option to ignore double data records in the infopackage, but, as far as I'm aware, this is not apt for HR data.

Thanks.

[Former Member]

Hello Anthony,

overlapping time-dependant data in HR:

regarding my experience there are two main causes:

- incorrect data in the SAP R/3

HR infotypes and HRP-tables due to migration,

interfaces

- programming errors in customer exit of extraction

or customer data sources

Please check your datasources (business content or modification), user exit (ZXRSAU02 in SAP R/3 HR) and

of course the data in the SAP R/3 HR system.

In PSA you can identify the objects (pernr, orgunit..) which causes the problem.

Best regards

Lothar

[Former Member]

Lothar, I'm working in an environment that has never had any BW before: we just installed BW, activated the content and ran the loads. So I think your first explanation (incorrect data) is the right one. But before telling the customer to fix it, I want to make sure that I didn't miss setting some parameters somewhere.

By the sounds of it, I didn't...

Thanks for your help!

[Former Member]

To identify the errors, why not change the error handling on the infopackage to allow valid records but capture the error records in the PSA. Should make it a little easier to analyse the bad data.

Regards,

Pete