cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Transformation Error - Duplicate Data Record Detected

Former Member
0 Likes
2,701

Dear BI experts, I'm hoping someone can help me with this particular BI7 problem, with regard to a transformation expert routine on a DSO.

We have created a transformation, which uses an expert routine. It takes source data drom an existing DSO, checks each SOURCE_PACKAGE record and then generates additional records (based upon look-ups to other DSOs) appending the records to RESULTS_PACKAGE. This process works fine in many of our other scenarios, exept for this one case:

In this specific instance we're getting an error message of "Duplicate data record detected (DS....., data package: 000001 , data record: 149)", with a message class of RSODSO_UPDATE, and a message no. of 19.

We have debugged the routine carefully, and checked the entries in RESULTS_PACKAGE, and there are, to the best of our knowledge, no duplicate records conatined in the table.

Once the routine has failed, we can then manually activate the data request in the DSO, and it activates OK, missing out the records that apear to have caused the error. We have examined the error stack carefully, and as far as we can see these records do not have duplicates, so we're a little bit confused as to where the problem is.

As this is a transactional full load, I don't appear to have the option on the DTP to ignore duplicates.

When I run the DTP in debug mode, the job runs through the simulation to completion without any error messages.

We're on patch level 21 within BI 7.0. Any help or advice on this would be greatly appreciated.

All the best,

Jeff.

View Entire Topic
Former Member
0 Likes

Jeff,

Are there any internal tables defined with unique key?

Does any of the select statements in your look up return mulitiple records for the key combination?

The above check points might give some direction.

Former Member
0 Likes

Hi Sharat, thanks for taking the time to reply.

All internal tables have been defined with non-unique keys, and I've also ensured that the "Unique Data Records" checkbox setting on the DSO is not ticked. The select statements don't return multiple records for the same key.

All the best,

Jeff.