Whitespaces in XML during message mapping not preserved

I use a twostep mapping process during Interface Mapping. The first one is the standard message mapping and the second one is a Java mapping. However, during the second step, the white spaces that should be preserved from the output of the first mapping is not there anymore. I created the XSD and specified in the details that the white spaces should be preserved.
I need the whitespaces since the output of the second mapping would be used for file content conversion in a file adapter to create the output:
MSGTYP CONTROLNOMSGID VALUE1VALUE2 VALUEn.....
Is there any way to preserve the white spaces?
Thanks!
Best Regards,
Rommel Mendoza

This is odd. Java won't condense/trim the whitespaces unless explicitely told so.
Where are you seeing the missing whitespaces?
Please notice that SXMB_MONI won't show the spaces because it uses a HTML representation of the XML (and, by default, HTML condenses the whitespaces). But the actual XML file should have all the spaces (check the XML document source code, through mouse right click over payload, to be sure).
Also, what are the conversions you do in the java mapping?
Are you sure the java mapping input has the whitespaces?
Regards,
Henrique.

Similar Messages

System Error During Message Mapping

I've set up a simple mapping scenario that sends a DEBMAS06 IDoc from our R/3 system to XI mapping to DEBMAS06 and writing out to a file. I am getting the following system error during message mapping:
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">JCO_SYSTEM_FAILURE</SAP:Code>
<SAP:P1>Server repository could not create function template for 'SMPP_CALL_JAVA_RUNTIME</SAP:P1>
I have gone back to the Design Builder and tested out the message mapping and the interface mapping and both work successfully. I have also taken the payload of the message and submitted it via the RWB and it generates the same error as when sent from R/3. Any other places I can look?

Hi Mike,
You have got the connectivity issue problem between ABAP and J2EE stack. When do the test in the Message Mapping, thats the J2EE and it works. But during the runtime it has to go to the Integratin Server, which is the ABAP stack. Fix the connectivity issue, check the smicm,trace and debug log etc.
Hope this helps.
Cheers,
Ranjan

RFC lookUp during Message mapping

All
I want to get soem values from SAP table during message mapping.After getting the values am going to do 2:1 mapping by using BPM.
Could you please let me know the basic and fundamental things about RFC look up during mapping and RFC settings in XI as well in R3?
Please explain

Hi Rajesh,
Pl post this in XI Forums to get quick replies.
Regards
Ayyapparaj

Seeking examples of custom XML Gateway message map

I've been asked to create some custom XML Gateway message maps for inbound/outbound XML data feeds.
I've followed along at [this tutorial|http://docs.oracle.com/cd/E12839_01/integration.1111/e10537/T430238T430339.htm#T430357], but it stops short of telling me how to define a custom message map.
Does anyone know of a resource I could look at - a web site, book, etc., that would cover the creation of a custom message map?

Have a look
http://docs.oracle.com/cd/E18727_01/doc.121/e12954/T319774T319778.htm

IDOC Segment not getitng populated during message mapping

Hi,
In my scenario when i am testing, I send IDOC to XI and getting following message
<Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: RuntimeException in Message-Mapping transformation: Cannot produce target element /ns0:I805_Abstr_CustOutlet_MT/Records/AMA_E1KNA1M_STATUS.
When I checked th IDOC xsd, it doesn't show the segment which mapped to above status field.
Can anyone of you please let me know what it is and how it can be resolved.
Regards
Edited by: ria sen on Jun 30, 2008 5:15 AM

