Full loads fails due to old requests in the PSA

[Former Member]

For updating our master data, we load the data into the PSA using an InfoPackage and from there into the InfoObjects using a DTP (running on NW2004s, SP11).

Executing the IP and DTP the first time works fine. When running these steps a second time, the DTP fails because of duplicate records. It turns out that the old request from the PSA got loaded again which lead to the duplicate records even though this data loaded successfully before and we are performing a "full load".

Can someone explain this behavior and tell me how to resolve it? When I manually delete the old requests in the PSA, the DTP runs without any errors (updating existing data in the InfoObjects).

Thank you,

Dennis

[Former Member · Accepted solution]

Don't know if things are different with 2004s, but what you describe certainly doesn't sound right. The InfoObject should know wha it has loaded form the PSA and not load it again unless you have some sort of Repair option set. I wouldn't think the Duplicate Keey setting is teh appropraite resolution. Hopefully some more folks running 2004s will post.

[Former Member]

Checking "Handle Duplicate Record Keys" on the DTP works around the problem (together with Delta loading), but we will now loose the ability to actually identify duplicate records as the system silently resolves it.

Is there a better solution?

[Former Member]

well yes since you are on >SP-10 you can avoid dupilcates using "Duplicate keys" in DTP as you mentioned,is your master data time dependent??

I guess SAP can only answer on this..abt the other solution

Fyip only.

Note 978960 - Duplicate record handling when you load master data with DTP

Hope it Helps

Chetan

@CP..

[Former Member]

I think your note describes exactly my problem. As I said, turning the "handle duplicate records" setting on works, but it only looks like a temporary solution to me. Loading master data without this setting always fails (if there is more than 1 request in the PSA).

For now, I assume this is the only way to get around it without reverting to a 3.5 update/transformation?