TDMS _ BPL- Data transfer start - activity in error

[Former Member]

Dear All,

I'm trying to execute a BPL scenario.

I have selected the purchase order object with a selection on company code and data of creation of purchase order.

I did not have any issue except during the Data Transfer Step.

This step has finished with "Error Status", mainly for duplicate key error.

So i have executed the Troubleshooting activity, (change write behavior step)

Badly, there still an issue:

Please find below the error message:

Run *********** resulted in duplicates at modify for unique secondary index.

Benjamin

Subactivity in error: MERGEMCHBH

Does anyone know how i can solve this issue?

Regards

[Former Member]

Sub activity in error is MERGEMBEW and not MERGEMCHBH

[former_member65049]

Hi,

This problem is caused for tables MBEW and MCHBH, which has an unique
secondary index that already contains data on receiver side.

This is conflicting with the data that TDMS is transferring from sender
side.

To solve this issue,  you can follow any of the below approaches:

1. Either drop the unique secondary index or make it a non-unique secondary index on the receiver side.

2. Another option is to delete the conflicting entries from the reciver system. To do this, you need to check the

spool of the data transfer job in error in central system.

It will show the confliucting entries.

Then you need to delete these conflicting entries manually from the receiver system.

Once this is done, you need to restart the data transfer activity from the process tree.

Regards,

Rupam

[Former Member]

Hi Rupam,

Thank you for this answer, but about the second option, i did not find any spool.

I can see the job, but there is not spool, so i am not able to check the confliucting entries.

Do you have some reasons?

Regards,

Benjamin

[former_member65049]

Hi Benjamin,

You should be able to see the spool list for the data transfer jobs in error state.

You can search these jobs using the string *LOAD_MT*.

In case you are still not able to see the details, please raise the OSS message in CA-TDM* component.

We would check the details then.

Regards,

Rupam