Hi Amit,
Following is the payload from SXMB_MONI
<?xml version="1.0" encoding="UTF-8" ?>
- <_-AMA_-DEBMAS06E11>
- <IDOC BEGIN="1">
- <EDI_DC40 SEGMENT="1">
<TABNAM>EDI_DC40</TABNAM>
<MANDT>110</MANDT>
<DOCNUM>0000000000415387</DOCNUM>
<DOCREL>700</DOCREL>
<STATUS>30</STATUS>
<DIRECT>1</DIRECT>
<OUTMOD>2</OUTMOD>
<IDOCTYP>DEBMAS06</IDOCTYP>
<CIMTYP>/AMA/DEBMAS06E11</CIMTYP>
<MESTYP>/AMA/DEBMAS</MESTYP>
<STDMES>/AMA/D</STDMES>
<SNDPOR>SAPDAR</SNDPOR>
<SNDPRT>LS</SNDPRT>
<SNDPRN>DARCLNT110</SNDPRN>
<RCVPOR>DAX_001</RCVPOR>
<RCVPRT>LS</RCVPRT>
<RCVPRN>CCABASIS</RCVPRN>
<CREDAT>20080630</CREDAT>
<CRETIM>133535</CRETIM>
<SERIAL>20080627162157</SERIAL>
</EDI_DC40>
- <E1KNA1M SEGMENT="1">
<MSGFN>018</MSGFN>
<KUNNR>0001231235</KUNNR>
<BBBNR>0000000</BBBNR>
<BBSNR>00000</BBSNR>
<BUBKZ>0</BUBKZ>
<KTOKD>S</KTOKD>
<KUKLA>S</KUKLA>
<LAND1>AU</LAND1>
<NAME1>Drew Smith again</NAME1>
<ORT01>Ashfield</ORT01>
<PSTLZ>2193</PSTLZ>
<REGIO>NSW</REGIO>
<SORTL>DREW</SORTL>
<SPRAS>E</SPRAS>
<STRAS>29 Hardy Street</STRAS>
<UMJAH>0000</UMJAH>
<JMZAH>000000</JMZAH>
<JMJAH>0000</JMJAH>
<UMSA1>0</UMSA1>
<HZUOR>00</HZUOR>
<SPRAS_ISO>EN</SPRAS_ISO>
- <_-AMA_-E1KNA1M SEGMENT="1">
<_-AMA_-REF_KUNNR>200</_-AMA_-REF_KUNNR>
</_-AMA_-E1KNA1M>
- <_-SCL_-E1ADRMAS SEGMENT="1">
<QUALF>ADRMAS02</QUALF>
<OBJ_TYPE>KNA1</OBJ_TYPE>
<OBJ_ID>0001231235</OBJ_ID>
<CONTEXT>0001</CONTEXT>
<IV_CHECK_ADDRESS>X</IV_CHECK_ADDRESS>
<IV_TIME_DEPENDENT_COMM_DATA>X</IV_TIME_DEPENDENT_COMM_DATA>
- <_-SCL_-E1BPAD1VL SEGMENT="1">
<FROM_DATE>00010101</FROM_DATE>
<TO_DATE>99991231</TO_DATE>
<NAME>Drew Smith again</NAME>
<CITY>Ashfield</CITY>
<POSTL_COD1>2193</POSTL_COD1>
<STREET>29 Hardy Street</STREET>
<COUNTRY>AU</COUNTRY>
<COUNTRYISO>AU</COUNTRYISO>
<LANGU>E</LANGU>
<LANGU_ISO>EN</LANGU_ISO>
<REGION>NSW</REGION>
<SORT1>DREW</SORT1>
<TIME_ZONE>AUSNSW</TIME_ZONE>
- <_-SCL_-E1BPAD1VL1 SEGMENT="1">
<LANGU_CR>E</LANGU_CR>
<LANGUCRISO>EN</LANGUCRISO>
<ADDR_GROUP>BP</ADDR_GROUP>
<COUNTRY>AU</COUNTRY>
<COUNTRYISO>AU</COUNTRYISO>
<REGION>NSW</REGION>
<TIME_ZONE>AUSNSW</TIME_ZONE>
</_-SCL_-E1BPAD1VL1>
</_-SCL_-E1BPAD1VL>
</_-SCL_-E1ADRMAS>
<_-SCL_-DSD_FIELDS SEGMENT="1" />
<_-SCL_-E1KNA1M SEGMENT="1" />
<E1KNA11 SEGMENT="1" />
- <E1KNVVM SEGMENT="1">
<MSGFN>018</MSGFN>
<VKORG>AU01</VKORG>
<VTWEG>Z2</VTWEG>
<SPART>Z0</SPART>
<KALKS>1</KALKS>
<BZIRK>AU4</BZIRK>
<PLTYP>02</PLTYP>
<AWAHR>100</AWAHR>
<ANTLF>9</ANTLF>
<LPRIO>00</LPRIO>
<PERFK>AU</PERFK>
<PERRL>AU</PERRL>
<WAERS>AUD</WAERS>
<KTGRD>01</KTGRD>
<ZTERM>Z060</ZTERM>
<VWERK>1005</VWERK>
<VKBUR>A4TT</VKBUR>
<BOKRE>X</BOKRE>
<UEBTO>0.0</UEBTO>
<UNTTO>0.0</UNTTO>
<PODTG>0</PODTG>
- <_-SCL_-E1KNVVM SEGMENT="1">
<_-SCL_-CU_KZREG>000000</_-SCL_-CU_KZREG>
<_-SCL_-CU_KZPLP>000000</_-SCL_-CU_KZPLP>
<_-SCL_-CU_FBDWE>0000</_-SCL_-CU_FBDWE>
<_-SCL_-CU_VBDG1>0000</_-SCL_-CU_VBDG1>
<_-SCL_-CU_VBDG2>0000</_-SCL_-CU_VBDG2>
<_-SCL_-CU_VBDG3>0000</_-SCL_-CU_VBDG3>
<_-SCL_-CU_FEDWE>0000</_-SCL_-CU_FEDWE>
<_-SCL_-CU_VEDG1>0000</_-SCL_-CU_VEDG1>
<_-SCL_-CU_VEDG2>0000</_-SCL_-CU_VEDG2>
<_-SCL_-CU_VEDG3>0000</_-SCL_-CU_VEDG3>
<_-SCL_-CU_MTPST>0000000000</_-SCL_-CU_MTPST>
<_-SCL_-CU_MXHUB>0000000000</_-SCL_-CU_MXHUB>
<_-SCL_-CU_SORTR>0</_-SCL_-CU_SORTR>
<_-SCL_-PO_ZFHMG>0.000</_-SCL_-PO_ZFHMG>
<_-SCL_-PO_MXSTH>0</_-SCL_-PO_MXSTH>
<_-SCL_-PO_TWPLUS>000000</_-SCL_-PO_TWPLUS>
<_-SCL_-GC_LONGITUD>0.000000000000</_-SCL_-GC_LONGITUD>
<_-SCL_-GC_LATITUDE>0.000000000000</_-SCL_-GC_LATITUDE>
<_-SCL_-GC_REFID>0000000000</_-SCL_-GC_REFID>
</_-SCL_-E1KNVVM>
- <E1KNVPM SEGMENT="1">
<MSGFN>009</MSGFN>
<PARVW>YM</PARVW>
<KUNN2>0001231235</KUNN2>
<KNREF>00000038</KNREF>
<PARZA>0</PARZA>
</E1KNVPM>
- <E1KNVPM SEGMENT="1">
<MSGFN>009</MSGFN>
<PARVW>RE</PARVW>
<KUNN2>0001231235</KUNN2>
<PARZA>0</PARZA>
</E1KNVPM>
- <E1KNVPM SEGMENT="1">
<MSGFN>009</MSGFN>
<PARVW>RG</PARVW>
<KUNN2>0001231235</KUNN2>
<PARZA>0</PARZA>
</E1KNVPM>
- <E1KNVPM SEGMENT="1">
<MSGFN>009</MSGFN>
<PARVW>WE</PARVW>
<KUNN2>0001231235</KUNN2>
<PARZA>0</PARZA>
</E1KNVPM>
</E1KNVVM>
</E1KNA1M>
</IDOC>
</_-AMA_-DEBMAS06E11>

