on 07-10-2015 9:55 AM
Hello guys,
We have been facing an error in Process chain since a few days. Let me explain briefly about this. There is a PC with APD as a process step and its target is a Direct Update DSO. We are facing an issue with message 'Duplicate data records when writing data to DataStore object <DSO_Name>'.
We have identified the duplicate records by sorting the data with the primary keys of the DSO. And have manually deleted the interim results of this APD and then deleted the duplicate records by creating a temporary APD and added one Routine step just before DSO which will delete adjacent duplicates from the result set on the basis of DSO key fields.
Though I have went through many threads but not sure how to proceed about identification for cause of duplicity of records. Usually duplication is based on primary keys of DSO. As I have not used APD before, so was wondering how do we identify the cause?
Any advice would be greatly appreciated. Thanks in advance.
Regards,
Sambit
In the APD - you can have an aggregation step which can be used to sum up the records thereby avoiding the duplicate record issue.
If you put the aggregation step before writing to the DSO in the APD - you can handle this in the APD itself and the APD will not fail.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please check the source of the APD. This is where the duplicates are getting generated. Usually the source is a BEx query - if so, please ensure that all characteristics used in the Bex query are present as Key fields of the target DSO.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Suhas,
The Sources are all Standard DSOs and not a BEx query. In this case, what can be the probable reasons?
Also can you please let me know, if I want to calculate intermediate results at each step either by 'Calculate Direct or Schedule' option to check data at each step in order to identify duplicity, then will it be a problem when the process chain will run next time? Or this can be used for testing without actually saving results in any temporary table? FYI. I am checking in production system.
Regards,
Sambit
Hi Dash,
Please try activate DSO again,
kindly update unique selection otion in DSO settings ( Unique selection ),
might may be resolve the problem.
Thanks,
Rams
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
80 | |
9 | |
9 | |
7 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.