Debuggung of inbound proxy

[former_member201264]

I have error msg in in debugging in inbound of proxy

error:

- <CX_AI_SYSTEM_FAULT>

<CODECONTEXT>Local</CODECONTEXT>

<CODE>PARSE_APPLICATION_DATA</CODE>

<ERRORTEXT>Error during XML => ABAP conversion (Request Message; error ID: CX_ST_MATCH_ELEMENT; (/1SAI/TXS00000000000000000005 XML Bytepos.: 41 XML Path: Error Text: Element 'MT_BRIDGE_SALES_FORECAST' expected))</ERRORTEXT>

<LANGUAGE />

</CX_AI_SYSTEM_FAULT>

plz it is urgent

points will be rewareded

[former_member201264]

Hi friends,

thsanks a lot for giving immediate replies.

i have tested the inbound interface in the debugging mode.

While pasting the payload data in the XML editor of Proxy---->TestInterface here we have to check the XML Editor check box

Then it will open XML editor where we have to paste the payload.

After pating the payload delete all "-" before the nodes of XML data and execute the interface.

regards

sreeni

[Former Member]

Hi,

Before testing from SXMB_MONI,

first test your proxy code locally... i mean double click the proxy.

select Proxy->test ..select the xml file that will sent by XI to proxy...

and test ..

if it is working fine ..means your proxy code is ok...

[former_member201264]

hi experts

my scenario flow is r/3 ---> Xi -

---

> again same R/3

data is going to XI automatically and in also from XI inbound QUeue

but the problem is that it is showing Green flag

if we relase the msgs maually from the queues then it showing Single black arrow in place of green flag

if release from here by doing the same thing in queues then it going the R/3 and doing further in R/3

so i want to know why the messages are getting blocked in queues

plz help me its urgent

points should be rewarded

thanks

sreeni

[turmoll]

Hi,

What's the error message in XI? There will be some statement ...

Check the RFC destination type H on XI which points your R/3 server.

Regards,

Jakub

[Former Member]

go to the queue using smq2 or click the queue Id name where message is getting stucked...

if there is only one entry there.. it means it only yours ( sometime message get stucked because some other interface message are already present in error state and if during our proxy XI pick up the same queue then our message will get stucked up even though there is no error)...

are u getting more than one message in the queue.?

if there is only one ... select the first entry... click the last column of the entry ... it will show you error if there is any...

try this ..

[nisarkhan_n]

try to execute the payload which you are getting the from SXMB_MONI in the Sproxy TC if you are getting the same error then you have to regenerate the PROXY.

Make sure you are generating the proxy on the right message interface.

[turmoll]

Hi,

It looks like your proxy expects the message of this kind: MT_BRIDGE_SALES_FORECAST but you sent different ...

Check your interface in XI and compare it to the generated proxy in your SAP for that interface. transaction: SPROXY.

Regards,

Jakub

[Former Member]

Have you changed the structure of proxy in IR in XI but not regenerated proxy in application system..??

If so then try to regenrate the proxy in application system & test it again.

Regards

Sushil

[former_member201264]

hi susil

i have kept break point in the inbound proxy code , and i have given the XML payload from SXMB_MONI message.

It is not stopping there but giving this error message

i dont know this msg wht it is saying.

please help me

_

[Former Member]

From the payload it seems that payload format is nt matching with expected format. Can u please regenrate proxy in application system & then try to process the message.

Regards

Sushil

[former_member201264]

hi

i am sending complete error msg

check this

<?xml version="1.0" encoding="utf-8" ?>

- <asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">

- <asx:values>

<ERROR href="#o155" />

</asx:values>

- <asx:heap xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:abap="http://www.sap.com/abapxml/types/built-in" xmlns:cls="http://www.sap.com/abapxml/classes/global" xmlns:dic="http://www.sap.com/abapxml/types/dictionary">

- <cls:CX_XMS_SYSERR_PROXY id="o155">

- <CX_ROOT>

<TEXTID>392B46E58AC0F445B64639726E2A3D85</TEXTID>

<PREVIOUS href="#o154" />

<KERNEL_ERRID />

- <INTERNAL_SOURCE_POS>

<PROGID>239</PROGID>

<CONTID>647</CONTID>

</INTERNAL_SOURCE_POS>

</CX_ROOT>

<CX_STATIC_CHECK />

- <CX_XMS_SYSTEM_ERROR>

<ID>PARSE_APPLICATION_DATA</ID>

<P1 />

<P2 />

<P3 />

<P4 />

<INFO />

<CATEGORY />

<AREA />

<RETRY />

</CX_XMS_SYSTEM_ERROR>