Attachments deleted during message mapping in PI 7.1

We have upgraded our SAP XI 3.0 SP 22 system to SAP PI 7.1 SP06. In XI 3.0 we created some message mappings that mapped an XML payload with attachments to another message type. The attachments would still exist after the mapping step. In SAP PI 7.1 we now see that attachements are deleted from the message. We cannot see why this is happening. We have tried to set the 3 new option in the operation mappings without any results. The attachements are still being deleted.
Active Options in operation mappings:
 Use SAPXMLToolkit = true
 Do Not Resolve XOP includes = false
 Read Attachements = false
In the SXMB_MONI we can see that the attachements are deleted after the Request Message Mapping step. It is a simple proxy-to-proxy scenario with interface and message mapping.
<Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
<Trace level="2" type="T">......attachment XI_Context not found</Trace>
<Trace level="3" type="T">Mapping already defined in interface determination</Trace>
<Trace level="3" type="T">Object ID of Interface Mapping 46842937562139BCA3F2AC1F36E729FE</Trace>
<Trace level="3" type="T">Version ID of Interface Mapping 5D945F00B00611DDB04FF8CF0A5B0156</Trace>
<Trace level="1" type="T">Interface Mapping urn:kadaster-nl:SERV:ZA:KAD:DOVO im_mail_to_dms</Trace>
<Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_mm_mail_to_dms_</Trace>
<Trace level="3" type="T">MTOM Attachments are Transferred to the Payload</Trace>
<Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>
<Trace level="2" type="T">Mode 0</Trace>
<Trace level="3" type="T">Search com/sap/xi/tf/_mm_mail_to_dms_.class (urn:kadaster-nl:SERV:ZA:KAD:DOVO, -1) in swcv 5d945f00-b006-11dd-b04f-f8cf0a5b0156.</Trace>
<Trace level="2" type="T">Loaded class com.sap.xi.tf._mm_mail_to_dms_</Trace>
<Trace level="3" type="T">Search com/sap/xi/tf/_mm_mail_to_dms_$MT$InnerLibsList.class (urn:kadaster-nl:SERV:ZA:KAD:DOVO, -1) in swcv 5d945f00-b006-11dd-b04f-f8cf0a5b0156.</Trace>
<Trace level="2" type="T">Loaded class com.sap.xi.tf._mm_mail_to_dms_$MT$InnerLibsList</Trace>
<Trace level="3" type="T">Search com/sap/xi/tf/_mm_mail_to_dms_$MT$InnerParamsList.class (urn:kadaster-nl:SERV:ZA:KAD:DOVO, -1) in swcv 5d945f00-b006-11dd-b04f-f8cf0a5b0156.</Trace>
<Trace level="2" type="T">Loaded class com.sap.xi.tf._mm_mail_to_dms_$MT$InnerParamsList</Trace>
<Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._mm_mail_to_dms_</Trace>
<Trace level="1" type="T">*** START APPLICATION TRACE ***</Trace>
<Trace level="3" type="T">Document start</Trace>
<Trace level="3" type="T">Start tag [ns1:OpvoerenDocumentRequest]</Trace>
<Trace level="3" type="T">Add raw attribute [ xmlns:ns1="urn:kadaster-nl:SERVICES:DMS:Opvoeren:ZI_KAD_DMS_MAIN"]</Trace>
<Trace level="3" type="T">Start tag [DocumentInfoRecord]</Trace>
<Trace level="3" type="T">Start tag [Type]</Trace>
<Trace level="3" type="T">Put value [302]</Trace>
<Trace level="3" type="T">Close tag [Type]</Trace>
<Trace level="3" type="T">Start tag [Omschrijving]</Trace>
<Trace level="3" type="T">Put value [Apeldoorn]</Trace>
<Trace level="3" type="T">Close tag [Omschrijving]</Trace>
<Trace level="3" type="T">Close tag [DocumentInfoRecord]</Trace>
<Trace level="3" type="T">Close tag [ns1:OpvoerenDocumentRequest]</Trace>
<Trace level="3" type="T">Document end</Trace>
<Trace level="1" type="T">*** END APPLICATION TRACE ***</Trace>
<Trace level="2" type="T">Java mapping com/sap/xi/tf/_mm_mail_to_dms_ completed. (executeStep() of com.sap.xi.tf._mm_mail_to_dms_).</Trace>
<Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>
<Trace level="3" type="T">Attached will be Deleted cid:payload-001708D1A20E1DEDAD96471B4CCBC447(@)sap.com</Trace>
<Trace level="3" type="T">Attached will be Deleted cid:payload-001708D1A20E1DEDAD96471B4C758447(@)sap.com</Trace>
<Trace level="1" type="T">ContentType application/xml</Trace>
Regards,
Jeroen

