XML - FML conversion

Hi,
We want to make use of the XML - FML conversion methods available in weblogic.wtc.gwt; specifically XmlFmlCnv.XMLtoFML32 and XmlFmlCnv.FML32toXML. We cannot find any reference to these in WLS 8.1, the only references found relate to WLS 6.1 (see http://edocs.beasys.co.jp/e-docs/wls61/javadocs/weblogic/wtc/jatmi/class-use/TypedFML32.html
and
http://edocs.beasys.co.jp/e-docs/wls61/javadocs/weblogic/wtc/jatmi/class-use/FldTbl.html)
Are these facilities available in 8.1 for developer use?
If so can anyone point me to documentation, etc.
or if not any suggestions as to how we can accomplish such transformation?
Thanks in advance,
Malcolm.

Hi Todd,
Thanks for the feedback. We had considered the options you suggested; we cannot use the tBridge option because we require a real-time request response operation; and secondly, we require the conversion to occur on the WLS/WTC side rather than within Tuxedo - essentially the simple XML/FML conversion available in tBridge.
The site currently has a Tuxedo/eLink integration environment. They are introducing WebLogic Integration, and want to use WTC to provide a seamless interconnection between the two integration environments without modifying the Tuxedo side in any significant way.
Regards,
Malcolm.

Similar Messages

PARSE_APPLICATION_DATA Error during XML = ABAP conversion: Response Message; CX_ST_DESERIALIZATION_ERROR in /1SAI/SAS0446CC11CC6EC1AD4789 Line 24 An error occurred when deserializing in the simple transformation program /1SAI/SAS0446CC11CC6EC1AD4789

Hi Experts ,
i have a scenario proxy to soap where i am getting error while getting the response .
we are sending the request successfully and getting response .some times we are getting in proxy level error below
PARSE_APPLICATION_DATA Error during XML => ABAP conversion: Response Message; CX_ST_DESERIALIZATION_ERROR in /1SAI/SAS0446CC11CC6EC1AD4789 Line 24 An error occurred when deserializing in the simple transformation program /1SAI/SAS0446CC11CC6EC1AD4789 (Cha
Please help us to fix this bug in proxy response.
Regards
Ravi

Hello Ravinder,
Can you please post the complete stack trace, it seems to be some fields are getting truncated i,e data sent from the program to the proxy object might be violating some length restrictions.
Please check your message interface field lengths and what is being passed to the proxy.
Regards,
Ravi.

XML IDoc conversion: No known segments identified

Hi all,
am working on a File to IDoc scenario. In runtime, error occurs at Call Adapter phase.
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>XML IDoc conversion: No known segments identified</SAP:P1>
Can anyone help me in diagnosing.
Thanks,
Chilanka

Hi,
This issue wis not with Mapping.
The issue is that the utout of the mapping does not confirm to the Idoc metadata,
Exactly why I want to look at the output of the mapping.
Regards
Bhavesh

StrictXml2PlainBean - to have an XML - EDI conversion?

Dear Experts,
I'm experimenting with the EDIFACT XML --> EDIFACT conversion in XI. As we already know, there is no "out of the box" solution for it from SAP itslef. That's why we have to use a 3rd party solution for this conversion. (e.g. Seeburger, ACTIS, conversion agent,...)
But what about the StrictXml2PlainBean adapter module?
In this docu I read that it's good for XML to plain text conversions:
http://help.sap.com/saphelp_nw04/helpdata/en/44/748d595dab6fb5e10000000a155369/content.htm
Do you have any experience with this?
Is it OK for this kind of complex tasks or is it just an alternative for the File adapter's file content conversion funcionality?
Any comments/experiences are welcome!
Thank you in advance!
Andras

But what about the StrictXml2PlainBean adapter module?
>>>
this module is very similar to what we have as FCC in the file adapter. But for complex structure like EDIFACT, i dont think it can be of much use.

Error in IDOC: XML IDoc conversion: No known segments identified

Hi Team
i am facing error in my scenario. When we are testing my interface, another Interface is picking up the Messages and resulting into an error.
There is no mapping involved in my scenario.
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<SAP:P1>XML IDoc conversion: No known segments identified</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Error: XML IDoc conversion: No known segments identified</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
please help me out
thanx in advance

Hi,
Do The following:
1) Delete the IDX2 entry and try to reimport once again....and in the IR also do the same.
2) Have a look into this SAP Note- 742093
3) Check the IDX1 entry , RFC destination entry... may be not pointing correctly.
4) If any field which is mandatory in the idoc must not be disabled...take care about it.
Hope this will help you...
Regds,
Pinangshuk.

