cancel
Showing results for 
Search instead for 
Did you mean: 

EXCEPTION_DURING_EXECUTE - PI don't receive the new correct structure

Former Member
0 Kudos

Hello everybody,

I have a problem with the data sent from a RFC.

PI receives the data from R3 via RFC and than it writes these data into a DB.

The error message in the PI monitor tool is:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?> 
<!--  Request Message Mapping 
  --> 
<SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
  <SAP:Category>Application</SAP:Category> 
  <SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code> 
  <SAP:P1>com/sap/xi/tf/_MM_SP2QUID_ANA_GREZZI_</SAP:P1> 
  <SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException:</SAP:P2> 
  <SAP:P3>Character reference "&#02" is an invalid XML chara</SAP:P3> 
  <SAP:P4>cter.</SAP:P4> 
  <SAP:AdditionalText /> 
  <SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_MM_SP2QUID_ANA_GREZZI_; com.sap.aii.utilxi.misc.api.BaseRuntimeException:Character reference &quot;&amp;#02&quot; is an invalid XML character.</SAP:Stack> 
  <SAP:Retry>N</SAP:Retry> 
</SAP:Error>

This error appeared only after I changed the exported table structure of the RFC and the corresponding message mapping, imported RFC, data type, etc... in PI.

In the "monitor for processed XML messages" I saw the message from R3. This XML message doesn't update with the new structure of the exported table.

Why don't PI receive the new correct structure?

What is my problem?

thanks,

Damiano

Accepted Solutions (0)

Answers (5)

Answers (5)

Former Member
0 Kudos

Hi Damiano, I have the same problem as you did, only that my RFC structure seems to be up to date, but I still get the corrupted data. Can you tell me how exactly did you solve iti? (how did you make that cache refresh?).

Thanks in advance.

former_member200962
Active Contributor
0 Kudos
<SAP:P3>Character reference " " is an invalid XML chara</SAP:P3>

This is error...not related to cache or other thing....if you want to test create a scenario with any sender system and include this character in the payload you will get the same error....

the reason is & and # both are invalid characters in XML terms....so youu can either take care that tha payload does not have the special character or your mapping in PI is capable of handling it

the above character is getting into the mapping program whwre you are getting the error.....

Runtime exception occurred during application mapping com/sap/xi/tf/_MM_SP2QUID_ANA_GREZZI_;

test with the same payload in IR and you will find the same error coming

Edited by: abhishek salvi on May 15, 2009 3:04 PM

Former Member
0 Kudos

PI receives this message

<?xml version="1.0" encoding="UTF-8" ?> 
- <rfc:Z_RFC xmlns:rfc="urn:sap-com:document:sap:rfc:functions">
- <T_ZSTRUCTURE>
- <item>
  <IDCARAC>00005</IDCARAC> 
  <ZINTEXT>I</ZINTEXT> 
  <DESCR>CC240X200</DESCR> 
  <IDPERF>00010</IDPERF> 
  <IDPROD>00030</IDPROD> 
  <ZIDDIM1> u4000  </ZIDDIM1> 
  <ZIDDIM2> 0639</ZIDDIM2> 
  <ZAREA>35003000.300</ZAREA> 
  <ZLAMINATI>3</ZLAMINATI> 
  <ZPRIORITA>1 u7384</ZPRIORITA> 
  <ZFORGIA>u0C00</ZFORGIA> 
  <ZGREZZI_VENDITA>X</ZGREZZI_VENDITA> 
  <PESO_STD>30003000.310</PESO_STD> 
  <SPUNTATURA>3000200058.000</SPUNTATURA> 
  <LUNGHSTD>5300000<.000</LUNGHSTD> 
  <TOLLERANZA><.000</TOLLERANZA> 
  <PESO_MTR>14000.000<0</PESO_MTR> 
  <FLG_MROZZA></FLG_MROZZA> 
  </item>
  </T_ZSTRUCTURE>
  </rfc:Z_RFC>

this message contains wrong characters... so I have the error.

The problem is that... these data aren't the data sent from R3...

the exported table have a different structure and different values.

damiano

former_member200962
Active Contributor
0 Kudos

as per my little knowledge you have two options:

1)Try to make the sender application send only the values which are accepted by the XML format

This is not always a feasible option:(

2) in your mapping program include the logic which will ignore the presence of special characters and pass them as is...

This is achieved using an element called CDATA...just try to do a search on SDN itself and you will get the answer

Former Member
0 Kudos

problem solved.

I had to refresh all the Java Virtual-Machine Cache.

thanks to all

damiano

Former Member
0 Kudos

Hi,

I feel u r sending data which has some special character and hence creating some problem.

Please check is this the case??

regards,

Manisha

Former Member
0 Kudos

The problem is just that.

PI receives the XML message with the old structure and also with wrong and strange characters.

Instead, the data sent by the RFC are corrected.

Damiano

Former Member
0 Kudos

Hi,

Please check follow the steps in IR as import RFC, then change Mapping and activate it.

even if it does not work then try to clear cache.

Regards,

Manisha

Former Member
0 Kudos

Hi,

First try by refreshing the CPA cache. If this doesnt work hen reimport your RFC in PI, and reactivate relevant objects like message mapping.

Hope this helps.

Regards,

Siddhesh S.Tawate

former_member181962
Active Contributor
0 Kudos

Hi,

If i have understood your question correctly, YOu should have made the changes to the RFC Exporting Table structure in R/3 system first and then import it in PI Integration Repository instead of doing it the other way round

Regards,

Ravi Kanth Talagana

Former Member
0 Kudos

refresh the cache, try activating ur RFC sender adapter again...

Former Member
0 Kudos

I tried to refresh the cache with SXI_CACHE transaction and the same in the Administration page of the Process Integration Tool, but I have the same error.

Is there another transaction to refresh the cache?