Mapping Exception

[Former Member]

Hi,

I try to send an IDOC to the XI, convert it and send it to the file adapter.

I defined a mapping to map the IDOC to another file format. I tested the mapping successfully (with the content taken from the same IDOC I am trying to send).

When I send the IDOC, the XML-Message monitor shows the following error:

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

<SAP:Code area="MAPPING">&#20299;††††††††††††††</SAP:Code>

<SAP:P1>†††††††††††††††††††††††††</SAP:P1>

<SAP:P2>†††††††††††††††††††††††††</SAP:P2>

<SAP:P3>†††††††††††††††††††††††††</SAP:P3>

<SAP:P4>†††††††††††††††††††††††††</SAP:P4>

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>The exception occurred (program: CL_XMS_MAIN===================CP, include CL_XMS_MAIN===================CM00A, line: 535)</SAP:Stack>

I also had japanese letters instead of the crosses. Is there a codepage problem ?

What can be the cause for the exception, if the mapping runs fine in testing ?

Best regards,

Linus

[Former Member]

Has anyone figured this out? We have the same issue and any help would be GREATLY appreciated. There is a proxy ( srm bid request ) sending data from a non-unicode srm system to xi 3.0.

Thanks in advance!!!

[Former Member]

Linus,

Were you ever able to resolve this issue? We are having the same exact problem when trying any simple mapping scenarios.

Thanks,

Sean

[former_member184154]

It's a silly unicode problem happaning tipically when you are trying to address a non-unicode system declared as unicode... Check all RFC destinations created during post-installation in SM59.

Hope it helps.

Alex

[Former Member]

I have the same problem.

thanks