Hi Michal,
Already tried this option too. However this option would only transfer the attachments to
the mapping runtime in JAVA. We only map the actual payload in a graphical message
mapping, so for our purpose, the other attachments could stay untouched and remain
in the abap part for further pipeline processing.
You can find the result of the Read attachment option during runtime here:

- <Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV">
<Trace level="2" type="T">......attachment XI_Context not found</Trace>
<Trace level="3" type="T">Mapping already defined in interface determination</Trace>
<Trace level="3" type="T">Object ID of Interface Mapping 46842937562139BCA3F2AC1F36E729FE</Trace>
<Trace level="3" type="T">Version ID of Interface Mapping 5D945F00B00611DDB04FF8CF0A5B0156</Trace>
<Trace level="1" type="T">Interface Mapping urn:kadaster-nl:SERV:ZA:KAD:DOVO im_mail_to_dms</Trace>
<Trace level="3" type="T">Mapping Steps 1 JAVA com/sap/xi/tf/_mm_mail_to_dms_</Trace>
<Trace level="3" type="T">MTOM Attachments are Transferred to the Payload</Trace>
<Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>
<Trace level="2" type="T">Mode 0</Trace>
<Trace level="3" type="T">Search com/sap/xi/tf/_mm_mail_to_dms_.class (urn:kadaster-nl:SERV:ZA:KAD:DOVO, -1) in swcv 5d945f00-b006-11dd-b04f-f8cf0a5b0156.</Trace>
<Trace level="2" type="T">Loaded class com.sap.xi.tf._mm_mail_to_dms_</Trace>
<Trace level="3" type="T">Search com/sap/xi/tf/_mm_mail_to_dms_$MT$InnerLibsList.class (urn:kadaster-nl:SERV:ZA:KAD:DOVO, -1) in swcv 5d945f00-b006-11dd-b04f-f8cf0a5b0156.</Trace>
<Trace level="2" type="T">Loaded class com.sap.xi.tf._mm_mail_to_dms_$MT$InnerLibsList</Trace>
<Trace level="3" type="T">Search com/sap/xi/tf/_mm_mail_to_dms_$MT$InnerParamsList.class (urn:kadaster-nl:SERV:ZA:KAD:DOVO, -1) in swcv 5d945f00-b006-11dd-b04f-f8cf0a5b0156.</Trace>
<Trace level="2" type="T">Loaded class com.sap.xi.tf._mm_mail_to_dms_$MT$InnerParamsList</Trace>
<Trace level="2" type="T">Call method execute of the application Java mapping com.sap.xi.tf._mm_mail_to_dms_</Trace>
<Trace level="1" type="T">*** START APPLICATION TRACE ***</Trace>
<Trace level="3" type="T">Document start</Trace>
<Trace level="3" type="T">Start tag [ns1:OpvoerenDocumentRequest]</Trace>
<Trace level="3" type="T">Add raw attribute [ xmlns:ns1="urn:kadaster-nl:SERVICES:DMS:Opvoeren:ZI_KAD_DMS_MAIN"]</Trace>
<Trace level="3" type="T">Start tag [DocumentInfoRecord]</Trace>
<Trace level="3" type="T">Start tag [Type]</Trace>
<Trace level="3" type="T">Put value [302]</Trace>
<Trace level="3" type="T">Close tag [Type]</Trace>
<Trace level="3" type="T">Start tag [Omschrijving]</Trace>
<Trace level="3" type="T">Put value [Apeldoorn]</Trace>
<Trace level="3" type="T">Close tag [Omschrijving]</Trace>
<Trace level="3" type="T">Close tag [DocumentInfoRecord]</Trace>
<Trace level="3" type="T">Close tag [ns1:OpvoerenDocumentRequest]</Trace>
<Trace level="3" type="T">Document end</Trace>
<Trace level="1" type="T">*** END APPLICATION TRACE ***</Trace>
<Trace level="2" type="T">Java mapping com/sap/xi/tf/_mm_mail_to_dms_ completed. (executeStep() of com.sap.xi.tf._mm_mail_to_dms_).</Trace>
<Trace level="3" type="T">Dynamic Configuration Is Empty</Trace>
<Trace level="3" type="T">Attached will be Deleted cid:payload-001708D1A20E1DDDAD97A993DAB6CB91(@)sap.com</Trace>
<Trace level="3" type="T">Attached will be Deleted cid:payload-001708D1A20E1DDDAD97A993DB0E4B91(@)sap.com</Trace>
<Trace level="1" type="T">ContentType application/xml</Trace>
</Trace>
</Trace>
</Trace>
Thanks

