IDOC Mapping ; Error CX_XMS_SYSERR_MAPPING

[Former Member]

After we transfered an IDoc 1:1, w/o mapping, successfully from one to another SAP system, we added a mapping like follows:

1. created a message mapping per drag&drop from imported objects - IDocs, using a 1:1 mapping (no field changes, just for testing purposes)

2. created an interface mapping using that message mapping.

3. after activating in repository, we added that interface mapping in interface determination in configured inbound-interfaces.

After starting a test data transfer we received the error message

"CX_XMS_SYSERR_MAPPING Programm: CL_XMS_MAIN===================CP, Include CL_XMS_MAIN===================CM00A, line: 535"

And an odd error id with strange crosses in the overview.

Did we forget something? Any hint is welcome.

[former_member185751]

Hi,

Can you try making a small change in your message mapping (for e.g. insert a space in the description field and remove it immediately) and save it. Reactivate it again. Test your message mapping and interface mapping in the IB itself and then run your scenario.

Regards,

Sridhar

[Former Member]

Hi,

Did you test your mapping first with the mapping tool?

Bill

[Former Member]

@Sridhar: Thanks for the hint, but unfortunately it did not change anything. Do you think it has something to do with cached information?

@Bill: Yes, we test it in the IB Repository using the mapping tool. The mapping is very simpel each field from the source IDoc is mapped to the same field in the target IDoc.

Maybe the problem ist because of the different SAP releases (we send from an 4.6C to an 4.7) ?

[former_member185751]

Hi,

Just your cache notifications in IB.

Regards,

Sridhar

[Former Member]

Hi,

Pls check the following:

1. tx: SXI_CACHE

Make sure the mapping objects are present.

2. tx: SM59

check in "TCP/IP Connections", make sure all the RFC destinations starting with "AI*" has UNICODE selected.

Bill

[Former Member]

Hi all,

I have found "exactly" the same issue than our colleague. Just let you know that my problem was with the RFC destinations marked as NON-UNICODE (my fault ).

regards,

David R.