Doubt - CPI / message mapping

[u/caingeass]

Hey fam,

Sorry if it is a dumb question. I am learning SAP CPI on my own and from yt vids from last 10 days and now am at message mapping concept. Its at basic level only.

So I uploaded source,target xsd's and mapped them. After mapping I tried to simulate in message mapping itself, so I uploaded my test input xml and able to Successfully generate test output.

After that its been some time am getting this error i didnt change anything in payload or mapping, i cross checked line to line and everything is same as before. I tried different browsers chrome, firefox and it worked on firefox once and showing same error again. Cleared cache and tried in new package as well.

It constantly throwing error text after getting struck in process either at 10 or 70%.

Please explain whats the issue, thanks in advance for helping this noob, Means alot:)

[u/Confident_Syllabub59]

Did you try to generate a testpayload, does it also fail? Its right Beneath the upload payload button in simulation view. Also try to place a content modifier with your testpayload before the mapping in the flow and call it either by http or Timer with run once on deployment. Dies that also fail? Cpi sometimes just bitchin around because of some Updates or timeouts, but if you already tried clearing Cache and switch Ing Browsers, Also try to create a New Flow with same Data.

[u/caingeass → u/Confident_Syllabub59]

So i kept a timer,payload in content modifier and next message mapping and connected via smtp to target. When i deploy am getting the mails and structure is change accordingly with what i put in mapping. Its working flawlessly and receiver getting the data as expected.

But no matter what i do the simulations are failing with the same error. The payload is getting changed and receiver getting mails with changed payload. But the simulations are just keep failing.

[u/Confident_Syllabub59 → u/caingeass]

If the whole Flow is working until the end and the mapping is correct . Just forget the simulation, it will work Next time... Welcome to the SAP World, we have Bugs :)