Error during XML = ABAP conversion

Hi
We have a synchronous call from a SRM application through a proxy framework to a vendor http server through XI. The response from the vendor's http server is returned through a custom structure -and is returned through XI back to the calling SRM application.
After receiving the response, the calling SRM application checks for a particular field value of the custom return structure for a error code and sends out an email - accordingly.
Now, the response message comes back from the vendor's server - but the lines of code beyond the synchronous call in the SRM calling application does not get executed ( mail generation part ) I get the following error on the SRM front end - Error in Exchange Infrastructure: Error during XML => ABAP conversion (Response Message; error ID: CX_ST_MATCH_ELEMENT; (/1SAI/TXS00000000000000000001 XML Bytepos.: 39 XML Path: Error Text: System e
Now, this error when occured in our dev environment, I set the extended xml attribute property to 'X' for the synchronous payload in calling SRM application code. The problem is, this error is occuring now in our QA environment inspite of this property being set.
Any ideas/suggestions as to why this message occurs in a standard proxy framework setup ?

Hi,
Please check this link <a href="http://help.sap.com/saphelp_nw04/helpdata/en/0c/402040abf2c442e10000000a1550b0/content.htm"></a>
This talks about having the first element of the xml fragment as X0.
Hope this helps.
Regards,
Smitha.

Error during XML = ABAP conversion, empty tag