BaseRuntime Exception during Message Mapping

Hi I am performing the scenario File --> XI --> File
I want to do the File content Conversion (FCC) only at the Receiver side.
My source file(Message Type) is XML which looks like as below:
<?xml version="1.0" encoding="UTF-8" ?>
- <ns0:MT1_FCC xmlns:ns0="http://accenture.com/xi/F2F">
- <Name_>
- <Name>
<FName>abc</FName>
<MName>bcd</MName>
<LName>cde</LName>
</Name>
</Name_>
</ns0:MT1_FCC>
My target file would be the text file which will look like as follows:
abc#bcd#cde
However at runtime the Error is thrown with BaseRuntimeException in Message Mapping which simple one to one mapping from source message to target message . the source and the target message are same.
The Error message is as follows:
<Trace level="1" type="T">RuntimeException during appliction Java mapping com/sap/xi/tf/_MM_FCC_</Trace>
<Trace level="1" type="T">com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: XML Declaration not allowed here.(:main:, row:1, col:8) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException
Kindly Look into the Issue..

Hi i think you are getting confused by the Sorce Structure...
Ok lemme retype it for You and please then tell me the necessary parameters needed to convert the source xml file into the target text file
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT1_FCC xmlns:ns0="http://accenture.com/xi/F2F">
 <FullName>
 <Name>
 <FName>abc</FName>
 <MName>bcd</MName>
 <LName>cde</LName>
 </Name>
 </FullName>
