Multimapping problem

[Former Member]

Hi all,

I have got the following problem with multimapping:

In a <b>source message1</b> is on the sixth context one element. Is the content of this source field is 'A' so a <b>target field1</b> has to be 'A'. But if the content of the source field is 'B', so a <b>target field2</b> has to be filled with a field of a second <b>source message2</b>. The field of the source feld2 is on the second context.

I ve got only a correct result if 'B' is first processes. If i change the context of the source fields so the results of the second entries are lost.

Are there any tips or blogs?

Regards

Mathias

[agasthuri_doss]

Hi,

This Blog might help

BPM involved:

/people/sudharshan.aravamudan/blog/2005/12/01/illustration-of-multi-mapping-and-message-split-using-bpm-in-sap-exchange-infrastructure

/people/narendra.jain/blog/2005/12/30/various-multi-mappings-and-optimizing-their-implementation-in-integration-processes-bpm-in-xi

Without BPM:

/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible

Regards

Agasthuri Doss

[Former Member]

Mathias,

Your requirement is not very clear. Can you give the source and target structures? with a bit more explanation?

Regards,

Jai Shankar

[Former Member]

Hello Jai,

in source message1 are under the node pet_files three items.

If the ABLTYP = SIG or RDOC so in target structure message1-exchange-request-body-files-file the field BINARYDATA has to filled with source field CONTENT. But if the ABLTYP = XML, so the field XMLDATA has to field with source Message3-rechnung-zuordnungsnummer (e.g.)

The target:

<?xml version="1.0" encoding="UTF-8"?>

<ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge"><ns0:Message1><ns4:Exchange xmlns:ns4="http://capevision/2006/11/DocumentService"><ns5:Request xmlns:ns5="http://capevision/2006/11/DocumentService.Exchange/1.0"><ns5:Header><ns5:Identification>4711</ns5:Identification></ns5:Header><ns5:Body><ns6:Files xmlns:ns6="http://capevision/2006/11/Basic/1.0"><ns6:File><ns6:Name>SIG_filename</ns6:Name><ns6:Type>SIG</ns6:Type><ns6:BinaryData>SIG_content</ns6:BinaryData></ns6:File><ns6:File><ns6:Name>rdoc_name</ns6:Name><ns6:Type>RDOC</ns6:Type><ns6:BinaryData>rdoc_content</ns6:BinaryData></ns6:File><ns6:File><ns6:Name>XML_name</ns6:Name><ns6:Type>XML</ns6:Type></ns6:File></ns6:Files></ns5:Body></ns5:Request></ns4:Exchange></ns0:Message1></ns0:Messages>

The source:

<?xml version="1.0" encoding="UTF-8"?>

<ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">

<ns0:Message1>

<ns1:Z_ERAPE_READ_BILLDOC_BIN.Response xmlns:ns1="urn:sap-com:document:sap:rfc:functions">

<PET_FILES>

<item>

<ABLTYP>SIG</ABLTYP>

<FILE_NUM/>

<FILE_NAME>SIG_filename</FILE_NAME>

<COMP_ID/>

<COMP_SIZE/>

<MIMETYPE/>

<CREA_TIME/>

<CHNG_TIME/>

<CONTENT>SIG_content</CONTENT>

</item>

<item>

<ABLTYP>RDOC</ABLTYP>

<FILE_NUM/>

<FILE_NAME>rdoc_name</FILE_NAME>

<COMP_ID/>

<COMP_SIZE/>

<MIMETYPE/>

<CREA_TIME/>

<CHNG_TIME/>

<CONTENT>rdoc_content</CONTENT>

</item>

<item>

<ABLTYP>XML</ABLTYP>

<FILE_NUM/>

<FILE_NAME>XML_name</FILE_NAME>

<COMP_ID/>

<COMP_SIZE/>

<MIMETYPE/>

<CREA_TIME/>

<CHNG_TIME/>

<CONTENT>xml_content</CONTENT>

</item>

</PET_FILES>

<PE_RETURN>

<TYPE/>

<ID/>

<NUMBER/>

<MESSAGE/>

<LOG_NO/>

<LOG_MSG_NO/>

<MESSAGE_V1/>

<MESSAGE_V2/>

<MESSAGE_V3/>

<MESSAGE_V4/>

<PARAMETER/>

<ROW/>

<FIELD/>

<SYSTEM/>

</PE_RETURN>

</ns1:Z_ERAPE_READ_BILLDOC_BIN.Response>

</ns0:Message1>

<ns0:Message2>

<ns2:MT_ProcessDocument xmlns:ns2="http://www.gasag.de/brda">

<RATYP/>

<RECHNR/>

<DRUCKNR/>

<STATUS/>

<IDENTIFICATION>4711</IDENTIFICATION>

<ANZ_START/>

</ns2:MT_ProcessDocument>

</ns0:Message2>

<ns0:Message3>

<ns3:Rechnung Rechnungsdatum="" Rechnungstyp="3" Dokumentname="4" Zuordnungsnummer="5" Rechnungsnummer="6" RefRechnungsnummer="7" Waehrung="2" xmlns:ns3="http://capevision/2006/11/Invoice.Exchange/1.0">

<ns3:Rechnungssteller Referenznummer="">

<ns3:Name/>

<ns3:Strasse/>

<ns3:Hausnummer/>

<ns3:Postfach/>

<ns3:Postleitzahl/>

<ns3:Ort/>

</ns3:Rechnungssteller>

<ns3:Rechnungsempfaenger Vertragskonto="">

<ns3:Name/>

<ns3:Strasse/>

<ns3:Hausnummer/>

<ns3:Postfach/>

<ns3:Postleitzahl/>

<ns3:Ort/>

<ns3:Bankverbindung Kennzeichnung_Bankeinzug="">

<ns3:Kontonummer/>

<ns3:Kontoinhaber/>

<ns3:Bankleitzahl/>

</ns3:Bankverbindung>

</ns3:Rechnungsempfaenger>

<ns3:Verbrauchsstelle>

<ns3:Name/>

<ns3:Strasse/>

<ns3:Hausnummer/>

<ns3:Postfach/>

<ns3:Postleitzahl/>

<ns3:Ort/>

</ns3:Verbrauchsstelle>

<ns3:Verbrauchszeitraum>

<ns3:von/>

<ns3:bis/>

</ns3:Verbrauchszeitraum>

<ns3:Rechnungsposition Nr="" bis="" von="">

<ns3:Leistungsart/>

<ns3:Menge/>

<ns3:Masseinheit/>

<ns3:Positionsbetrag>

<ns3:Steuer Schluessel="">

<ns3:Prozent/>

</ns3:Steuer>

<ns3:Bruttobetrag/>

<ns3:Nettobetrag/>

</ns3:Positionsbetrag>

</ns3:Rechnungsposition>

<ns3:Endbetrag Faelligkeit="">

<ns3:Steuer Schluessel="">

<ns3:Prozent/>

<ns3:Betrag/>

</ns3:Steuer>

<ns3:Bruttobetrag/>

<ns3:Nettobetrag/>

<ns3:Verrechnet Bezug=""/>

<ns3:Restbetrag/>

</ns3:Endbetrag>

<ns3:Zukuenftige_Faelligkeit Datum="" Leistungsart="">

<ns3:Steuer Schluessel="">

<ns3:Prozent/>

<ns3:Betrag/>

</ns3:Steuer>

<ns3:Bruttobetrag/>

<ns3:Nettobetrag/>

</ns3:Zukuenftige_Faelligkeit>

</ns3:Rechnung>

</ns0:Message3>

</ns0:Messages>