Error while Adding Message Mapping in cpi iflow

[Akash]

Hi,

When i add Message Mapping step in iflow then it showing this kind of error

[Ryan-Crosby]

What is the source payload for your message mapping?

[Akash]

the error is coming during testing

[clinito]

If Header CancInvSet only occurs once then map Constant "". If it occurs multiple time you need to map it with the source field of the correct context/occurrences.

[MaAll]

Hi Akash,

To get a more complete answer, I think you'll need to provide more information on what the mapping looks like for the CancInvSet element.

The short answer is that you're not creating an entry for the element CancInvSet which is mandatory in the target message. The cause of this is very dependent on the message mapping itself, so it's difficult to speculate without more details.

An initial simple fix to remove the error is to map a constant as was suggested in the first answer, but if it's a mandatory field, then usually I'd expect a value would be expected in the receiving system.

[Akash]

Please see the attachment.

[MaAll]

Hi Akash,

The message mapping looks like a simple mapping and technically correct. Can you confirm that the source structure you've used in the mapping for the CancInvSet is the same structure as the response message from the request reply 1 step?

When to you get the error message? Is it during save/deployment or is it when testing?

[joel_langoyan]

Akash,

You don't have to map your root node CanInvSet as already 1..1 occurrence. Remove the mapping and your message mapping would work fine.