Multimapping Problem - PI 7.0
Hi,
To interface with a web service created in a BMC Remedy platfrom I need to create a Soap Envelope as detailed below:
<soapenv: envelopeu2026.>
<soapenv: header>
<urn:AuthenticationInfo>
<user nameu2026>
<passwordu2026>
u2026etc
</urn:AuthenticationInfo>
</soapenv: header>
<soapenv: body>
<urn:ReceiveCallsFromRemedyDev>
<categoryu2026.>
<Locationu2026>
<callerNameu2026>
u2026.etc
</urn:ReceiveCallsFromRemedyDev>
</soapenv:body>
</soapenv:envelope>
AuthenticationInfo and ReceiveCallsFromRemedyDev are separate message types.
Does anyone know how or if indeed it is possible to to get two message types into one soap envelope in 7.0. At the moment I am not even sure how to send two message types to the same inbound interface.
Any help would be appreciated.
PaulC.
>
paul clements wrote:
> Thanks for the link.
>
> Unfortunately I can't access it due to Firewall restrictions at my workplace. Could you paste the contents into this thread or provide a similar link to something on a SAP site ?
Sorry.... in future i've to create a sap blog (the link refer to my personal blog...)
This is the sample code:
<xsl:stylesheet version=u201D1.0u2033 xmlns:xsl=u201Dhttp://www.w3.org/1999/XSL/Transformu201D>
<xsl:template match=u201D/u201D>
<soap:Envelope xmlns:soap=u201Dhttp://schemas.xmlsoap.org/soap/envelope/u201D xmlns:xsi=u201Dhttp://www.w3.org/2001/XMLSchema-instanceu201D xmlns:xsd=u201Dhttp://www.w3.org/2001/XMLSchemau201D>
<soap:Header>
<ServiceAuthHeader xmlns=u201Dhttp://test.webservice.it/u201D>
<Username>USERNAME</Username>
<Password>PASSWORD</Password>
</ServiceAuthHeader>
</soap:Header>
<soap:Body>
<xsl:copy-of select=u201D*u201D/>
</soap:Body>
</soap:Envelope>
</xsl:template>
</xsl:stylesheet>
Similar Messages
-
Hi,
I did multimapping without a Bpm.
I reffered the following blog
/people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
I'm getting the below stach trace in moni.
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">GENERIC</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM_MULTI_MAPPING_</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
<SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>com/sap/xi/tf/_MM_MULTI_MAPPING_com.sap.aii.utilxi.misc.api.BaseRuntimeExceptionRuntimeException in Message-Mapping transformatio~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
wat wud be the problem?In your source data file do you tags like </ns0:Messages> <ns0:Message1> ... if yes then remove these and corresponding end tags before placing a file.
In IR while testing mapping , you need these tags but not while testing end to end
Also check if all mandatory elements at target are getting corresponding source value -
Problem with Multimapping with out using BPM
Hi All,
Here i have face a problem when working with multi mapping.
For example I explain u with the following example.
<Message1>
<Employee>
<Eno>
<Ename>
</Employee>
</Message1>
<Message2>
<City>
<Address>
<Dno>
</City>
</Message2>
Message1,Employee,Message2,City are mapped with constant("").
Here my aim is to create 2 different files with the format as xml structure.
One file with -
<Message1>
Second file with ---<Message2>
this my example... Now I am explaining where i encountered problem in runtime.
Error: Mapping exception
Can not produce target element <Employee>....
Hint: Iam presently using service pack-9.
can one one assist....Hi,
The problem is in the mapping, you need to check the mapping..
1) did you change the occurence of the messages for the multimapping.. Go to Mapping-->Messages (Tab) and change the occurence of the messages
2) Check the all fields,segments are mapped correctly
3) Test the mapping
4) Check the occurence of the Interface Mapping, and test it in the integration respository
5) check the Source Message Structure and make sure that, it is a valid input to your mapping rules..
Hope this helps,
Regards,
Moorthy -
Hi ,
I am trying to map a idoc to a falt file using multimapping .
I have two interfaces ...Header and item respectively.
the idoc I am using is DESADV./AFS/DELVRY03.ZASNDELVRY03.
It has the following kind of structure .
Single Idoc .
Multiple headers ...
Multiple lines items...
Such that the target looks like
Messages .
Message1.....
header.....
Message2..
Item...
The problem that I am facing is that when I test my mapping ...
for two headers and there corresponding 2 line items (2 for each header)
I get two headers in the target .
But I get only line items for the the first header only<b>Source</b>
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
<ns0:Message1>
<ZASNDELVRY03>
<IDOC BEGIN="1">
<EDI_DC40 SEGMENT="1">
<TABNAM>EDI_DC40</TABNAM>
<MANDT>100</MANDT>
<DOCNUM>0000000002165287</DOCNUM>
<DOCREL>640</DOCREL>
<STATUS>30</STATUS>
<DIRECT>1</DIRECT>
<OUTMOD>4</OUTMOD>
<IDOCTYP>/AFS/DELVRY03</IDOCTYP>
<CIMTYP>ZASNDELVRY03</CIMTYP>
<MESTYP>DESADV</MESTYP>
<MESCOD>ASN</MESCOD>
<SNDPOR>SAPJEP</SNDPOR>
<SNDPRT>LS</SNDPRT>
<SNDPRN>JEPCLNT100</SNDPRN>
<RCVPOR>WM242_ASN</RCVPOR>
<RCVPRT>LS</RCVPRT>
<RCVPRN>WM242</RCVPRN>
<CREDAT>20070130</CREDAT>
<CRETIM>160420</CRETIM>
<SERIAL>20070130160418</SERIAL>
</EDI_DC40>
<E1EDL20 SEGMENT="1">
<VBELN>180007392</VBELN>
<ZASN_HDR SEGMENT="1">
<ASNTY>3</ASNTY>
<VBELN>180007392</VBELN>
<TOLOC>15</TOLOC>
<WHTRF>N</WHTRF>
<QCHLD>N</QCHLD>
<OUTSF>Y</OUTSF>
<BOLNR>NOSU4347279</BOLNR>
<LIFNR>0001000088</LIFNR>
<CSSHP>0000000</CSSHP>
<LFIMG> 275.0000</LFIMG>
<SHPDT>000000000</SHPDT>
<SSRDT>020070130</SSRDT>
<SCODE>10</SCODE>
<MISC1>32</MISC1>
<MISC3>60</MISC3>
<FCODE>1</FCODE>
</ZASN_HDR>
<E1EDL24 SEGMENT="1">
<POSNR>00001</POSNR>
<ZASN_ITM SEGMENT="1">
<ASNTY>3</ASNTY>
<VBELN>180007392</VBELN>
<VGBEL>AW2026121</VGBEL>
<VGPOS>000010</VGPOS>
<CMPNY>01</CMPNY>
<DIVSN>01</DIVSN>
<STYLE>60000769</STYLE>
<COLOR>358</COLOR>
<SZRCD>M-1</SZRCD>
<SZRPO>11</SZRPO>
<SEQNR>00001</SEQNR>
<ASIZE>4</ASIZE>
<INVTY>F</INVTY>
<IPQTY> 25.0000</IPQTY>
<CSSHP>0000000</CSSHP>
<LFIMG> 23.0000</LFIMG>
<SCQTY> 0.0000</SCQTY>
<IMIND>Y</IMIND>
<SCODE>10</SCODE>
<REFR1>900001</REFR1>
<MISC1>32</MISC1>
<MISC2>01</MISC2>
<MISC3>60</MISC3>
<MISCN> 0.00000</MISCN>
<FCODE>1</FCODE>
</ZASN_ITM>
</E1EDL24>
<E1EDL24 SEGMENT="1">
<POSNR>00002</POSNR>
<ZASN_ITM SEGMENT="1">
<ASNTY>3</ASNTY>
<VBELN>180007392</VBELN>
<VGBEL>AW2026121</VGBEL>
<VGPOS>000010</VGPOS>
<CMPNY>01</CMPNY>
<DIVSN>01</DIVSN>
<STYLE>60000769</STYLE>
<COLOR>358</COLOR>
<SZRCD>M-1</SZRCD>
<SZRPO>12</SZRPO>
<SEQNR>00002</SEQNR>
<ASIZE>6</ASIZE>
<INVTY>F</INVTY>
<IPQTY> 25.0000</IPQTY>
<CSSHP>0000000</CSSHP>
<LFIMG> 38.0000</LFIMG>
<SCQTY> 0.0000</SCQTY>
<IMIND>Y</IMIND>
<SCODE>10</SCODE>
<REFR1>900002</REFR1>
<MISC1>32</MISC1>
<MISC2>01</MISC2>
<MISC3>60</MISC3>
<MISCN> 0.00000</MISCN>
<FCODE>1</FCODE>
</ZASN_ITM>
</E1EDL24>
<E1EDL24 SEGMENT="1">
<POSNR>00003</POSNR>
<ZASN_ITM SEGMENT="1">
<ASNTY>3</ASNTY>
<VBELN>180007392</VBELN>
<VGBEL>AW2026121</VGBEL>
<VGPOS>000010</VGPOS>
<CMPNY>01</CMPNY>
<DIVSN>01</DIVSN>
<STYLE>60000769</STYLE>
<COLOR>358</COLOR>
<SZRCD>M-1</SZRCD>
<SZRPO>13</SZRPO>
<SEQNR>00003</SEQNR>
<ASIZE>8</ASIZE>
<INVTY>F</INVTY>
<IPQTY> 25.0000</IPQTY>
<CSSHP>0000000</CSSHP>
<LFIMG> 42.0000</LFIMG>
<SCQTY> 0.0000</SCQTY>
<IMIND>Y</IMIND>
<SCODE>10</SCODE>
<REFR1>900003</REFR1>
<MISC1>32</MISC1>
<MISC2>01</MISC2>
<MISC3>60</MISC3>
<MISCN> 0.00000</MISCN>
<FCODE>1</FCODE>
</ZASN_ITM>
</E1EDL24>
<E1EDL24 SEGMENT="1">
<POSNR>00004</POSNR>
<ZASN_ITM SEGMENT="1">
<ASNTY>3</ASNTY>
<VBELN>180007392</VBELN>
<VGBEL>AW2026121</VGBEL>
<VGPOS>000010</VGPOS>
<CMPNY>01</CMPNY>
<DIVSN>01</DIVSN>
<STYLE>60000769</STYLE>
<COLOR>358</COLOR>
<SZRCD>M-1</SZRCD>
<SZRPO>02</SZRPO>
<SEQNR>00004</SEQNR>
<ASIZE>10</ASIZE>
<INVTY>F</INVTY>
<IPQTY> 25.0000</IPQTY>
<CSSHP>0000000</CSSHP>
<LFIMG> 62.0000</LFIMG>
<SCQTY> 0.0000</SCQTY>
<IMIND>Y</IMIND>
<SCODE>10</SCODE>
<REFR1>900004</REFR1>
<MISC1>32</MISC1>
<MISC2>01</MISC2>
<MISC3>60</MISC3>
<MISCN> 0.00000</MISCN>
<FCODE>1</FCODE>
</ZASN_ITM>
</E1EDL24>
<E1EDL24 SEGMENT="1">
<POSNR>00005</POSNR>
<ZASN_ITM SEGMENT="1">
<ASNTY>3</ASNTY>
<VBELN>180007392</VBELN>
<VGBEL>AW2026121</VGBEL>
<VGPOS>000010</VGPOS>
<CMPNY>01</CMPNY>
<DIVSN>01</DIVSN>
<STYLE>60000769</STYLE>
<COLOR>358</COLOR>
<SZRCD>M-1</SZRCD>
<SZRPO>03</SZRPO>
<SEQNR>00005</SEQNR>
<ASIZE>12</ASIZE>
<INVTY>F</INVTY>
<IPQTY> 25.0000</IPQTY>
<CSSHP>0000000</CSSHP>
<LFIMG> 50.0000</LFIMG>
<SCQTY> 0.0000</SCQTY>
<IMIND>Y</IMIND>
<SCODE>10</SCODE>
<REFR1>900005</REFR1>
<MISC1>32</MISC1>
<MISC2>01</MISC2>
<MISC3>60</MISC3>
<MISCN> 0.00000</MISCN>
<FCODE>1</FCODE>
</ZASN_ITM>
</E1EDL24>
<E1EDL24 SEGMENT="1">
<POSNR>00006</POSNR>
<ZASN_ITM SEGMENT="1">
<ASNTY>3</ASNTY>
<VBELN>180007392</VBELN>
<VGBEL>AW2026121</VGBEL>
<VGPOS>000010</VGPOS>
<CMPNY>01</CMPNY>
<DIVSN>01</DIVSN>
<STYLE>60000769</STYLE>
<COLOR>358</COLOR>
<SZRCD>M-1</SZRCD>
<SZRPO>04</SZRPO>
<SEQNR>00006</SEQNR>
<ASIZE>14</ASIZE>
<INVTY>F</INVTY>
<IPQTY> 25.0000</IPQTY>
<CSSHP>0000000</CSSHP>
<LFIMG> 34.0000</LFIMG>
<SCQTY> 0.0000</SCQTY>
<IMIND>Y</IMIND>
<SCODE>10</SCODE>
<REFR1>900006</REFR1>
<MISC1>32</MISC1>
<MISC2>01</MISC2>
<MISC3>60</MISC3>
<MISCN> 0.00000</MISCN>
<FCODE>1</FCODE>
</ZASN_ITM>
</E1EDL24>
<E1EDL24 SEGMENT="1">
<POSNR>00007</POSNR>
<ZASN_ITM SEGMENT="1">
<ASNTY>3</ASNTY>
<VBELN>180007392</VBELN>
<VGBEL>AW2026121</VGBEL>
<VGPOS>000010</VGPOS>
<CMPNY>01</CMPNY>
<DIVSN>01</DIVSN>
<STYLE>60000769</STYLE>
<COLOR>358</COLOR>
<SZRCD>M-1</SZRCD>
<SZRPO>05</SZRPO>
<SEQNR>00007</SEQNR>
<ASIZE>16</ASIZE>
<INVTY>F</INVTY>
<IPQTY> 25.0000</IPQTY>
<CSSHP>0000000</CSSHP>
<LFIMG> 26.0000</LFIMG>
<SCQTY> 0.0000</SCQTY>
<IMIND>Y</IMIND>
<SCODE>10</SCODE>
<REFR1>900007</REFR1>
<MISC1>32</MISC1>
<MISC2>01</MISC2>
<MISC3>60</MISC3>
<MISCN> 0.00000</MISCN>
<FCODE>1</FCODE>
</ZASN_ITM>
</E1EDL24>
</E1EDL20>
<E1EDL20 SEGMENT="2">
<VBELN>180007393</VBELN>
<ZASN_HDR SEGMENT="2">
<ASNTY>3</ASNTY>
<VBELN>180007393</VBELN>
<TOLOC>15</TOLOC>
<WHTRF>N</WHTRF>
<QCHLD>N</QCHLD>
<OUTSF>Y</OUTSF>
<BOLNR>NOSU4347279</BOLNR>
<LIFNR>0001000088</LIFNR>
<CSSHP>0000000</CSSHP>
<LFIMG> 275.0000</LFIMG>
<SHPDT>000000000</SHPDT>
<SSRDT>020070130</SSRDT>
<SCODE>10</SCODE>
<MISC1>32</MISC1>
<MISC3>60</MISC3>
<FCODE>1</FCODE>
</ZASN_HDR>
<E1EDL24 SEGMENT="2">
<POSNR>00001</POSNR>
<ZASN_ITM SEGMENT="1">
<ASNTY>3</ASNTY>
<VBELN>180007393</VBELN>
<VGBEL>AW2026121</VGBEL>
<VGPOS>000010</VGPOS>
<CMPNY>01</CMPNY>
<DIVSN>01</DIVSN>
<STYLE>60000769</STYLE>
<COLOR>358</COLOR>
<SZRCD>M-1</SZRCD>
<SZRPO>11</SZRPO>
<SEQNR>00001</SEQNR>
<ASIZE>4</ASIZE>
<INVTY>F</INVTY>
<IPQTY> 25.0000</IPQTY>
<CSSHP>0000000</CSSHP>
<LFIMG> 23.0000</LFIMG>
<SCQTY> 0.0000</SCQTY>
<IMIND>Y</IMIND>
<SCODE>10</SCODE>
<REFR1>900001</REFR1>
<MISC1>32</MISC1>
<MISC2>01</MISC2>
<MISC3>60</MISC3>
<MISCN> 0.00000</MISCN>
<FCODE>1</FCODE>
</ZASN_ITM>
</E1EDL24>
<E1EDL24 SEGMENT="2">
<POSNR>00002</POSNR>
<ZASN_ITM SEGMENT="2">
<ASNTY>3</ASNTY>
<VBELN>180007393</VBELN>
<VGBEL>AW2026121</VGBEL>
<VGPOS>000010</VGPOS>
<CMPNY>01</CMPNY>
<DIVSN>01</DIVSN>
<STYLE>60000769</STYLE>
<COLOR>358</COLOR>
<SZRCD>M-1</SZRCD>
<SZRPO>12</SZRPO>
<SEQNR>00002</SEQNR>
<ASIZE>6</ASIZE>
<INVTY>F</INVTY>
<IPQTY> 25.0000</IPQTY>
<CSSHP>0000000</CSSHP>
<LFIMG> 38.0000</LFIMG>
<SCQTY> 0.0000</SCQTY>
<IMIND>Y</IMIND>
<SCODE>10</SCODE>
<REFR1>900002</REFR1>
<MISC1>32</MISC1>
<MISC2>01</MISC2>
<MISC3>60</MISC3>
<MISCN> 0.00000</MISCN>
<FCODE>1</FCODE>
</ZASN_ITM>
</E1EDL24>
<E1EDL24 SEGMENT="2">
<POSNR>00003</POSNR>
<ZASN_ITM SEGMENT="2">
<ASNTY>3</ASNTY>
<VBELN>180007393</VBELN>
<VGBEL>AW2026121</VGBEL>
<VGPOS>000010</VGPOS>
<CMPNY>01</CMPNY>
<DIVSN>01</DIVSN>
<STYLE>60000769</STYLE>
<COLOR>358</COLOR>
<SZRCD>M-1</SZRCD>
<SZRPO>13</SZRPO>
<SEQNR>00003</SEQNR>
<ASIZE>8</ASIZE>
<INVTY>F</INVTY>
<IPQTY> 25.0000</IPQTY>
<CSSHP>0000000</CSSHP>
<LFIMG> 42.0000</LFIMG>
<SCQTY> 0.0000</SCQTY>
<IMIND>Y</IMIND>
<SCODE>10</SCODE>
<REFR1>900003</REFR1>
<MISC1>32</MISC1>
<MISC2>01</MISC2>
<MISC3>60</MISC3>
<MISCN> 0.00000</MISCN>
<FCODE>1</FCODE>
</ZASN_ITM>
</E1EDL24>
<E1EDL24 SEGMENT="2">
<POSNR>00004</POSNR>
<ZASN_ITM SEGMENT="1">
<ASNTY>3</ASNTY>
<VBELN>180007393</VBELN>
<VGBEL>AW2026121</VGBEL>
<VGPOS>000010</VGPOS>
<CMPNY>01</CMPNY>
<DIVSN>01</DIVSN>
<STYLE>60000769</STYLE>
<COLOR>358</COLOR>
<SZRCD>M-1</SZRCD>
<SZRPO>02</SZRPO>
<SEQNR>00004</SEQNR>
<ASIZE>10</ASIZE>
<INVTY>F</INVTY>
<IPQTY> 25.0000</IPQTY>
<CSSHP>0000000</CSSHP>
<LFIMG> 62.0000</LFIMG>
<SCQTY> 0.0000</SCQTY>
<IMIND>Y</IMIND>
<SCODE>10</SCODE>
<REFR1>900004</REFR1>
<MISC1>32</MISC1>
<MISC2>01</MISC2>
<MISC3>60</MISC3>
<MISCN> 0.00000</MISCN>
<FCODE>1</FCODE>
</ZASN_ITM>
</E1EDL24>
<E1EDL24 SEGMENT="2">
<POSNR>00005</POSNR>
<ZASN_ITM SEGMENT="2">
<ASNTY>3</ASNTY>
<VBELN>180007393</VBELN>
<VGBEL>AW2026121</VGBEL>
<VGPOS>000010</VGPOS>
<CMPNY>01</CMPNY>
<DIVSN>01</DIVSN>
<STYLE>60000769</STYLE>
<COLOR>358</COLOR>
<SZRCD>M-1</SZRCD>
<SZRPO>03</SZRPO>
<SEQNR>00005</SEQNR>
<ASIZE>12</ASIZE>
<INVTY>F</INVTY>
<IPQTY> 25.0000</IPQTY>
<CSSHP>0000000</CSSHP>
<LFIMG> 50.0000</LFIMG>
<SCQTY> 0.0000</SCQTY>
<IMIND>Y</IMIND>
<SCODE>10</SCODE>
<REFR1>900005</REFR1>
<MISC1>32</MISC1>
<MISC2>01</MISC2>
<MISC3>60</MISC3>
<MISCN> 0.00000</MISCN>
<FCODE>1</FCODE>
</ZASN_ITM>
</E1EDL24>
<E1EDL24 SEGMENT="2">
<POSNR>00006</POSNR>
<ZASN_ITM SEGMENT="2">
<ASNTY>3</ASNTY>
<VBELN>180007393</VBELN>
<VGBEL>AW2026121</VGBEL>
<VGPOS>000010</VGPOS>
<CMPNY>01</CMPNY>
<DIVSN>01</DIVSN>
<STYLE>60000769</STYLE>
<COLOR>358</COLOR>
<SZRCD>M-1</SZRCD>
<SZRPO>04</SZRPO>
<SEQNR>00006</SEQNR>
<ASIZE>14</ASIZE>
<INVTY>F</INVTY>
<IPQTY> 25.0000</IPQTY>
<CSSHP>0000000</CSSHP>
<LFIMG> 34.0000</LFIMG>
<SCQTY> 0.0000</SCQTY>
<IMIND>Y</IMIND>
<SCODE>10</SCODE>
<REFR1>900006</REFR1>
<MISC1>32</MISC1>
<MISC2>01</MISC2>
<MISC3>60</MISC3>
<MISCN> 0.00000</MISCN>
<FCODE>1</FCODE>
</ZASN_ITM>
</E1EDL24>
<E1EDL24 SEGMENT="2">
<POSNR>00007</POSNR>
<ZASN_ITM SEGMENT="2">
<ASNTY>3</ASNTY>
<VBELN>180007393</VBELN>
<VGBEL>AW2026121</VGBEL>
<VGPOS>000010</VGPOS>
<CMPNY>01</CMPNY>
<DIVSN>01</DIVSN>
<STYLE>60000769</STYLE>
<COLOR>358</COLOR>
<SZRCD>M-1</SZRCD>
<SZRPO>05</SZRPO>
<SEQNR>00007</SEQNR>
<ASIZE>16</ASIZE>
<INVTY>F</INVTY>
<IPQTY> 25.0000</IPQTY>
<CSSHP>0000000</CSSHP>
<LFIMG> 26.0000</LFIMG>
<SCQTY> 0.0000</SCQTY>
<IMIND>Y</IMIND>
<SCODE>10</SCODE>
<REFR1>900007</REFR1>
<MISC1>32</MISC1>
<MISC2>01</MISC2>
<MISC3>60</MISC3>
<MISCN> 0.00000</MISCN>
<FCODE>1</FCODE>
</ZASN_ITM>
</E1EDL24>
</E1EDL20>
</IDOC>
</ZASNDELVRY03>
</ns0:Message1>
</ns0:Messages>
<b>Target</b>
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
<ns0:Message1>
<ns1:Mt_inboundelv_header xmlns:ns1="urn:jag.com.inbounddelv.test01">
<AHPRDT>000000000</AHPRDT>
<AHPRTM>0000000</AHPRTM>
<ADBCTN>0000000002165287</ADBCTN>
<AHASTP>3</AHASTP>
<ADSHMT>180007392</ADSHMT>
<AHTLOC>15</AHTLOC>
<AHTLOC>00</AHTLOC>
<AHTLOC>00</AHTLOC>
<AHTLOC>00</AHTLOC>
<AHTLOC>00</AHTLOC>
<AHTLOC>00</AHTLOC>
<AHTLOC>00</AHTLOC>
<AHTLOC>15</AHTLOC>
<AHTLOC>15</AHTLOC>
<AHTLOC>15</AHTLOC>
<AHTLOC>15</AHTLOC>
<AHTLOC>15</AHTLOC>
<AHTLOC>15</AHTLOC>
<AHTLOC>15</AHTLOC>
<AHWHTF>N</AHWHTF>
<AHQCHD>N</AHQCHD>
<AHOSRC>Y</AHOSRC>
<AHSVIA>0000</AHSVIA>
<AHMANI>0000000000</AHMANI>
<AHBLAD>00000000000000000000</AHBLAD>
<AHTRLN>000000000000</AHTRLN>
<AHPRON>00000000000000000000</AHPRON>
<AHWKON>000000000000</AHWKON>
<AHRCFR>0001000088</AHRCFR>
<AHCSSH>0000000</AHCSSH>
<AHUNSH>000000000000000</AHUNSH>
<AHUNSH>000000000000000</AHUNSH>
<AHUNSH>000000000000000</AHUNSH>
<AHUNSH>000000000000000</AHUNSH>
<AHUNSH>000000000000000</AHUNSH>
<AHUNSH>000000000000000</AHUNSH>
<AHUNSH>000000000000000</AHUNSH>
<AHUNSH>000000000000000</AHUNSH>
<AHUNSH>000000000000000</AHUNSH>
<AHUNSH>000000000000000</AHUNSH>
<AHUNSH>000000000000000</AHUNSH>
<AHUNSH>000000000000000</AHUNSH>
<AHUNSH>000000000000000</AHUNSH>
<AHUNSH>000000000000000</AHUNSH>
<AHSHDT>000000000</AHSHDT>
<AHSSRD>000000000</AHSSRD>
<AHSSRT>0000000</AHSSRT>
<AHSTAT>10</AHSTAT>
<AHMIS1>00000000000000000000</AHMIS1>
<AHMIS2>00000000000000000000</AHMIS2>
<AHMIS3>00000000000000000000</AHMIS3>
<AHMIS3>00000000000000000000</AHMIS3>
<AHMIS3>00000000000000000000</AHMIS3>
<AHMIS3>00000000000000000000</AHMIS3>
<AHMIS3>00000000000000000000</AHMIS3>
<AHMIS3>00000000000000000000</AHMIS3>
<AHFUNC>1</AHFUNC>
</ns1:Mt_inboundelv_header>
<ns1:Mt_inboundelv_header xmlns:ns1="urn:jag.com.inbounddelv.test01">
<AHPRDT>000000000</AHPRDT>
<AHPRTM>0000000</AHPRTM>
<ADBCTN>0000000002165287</ADBCTN>
<AHASTP>3</AHASTP>
<ADSHMT>180007393</ADSHMT>
<AHWHTF>N</AHWHTF>
<AHQCHD>N</AHQCHD>
<AHOSRC>Y</AHOSRC>
<AHSVIA>0000</AHSVIA>
<AHMANI>0000000000</AHMANI>
<AHBLAD>00000000000000000000</AHBLAD>
<AHTRLN>000000000000</AHTRLN>
<AHPRON>00000000000000000000</AHPRON>
<AHWKON>000000000000</AHWKON>
<AHRCFR>0001000088</AHRCFR>
<AHCSSH>0000000</AHCSSH>
<AHSHDT>000000000</AHSHDT>
<AHSSRD>000000000</AHSSRD>
<AHSSRT>0000000</AHSSRT>
<AHSTAT>10</AHSTAT>
<AHMIS1>00000000000000000000</AHMIS1>
<AHMIS2>00000000000000000000</AHMIS2>
<AHFUNC>1</AHFUNC>
</ns1:Mt_inboundelv_header>
</ns0:Message1>
<ns0:Message2>
<ns1:Mt_inboundelv_item xmlns:ns1="urn:jag.com.inbounddelv.test01">
<ADBCTN>0000000002165287</ADBCTN>
<ADASTP>3</ADASTP>
<ADSHMT>180007392</ADSHMT>
<ADPON>AW2026121</ADPON>
<ADPOLN>000010</ADPOLN>
<ADCO>01</ADCO>
<ADDIV>01</ADDIV>
<ADCOLR>0000</ADCOLR>
<ADSDIM>000</ADSDIM>
<ADSZCD>M-1</ADSZCD>
<ADSZPO>11</ADSZPO>
<ADSEQN>00001</ADSEQN>
<ADSZDS>4</ADSZDS>
<ADINVT>F</ADINVT>
<ADBCHN>000000000000000</ADBCHN>
<ADIPQT> 25.0000</ADIPQT>
<ADCSSH>0000000</ADCSSH>
<ADUNSH>000000000000000</ADUNSH>
<ADIMND> N</ADIMND>
<ADSTAT>00</ADSTAT>
<ADREF1>0000000000</ADREF1>
<ADSC1>00</ADSC1>
<ADNUM4>0000000000000</ADNUM4>
<ADFUNC>1</ADFUNC>
</ns1:Mt_inboundelv_item>
<ns1:Mt_inboundelv_item xmlns:ns1="urn:jag.com.inbounddelv.test01">
<ADBCTN>0000000002165287</ADBCTN>
<ADASTP>3</ADASTP>
<ADSHMT>180007392</ADSHMT>
<ADPON>AW2026121</ADPON>
<ADPOLN>000010</ADPOLN>
<ADCO>01</ADCO>
<ADDIV>01</ADDIV>
<ADCOLR>0000</ADCOLR>
<ADSDIM>000</ADSDIM>
<ADSZCD>M-1</ADSZCD>
<ADSZPO>12</ADSZPO>
<ADSEQN>00002</ADSEQN>
<ADSZDS>6</ADSZDS>
<ADINVT>F</ADINVT>
<ADBCHN>000000000000000</ADBCHN>
<ADIPQT> 25.0000</ADIPQT>
<ADCSSH>0000000</ADCSSH>
<ADUNSH>000000000000000</ADUNSH>
<ADIMND> N</ADIMND>
<ADSTAT>00</ADSTAT>
<ADREF1>0000000000</ADREF1>
<ADSC1>00</ADSC1>
<ADNUM4>0000000000000</ADNUM4>
<ADFUNC>1</ADFUNC>
</ns1:Mt_inboundelv_item>
<ns1:Mt_inboundelv_item xmlns:ns1="urn:jag.com.inbounddelv.test01">
<ADBCTN>0000000002165287</ADBCTN>
<ADASTP>3</ADASTP>
<ADSHMT>180007392</ADSHMT>
<ADPON>AW2026121</ADPON>
<ADPOLN>000010</ADPOLN>
<ADCO>01</ADCO>
<ADDIV>01</ADDIV>
<ADCOLR>0000</ADCOLR>
<ADSDIM>000</ADSDIM>
<ADSZCD>M-1</ADSZCD>
<ADSZPO>13</ADSZPO>
<ADSEQN>00003</ADSEQN>
<ADSZDS>8</ADSZDS>
<ADINVT>F</ADINVT>
<ADBCHN>000000000000000</ADBCHN>
<ADIPQT> 25.0000</ADIPQT>
<ADCSSH>0000000</ADCSSH>
<ADUNSH>000000000000000</ADUNSH>
<ADIMND> N</ADIMND>
<ADSTAT>00</ADSTAT>
<ADREF1>0000000000</ADREF1>
<ADSC1>00</ADSC1>
<ADNUM4>0000000000000</ADNUM4>
<ADFUNC>1</ADFUNC>
</ns1:Mt_inboundelv_item>
<ns1:Mt_inboundelv_item xmlns:ns1="urn:jag.com.inbounddelv.test01">
<ADBCTN>0000000002165287</ADBCTN>
<ADASTP>3</ADASTP>
<ADSHMT>180007392</ADSHMT>
<ADPON>AW2026121</ADPON>
<ADPOLN>000010</ADPOLN>
<ADCO>01</ADCO>
<ADDIV>01</ADDIV>
<ADCOLR>0000</ADCOLR>
<ADSDIM>000</ADSDIM>
<ADSZCD>M-1</ADSZCD>
<ADSZPO>02</ADSZPO>
<ADSEQN>00004</ADSEQN>
<ADSZDS>10</ADSZDS>
<ADINVT>F</ADINVT>
<ADBCHN>000000000000000</ADBCHN>
<ADIPQT> 25.0000</ADIPQT>
<ADCSSH>0000000</ADCSSH>
<ADUNSH>000000000000000</ADUNSH>
<ADIMND> N</ADIMND>
<ADSTAT>00</ADSTAT>
<ADREF1>0000000000</ADREF1>
<ADSC1>00</ADSC1>
<ADNUM4>0000000000000</ADNUM4>
<ADFUNC>1</ADFUNC>
</ns1:Mt_inboundelv_item>
<ns1:Mt_inboundelv_item xmlns:ns1="urn:jag.com.inbounddelv.test01">
<ADBCTN>0000000002165287</ADBCTN>
<ADASTP>3</ADASTP>
<ADSHMT>180007392</ADSHMT>
<ADPON>AW2026121</ADPON>
<ADPOLN>000010</ADPOLN>
<ADCO>01</ADCO>
<ADDIV>01</ADDIV>
<ADCOLR>0000</ADCOLR>
<ADSDIM>000</ADSDIM>
<ADSZCD>M-1</ADSZCD>
<ADSZPO>03</ADSZPO>
<ADSEQN>00005</ADSEQN>
<ADSZDS>12</ADSZDS>
<ADINVT>F</ADINVT>
<ADBCHN>000000000000000</ADBCHN>
<ADIPQT> 25.0000</ADIPQT>
<ADCSSH>0000000</ADCSSH>
<ADUNSH>000000000000000</ADUNSH>
<ADIMND> N</ADIMND>
<ADSTAT>00</ADSTAT>
<ADREF1>0000000000</ADREF1>
<ADSC1>00</ADSC1>
<ADNUM4>0000000000000</ADNUM4>
<ADFUNC>1</ADFUNC>
</ns1:Mt_inboundelv_item>
<ns1:Mt_inboundelv_item xmlns:ns1="urn:jag.com.inbounddelv.test01">
<ADBCTN>0000000002165287</ADBCTN>
<ADASTP>3</ADASTP>
<ADSHMT>180007392</ADSHMT>
<ADPON>AW2026121</ADPON>
<ADPOLN>000010</ADPOLN>
<ADCO>01</ADCO>
<ADDIV>01</ADDIV>
<ADCOLR>0000</ADCOLR>
<ADSDIM>000</ADSDIM>
<ADSZCD>M-1</ADSZCD>
<ADSZPO>04</ADSZPO>
<ADSEQN>00006</ADSEQN>
<ADSZDS>14</ADSZDS>
<ADINVT>F</ADINVT>
<ADBCHN>000000000000000</ADBCHN>
<ADIPQT> 25.0000</ADIPQT>
<ADCSSH>0000000</ADCSSH>
<ADUNSH>000000000000000</ADUNSH>
<ADIMND> N</ADIMND>
<ADSTAT>00</ADSTAT>
<ADREF1>0000000000</ADREF1>
<ADSC1>00</ADSC1>
<ADNUM4>0000000000000</ADNUM4>
<ADFUNC>1</ADFUNC>
</ns1:Mt_inboundelv_item>
<ns1:Mt_inboundelv_item xmlns:ns1="urn:jag.com.inbounddelv.test01">
<ADBCTN>0000000002165287</ADBCTN>
<ADASTP>3</ADASTP>
<ADSHMT>180007392</ADSHMT>
<ADPON>AW2026121</ADPON>
<ADPOLN>000010</ADPOLN>
<ADCO>01</ADCO>
<ADDIV>01</ADDIV>
<ADCOLR>0000</ADCOLR>
<ADSDIM>000</ADSDIM>
<ADSZCD>M-1</ADSZCD>
<ADSZPO>05</ADSZPO>
<ADSEQN>00007</ADSEQN>
<ADSZDS>16</ADSZDS>
<ADINVT>F</ADINVT>
<ADBCHN>000000000000000</ADBCHN>
<ADIPQT> 25.0000</ADIPQT>
<ADCSSH>0000000</ADCSSH>
<ADUNSH>000000000000000</ADUNSH>
<ADIMND> N</ADIMND>
<ADSTAT>00</ADSTAT>
<ADREF1>0000000000</ADREF1>
<ADSC1>00</ADSC1>
<ADNUM4>0000000000000</ADNUM4>
<ADFUNC>1</ADFUNC>
</ns1:Mt_inboundelv_item>
</ns0:Message2>
</ns0:Messages> -
Problem with multimapping in BPM
Hy,
I still have a problem with a multimapping in BPM. I add a new message into the input message of the mapping definition. I have now 10 input message mapped to a Idoc. I have the problem that yet the last message is no more treated by the mapping step.
Anyone can help me.
ThanksHi,
After adding the new input file, the cache may not be refreshed properly.
Please refer to this for Cache Refresh:
<a href="https://www.sdn.sap.comhttp://www.sdn.sap.comhttp://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/1a69ea11-0d01-0010-fa80-b47a79301290">How to Handle Caches in SAP XI 3.0</a>
JE -
Problem in multimapping without BPM
Hi,
I am doing a file to file multimapping scenario (1:n) in PI 7.0. In interface mapping the source has occurence of 1 and target occurrence is 0..unbounded.
Problem is with this configuration, in my ID interface determination, the interface mapping is not being recognised and I'm getting "object not found" when trying to select the interface mapping. and there is no problem with inbound and outbound interfaces.
However, when I change the occurrence of my target to 1 in IR, then I can select the interface mapping in Interface Determination in ID.
Could any one please throw some light on this problem?
Regards,
ShiladityaHi,
Pls use Enhanced option in Interface determination.
try to assigh interface mapping and your inbound interfaces.
check the following blog.
https://weblogs.sdn.sap.com/pub/wlg/3115. [original link is broken] [original link is broken] [original link is broken]
regards
mahesh. -
Problem with Multimapping using Variable Susbtitution
Hi,
I have done a Multi-Mapping where I have used variable substitution in the mapping
The problem I am facing is that when my target message generates multiple messages the files are creating successfully on the FTP server but if only a
single message generates on the target side then my message is successfully processed in IS but in adapter engine the message status is in "Waiting" state.
When i see the audit log i found the following details:
Time Stamp Status Description
2007-09-18 06:10:24 Success The message was successfully received by the messaging system. Profile: XI URL: https://dx1-60.ra.rockwell.com:56001/MessagingSystem/receive/AFW/XI
2007-09-18 06:10:24 Success Using connection AFW. Trying to put the message into the receive queue.
2007-09-18 06:10:24 Success Message successfully put into the queue.
2007-09-18 06:10:24 Success The message was successfully retrieved from the receive queue.
2007-09-18 06:10:24 Success The message status set to DLNG.
2007-09-18 06:10:24 Error Unable to find channel ID
2007-09-18 06:10:24 Error Delivery of the message to the application using connection AFW failed, due to: Couldn't find delivery channel for message: 46ee0b73-f266-3794-e100-000082974e17.
2007-09-18 06:10:24 Success The asynchronous message was successfully scheduled to be delivered at Tue Sep 18 06:15:24 GMT 2007.
2007-09-18 06:10:24 Success The message status set to WAIT.
2007-09-18 06:15:24 Success Retrying to deliver message to the application. Retry: 1
Iam using SP14
Can anyone help me to solve the above problemDATA: l_tabname TYPE tabname .
DATA : gi_mara TYPE TABLE OF mara ,
gi_makt TYPE TABLE OF makt .
l_tabname = 'MARA' .
DATA : l_dref TYPE REF TO data.
FIELD-SYMBOLS: <li_itab> TYPE ANY TABLE.
CREATE DATA l_dref TYPE TABLE OF (l_tabname).
ASSIGN l_dref->* TO <li_itab> .
*Define another field symbol and asign it to right internal table
*here naming of internal table is important
FIELD-SYMBOLS : <fs_tab> TYPE ANY TABLE .
CONCATENATE 'GI_' l_tabname INTO l_tabname .
ASSIGN (l_tabname) TO <fs_tab>.
<fs_tab> = <li_itab> . -
Problem in multimapping(File to File)
Hi Experts,
I have a scenarion in which i have
1:N multimapping(for file to file)....
I am using java mapping for that.
During mapping it's creating more than 1 message type in one message ....that's fine
eg:
Message1
mt_1
mt_1
mt_1
Message2
Mt_2
Mt_2
I get the above proper output while testing in Mapping......But if i test in Test Configuration or in End to End.... it throws an error
Interface Determination Cannot be found
Is it because i have multiple same message types for a given Message1 or Message2(As shown above).. or something else
Thanks,
Babu.Hi Hibabu,
1. Please try to make sure that the interface mapping also works fine with the given interfaces for the mentioned message mapping in.
2. Check the interface determination again .wether wether u mentioned all the required parameters properly or not and activate it again.
3.In configuration during interface determination .use Enhanced Interface determination and mention the multimapping mentioned interface mapping there.
Thanks,
Ram. -
Hi ,
I am doing multimapping in which there are two source files having structure as below
MT_Carrierdata target structure is
Country MT_SAPusagedat
Enhanced users country
basic users Gl account
<----
> cost centre
MT_Agentsdata
Country
Enhanced users
basic users
Now I have to map GL account on the basis of the table below
New SAP GL Account Description
99995151 Agents Enhanced Users
99995152 Agents Basic Users
99995153 Carriers Enhanced Users
99995154 Carriers Basic Users
like for eg :: if first file for carrier is arrived the GL account should be 99995153 for enhanced user and for and 99995154 for basic user
Any clues how to achieve this ???
Please let me know
thnx
NinadHi,
Pls use Enhanced option in Interface determination.
try to assigh interface mapping and your inbound interfaces.
check the following blog.
https://weblogs.sdn.sap.com/pub/wlg/3115. [original link is broken] [original link is broken] [original link is broken]
regards
mahesh. -
Multimapping to IDOC 1:n via IDOC bundling: Problem
Hi,
Trying the above procedure to send several IDOCS as one bundle to R/3. I followed note 814393 and also checked with weblog https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/2762. [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken] [original link is broken]
The tests in message mapping run ok, I get exactly the screens as are mentioned in the weblog. yet when I send the actual interface, the message stays on recorded for outbound processing for 4 minutes in SXMB_MONI, then cancels with the following error:
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">GENERIC</SAP:Code>
<SAP:P1>com/sap/xi/tf/_IF021_Ordrsp_TD_to_Ordrsp_CCS_</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
<SAP:P3>Failed to load resource from the context classloa~</SAP:P3>
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
The trace says:
<Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_IF021_Ordrsp_TD_to_Ordrsp_CCS_</Trace>
<Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: Failed to load resource from the context classloader of the current thread! Loading from classloader was caused by: java.net.ConnectException: Connection timed out at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:37) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:63) etc
The scenario is client proxy to XI - BPM with sync HTTP - resulting XML mapped to multiple occurence IDOC and then to the IDOC adapter.
Everything works except the last mapping from BPM to outbound IDOC although that works in test as well.
Any ideas?
Thanks
TomHi Tom,
1. Please can you check if your HTTP synch is working fine.
2. Please can you goto SXMB_MONI and take the Payload and see if your mapping is fine.
Regards
Vijaya -
Problem in Variable Substitution (Receiver File Adapter)
Hi,
I am facing problem in the variable substitution in receiver file Communication channel. My expected file name is A_C.xml; but my actual output filename obtained is C_C.xml for the below example target file:
<ProductionSch>
<CustomField>
<value>
<ValueString>A</ValueString>
</value>
</CustomField>
<CustomField>
<value>
<ValueString>B</ValueString>
</value>
</CustomField>
<CustomField>
<value>
<ValueString>C</ValueString>
</value>
</CustomField>
</ProductionSch>
I have used the following parameters in the file communication channel:
File Name Schema: %var1%_%var2%.xml
Variable Substitution:
Variable Name Reference
var1 payload:ProductionSch,1,CustomField,1,value,1,ValueString,1
var2 payload:ProductionSch,1,CustomField,3,value,1,ValueString,1
When I try using either of the one in the file name schema and the corresponding variable reference in the variable substitution I am getting the correct output filename as A.xml or C.xml. However, when I give either of the one variable in file name schema and both the variable references in the variable substitution I am getting only C.xml as per the example file.
Can any of you suggest me where I am wrong or any other suggestion which I can try?
I cannot use dynamic configuration as I am using multimapping. Multiple file names cannot be generated using dynamic configuration.
Regards
Sowmyahi Sowmya,
refer you to this [Note 1581988 - Variable Substitution option does not work properly|https://service.sap.com/sap/support/notes/1581988] (2011.05), as SAP says " when there is more than one variable using the same name as the last element, File Adapter does not select the correct one.... ".
regards.
Mickael -
Hi All,
I am doing N:1 multimapping for files.
I have 2 senders and 1 receiver.
I created 2 sender interfaces and 1 receiver interface.
I did message mapping in which I added 2 sender message types in source and added the target message type.
I did Interface mapping with 2 sender message interface and 1 receiver interface.
But i faced problem when creating configurations in ID.
(a) I am not able to understand how many interface determination/Receiver determinations are required.
(b) Again I am not getting interface mapping in Interface Determination .
So can anyone help me to solve this?
Thanks
RabiHi,
You can use any of the collect message pattern provided. In your case any one of the following can be used:
1. BpmPatternCollectMessage
2. BpmPatternCollectTime
->There are some patterns in SWC : SAP BASIS --> namespace : http://sap.com/xi/XI/System/Patterns In ESR of your SAP PI System.
-> please go through this blogs it will help you.
Correlation Runtime Behavior of BPM.
http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/10526. [original link is broken] [original link is broken]
In Configuration By using of BPM.
-> two communication channels one for sender and one for receiver
-> 2 receiver Determinations
one for Sender to IP.
One for IP to Receiver.
-> 2 Interface Dtermination
one for Sender to Ip
one for IP two Receiver
-> 1 Sender agrement.
-> 1 receiver agrement for (IP to Receiver)
regards,
ganesh. -
Problem with Mulit Mapping/Message Split
Hi,
I am a newbie to XI trying to set up a file2file scenario with multi-mapping/message splitting without BPM.
System is XI 3.0 SP14
Scenario is:
read an XML-File and multiply it and write 2 XML-files using the File adaptor.
For reference I used "multimapping without BPM".
- setting occurancy of Message types to unbounded in both Message Mapping and Interface Mapping.
- using the RB_Split button
- setting up one business service containing 2 message interfaces and 2 communication channels for output.
Designing and Konfiguring worked fine.
File is read but no file is written.
XML-Moni tells me "Mapping did not create Messages"
I did extensive studies in sap.help, forum and various blogs. Also to verify Messagetypes and Kommunication channels I set up similar file2file scenario without splitting. Nothing really helped.
Any clues?Hi again,
very efficient method to test XML-source file. - Thanks.
Unfortunately it did not solve my problem.
Again: "Split mapping did not create messages"
Below you can find a part of the trace created when processing this message:
<Trace level="3" type="T">Multi mapping required.</Trace>
<Trace level="3" type="T">Creating Java mapping com/sap/xi/tf/_MM_data_duplic_async_.</Trace>
<Trace level="3" type="T">Load ac6179b0-a92e-11da-be15-e51f0a000472, http://MyTutorial/SHeinz05, -1, com/sap/xi/tf/_MM_data_duplic_async_.class.</Trace>
<Trace level="3" type="T">Search com/sap/xi/tf/_MM_data_duplic_async_.class (http://MyTutorial/SHeinz05, -1) in swcv ac6179b0-a92e-11da-be15-e51f0a000472.</Trace>
<Trace level="3" type="T">Loaded class com.sap.xi.tf._MM_data_duplic_async_</Trace>
<Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._MM_data_duplic_async_</Trace>
<Trace level="2" type="T">Java mapping com/sap/xi/tf/_MM_data_duplic_async_ completed. (executeStep() of com.sap.xi.tf._MM_data_duplic_async_</Trace>
<Trace level="3" type="T">Nachrichtentyp 1 Anzahl der Nachrichten 0</Trace>
<Trace level="3" type="T">Nachrichtentyp 2 Anzahl der Nachrichten 0</Trace>
<Trace level="1" type="E">CL_XMS_PLSRV_MAPPING~ENTER_PLSRV</Trace>
</Trace>
- <Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST">
<Trace level="3" type="T">Persisting message after plsrv call</Trace>
<Trace level="3" type="T">Message-Version = 005</Trace>
<Trace level="3" type="T">Message version 005</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</Trace>
<Trace level="3" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- <!-- ************************************
-->
<Trace level="3" type="T">Persisting message Status = 014</Trace>
<Trace level="3" type="T">Message version 006</Trace>
<Trace level="3" type="T">Pipeline CENTRAL</Trace>
</SAP:Trace>
Test of MM and IM is always successful.
Any clues? -
Problem in 1toN message mapping,payload not populated but file created
I am doing 1:N multimapping From Proxy to File scenario .Proxy send three types of data all having same stucture but depending on the value of First field we split the whole stucture in 3 parts on target side and generating three files on taget side.During testing values get Passed from the SXMB_MONI(processed) and we get whole payload data upto
"Message Branch Acording to Reciever List" .But when i check payload data in 'Request Message Mapping" we donot get any data in Payload.Taget File is generated but when we try to oen the file I get message " Unable to display the File".
can any expert help me resolve this problem.I need to generate 3 files each having similar structures depending upon the first field 'listcode' values whose values are 'N0','MA','MY' coming in a proxy structure.The source structure is as follows::
MT_Source
>Detailrecord..0..unbounded
>listcode..0.1...xsd:string
>itemcode...0.1...xsd:string
>description1...0.1..xsd:string
>description2...0.1..xsd:string
The target stuctures are:
MT_Target_N0
>Detailrecord..0..unbounded
>listcode..0.1...xsd:string
>itemcode...0.1...xsd:string
>description1...0.1..xsd:string
>description2...0.1..xsd:string
MT_Target_MA
>Detailrecord..0..unbounded
>listcode..0.1...xsd:string
>itemcode...0.1...xsd:string
>description1...0.1..xsd:string
>description2...0.1..xsd:string
MT_Target_MY
>Detailrecord..0..unbounded
>listcode..0.1...xsd:string
>itemcode...0.1...xsd:string
>description1...0.1..xsd:string
>description2...0.1..xsd:string
I need to do mapping of such 1:n multimapping mapping.I have done mapping but getting error in moni "Split mapping created no messages".Please suggest me some right way to do mapping -
Hi Experts,
Scenario : SOAP -> XI -> RFC
Source side : One message
Target side : Two RFCs
Depends on..one of the source field value I have to trigger the particular RFC.
IR Objects
1. Interface mapping - 1
Source message interface occurance - 1
Target RFCs 0 to Unbounded occurance
Mapping
1. XSLT Step1 - Source rootnode contains namespace. To remove that I have used the XSLT mapping.
CODE:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/>
<xsl:template match="*">
<xsl:element name="{local-name()}">
<xsl:apply-templates select="@* | node()"/>
</xsl:element>
</xsl:template>
</xsl:stylesheet>
2. XSLT Step2 - To add the Message tags in the starting for multimapping.
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes"/>
<xsl:template match="/">
<ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
<ns0:Message1>
<xsl:apply-templates/>
</ns0:Message1>
</ns0:Messages>
</xsl:template>
<xsl:template match="@*|node()">
<xsl:copy>
<xsl:apply-templates select="@*|node()"/>
</xsl:copy>
</xsl:template>
</xsl:stylesheet>
3. Graphical - Multimapping
ID objects
Interface determination - Selected the option enhanced. remaining all similar to normal interface.
Able to get the required results from MM and IM testing, but not from ID Test Configuration and runtime workbench.
(For IM testing : I have used the acutal payload)
Getting the below error from runtime workbench.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- <!-- Request Message Mapping
-->
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">GENERIC</SAP:Code>
<SAP:P1>Split mapping created no messages</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Split mapping created no messages</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Could you please tell me how to resolve the issue.
Edited by: Sundari David on Nov 29, 2011 11:52 AMHi,
if you are going with the option of mapping based message split with you XSLT mapping , you need to include Message and MessageN tags as the top nodes in your target msgs.
The problem is the Target XML that is produced contains the namespace
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
<ns0:Message1>
</ns0:Message1
u2026
This needs to be removed.
Use this XSLT as post processing after the main message mapping. Save this code as XSLT, zip and then import as external archive and then add this as last step in interface mapping.
Let me know how it goes - it will fix your namespace issue not sure if you'll have problems with the result it produces.
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml" indent="no"/>
<xsl:template match="/|comment()|processing-instruction()">
<xsl:copy>
<xsl:apply-templates/>
</xsl:copy>
</xsl:template>
<xsl:template match="*">
<xsl:element name="{local-name()}">
<xsl:apply-templates select="@*|node()"/>
</xsl:element>
</xsl:template>
<xsl:template match="@*">
<xsl:attribute name="{local-name()}">
<xsl:value-of select="."/>
</xsl:attribute>
</xsl:template>
</xsl:stylesheet>
i hope it will helpful.
regards,
ganesh.
Maybe you are looking for
-
IOS 8.1 Music app not allowing search by artist
On my iPhone 4S, I usually search music by artist. Since the update to 8.1, my phone no longer responds to searching through the alphabet down the RHS for Artist. It does for the Category Songs , but not for Artists. Have others experienced this? Is
-
My mac Doesn't seem to see my external hard drive (seagate 1tb) I have it usb'd in to the back of my computer, but when I open time machine...it does not see it. Help...please
-
Here is my situation. I have a table that has a list of codes almost 100K. I have another table that has code listed in term of an in house regular expression. Example: 40a.[1,2,3] 12b Where a is 0 - 9 b is 1 - 9 I have tried using REGEXP_LIKE but I
-
Dear all, How can i find the Service product List and Combinationof Service product and Serviceable Material. Regards Raj
-
Unable to set JVM file encoding to UTF-8 on Windows
Hi, I am running Tomcat on 1.5.0_05 JRE. I tried several things to set the jvm file encoding to UTF-8 instead of the default Cp1252, but no luck yet. The most intuitive approach seems to be to use a JVM option like "-Dfile.encoding=UTF-8" but this do