cancel
Showing results for 
Search instead for 
Did you mean: 

Error when calling inbound proxy

Former Member
0 Kudos

Hi all,

I´m facing the following problem in the R/3 monitoring:

<SAP:Code p1="Request Message" p2="CX_XSLT_RUNTIME_ERROR" p3="/1SAI/XS00000000000000000035: 0000000000" p4="Error Text: No valid source context supplied Kernel ErrorId: CX_XSLT_RUNTIME_ERROR">APPLICATIONCALL.PARSE_APPLICATION_DATA</SAP:Code>

<SAP:Text language="EN">Error when handling Request Message; XSLT error: CX_XSLT_RUNTIME_ERROR: XSLT program and source line: /1SAI/XS00000000000000000035: 0000000000; Error Text: No valid source context supplied Kernel ErrorId: CX_XSLT_RUNTIME_ERROR</SAP:Text>

</SAP:ErrorHeader>

I'm pulling a file from an external server and I pass the data to R/3 thru ABAP proxies. The point is that I am splitting the message in different parts, using the parameter Recordsets per Message, and mostly all of them are processed correctly, but in a few of them i´ve got that error. And if I process that parts of the file, that have caused the error, separately, they surprisingly work fine..

I really do not know what happens and i really need help because I do not know what else to try or what could be the reason of this error.

Thanks a lot!!

Accepted Solutions (0)

Answers (5)

Answers (5)

Former Member
0 Kudos

Please, anybody has any idea? I really need help with this..

Thank you

Former Member
0 Kudos

Hi biplab,

there is no mapping involved in my configuration and i didnt get any clear result with the test...

More ideas?? Thank you

nisarkhan_n
Active Contributor
0 Kudos

the problem is INbound Message and the proxy genereted are not compatiable, can u check the field "S00000000000000000035: 0000000000;" whch field is atking this value from file, while passing to the R/3 check the lengths of this field....you will not c this error in MM, but you have to chcek the length of each field in proxy with data coming.......

copy the payload from SXMB_MONI and directly try to send the data from SPROXY you will get the error detail....

U can refer to the following thread where they has the same exception APPLICATIONCALL.PARSE_APPLICATION_DATA( b'cos of improper date formats...)So urs should also be a simlilar problem i guess..

https://www.sdn.sap.com/sdn/collaboration.sdn?contenttype=url&content=https%3A//forums.sdn.sap.com/t...

Former Member
0 Kudos

Hi Nisar,

<i><b>can u check the field "S00000000000000000035: 0000000000;" whch field is atking this value from file</b></i> ->How can i check this??

https://www.sdn.sap.com/sdn/collaboration.sdn?contenttype=url&content=https%3A//forums.sdn.sap.com/t... -> this link doesnt work

Thanks a lot for your help

nisarkhan_n
Active Contributor
0 Kudos

goto the SXMB_MONI and check the call adapter --payload there.....look for values there compare the length with that of the ABAP lenght.......

sorry for that link

Former Member
0 Kudos

Hi Chemmanz,

Thanks for your help, but it didnt help a lot cause the link in that forum thread does not work. Do you have more info about this error?

Thanks a lot!

Former Member
0 Kudos

Hi gracia,

check ur message mapping and file structure!!

and try to test ur scenario from proxy itself and check ...where is the error..

if it works fine from proxy then....u have problem in mapping or source structure....

otherwise problem is in code!!!

check here how to test from proxy!!!

/people/stefan.grube/blog/2006/07/28/xi-debug-your-inbound-abap-proxy-implementation

regards

biplab

arunneerolil
Contributor
0 Kudos

Hi

chk this thrd

rgds

Chemmanz