Code 8 retransporting SWCV

[Former Member]

Dear experts,

We are having issues with correction transport in Quality Syteme.

After first transport of the model in QAS, we are trying to send correction but the request has a RC 8 with the message :

Adapter name ZBA_PO is already in use; duplicates not allowed

Message no. MMWADP_TRANSPORT005

We changed couple bapi's in the BEA and we were expecting the new request to repalce the model in quality. Is there something we are not doing well or something we are forgetting? Does anyone already has this kind of issues?

Thank you for your help,

Regards,

Franck

[sivasatyaprasad_yerra]

Error is Adapter name is duplicated Which means There are two adapters with same name for a data object.

So, please check in SDOE_WB if the data object has two adapter's with same name.

Is the adapter was deleted and recreated in source system with same name? If yes, did you transport deleted backend adapter also?

[Former Member]

Hi Frank,

Can you check if the adapter was not transported twice? also please provide the exact error/warning msg there.

Thanks,

Rohit

[Former Member]

Hi Rohit,

Thank you for your quick answer.

The adapter had been transported once in the first request and we are trying to transport modifications in a second request but we have a RC 8.

here are the logs that we get in SE10 :

Adapter name ZBA_PO is already in use; duplicates not allowed

Message no. MMWADP_TRANSPORT005

Thank you for your help,

Franck

[Former Member]

Hi Frank,

this error can occur in following cases:

-if it is deleted recreated with the same name and transported to Q system.

-If it was deleted reacreated with the same name in target(Q) system and then a modification is sent from the source.

Regards,

Rohit

[Former Member]

Hi Rohit,

We did delete the BEA and recreated it with the same name before transport. I am going to work on this point and I will let you know.

Thank you for your time,

Regards,

Franck

Edited by: Franck MOUROT on Sep 7, 2009 2:03 PM

[Former Member]

Hi,

The issue was due to the fact that no entry had been generated for the deletion of the BEA in the TR. We had to recreate a TR with the suppression of this entry and import again the TR.

Thank you all for you help.

Best regards,

Franck