OutBound IDOC Processing

[Former Member]

Hi Experts,

I am getting the following error while sending outbound IDOC (Multiple IDOCS as a single message) to SAP-XI.I am trying to send the IDOC using WE19 transaction and getting the following error.

500 error during parsing of SOAP Header.Status record 02

Thanks

Ajay Garg

[Former Member]

Hi Ajay,

You can not use WE 19 to send multiple IDOCS to XI. There is a blog by Stefan Grube explaining a work around for this. The idea is instead of creating tRFC port in WE21 create a File port and associate it with the partner profile in WE20. THis will create IDOC files in SAP system. Use FIle adapter of XI to process these IDOC files. Make sure the package size is set to a optimum value. There were also guides explaining the use of XML FIle and XML HTTP ports for achieveing the same results. Search in SDN for those guides.

Regards.

Jaishankar

[Former Member]

HI,

500 error during parsing of SOAP Header.Status record 02

The Idoc Status code 02 indicates as 02---> Error passing data to port

And the 500 error of parsing of SOAP header is internal server error.

HTTP 500 can be any problem at XI. Plz chk all the setting on the XI side.

Check this SAP SOAP Note for FAQ-856597 (Question No 1)

By default, the SOAP adapter sends the SOAP message with the content type text/xml.

When you check "Do not use SOAP envelope", the default contnet type is application/xml.

You can change the content type like this: Go to the SOAP receiver communication channel module tab. Add the module "localejbs/AF_Modules/MessageTransformBean" before the standard module. Add the parameter name Transform.ContentType and value text/xml.

Check out this

/people/varadharajan.krishnasamy/blog/2007/01/09/troubleshooting-soap-message--xi

One way of testing ur scenario

/people/michal.krawczyk2/blog/2005/08/25/xi-sending-a-message-without-the-use-of-an-adapter-not-possible

Can you refer below steps for troubleshooting. it may help you

Troubleshooting IDOC scenario

1. Start with checking the status in sm58 of sender R/3

Follow the steps

2. Try deleating the IDoc from IDX2 and refiring the same.

3. Check your RFC destination definition (the one pointing to your XI server) to confirm that it is of type '3' (R/3 system) and not 'T' (TCP/IP).

In your ID, in the Sender Business System --> Adapter Specific Identifiers, give the logical name for the business System pointing to the R3 system

4. Monitor the SM58 in R/3 for IDOC status.

5. Trouble shooting file to IDOC and IDOC to file

/people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi

https://www.sdn.sap.com/irj/sdn/wiki?path=/display/xi/error%2bhandling%2bin%2bfile-idoc%2bscenario

Refer below links for indepth troubleshooting

Thanks

Swarup

Edited by: Swarup Sawant on May 26, 2008 11:15 AM

[former_member859847]

Hi,

Please check the SAP Notes u2013 804124, 807000 .

regards

mahesh.

[Former Member]

and also check this blog, for trouble shooting ALE process

/people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process

regards

chandrakanth

[Former Member]

hi ajay,

In transaction SM59 ("Display and Maintain RFC Destinations") in the SAP Unicode system, enter the RFC destination of the "TCP/IP connection" type for the non-Unicode subsystem as usual.

On the "Special Options" tab, specify that the target system is not a Unicode system ("Character Width in Target System" box). To set the required behavior in the event of conversion errors, select the Default Setting, Short Dump After Conversion Error or Ignore Conversion Error option with a replacement character ("Character Conversion" box).

When the transfer is made, the target code page is derived from the user's logon language (the user whose ID is used to send the Idoc). This is the active dialog user for individual processing or the user whose ID is used to execute RSEOUT00.

With kernel 6.20 PL1773, kernel 6.40 PL55 and kernel 7.00 PL82 and the described corrections in the RFC and ALE layers, the behavior is changed so that the target code page is requested from the subsystem instead of being implicitly derived from the users logon language.

Bear in mind, however, that more characters can be displayed in the Unicode system than in the non-Unicode code page of the subsystem. This means that characters may still not be received correctly in the subsystem. You can minimize this problem with the following steps:

1. Use several instances of the subsystem, each of which uses different code pages.

2. Create a user-defined RFC destination for each subsystem that has a different code page.

3. You must then enhance the receiver determination (EDI) or the ALE distribution model so that a specific recipient is assigned to each IDoc according to the characters it contains. The recipient then indicates the relevant subsystem with the "appropriate" code page via the port and the RFC destination.

If the IDocs contain characters from different code pages (which may be the case if you have descriptive texts for master data), you must also distribute the master IDOC in the distribution model to several communication IDocs, so that characters of a code page are contained within the individual communication IDocs.

Refer to Note 613389 for more information.

Note: reward points if solution found helpfull

Regards

Chandrakanth.k

[former_member556603]

Hi,

IDOC testing -

/people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario

/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133

/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi

/people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters

IDOC settings

/people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi

Trouble shooting

/people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process

Thanks

Satya Kumar

Edited by: SATYA KUMAR AKKARABOYANA on May 26, 2008 11:00 AM

[Former Member]

Hi Ajay,

Go through this block.

Please reward points if it helps

Thanks

Vikranth