Mapping exception in RWB in an ICO SOAP(with XI) to SOAP scenario in PI 7.11

[Former Member]

Hi Experts,

We are facing the below error while trying to post a to a webservice using SOAP. The scenario is from ECC to a third party. SOAP(with XI) to SOAP using ICO. When we trigger the payload using sproxy in dev landscpae it works fine. However in production, it fails with below error:

Execution of mapping failed. Reason: MappingException: 205

Transmitting the message to endpoint <local> using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.service.mapping.MappingException: 205.

Config and design is same in both landscapes. Please advise.

Regards,

Sriram

[Former Member · Accepted solution]

Hi All,

The issue was resolved after transporting all objects of the SWCV again. Some how this SWCV was not reflecting in the mapping run time cache.

Regards,

Sriram

[Former Member]

Hi,

if possible try to execute the mapping in prod system esr..as you mentioned it's simple one..shouldn't cause any harm...

HTH

Rajesh

[former_member190624]

Hi Sriram,

Try to regenerate ECC proxy interface class in SPROXY and make sure Operation mapping is having correct request message mapping and correct response message mapping.

Thanks

Hari.

[siddhardha_dnk]

Hi Sriram,

It would be better to analyze if you provide some screens.

Mean time, Compare Source Payload in Dev System and Pro System. There should be some difference in header nodes.

Regards,

Sid.

[Former Member]

Hi Siddartha,

I triggered the same payload as prod through SPROXY in Dev environment.  Just to let you know the scenario is that we trigger a outbound proxy message from ECC which consists of four fields, most of them directly mapped in PI. One of the fields contains a file which is base 64 encoded and zipped from ECC and send to PI in a field. This works fine(same content/payload/config/design) in Dev. But throws the aforementioned error in Prod.

Please advise.

Regards,
Sriram

[siddhardha_dnk]

HI Sriram,

1. Compare versions of your Message Mappings and Operaration Mappings in DEV and PRO.

2. Compare payloads in Receiver Grouping step in SXMB_MONI for this particular message in DEV and PRO (if  Dual Stack).

3. Compare Interface Determination (if Dual Stack) or (if Single Stack) in ID.

Regards,

Sid.

[Former Member]

Hi Sid,

1. Version IDs are same.

2. Payloads are same. Its using AAE so can check only ECC and RWB in PI.

3. Using ICO..

regards,

Sriram

[siddhardha_dnk]

Hi Sriram,

Can you provide some screens of source message from RWB in DEV and PRO.

--> My suggestion in the last message should be

3. Compare Interface Determination (if Dual Stack) or Integrated Configuration(if Single Stack) in ID, whether using same Operational Mapping or not.

Regards,

Sid.

[Former Member]

Hi Sid,

Its using the same operation mapping. Pls confirm what screen shot you require coz i have pasted the error as it is..

Regards,

Sriram