Multi-Mappings in BPM (XI 3.0)

[Former Member]

Hello,

I´am trying to create a multi-mapping to merge a list of messages into one single message.

Does anyone know if there is a multi-mapping testing environment ?

If I test the multi-mapping in the normal message mapping test environment every things is fine - nevertheless I get a mapping error during workflow runtime.

Thanks a lot for your comments,

René de Daniel

[STALANKI]

We configured the same scenario with the concept of idoc packages.Try to import the target structure xsd from data type editor and change the <xsd:element name="IDOC" type="PROACT01" minOccurs="0" maxOccurs="unbounded" /> and then re-import it as an external definition.Change the target message in the message and interface mapping accordingly and map the E1EDP1 segment to the proact and change the context of E1EDP1 segment to message1 in the mapping editor.revert to me incase of any problem as we are able to do without message mapping itself.

[Former Member]

Hi Rene,

Did you solve your problem with multi-mapping? Are you using message mapping or XSLT?

We are facing a similar issue using an XSLT stylesheet to merge two

messages into one. The mapping always fails in bpm. No output is generated.

-Simon

[Former Member]

Hello,

Namespace could be missing in the message that is being passed to XI. In that case mapping will fail at runtime. In testing environment, namespace will be automatically available in the message and hence the test will be succesful. May be you should check whether namespace is provided in the inbound message to XI.

Regards

Rampi.

[Former Member]

Hello,

I'm trying to splitt up an Idoc to several idoc:s of the same type (PROACT01). I would like to create a new IDoc per line item segment (E1EDP31). But I do not get it to work? I get the following error:

12:05:00 Start of test

Cannot produce target element /ns:Messages/ns:Message1/PROACT01[2]/IDOC. Check xml instance is valid for source xsd and target-field mapping fulfills requirements of target xsd

12:05:16 End of test

The segment has occurance 0-9999 and the Proact is 0-unbounded.

Brgds

Kalle

[Former Member]

Hi Karl,

The problem is not with PROACT element, but IDOC. What occurence does it have? What have mapped to it? The message says you have not enougth source elements for IDOC tag. seems like you have mapped some node which occurs exactly once to it, for example root tag.

Regards,

Alexey

[Former Member]

Hello Alexey,

The Idoc element has occurance 1, and it is mapped to the Idoc element of the source structure. It seems that it is trying to create a second IDoc element, but I want it to be n target Idoc:s based on number of segments (E1EDP31) of the source IDoc.

Brgds

Kalle

[Former Member]

Hi Karl,

It tries to create an IDOC element in the second PROACT element and fails, because the source structure contains exactly one IDOC element, while the result document must have as many IDOC elements as there are PROACT elements. In 99% of the cases when a target node has minOccurs=maxOccurs=1, the best thing you can do about it is to leave mapping blanck, i.e. map nothing to it, then you won't get such problems in runtime. If you really want to map something to it you should map a node, which occurs in source document exactly the number of times, that the target node must occur in result document. In your case it would be E1EDP31 but you should not map it directly to IDoc, but through a SplitByValue function.

Best regards,

Alexey