IDOC Status

[Former Member]

Hi,

I created an IDOC, but the status of an IDOC is 32. May i know why that error has occured.

Please can any one explain clearly?

Thanks in advance

[Former Member]

Hi,

I created an IDOC, but the status of an IDOC is 32. May i know why that error has occured.

Please can any one explain clearly?

Thanks in advance

[Former Member]

For outbound Idocs run the Program RBDOUTPU, and select the last Radio button with 32 status and run , give the IDoc number and process

[Former Member]

Hi,

In table EDIFCT there is the combination of message type and IDoc type assigned to a function module to processs the IDoc. Find this function and put a break-point in it. Then reprocess the IDoc with BD87 (or the ABAP RBDOUTPUT to save an extra step) and debug from where the procedure stops. From here, you are in the application and can to see what goes awry.

Thanks,

Sandeep.

[Former Member]

see these status descriptions

Status Description

00 Not used, only R/2

01 IDoc generated

02 Error passing data to port

03 Data passed to port OK

04 Error within control information of EDI subsystem

05 Error during translation

06 Translation OK

07 Error during syntax check

08 Syntax check OK

09 Error during interchange handling

10 Interchange handling OK

11 Error during dispatch

12 Dispatch OK

13 Retransmission OK

14 Interchange Acknowledgement positive

15 Interchange Acknowledgement negative

16 Functional Acknowledgement positive

17 Functional Acknowledgement negative

18 Triggering EDI subsystem OK

19 Data transfer for test OK

20 Error triggering EDI subsystem

21 Error passing data for test

22 Dispatch OK, acknowledgement still due

23 Error during retransmission

24 Control information of EDI subsystem OK

25 Processing despite syntax error (outbound)

26 Error during syntax check of IDoc (outbound)

27 Error in dispatch level (ALE service)

28 Not used

29 Error in ALE service

30 IDoc ready for dispatch (ALE service)

31 Error - no further processing

32 IDoc was edited

33 Original of an IDoc which was edited

34 Error in control record of IDoc

35 IDoc reloaded from archive

36 Electronic signature not performed (timeout)

37 IDoc added incorrectly

38 IDoc archived

39 IDoc is in the target system (ALE service)

40 Application document not created in target system

41 Application document created in target system

42 IDoc was created by test transaction

50 IDoc added

51 Application document not posted

52 Application document not fully posted

53 Application document posted

54 Error during formal application check

55 Formal application check OK

56 IDoc with errors added

57 Test IDoc: Error during application check

58 IDoc copy from R/2 connection

59 Not used

60 Error during syntax check of IDoc (inbound)

61 Processing despite syntax error (inbound)

62 IDoc passed to application

63 Error passing IDoc to application

64 IDoc ready to be transferred to application

65 Error in ALE service

66 IDoc is waiting for predecessor IDoc (serialization)

67 Not used

68 Error - no further processing

69 IDoc was edited

70 Original of an IDoc which was edited

71 IDoc reloaded from archive

72 Not used, only R/2

73 IDoc archived

74 IDoc was created by test transaction

regards,

srinivas

<b>*reward for useful answers*</b>

[Former Member]

Hi Sree hari,

chk this one,

My question is regarding Outbound EDI of the Advance Shipping Notice, which has produced an IDoc. The IDoc was successfully sent to the customer, but it turns out we have missing or incomplete data. This means the customer is unable to receive the goods into stock!

One of the missing pieces of information is the Customer Material Number(KDMAT). The problem is that the Goods Issue has already taken place and the Invoice sent to the customer. In the delivery it is not possible to manipulate the KDMAT field. Rather than canceling the Customer Invoice, canceling the Goods Issue, deleting the Delivery and re-creating I looked at the possibility of editing the IDoc, which is possible with transaction WE02 in change mode. This sets the IDoc status to 32 - IDoc has been edited. Next I expected to be able to use transaction BD88 - Process Outbound IDocs to resend the edited IDoc but this is where I have my problem! I get a hard error telling me that the previous status was 03 meaning that it was processed ok! I presume that it's not allowing the IDoc to be resent because it's already been successfully sent! There must be a way to do this! QUESTION POSED ON: 13 MAY 2003

QUESTION ANSWERED BY: Axel Angeli Unfortunately, SAP prohibits resending an already send IDoc.

However, an incomplete IDoc should never leave the factory anyway. So it is better to catch the error before you publish it.

In the case you described the ideal solution would be building an automatic check routines in the user-exit of the function that creates the outbound IDoc. There you could either try to enrich the document, so that the missing data is there. Alternatively you set the status of the IDoc (control_record_out-status) to something other than 30, e.g. '26' (Syntax error).

But I have to tell you that I do not see a sound standard way to inhibit sending due to incorrect data while still creating the IDoc. You cannot manipulate the status or any other control parameter. You can exit the creating function module by raising an error. This will cause the IDoc creation to fail and a workflow will be starting notifying someone that the send has failed.

So far, the proper options. Now the dirty solutions. (Some say, these are my preferred solutions, who knows.)

If you want to resend just in exceptional cases you may use WE19, the test tool and recreate the IDoc as a copy of the original. WE19 will also allow to edit the IDoc properly. Since release 4.6 the tool became pretty cool to use.

Another option is a little ABAP, like the following two-liner:

PARAMETERS: docnum like edidc-docnum.

update edids set status = '30' where docnum eq docnum and status eq '03'

reward points to all helpful answers

kiran.M

[Former Member]

Hi Sree,

This status shows

IDOC was edited.

May be the IDOC is changed after it has processed

Regards

Arun