</ns0:MT1_FCC>

Run time error during message mapping transformation

Hello,
i created a scenario and tried to execute . i got this error .
RuntimeException in Message-Mapping transformation: Runtime exception during processing target field mapping /ZCRM_CRMXIF_ORDER_SAVE_M01/IDOC/BEGIN. The message is: Exception:[java.lang.RuntimeException: Error: Occurred in RFC Look UpPlain exception:Problem when calling an adapter by using communication channel RFC_Lookup_Receiver (Party: , Service: Test_ReceiverSystem, Object ID: 1772b13e46b93b99bca48e278463007d) Check whether the communication channel exists in the Integration Directory; also check the cache notifications for the instance Integration Server (central Adapter-Engine) Channel object with Id Channel:1772b13e46b93b99bca48e278463007d not available in CPA Cache. com.sap.aii.mapping.lookup.LookupException: Problem when calling an adapter by using communication channel RFC_Lookup_Receiver (Party: , Service: Test_ReceiverSystem, Object ID: 1772b13e46b93b99bca48e278463007d) Check whether the communication channel exists in the Integration Directory; also check the cache notifications for the instance Integration Server (central Adapter-Engine) Channel object with Id Channel:1772b13e46b93b99bca48e278463007d not available in CPA Cache. at com.sap.aii.ibrun.server.lookup.AdapterProxyLocal.<init>(AdapterProxyLocal.java:61) at com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.getProxy(SystemAccessorInternal.java:98) at com.sap.aii.ibrun.server.lookup.SystemAccessorInternal.<init>(SystemAccessorInternal.java:38) at com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.getConnection(SystemAccessorHmiServer.java:270) at com.sap.aii.ibrun.server.lookup.SystemAccessorHmiServer.process(SystemAccessorHmiServer.java:70) at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169) at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:296) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:211) at com.sap.aii.utilxi.hmis.web.workers.HmisInternalClient.doWork(HmisInternalClient.java:70) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496) at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634) at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325) at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887) at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241) at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92) at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148) at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33) at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41) at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37) at java.security.AccessController.doPrivileged(Native Method) at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170) ] in class com.sap.xi.tf._XiameterBasicRegistration_MM_ method crmRfcLookUp$[, , , , Test_ReceiverSystem, , com.sap.aii.mappingtool.tf3.rt.Context@26dd0a50]
can any one tel me wats going wrong ??

