XML integration: SOAP Runtime Exception

[Former Member]

Hi, and a happy new year to all of you.

I'm quite in trouble right now: I'm trying to process an XML flow into BW, but I receive the following error when trying:

-

---

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/">
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
<faultcode>SOAP-ENV:Server</faultcode>
<faultstring>Internal Server Error</faultstring>
<detail>SOAP Runtime Exception: CSoapExceptionInternal : XML kernel processor cannot prepare function call ( kernel rc=2 ) </detail>
</SOAP-ENV:Fault>
</SOAP-ENV:Body></SOAP-ENV:Envelope>

-

---

The strangest thing is:

- I don't see any XML error

- When I try to send the flow into another system (Without the right datasource name), i get the same error

- When I add an error in my XML code, I still have the same error

- When I try another flow for another DataSource on the target system... it works quite well

It should mean that something wrong with my xml file, but I really don't see what. Could someone help me there?

-

---

<?xml version="1.0" ?>
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP:Body>
<rfc:_-BI0_-QI6AZtX_ST_UPFRONT_TOOLS_RFC xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
  <DATASOURCE>6AZX_ST_UPFRONT_TOOLS</DATASOURCE>
  <DATA>
    <item>
      <LONUM></LONUM>
      <DOCNUM></DOCNUM>
      <BDLST></BDLST>
      <BU></BU>
      <BD></BD>
      <PARZC></PARZC>
      <COUNTRY></COUNTRY>
      <CREATEDON></CREATEDON>
      <DOCRY></DOCRY>
      <SOLDNUM>1000000001</SOLDNUM>
      <CUACCREQ></CUACCREQ>
      <CUCTAGGN></CUCTAGGN>
      <CUPOLAMD></CUPOLAMD>
      <CPOD></CPOD>
      <BPBSTKD>TESTLFH210</BPBSTKD>
      <CPORCVD></CPORCVD>
      <CAEATBPD></CAEATBPD>
      <DTCAED></DTCAED>
      <LABPD></LABPD>
      <LAEDCAED></LAEDCAED>
      <TVRDTD></TVRDTD>
      <FVRDTD></FVRDTD>
      <SVRDTD></SVRDTD>
      <FFHAGO>A</FFHAGO>
      <INCOCODE></INCOCODE>
      <INCOSITE></INCOSITE>
      <KTEXTSO></KTEXTSO>
      <IDNUM>10CAELA1</IDNUM>
      <IDLAV></IDLAV>
      <PARZK></PARZK>
      <TVRDTN></TVRDTN>
      <FVRDTN></FVRDTN>
      <SVRDTN></SVRDTN>
      <PARZO></PARZO>
      <ORCAT></ORCAT>
      <ORCREAV></ORCREAV>
      <PARZP></PARZP>
      <RQDATE></RQDATE>
      <FIRSTDT></FIRSTDT>
      <PARZA></PARZA>
      <SALESGRP></SALESGRP>
      <SHIPRES></SHIPRES>
      <SCTDESC></SCTDESC>
      <SELUNIT></SELUNIT>
      <SCWWBU></SCWWBU>
      <LACTV></LACTV>
      <CUPOTST></CUPOTST>
      <TOOLNUM></TOOLNUM>
      <BPROJET></BPROJET>
      <AMOUNT></AMOUNT>
      <UPDMOD></UPDMOD>
      <LBD></LBD>
      <LBGRP></LBGRP>
      <SOLANM>L-A</SOLANM>
      <SOCAENM></SOCAENM>
      <SORDNM></SORDNM>
      <FHAGO>10LA3</FHAGO>
    </item>
  </DATA>
</rfc:_-BI0_-QI6AZX_ST_UPFRONT_TOOLS_RFC>
</SOAP:Body>
</SOAP:Envelope>

-

---

Thanks a lot, and please be gentle with the humble beginner I am.

Sylvain

[athavanraja · Accepted solution]

upfront i can see one erro is that your SOAP message is not a valid XML format.

the start tag

(rfc:_-BI0_-QI6AZtX_ST_UPFRONT_TOOLS_RFC) dosent match with the end tag (rfc:_-BI0_-QI6AZX_ST_UPFRONT_TOOLS_RFC)

this may be a typo?

also since you are getting internal error, there is a chance that it might have created a ABAP dump. check in transaction ST22.

Regards

Raja

[Former Member · Accepted solution]

Thanks for your answer and an happy new year.

I did correct the typo error, but I still have the same issue... and there is no trace in the ST22 transaction.

It's quite hard to start a new year with such a problem...

Gratefully

Sylvain

[athavanraja · Accepted solution]

try to activate the ICM trace from transaction SICF and analyze the trace,

Regards

Raja

[Former Member · Accepted solution]

Thanks for your answers.

But since the dead line was coming a bit fast for me, I managed to redo the whole thing. It works right now, but I still don't understand what occured.

Hope to see you around and many thanks again.

Sylvain

[stefan_kittler]

Hi Sylvain

This message is displayed, when your function module is not RFC enabled. See http://help.sap.com/saphelp_ish472/helpdata/EN/2d/64d041e74911d6b2e400508b6b8a93/content.htm

Regards

Stefan