Outbound Idoc 03 status - SM58 error

[Former Member]

Hi ,

For Oubound Idoc, I am getting Idoc with status 03 but is not there in Receipient system.

When I check Idoc in Sm58, Idoc has error <b>"The ABAP/4 Open SQL array insert results in duplicate database records".</b>

Can anybody help me how to solve this issue?

Thanks & regards,

Yogita

[Former Member]

yogita,

Hope u can do through debugging only

Rerun the Idoc resulting in error in foreground (try with BD87 transaction) debugging mode... set break point on MESSAGE statement as well as INSERT statement..

then check the code throughly for the data which resultys in duplicates entries..

Mostly it is through Exits or some non SAP code

[Former Member]

Hi Navin,

I am not able to rerun Idoc in BD87. This Idoc has already status 03.

Do you know anyother way to debug this?

Regards,

Yogita

[Former Member]

use FM idoc_status_write_to_database to change the IDoc status from 03 to 30 and then run WE14 or RSEOUT00 to change the status back to 03

resending idoc from status 03 ...is a data duplicatino issue on receiving side...why do u need to do that ?

Use WE19 tcode to debug

In we19

1)U can choose your Idoc number in existing Idoc textbox

2)Press execute

3)u will display ur Idoc struct

4)Dbl click on any field then u can modify its content

5)PressStd Outbound Processing Btn to process modified Idoc

Thats it

[Former Member]

Hi,

Tried to debug using WE19 but couldn't reach to problem.

Do you know why doesn't it create entry in ST22 so that can check at what point it is failing?

Regards,

[Former Member]

check the corresponding tables for that tcode like

SNAP-FLIST or ERRID

or

table rdumpov

[Former Member]

Hi!

I have the same problem like Yogita.

What do you exactly mean by "check the corresponding tables for that tcode"?

@yogita: How did you solve the problem?

Thanks and best regards,

Stefan

[Former Member]

my colleague was able to provide a solution for my problem:

1. Look into table EDIDC in the target system for MAX ( DOCNUM ).

2. Transaction SNUM, object EDIDOC, intervals

3. change current number (NRLEVEL) to MAX ( DOCNUM ) + 1

it seems that the problem occured due to a insufficient client copy.

regards

[former_member335035]

Thanks Stefan.

It helped me to fixed the issue