Hi.
Im sending data from a Data Base to a proxy using BI.
But when I get an empty response from the data base wich gives me an empty XML tag the proxy shows me an error:
-PARSE_APPLICATION_DATA Error during XML => ABAP conversion (Response Message; error ID: CX_ST_MATCH_ELEMENT;
-Error during XML => ABAP conversion (Response Message; error ID: CX_ST_MATCH_ELEMENT;
-System expected the end of the element 'STMT_DC_response'
This is the message that originates the fail:
<?xml version="1.0" encoding="utf-8" ?>
<ns0:MT_PRV23_BS_desg_response xmlns:ns0="urn:tompla-com:xi:ventas_SD">
<STMT_response>
<row>
 <TIPO>P</TIPO>
 <NUM_OT>55062330</NUM_OT>
 <NUM_DESGLOSE>1</NUM_DESG>
 <CANT_DESG>1724000</CANT_DESG>
</row>
</STMT_response>
<STMT_DC_response />
</ns0:MT_PRV23_BD_desg_response>
In case that the tag is filled runs ok
<?xml version="1.0" encoding="utf-8" ?>
<ns0:MT_PRV23_BD_desg_response xmlns:ns0="urn:tompla-com:xi:ventas_SD">
<STMT_response>
 <row>
 <TIPO>P</TIPO>
 <NUM_OT>55062330</NUMERO_OT>
 <NUM_DESG>1</NUM_DESG>
 <CANT_DESG>1724000</CANT_DESG>
 </row>
</STMT_response>
<STMT_DC_response>
 <row>
 <TIPO>P</TIPO>
 <NUMERO_OT>55062330</NUMERO_OT>
 <NUMERO_DESGLOSE />
 <COD_CAR_ADICIONA>8</COD_CAR_ADICIONA>
 <PORC_CAR_ADICION>1</PORC_CAR_ADICION>
</row>
</STMT_DC_response>
</ns0:MT_PRV23_BD_desg_response>
The definition for the data is:
STMT_DC_response 0..1
row 0..n
 tipo 0..1
Thanks for the help you can give me about my problem with empty tags.

I moved this question to other forum
Expert Forums » SAP NetWeaver » Exchange Infrastructure

XML - ABAP conversion, empty tag

Hi.
Im sending data from a DB to a proxy using XI.
But when I get an empty response from the DB, wich gives me an empty XML tag the proxy shows me an error:
-PARSE_APPLICATION_DATA Error during XML => ABAP conversion (Response Message; error ID: CX_ST_MATCH_ELEMENT;
-Error during XML => ABAP conversion (Response Message; error ID: CX_ST_MATCH_ELEMENT;
-System expected the end of the element 'STMT_DC_response'
This is the message that originates the fail:
<ns0:MT_xxx_response xmlns:ns0="urn:s-com:xi:SD">
<STMT_response>
<row>
 <c11>P</c11>
 <c12>55062330</c12>
 <c13>1</c13>
</row>
</STMT_response>
<STMT_DC_response />
</ns0:MT_xxx_response>
In case that the tag is filled runs ok
<ns0:MT_xxx_response xmlns:ns0="urn:s.com:xi:SD">
<STMT_response>
 <row>
 <c11>P</c11>
 <c12>55062330</c12>
 <c13>1</c13>
 </row>
</STMT_response>
<STMT_DC_response>
 <row>
 <c21>P</c21>
 <c22>55062330</c22>
 <c23 />
</row>
</STMT_DC_response>
</ns0:MT_xxx_response>
The definition for the data is:
STMT_DC_response 0..1
row 0..n
 tipo 0..1
Thanks for the help you can give me about my problem with empty tags.

thanks for your help!
yes, The definition for the data is:
STMT_DC_response 0..1
to be sure I disabled that node, so I wont get it from the DB, and It was ok
this is ok:
<ns0:MT_xxx_response xmlns:ns0="urn:s-com:xi:SD">
<STMT_response>
<row>
<c11>P</c11>
<c12>55062330</c12>
<c13>1</c13>
</row>
</STMT_response>
</ns0:MT_xxx_response>
but this is not
<ns0:MT_xxx_response xmlns:ns0="urn:s-com:xi:SD">
<STMT_response>
<row>
<c11>P</c11>
<c12>55062330</c12>
<c13>1</c13>
</row>
</STMT_response>
<STMT_DC_response />
</ns0:MT_xxx_response>

XML = ABAP conversion error (CX_ST_GROUP_MISSING_CASE)

Hi ,
we are using wsdl connection
We are not able to display data in SAP
its showing error :
Error during XML => ABAP conversion (Response Message; error ID: CX_ST_GROUP_MISSING_CASE; (/1SAI/TXS00000000000000000010 XML Bytepos.: 205 XML Path: root(1)ns0:requestEventResponse(1) Error Text: Element 'TESTRESPONSE' missing))

Are you by any chance using a message interface with multiple namespaces as source for your ABAP proxy? I am currently facing the very same problem and my best guess so far is that the ABAP proxy cannot handle multiple namespaces in one message.
Did you get open a ticket on SapOSS? Any hints are very welcome!
Stefan

IDOCType PORDCR101 : XML IDoc conversion: No known segments identified

Hello all,
I'm strugling with the mapping to the IDOC create puchase order PORDCR1.PORDCR101.
The source structure for the moment is exactly the same as the target strcuture i.e. our IDOC.
So I would not expect to much problems with this one.
However, when sending the message we get the following error in SXI_MONITOR:
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<SAP:P1>XML IDoc conversion: No known segments identified</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: XML IDoc conversion: No known segments identified</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
I also augmented the trace lvl to 3 and got the following in the Trace-part of TC SXI_MONITOR and
suspect it starts to get wrong already in the beginning
- 
<Trace level="1" type="T">----
</Trace>
<Trace level="1" type="T">---- Outbound IDoc-Adapter -
</Trace>
<Trace level="1" type="T">----
</Trace>
Trace level="1" type="T">Convert one IDoc</Trace> .
<Trace level="2" type="T">Convert Control Record</Trace>
<Trace level="2" type="T">Convert Data Records</Trace>
<Trace level="3" type="T">Segment= E1BPMEPOHEADER</Trace>
<Trace level="2" type="T">Ignore unknown Segment E1BPMEPOHEADER</Trace>
<Trace level="2" type="T">Ignore segment field: COMP_CODE</Trace>
<Trace level="3" type="T">Segment= E1BPMEPOHEADERX</Trace>
<Trace level="2" type="T">Ignore unknown Segment E1BPMEPOHEADERX</Trace>
<Trace level="3" type="T">Segment= E1BPMEPOADDRVENDOR</Trace>
<Trace level="2" type="T">Ignore unknown Segment E1BPMEPOADDRVENDOR
I already found the four or so other threads on the SDN website about this error and in the mean-time tried them (delete and reload the structure with IDX2, set the begin and segment-attribute to 1, make sure that the segments-names self are also mappend) but to no avail.
We just implemented two other IDOC's (DELVRY03 and WMMBID02) and they arrive at SAP without problmens.
Hope you have form ideas to get me out of this one.
Tnx and best regards.
Bart.

Hi Bart,
We had a similar problem.... It took us 2 days to find out what the problem was... Nothing on SDN was helpfull so far... First we incremented the trace level of XI to see the debug messages... Then we saw that certain segments could not be identified and are ignored, others not...
So further investigation in IDX2 to the specific IDoc with problems showed us a list with all used segments and their versions. Some segments had only 1, others had more versions....
So we could identify the problem as a segment version problem. It seemed that our IDoc Communication Channel took not the most recent version. So we changed the "Segment Version" to the most recent one and the problem was solved!
Please reward points if this was usefull to you...
cheers!
Pedro

XML IDoc conversion: No known segments identified PPCC2PRETTICKET01

Hello to everybody,
I'm working with JDBC adapter to IDOC scenario with standard message PPCC2PRETTICKET01 and I found this message:
IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME
XML IDoc conversion: No known segments identified
I've read previous thread and I've already try to Reimport the Idocs into Repository
and Delete the Idoc metadata from the in Transaction IDX2 and reimport the same.
I'm in SAP NetWeaver 2004s.
Do you have another ideas?
Many thanks

Hi,
I've filled up control record in message mapping, I tried with Apply C R but it doesn't work.
I don't know how to disable EDI_DC40 in message mapping because the fields are red.
I've filled up every segment field with a constant with the right segment name but nothing.
This is the payload after the error but since the JDBC adapter in:
<?xml version="1.0" encoding="UTF-8" ?>
- <PPCC2PRETTICKET01>
- <IDOC BEGIN="1">
- <EDI_DC40 SEGMENT="EDI_DC40">
<TABNAM>EDI_DC40</TABNAM>
<DIRECT>2</DIRECT>
<IDOCTYP>PPCC2PRETTICKET01</IDOCTYP>
<MESTYP>PPCC2PRETTICKET</MESTYP>
<SNDPOR>SAPXI0</SNDPOR>
<SNDPRT>LS</SNDPRT>
<SNDPRN>XIDEV100</SNDPRN>
<RCVPOR>SAPDEV</RCVPOR>
<RCVPRT>LS</RCVPRT>
<RCVPRN>SYSDEV300</RCVPRN>
</EDI_DC40>
</IDOC>
</PPCC2PRETTICKET01>
Thank for more ideas.
Fabrizio

XML IDoc conversion: No known segments identified ,only few times

Hi all,
Our scenario is in production and is working fine,few times i get the below error.
This is a Daily run scenario.This week it ran 5 time right and 2 , times it failed to create Idocs for the same sccenario.
Can any one help me.
<SAP:Category>XIAdapter</SAP:Category>
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
<SAP:P1>XML IDoc conversion: No known segments identified</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Error: XML IDoc conversion: No known segments identified</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error

check if these discussions help you:
XML IDoc conversion: No known segments identified
IDOCType PORDCR101 : XML IDoc conversion: No known segments identified
Regards,
Abhishek.

File XML Content Conversion: Problem with special characters

Hello,
in a file sender cc content conversion is used to transform a flat structure to XML. What we experiencecd is that the message mapping failed due to a character that was not allowed in XML:
I was assuming that the file content conversion just creates XML messages with allowed characters. Is there any way to configure content conversion to remove control characters which are not allowed in XML? Unfortunately the sender system cannot be modified.
Thank you.

Hi Florian,
Please use this UDF to remove special characters which prevent XML messages to form properly.
public static String removeSpecialChar(String s)
 try
 s=s.replaceAll("&","& amp ;");
 s=s.replaceAll("<" , " & lt ;");
 s=s.replaceAll(">", "& gt ;");
 s=s.replaceAll("'", "& apos ;");
 s=s.replaceAll("\"", "& quot ;");
 catch(Exception e)
 e.printStackTrace();
 return s;
Please remove spaces between characters within double quotes. I have added them because otherwise you can't see this code properly. Please check this below link , please replace the characters with proper values as the display is causing a problem here
http://support.microsoft.com/kb/316063
regards
Anupam
Edited by: anupamsap on Jul 7, 2011 4:22 PM
Edited by: anupamsap on Jul 7, 2011 4:23 PM

XML document conversion to Plain document in XI using JMS Adapter?

Hi,
We are trying to send an soap based XML document from ECC to MQSeries 6.0 using PI 7.0. I created receiver communicaiton channel to MQ with the below modules
1. AF_Modules/MessageTransformBean - Module Key XML2Plain
2. SAP XI JMS Adapter/ConvertMessageToBinary - Module Key CallJMSService
3. SAP XI JMS Adapter/SendBinarytoXIJMSService - Module Key Exit
Module configuration parameters I provided are
XML2Plain- Transform.Class com.sap.aii.messaging.adapter.Conversion
 TransformContentType text/plain;charset=utf-8
 xml.addHeaderLine 0
 xml.conversionType SimpleXML2Plain
 xml.fieldSeparator ,
 xml.fixedLengthTooShortHandling Cut
The payload I am using is
<?xml version="1.0" encoding="UTF-8"?>
<ns0:MT_Company xmlns:ns0="http://bnsf.com/hr/tm">
 <Row CCODE="1001" DESC="test company"/>
</ns0:MT_Company>
When I test in RWB
1. The channel monitoring shows green and the below message
"Successfully connected to destination 'queue:///QL_DAVEOUT?targetClient=1"
2. RWB shows error message "Error while sending message:invalid content type for SOAP:TEXT/HTML;HTTP 500 Timeout"
3. when I look at the message, I see the last message shows as
"2008-06-16 15:16:44 Success Transform: transforming the payload ..." and I do not see any more messages.
Can anyone help me here? Thanks in advance

I changed the payload to
<xml version="1.0" encoding="UTF-8">
<ns0:MT_Company xmlns:ns0="http://bnsf.com/hr/tm">
<row CCODE="1001" DESC="TEST" />
</ns0:MT_Company>
this time i am getting
<Trace level="1" type="T">Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_MM_SAP_COMPANY_TO_MQ_COMPANY_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Fatal Error: com.sap.engine.lib.xml.parser.ParserException: </ expected(:main:, row:4, col:17)</Trace>
<Trace level="1" type="T">com.sap.aii.ibrun.server.mapping.MappingRuntimeException: Runtime exception occurred during execution of application mapping program com/sap/xi/tf/_MM_SAP_COMPANY_TO_MQ_COMPANY_: com.sap.aii.utilxi.misc.api.BaseRuntimeException; Fatal Error: com.sap.engine.lib.xml.parser.ParserException: </ expected(:main:, row:4, col:17) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:73) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0_0.processFunction(MappingServiceObjectImpl0_0.java:131) at sun.reflect.GeneratedMethodAccessor411.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy220.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260) 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:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: </ expected(:main:, row:4, col:17) at com.sap.aii.mappingtool.tf3.Transformer.checkParserException(Transformer.java:187) at com.sap.aii.mappingtool.tf3.Transformer.start(Transformer.java:151) at com.sap.aii.mappingtool.tf3.AMappingProgram.execute(AMappingProgram.java:118) at com.sap.aii.ibrun.server.mapping.JavaMapping.executeStep(JavaMapping.java:64) at com.sap.aii.ibrun.server.mapping.Mapping.execute(Mapping.java:92) at com.sap.aii.ibrun.server.mapping.MappingHandler.run(MappingHandler.java:90) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleMappingRequest(MappingRequestHandler.java:95) at com.sap.aii.ibrun.sbeans.mapping.MappingRequestHandler.handleRequest(MappingRequestHandler.java:68) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceImpl.processFunction(MappingServiceImpl.java:79) at com.sap.aii.ibrun.sbeans.mapping.MappingServiceObjectImpl0_0.processFunction(MappingServiceObjectImpl0_0.java:131) at sun.reflect.GeneratedMethodAccessor411.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.ejb.session.stateless_sp5.ObjectStubProxyImpl.invoke(ObjectStubProxyImpl.java:187) at $Proxy220.processFunction(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.call(RFCDefaultRequestHandler.java:277) at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:219) at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:260) 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:102) at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172) Root Cause: com.sap.aii.utilxi.misc.api.BaseRuntimeException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: </ expected(:main:, row:4, col:17) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:157) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Root Cause: com.sap.engine.lib.xml.parser.NestedSAXParserException: Fatal Error: com.sap.engine.lib.xml.parser.ParserException: </ expected(:main:, row:4, col:17)(:main:, row=4, col=17) -> com.sap.engine.lib.xml.parser.ParserException: </ expected(:main:, row:4, col:17) at com.sap.engine.lib.xml.parser.XMLParser.scanEndTag(XMLParser.java:1872) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1846) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2845) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) -
at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:144) at javax.xml.parsers.SAXParser.parse(SAXParser.java:345) at com.sap.aii.mappingtool.tf3.rt.xparser.MTSaxHandler.run(MTSaxHandler.java:155) at com.sap.aii.mappingtool.tf3.rt.xparser.XParser.run(XParser.java:73) at java.lang.Thread.run(Thread.java:534) Caused by: com.sap.engine.lib.xml.parser.ParserException: </ expected(:main:, row:4, col:17) at com.sap.engine.lib.xml.parser.XMLParser.scanEndTag(XMLParser.java:1872) at com.sap.engine.lib.xml.parser.XMLParser.scanElement(XMLParser.java:1846) at com.sap.engine.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2845) at com.sap.engine.lib.xml.parser.XMLParser.parse0(XMLParser.java:231) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:145) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:160) at com.sap.engine.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:261) at com.sap.engine.lib.xml.parser.Parser.parseWithoutSchemaValidationProcessing(Parser.java:280) at com.sap.engine.lib.xml.parser.Parser.parse(Parser.java:342) at com.sap.engine.lib.xml.parser.SAXParser.parse(SAXParser.java:125) ... 4 more</Trace>

INVOIC96a to EDI-XML by Conversion Agent fails, Special Character Problem

Hi,
with your help in another thread, I recognized that the EDIFACT INVIOC96a Parser of the Itemfield Conversion Agent has a Problem with special characters.
So like described in this blog SAP XI supports EDIFACT i created a Library Project and tried to test the conversion.
It is only working when no special characters are in the EDI file. If there a special characters insight the file, conversion agent say's no error, but the xml file is corrupted. In fact you can't display it in IE or by opening it with XMLPad it says "Not well formed".
Hope that someone has an idea for this problem
Thank you
regards

Hi,
I have already faced the same problem when using Itemfield Conversion Agent.
I solved the same with change properties of the project.
In conversion agent project :
opne the menu : Project --> Properties --> Encoding --> Change the output Encoding Schema (None).
use None in that schema in place of XML.
Your problem can be solved.
Regards,
Sandeep Kaushik

XML - FML conversion

Similar Messages

Maybe you are looking for