Idoc not processed!

[#1]

Hi ,

mine is a xi to r3 scenerio.Data in the form of a .CSV file from a FTP server is entering R3 through XI and updating some tables in R3. The data being posted in r3 can be checked through the transaction say WPER in r3.

My data has successfully passed through XI, with no errors in SXMB_MONI in xi .But I can see the same data in we02/05 in r3 as erranous data. The error code is 51.Document not posted.

Now this business has been running for months without any error. But I cannot make out the probablre reason why I am getting this !. Is this due to some wrong data in CSV? Pls help

Regards,

Arnab

[shivhare]

Hi Arnab Mondal

you can also see error message in WPER please write down error message

and also wirte doen which type of Inbound IDOC you are using

If there is minor mistake in sale file then you can edit IDOC and save it and reprocess it

Thanks

Amit

[Former Member]

Well , i never checked in WPER for errors,,, well , that was the functionl part....hmm,, this would be nice......but tell me , do you support my reply to Nallams comment....is my understanding ok..can u comment!

Arnab

[shivhare]

sure i support Nallams comment.... it may be possble. But I think for error analysis part you should be go end to end monitoring that may be techinical or functional

[Former Member]

Hi Amit,

incase of a File to Idoc scenerio :

In error analysis, the probable steps would be

1. Checking the status in sxmb_moni

2. idx2/idx1

3. Runtime Workbench : messehe monitering : waiting, system and holding statsus

4. Checking the status of the communication Channel

5. Going to R/3 and checking the status of We02/05.

Did I miss out anything !!

Pls comment

Arnab.

[Former Member]

you need to check SM58 even to see whether msg stuck or not..

[shivhare]

Hi Arnab Mondal ,

you can also check QRFC and TRFC queue withe the help of tcode SMQ1, SMQ2 and Sm58

Thanks

Amit

[Former Member]

Hi,

idoc 51 mean, that the idoc's are erroneous and must be manually corrected. to see the errors use the transaktion bd87 (we02 is more for business users).

here you can see, in which segments the error occur.

after correcting the errors you should reprocess the idoc's, so that they get the status 53 - manually or per job (mostly per job is ok, because the IT peoplae should not have the authorization in prod. systems.)

Report:  RBDMANI2

save a variant and schedule it with a job in sm36

BR.

CT

Edited by: Cahit Temizkan on Oct 30, 2008 11:54 AM

[Former Member]

Many thanks to XI , Amit , Sridhar and Cahit.

Cahit, u asked me to check BD87, , yea, but ultimately it takes us to the WE02/05 screen. Right??

Anyways, many thanks for the help ful reply.

The debugging concept clear. So is the fact that the file is erraneous, and needs manual correction after debugging.

So is the concept of checkinh the occurance of Mandatory fields in XI to 1:1 from 0:1.

Gud Learning for me.

Awarding points and closing the chain.

Thanks to all of u,

Arnab