Solved: Exception CX_XMS_SYSERR_MAPPING occurred

Former Member · ‎07-23-2007

Hi,

I am working on FTP 2 FTP scenario and I am getting following Error. I even verified the Interface Mapping by testing the Payload Document from SXMB_MONI and the mapping is working fine. But the o/p file is not getting created and in SXMB_MONI I see the following error. Any help in this regard is highly appreciated.

Error:

<?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="">

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="MAPPING">OK ㈀　　       　</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>Exception CX_XMS_SYSERR_MAPPING occurred (program: CL_XMS_MAIN===================CP, include: CL_XMS_MAIN===================CM00A, line: 541).</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

Trace:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Request Message Mapping

-->

- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">

<Trace level="1" type="T">Party normalization: sender</Trace>

<Trace level="1" type="T">Sender scheme external = XIParty</Trace>

<Trace level="1" type="T">Sender agency external = http://sap.com/xi/XI</Trace>;

<Trace level="1" type="T">Sender party external =</Trace>

<Trace level="1" type="T">Sender party normalized =</Trace>

<Trace level="1" type="T">Party normalization: receiver</Trace>

<Trace level="1" type="T">Receiver scheme external =</Trace>

<Trace level="1" type="T">Receiver agency external =</Trace>

<Trace level="1" type="T">Receiver party external =</Trace>

<Trace level="1" type="T">Receiver party normalized =</Trace>

- <!-- ************************************

-->

<Trace level="1" type="T">XMB was called with URL /sap/xi/engine?type=entry</Trace>

<Trace level="1" type="T">COMMIT is done by XMB !</Trace>

- <!-- ************************************

-->

- <!-- ************************************

-->

<Trace level="1" type="T">XMB entry processing</Trace>

<Trace level="1" type="T">system-ID = XIS</Trace>

<Trace level="1" type="T">client = 001</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = PIAFUSER</Trace>

- <!-- ************************************

-->

<Trace level="1" type="T">Message-GUID = 2B74FC20393111DC8B82A6F46001A00D</Trace>

<Trace level="1" type="T">PLNAME = CENTRAL</Trace>

- <!-- ************************************

-->

<Trace level="1" type="T">Get definition of external pipeline = CENTRAL</Trace>

<Trace level="1" type="T">Get definition of internal pipeline = SAP_CENTRAL</Trace>

<Trace level="1" type="T">Queue name : XBTI0001</Trace>

<Trace level="1" type="T">Generated prefixed queue name = XBTI0001</Trace>

<Trace level="1" type="T">Schedule message in qRFC environment</Trace>

<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>

<Trace level="1" type="T">----

</Trace>

<Trace level="1" type="T">Going to persist message</Trace>

<Trace level="1" type="T">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">----

</Trace>

- <!-- ************************************

-->

<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>

- <!-- ************************************

-->

<Trace level="1" type="T">----

</Trace>

<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>

<Trace level="1" type="T">system-ID = XIS</Trace>

<Trace level="1" type="T">client = 001</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = PIAFUSER</Trace>

<Trace level="1" type="T">----

</Trace>

- <!-- ************************************

-->

<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>

<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>

- <Trace level="1" type="B" name="PLSRV_RECEIVER_DETERMINATION">

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

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

- <Trace level="1" type="B" name="CL_RD_PLSRV-ENTER_PLSRV">

<Trace level="1" type="T">Cache Content is up to date</Trace>

</Trace>

- <Trace level="1" type="B" name="PLSRV_INTERFACE_DETERMINATION">

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

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

- <Trace level="1" type="B" name="CL_ID_PLSRV-ENTER_PLSRV">

<Trace level="1" type="T">Cache Content is up to date</Trace>

</Trace>

- <!-- ************************************

-->

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

- <!-- ************************************

-->

- <!-- ************************************

-->

<Trace level="1" type="T">number of receivers: 1</Trace>

<Trace level="1" type="T">Single-receiver split case</Trace>

<Trace level="1" type="T">Post-split internal queue name = XBTO1___0000</Trace>

<Trace level="1" type="T">----

</Trace>

<Trace level="1" type="T">Persisting single message for post-split handling</Trace>

<Trace level="1" type="T">Going to persist message + call qRFC now...</Trace>

<Trace level="1" type="T">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">Async barrier reached. Bye-bye !</Trace>

<Trace level="1" type="T">----

</Trace>

- <!-- ************************************

-->

<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>

- <!-- ************************************

-->

<Trace level="1" type="T">----

</Trace>

<Trace level="1" type="T">Starting async processing with pipeline CENTRAL</Trace>

<Trace level="1" type="T">system-ID = XIS</Trace>

<Trace level="1" type="T">client = 001</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = PIAFUSER</Trace>

<Trace level="1" type="T">----

</Trace>

- <!-- ************************************

-->

<Trace level="1" type="T">Get definition of external pipeline CENTRAL</Trace>

<Trace level="1" type="T">Corresponding internal pipeline SAP_CENTRAL</Trace>

<Trace level="1" type="T">Start with pipeline element PLEL= 5EC3C53B4BB7B62DE10000000A1148F5</Trace>

- <!-- ************************************

-->

- <!-- ************************************

-->

- <!-- ************************************

-->

- <!-- ************************************

-->

<Trace level="1" type="T">Interface Mapping http://ftp_2_ftp im_mapping</Trace>

<Trace level="1" type="E">CL_XMS_PLSRV_MAPPING~ENTER_PLSRV</Trace>

</Trace>

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

- <!-- ************************************

-->

</SAP:Trace>

moorthy · ‎07-23-2007

HI,

Hope you have got correct message in the mapping i.e it is not empty ( SAP Note: 1060723) Related SAP note: 719301

Btw make sure that all mandatory nodes are mapped and there is no error in any UDF if used. Also check in the display queue context option

Rgds,

Moorthy

Former Member · ‎07-24-2007

Hi,

Any idea how to get rid of this error.

Thanks in advance.

Rajeev

Former Member · ‎07-23-2007

Hi Krishna and Raj,

Thanks for your quick response.

Krishna,

All the fields are properly mapped. I am using the ftp 2 ftp scenario avaiable on sdn:

/people/venkat.donela/blog/2005/03/02/introduction-to-simplefile-xi-filescenario-and-complete-walk-through-for-starterspart1

Raj,

I changed the description and then activated the changes, but still same error.

Thanks

Rajeev

justin_santhanam · ‎07-23-2007

Rajeev,

Since u said the mapping is working perfectly in Mapping editor. Try to change the mapping and activate again and run the scenario. Changes in the sense add some description to mapping program and activate again,juz to check whether its related to cache issue or not.

Best regards,

raj.

Exception CX_XMS_SYSERR_MAPPING occurred

Accepted Solutions (1)

Accepted Solutions (1)

Answers (3)

Answers (3)

Why html_repo_runtime is added in the resources se...

Re: Deploy Fiori Freestyle App to Cloud Foundry - ...

Re: SAP BO 4.3 Cloud: Error - The document has bee...

Re: How to get the FIRST Date in a date column

Re: SAP Cloud ALM - Granular Authorization to Scop...