cancel
Showing results for 
Search instead for 
Did you mean: 

ODATA data is duplicating values in BODS

vinaya_hg
Participant
0 Kudos

Hi experts ,

I was trying to extract ODATA service data from ECC and load it to HANA table using BODS .The data is getting duplicated at both source as well as destination i.e from entitySet table to Hana table but If I select distinct rows in the query transform I am able to see unique record in the query transform whereas in target again it gets duplicated. Please find the attached screenshot.

Please help me where I am going wrong

Thanks in advance.

Regards,

Vinaya

.

Accepted Solutions (1)

Accepted Solutions (1)

former_member466847
Active Participant
0 Kudos

Have you been able to confirm if there are duplicate records from the source ECC table?
Can you also confirm if the Degree of Parrelisim of the dataflow is set to 1, to limit the process threads to 1 instead of the default 2?

vinaya_hg
Participant
0 Kudos
  1. No in ECC there is no duplicate records.

  2. I changed it to 1 it was default .

But still it duplicates.

Regards,

Vinaya

former_member466847
Active Participant
0 Kudos

Thank you for confirming the source did not have duplicates.
You change the default Degree of Parellisim from the Dataflow properties as needed, or to effect the whole job design you would change it in the DSConfig.txt Global_DOP switch.

After you changed the DOP, did you execute the job again and what were the results?

Can you also provide what the following versions:
Data Services
Information Platform Services
Job server OS

vinaya_hg
Participant
0 Kudos

I checked the file in

C:\Program Files (x86)\SAP BusinessObjects\Data Services\conf\DSConfig

but after changing DOP value I am unable to save the file it is in read-only mode.Should I ask basis team to do it?

former_member466847
Active Participant
0 Kudos

Because the DSConfig.txt file edits and effects the performance of any job executed on the job server, we only recommend changing the file properties as needed.
For now please change the DOP at the job design/dataflow level and test.

Can you please confirm if the duplication is resolved and your versioning?

vinaya_hg
Participant
0 Kudos

Jessica ,

No luck. Inspite of changing with different values it is still duplicating .Do you think I can do any changes in the management console?

former_member466847
Active Participant
0 Kudos

Management Console would have most of the same execution options set as well.
How is the Target table set in Designer? are there multiple loaders set, set to drop and delete contents of the table each load or set to retain them?
In the Monitor log screen in Designer, during execution how many records are shown to load?

vinaya_hg
Participant
0 Kudos

Please find the attached screenshots

no-of-records.png

:target-table.png

former_member466847
Active Participant
0 Kudos

As this may take some deeper troubleshooting to find the root cause, can you please open a ticket with the component EIM-DS-EXE?
Please provide the Execution logs of the last run as well as the Data Services versioning and what environment this is occurring in.

former_member27665
Active Participant
0 Kudos

jessica.burley

We are facing the same issue while using OData adaptor to extract data from Successfactor. All the tables having employee information is returning duplicates.

vinaya_hg
Participant
0 Kudos

Hi Jessica ,

My senior gave me the solution to avoid duplicates in this situation is to use row generation transform.When I used it's not duplicating.

Thanks and Regards,

Vinaya

former_member466847
Active Participant
0 Kudos

Vinaya,
Thank you for the update and the workaround.
I have recently found the following KBA 2310626, which lists that duplication can occur from ECC tables when a setting in set in the Application Attributes.

https://launchpad.support.sap.com/#/notes/2310626

If this error occurs again please feel free to log a support ticket.

vinaya_hg
Participant
0 Kudos

Jessica ,

I am using data from custom table and created ODATA service on it. I think the above KBA is not applicable to my scenario.

Is it technically correct to eliminate duplicate values using row generation transform?

Regards,

Vinaya

former_member466847
Active Participant
0 Kudos

From the SAP Designer Guide : Row_Generation Generates a column filled with integer values starting at zero and incrementing by one to the end value you specify. The incoming data of one record is being assigned a temporary row id that overrides the duplication behavior from the source object.
Again this appears to be a workaround that is vaild for this time, but for deeper troubleshooting of the root cause, a service ticket will need to be created.

Answers (0)