The error shows that you are using business system and comm. channel in UDF for doing some processing. The error is because it is not able to locate the specified comm channel for the business sytem.
please check if the comm. channel name and business system names are spelled correctly. Also you can try refreshing the CPA cache/ XI cache.

Java heap space error occured during message mapping of FILE to IDOC

hello Friends,
I am trying to do the message mapping for File to Idoc scenario.
Idoc which I am using is HRMD_A.HRMD_A06 and infotype which I want to update is 14. I am trying to map the message type which I hav created for infotype 14 with the IDOC
Its very simple scenerio but every time I try to save the mapping before activating it I get an error:
Java heap space
Internal problem occurred (INTERNAL_PROBLEM)
Java heap space.
I am not able to figure out what possibly is the problem wheather its from my end or the BASIS end.
Kindly help.
Regards,
Lokesh

As the server probably survives (you restart your Integration Builder and can probably connect immediately), the problem will be on your side (client). Did you add one or more large xml-test-instances to the mapping ? If yes, delete them, because they lower the performance and can make problems. If not, then this is a strange problem. Even if the Idoc structure is complex, the mapping object itself cannot be that large.Is this problem only with this one mapping ?
CSY
Edited by: Christian Sy on Mar 9, 2010 6:26 AM

In Idoc bundling ...message mapping not found

Hi XI Friends..
In my File to Idoc scenario..i want to send multiple IDOCs from the XI without a BPM .
I am following blog by Michal.
<a href="///people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change:///people/michal.krawczyk2/blog/2005/12/04/xi-idoc-bundling--the-trick-with-the-occurance-change
I have xsd for source ..so i created one external definition .and message interface for outbound.
following the above blog by michal..
i imported idoc ..and i exported that idoc into xsd and i changed the occurance of idoc to unbounded and again imported as external definition.
i created the message mapping between these two external definitions.and tested ..
As in michal 's blog..
In Interface mapping..i given source and target interface as standard idoc.and clicked on Read interface then i am not finding the message mapping created in previous step..
i refreshed cache also..
please guide me.....
regards
ram

Hi bavesh...
thank you so much for very your quick responses..
i got xsd as source..based on xsd i created external definition for source xsd and i created outbound interface based on source external deifinition MI_OUT_WearUnits.
and i imported Idoc and exported as xsd and changed occurance to unbounded and again imported as external definition.
i did mapping between these two external definitions.
and i selected standard idoc for source and target interface for interface mapping and given message mapping of previous step.
In ID
sender agreement :
 sender service :BS_external
 sender interface :MI_OUT_WearUnits
receiver agreement:
 receiver service :R/3
 receiver interface : standard Idoc
Interface determination:
sender service :BS_external
sender interface :MI_OUT_WearUnits
reciever service :R/3
and clicked create
inbound interface : Standard IDOc
i am not getting Interface mapping which i created in IR.
i tried Enhance interface determination also..
please guide me....
waiting for your help.
regards
ram

Message Mapping : ( Not Activating )-Main Exception in thread "main"

Hi all
 I have configured a message mapping , with proper occurence checked for
