Skip to Content

Archived discussions are read-only. Learn more about SAP Q&A

Error in XI Message Processing

Hi

It's an SRM to ECC scenario through XI.

The standard content is already imported from Market place. I get a chequered flag from SXMB_MONI when I run the scenario. Which means all is fine from XI end. However, when we go to the ECC sytem, we see that there is an error. In SXMB_MONI of ECC I get this error

NOTE: The following trace entries are always lacking</Trace>

<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>

<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>

<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>

<Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>

<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />

<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>

<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />

I checked SXMB_ADM, and the current value of the paramter IS_URL contains port as 51000, shouldn't it be ABAP port? If the port is wrong how is it showing succes in XI, SXMB_MONI?

Also the Receiver com channel is XI adapter, so it should be a proxy. Is it because of any missing steps in ECC ?

Kindly give inputs

Regards

Former Member
Former Member replied

Login to your Client system (ECC) and see your proxy objects(tcode SPROXY) are created then follow this blog for step by step for debug.

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

Regards

Pothana

0 View this answer in context

Helpful Answer

by
Not what you were looking for? View more on this topic or Ask a question