Skip to Content
author's profile photo Former Member
Former Member

Reason for duplicity of records in Direct Update DSO

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.



Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Posted on Jul 10, 2015 at 09:08 AM

    Hi Dash,

    Please try activate DSO again,

    kindly update unique selection otion in DSO settings ( Unique selection ),

    might may be resolve the problem.



    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Ram,

      Thanks for the reply.

      DSO is activated the last day but still we faced the same issue. And this is a direct update DSO, so there is no option for unique selection in the settings.



  • Posted on Jul 10, 2015 at 10:39 AM

    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.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jul 12, 2015 at 03:27 AM

    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.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.