both source & target MesTypes.
But on activation it is throwing the error :
java.lang.NoClassDefFoundError: com/sun/tools/javac/Main Exception in thread "main"
Also my previous mappings are also not activating , which were running properly previously...
i tried these option already :-
--> i also restart the Java Stack...
---> Re: JAVA stack not starting
> SAp note 928038
still i am getting the same error..
Regards
Ashutosh Rawat

Ashutosh,
I am not sure weather it will resolve your problem but you can give a try to it.
If you have the access for tcode "SICF" then
1. Run tcode SICF, and press F8 button.
2. default_host>sap>xi.
3. Now check the below mentioned are activated (activated services will be in black) or not, if not then just right click and activate the service:
 i). adapter_plain
 ii). cache
 iii). cache_gui
 iv). cache_ssl
 v). docu_apperror
 vi). docu_syserror
 vii). engine
viii). simulation
Regards,
Sarvesh
Message was edited by:
 Sarvesh Singh
 SFIC is corrected to "SICF"

Set a variable in Adapter Module and read it during message mapping

Hi guys,
is there any way, how I could set some variable and store its value during the adapter module processing and read back this value in message mapping and use it? Without using a database or files.. I mean, some j2ee storage or something like that..
Thanks for your help,
Olian

Hi guys,
thanks for your answers.. just a clarification, what the problem is.
I need to validate a message in the adapter module, if it's digital signature is valid. If it is, I need to send back to the sender a return code (message) OK, otherwise ERROR. I can't modify the message (or dynamic configuration) as I'm using a WSS in the sender channel. The system doesn't allow me to change anything in the message, so I can't find out in the mapping what the validation result was. I then tried to do the validation directly in the message mapping, but I have some issues there with libraries or what, because the validation code, which works in the adapter module, doesn't work in the mapping java class. So my final thought was maybe I could validate the message in the adapter module and pass the result to the message mapping and then create an appropriate return message (in the mapping). However, I see no way of passing a value there. I'm stuck and have no Idea how to resolve the problem. Any hints guys?
Thanks a lot for your help!
Olian

How to get the message ID generated by the PI system during message mapping

Hi All,
I have a file to file scenario, where during the mapping, I want to map and send the Message ID generated by PI.
Can anyone please help me with this?
Kind regards,
Joe

Hi,
You have write UDF for this.
Please see the below code .
java.util.Map map = container.getTransformationParameters();
String MesID = (String)map.get(StreamTransformationConstants.MESSAGE_ID);
return MesID;
Hope this helps to you.
Regards,
P.Rajesh

Message mapping not generating target fields

hi
iam doing jdbc--->rfc (bpm) created a one2one message mapping to import rfc table.
thanks in advance
sri

Hi Sri Rao,
Since you have created a one to one mapping, it would be required to map all the fields in your target message to ur source fields. In case there r some target fields which do not relate to your source field, map it onto a constant. This is all that is required to be done from what i understand from your query. In case there r further problems send the source n target data structure n i will be able to help you out better.
Cheers,
Christina

Function Module Undefined during message mapping.

Hi,
My Scenario is Idoc to Multiple Files without any condition i have to drop 2 files at the 2 differient directories of FTP,
So we are using PI 7.1 and in the Message Mapping using Signature Tab we have added 2 Target messages and at the source we have used the IDOC.
When we see the structure under Definition Tab in Message Mapping, We are facing the below error
"FUNCTION MODEL UNDEFINED"
So can anyone suggest what could be the problem, do i need to change any occurence in the signature tab for the message types else what shuld i do to get the structures in the Definiton Tab.
Please suggest how to approach this..
Thanks,
--Kishore

My Scenario is Idoc to Multiple Files without any condition i have to drop 2 files at the 2 differient directories of FTP,
1. Use multi mapping - /people/jin.shin/blog/2006/02/07/multi-mapping-without-bpm--yes-it146s-possible
2. use two different inbound interfaces, and do two different interface determination without conditions for the same receiver determination

Whitespaces in XML during message mapping not preserved

Similar Messages

Maybe you are looking for