- <CX_XMS_SYSERR_PROXY>

<CO_AREA_ABAP>ABAP</CO_AREA_ABAP>

</CX_XMS_SYSERR_PROXY>

</cls:CX_XMS_SYSERR_PROXY>

- <cls:CX_AI_SYSTEM_FAULT id="o154">

- <CX_ROOT>

<TEXTID>F63AFF63DBE4BB4786A7F52CC4167145</TEXTID>

<PREVIOUS href="#o141" />

<KERNEL_ERRID />

- <INTERNAL_SOURCE_POS>

<PROGID>239</PROGID>

<CONTID>558</CONTID>

</INTERNAL_SOURCE_POS>

</CX_ROOT>

<CX_STATIC_CHECK />

- <CX_AI_SYSTEM_FAULT>

<CODECONTEXT>Local</CODECONTEXT>

<CODE>PARSE_APPLICATION_DATA</CODE>

<ERRORTEXT>Error during XML => ABAP conversion (Request Message; error ID: CX_ST_MATCH_ELEMENT; (/1SAI/TXS00000000000000000005 XML Bytepos.: 41 XML Path: Error Text: Element 'MT_BRIDGE_SALES_FORECAST' expected))</ERRORTEXT>

<LANGUAGE />

</CX_AI_SYSTEM_FAULT>

</cls:CX_AI_SYSTEM_FAULT>

- <cls:CX_XMS_SYSERR_PROXY id="o141">

- <CX_ROOT>

<TEXTID>8BB7CA726FE56F43BC4A06197ABFE5FD</TEXTID>

<PREVIOUS href="#o135" />

<KERNEL_ERRID />

- <INTERNAL_SOURCE_POS>

<PROGID>0</PROGID>

<CONTID>0</CONTID>

</INTERNAL_SOURCE_POS>

</CX_ROOT>

<CX_STATIC_CHECK />

- <CX_XMS_SYSTEM_ERROR>

<ID>PARSE_APPLICATION_DATA</ID>

<P1>Request Message</P1>

<P2>CX_ST_MATCH_ELEMENT</P2>

<P3>/1SAI/TXS00000000000000000005</P3>

<P4>XML Bytepos.: 41 XML Path: Error Text: Element 'MT_BRIDGE_SALES_FORECAST' expected</P4>

<INFO />

<CATEGORY>XIProxy</CATEGORY>

<AREA>ABAP</AREA>

<RETRY>M</RETRY>

</CX_XMS_SYSTEM_ERROR>

- <CX_XMS_SYSERR_PROXY>

<CO_AREA_ABAP>ABAP</CO_AREA_ABAP>

</CX_XMS_SYSERR_PROXY>

</cls:CX_XMS_SYSERR_PROXY>

- <cls:CX_ST_MATCH_ELEMENT id="o135">

- <CX_ROOT>

<TEXTID>544FAE4641562346A1372144E7396586</TEXTID>

<PREVIOUS />

<KERNEL_ERRID />

- <INTERNAL_SOURCE_POS>

<PROGID>118</PROGID>

<CONTID>1242</CONTID>

</INTERNAL_SOURCE_POS>

</CX_ROOT>

<CX_DYNAMIC_CHECK />

<CX_TRANSFORMATION_ERROR />

- <CX_ST_ERROR>

<ST_PROGNAME>/1SAI/TXS00000000000000000005</ST_PROGNAME>

<X-ML_OFFSET>41</X-ML_OFFSET>

<X-ML_PATH />

<ST_IC>0</ST_IC>

<ST_TIMESTAMP>20070228093023</ST_TIMESTAMP>

</CX_ST_ERROR>

- <CX_ST_MATCH>

<ACTUAL_TOKEN_TYPE>T</ACTUAL_TOKEN_TYPE>

<ACTUAL_NAME />

<ACTUAL_NAMESPACE />

<ACTUAL_VALUE>-</ACTUAL_VALUE>

</CX_ST_MATCH>

- <CX_ST_MATCH_NAMED>

<EXPECTED_NAME>MT_BRIDGE_SALES_FORECAST</EXPECTED_NAME>

<EXPECTED_NAMESPACE>http://bridgegcs.com/MF/SalesForecastTransfer_IMF001</EXPECTED_NAMESPACE>

<EXPECTED_OPEN>X</EXPECTED_OPEN>

</CX_ST_MATCH_NAMED>

<CX_ST_MATCH_ELEMENT />

</cls:CX_ST_MATCH_ELEMENT>

</asx:heap>

</asx:abap>

if it spots there i can do the further debugging

please help me

regards

sreeni