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" ?>
- <!-- Call Adapter
-->
- <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.
Similar Messages
-
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,
ChilankaHi,
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 -
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 thanksHi,
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:Errorcheck if these discussions help you:
XML IDoc conversion: No known segments identified
IDOCType PORDCR101 : XML IDoc conversion: No known segments identified
Regards,
Abhishek. -
Hi Everyone.
I've got some lovely XML IDocs. I'd like to read them into the IDOC Class Library and send them to SAP with JCo..........
But I can't get some simple code to parse the XML. I've been sending XMLs to SAP for a long time and they were always valid in SAP. They are also valid XML.
I also borrowed the code directly out of the JCo documentation, so you'd think it would work.
I'm using Java 6, IDoc Class lib 3.01. I've also tried Java 5. If I could parse the XML I would be using SAP 4.7 and JCo 3.01....
I've used JDOM for creating my XML. I've tried UTF-8 and ISO-8859-1 encoding. The error doesn't change
The error message i get is IDOC_ERROR_PARSE_FAILURE: Invalid charachter encountered in XML input data sourcee: state=EXPECTING_IMMEDIATE_TAG_END, charPosition=48, lineNumber=1, columnNumber=49, invalidChar=U+0053, sourceSnippet=...<?xml version "1.0" encoding="UTF-8"?>....
Heres my function I'm using.
(getRfcConnection is my own helper function to create a RFC Destination)
The rest of it is really just copied + pasted from the documentation.
public static void submitXml(Sap_Pruefziffer sap_pruefziffer, String language,String iDocXML)
throws JCoException, CS_Rfc_Exception, AbapException, IDocParseException
JCoDestination destination = getRfcConnection(sap_pruefziffer,language);
IDocRepository iDocRepository = JCoIDoc.getIDocRepository(destination);
String tid = destination.createTID();
IDocFactory iDocFactory = JCoIDoc.getIDocFactory();
//this would be great for re-implementing the OrderDataFactory
//although that works just fine
// a) create new idoc
/*IDocDocument doc = iDocFactory.createIDocDocument(iDocRepository,"MATMAS02");
IDocSegment segment = doc.getRootSegment();
segment = segment.addChild("E1MARAM");
// and so on. See IDoc Specification .....
JCoIDoc.send(doc, IDocFactory.IDOC_VERSION_DEFAULT, destination, tid);*/
// b) use existent xml file
//get IDOC XML/IDOC Parser
IDocXMLProcessor processor=iDocFactory.getIDocXMLProcessor();
//parse the XML/IDOC
IDocDocumentList iDocList=processor.parse(iDocRepository, iDocXML);//, IDocXMLFormat.SAP_RELEASE_610, IDocXMLProcessor.PARSE_WITH_FIELD_VALUE_CHECKING
//send the XML/IDOC per RFC (our destination)
JCoIDoc.send(iDocList, IDocFactory.IDOC_VERSION_DEFAULT, destination, tid);
//not really sure what this does
destination.confirmTID(tid);
Thanks for your help in advance
MartinHi Martin,
For the XML file processing we have to use XML Parsers, these are bit difficult.
We got the same issue in our project, we written normal java code to parse the xml file.
Do one thing, if the xml file is not big one then take the xml data into a string. parse the string based on characters < and >.
Suppose we have xml data as below
String str = "<emp>employee1</emp>"
You have to get the string between >,<.
Regards,
Lakshmi Prasad. -
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 <b>XML => ABAP conversion</b> (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 -
XML IDOC to Native IDOC Conversion
Hi,
We have a scenario, where we need to convert XML idoc into native idoc and write to a file. I am doing this based on
How To Convert an IDoc-XML structure to a flat file and vice versa in XI 3.0.
When I first executed the scenario, I was getting the following error
Z_ABAP_MAPPING_IDOC_TO_FLAT (type SAP-ABAP, kernel error ID UNCAUGHT_EXCEPTION) An exception with the type CX_SY_REF_IS_INITIAL occurred, but was neither handled locally, nor declared in a RAISING clause Dereferencing of the NULL reference.
After including the try-catch block, now i am just getting a blank file without any conversion.
Can anyone help me on this?
Regards,
RaviHi,
It looks to be error in ABAP mapping
To test ABAP mapping in XI use the transaction SXI_MAPPING_TEST after creating a little scenario in the directory.
Or even you could do this with below sample code
Lets create one ABAP mapping class with the method IF_MAPPING~EXECUTE
data: obj type ref to zcl_abap_mapping_test.
data: source type xstring,
result type xstring.
data: param type ref to IF_MAPPING_PARAM,
trace type ref to IF_MAPPING_trace.
create object obj.
try.
CALL METHOD obj->IF_MAPPING~EXECUTE
EXPORTING
SOURCE = source
PARAM = param
TRACE = trace
IMPORTING
RESULT = result.
CATCH CX_MAPPING_FAULT .
ENDTRY.
This is a link very useful for ABAP Mapping :
http://help.sap.com/saphelp_nw04/helpdata/en/86/8280ba12d511d5991b00508b6b8b11/frameset.htm
Or may be think this exception you need to catch it in the ABAP..
This may help u- http://help.sap.com/saphelp_47x200/helpdata/en/55/bff20efe8c11d4b54a006094b9456f/content.htm
just cross verify with this guide-
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e3ead790-0201-0010-64bb-9e4d67a466b4
Thanks
swarup -
IDOC_XML_FROM_FILE Error while loading XML as IDOC to ECC 6.0
I have successfully converted IDOC to XML file.
Getting Error while converting XML back to IDOC in ECC 6.0 using function: IDOC_XML_FROM_FILE
Segment EDI_DS40 is not defined.....I am really not sure about the error as this idoc was previously posted to the same ECC 6.0...
Exception SEGMENT_ERROR
Message ID: EA Message number: 721
Message:
The segment EDI_DS40 is not defined.
Secondly is there a way to load XML file via WE19?
Tx
SalmanThanks alot Oliver for taking a stab...
I created the XML file from within SAP by using the functionailty of this function module:-
IDOC_XML_TRANSFORM
I created my ZIDOC_XML_TRANSFORM and just added file download facility in that the rest is the same as the orignal function.
Is there any way for me to supress generation of ED_DS40 segements in the XML file?? -
XML IDOC post to R/3 Via WAS - want to see error content with JavaScript
Hi,
I am posting XML IDOCs to our R/3 system via a webpage that I have built with JavaScript. I am posting to the WAS, which is configured to read the XML IDOC with SAP's standard class handler CL_HTTP_IDOC_XML_REQUEST. We are on basis 620 support pack SAPKB62041.
In my webpage, I have the JavaScript code set to read the status and statusText so I can see the response from WAS when I post my XML IDOC. However, I am getting back very generic information when I encounter a 409 error. THe statusText is always "input_not_found". So I debugged the class handler code and found that SAP is returning back the more descriptive error info in HTML format.
I ran a packet sniffer to see what WAS returns and the info looks like this:
<html><head><title>IDoc-XML-inbound not ok</title><h1>IDoc-XML-inbound not ok</h1></head><body>
E:Table Lookup Error:300 Cannot map value for field MESCOD in table ZFI_IF_IDOCORG using values
SNDSAD = |TE| and RCVLAD = |GL| and MESTYP = |ACC_DOCUMENT|</body></html>
I want to know how I can get my webpage to read this HTML info and store that into an alert so I can read this text that I'm returning back to the HTTP post.
This is how my script looks. I'm using IE6.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<head>
<title>Test XML</title>
<SCRIPT ID=clientEventHandlersJS LANGUAGE=javascript>
<!--
function XMLHTTPButton_onclick(DataToSend) {
var xmlhttp = new ActiveXObject("Microsoft.XMLHTTP");
xmlhttp.Open("POST","http://some_server:1089/sap/bc/zxml_idoc?sap-client=200&sap-language=EN",false);
xmlhttp.setRequestHeader("Content-Type", "text/xml");
xmlhttp.send(DataToSend);
alert(xmlhttp.Status);
alert(xmlhttp.statusText);
alert(xmlhttp.responseXML.xml);
//-->
</SCRIPT>
</head>
<body>
<BR>
This page posts to
<BR>
http://some_server:1089/sap/bc/zxml_idoc?sap-client=200&sap-language=EN
<FORM name=xmlform method=post >
<P><TEXTAREA style="WIDTH: 623px; HEIGHT: 369px" name=xmlData rows=23 cols=77>
</TEXTAREA>
<P>
<INPUT type="button" value="Submit XMLHTTP" id=XMLHTTPButton name=XMLHTTPButton
LANGUAGE=javascript onclick="return XMLHTTPButton_onclick(document.xmlform.xmlData.value)">
</form>
Previously with this class handler, SAP returned the detailed info back to the "alert(xmlhttp.statusText)" and I had no problem seeing the return info. But now they have decided to format it in HTML and I don't know how to view this text since it has no ID on it to pull this into an alert box.
If anyone has any ideas, please let me know.
Thanks,
AndreaOk!
I have solve the problem. So, I was trying to connect via SSO within an user that was not registered in R/3 and I forgot it.
Sorry for the inconvenience. -
Error: IDoc XML data record
Hi all,
We have file->XI->idoc scenario and the problem we are facing is like, when the idoc structure is prepared using XSLT mapping, when the idoc is ready to get in thru the idoc adapter we are getting the following error.
<i><b>Error: IDoc XML data record: In segment
Z1UKGAS_HEADR attribute occurred instead of SEGMENT </b></i>
Anyone faced the same issue....if so pls do throw some light into this issue....
We r in XI 3.0 SP13...
Thanks & regards,
JayakrishnanHi,
In an IDOC structure segment attribute is requried. From the error you posted, it looks like seqment attribute is missing.
<Z>
<IDOC BEGIN="">
<ED SEGMENT="">
</ED>
</IDOC>
</Z>
Naveen -
Error : idoc xml record in segment attribute instead of SEGMENT
hi friends
can any one solve my problem. In message mapping I mapped with a IDOC. In message mapping I Mapped all the fields. Still I am getting the error as "IDOC XML RECORD IN SEGMENT ATRIBUTE INSTEAD OF SEGMENT" I dont know about this error.
can any one solve this problem please . I am doing this scenario since 5 days. help me..
thanks in advance
VasuHi Vasudeva,
Can you pls provide little more details on the scenario ?
Also at which place are you getting this error ?
Assuming that you have created a message mapping for some source message to target IDoc message, here are some suggestions.
1) Test the message mapping. (are you getting the error in testing itself ?)
2) Apart from mandatory fields' mapping, are there any constants to be assigned to some IDoc fields ? Or any node to be disabled ? Or any such additional things...
Regards, -
Error : IDoc XML data record: In segment attribute occurred instead of SEGM
hi friends
i am doing the file to idoc scenario. in message mapping i had done the static test. but what ever the fields i mapped in the idoc it was not populated in the idoc. and i am getting the error as
error :IDoc XML data record: In segment attribute occurred instead of SEGMENT
can any one solve the problem please
thanks in advance
VasuHi Vasudeva,
Pls do check the nodes which you have mapped to. Also make sure that your SEGMENT field in the target structure is mapped properly.
Cheers
JK -
Error : idoc xml data record : in segment attribute instead of SEGMENT
hi all
i am doing the file to idoc scenario. in that i am getting the error
error : IDOC XML Data record : In segment attribute instead of SEGMENT
i am doing this scenario since 4 days.
can anyone help me
thanks a lot
Vasuin ref. to my post in your earlier thread.
>>>>
in your mapping check, in your IDOC if Begin , segment etc are mapped to a constant say '1'.
Also ref: In segment IDOC attribute I occurred instead of SEGMENT -
XML-IDOC to Plain File: File Receiver Cnt Conversion Problem Nested Stucts
Hi all,
I have an IDOC-XI-File scenario and I have a problem with the file receiver adapter and the content conversion parameters when the final data type has nested structures. Imagine that I have something similar to the following:
My desire is to get something similar to this in the output file:
SEGMENT0;HEADER
SEGMENT1;100
SEGMENT2;0200000716
SEGMENT3;1000
SEGMENT2;0200000717
SEGMENT3;1000
SEGMENT3;1001
SEGMENT3;1002
But what we are getting is this:
SEGMENT0;HEADER
SEGMENT1;100
SEGMENT2;0200000716;SEGMENT3;1000
SEGMENT2;0200000717;SEGMENT3;1000;SEGMENT3;1001;SEGMENT3;1002
The content conversion parameters of the file receiver are as follow:
Recordset Structure: IDOC,EDI_DC40,E1STATS,Z1HDSTAT,Z1ITSTAT
IDOC.fieldSeparator: ;
IDOC. endSeparator: nl
IDOC. addHeaderLine: 0
EDI_DC40.fieldSeparator: ;
EDI_DC40. endSeparator: nl
EDI_DC40. addHeaderLine: 0
E1STATS.fieldSeparator: ;
E1STATS. endSeparator: nl
E1STATS. addHeaderLine: 0
Z1HDSTAT.fieldSeparator: ;
Z1HDSTAT. endSeparator: nl
Z1HDSTAT. addHeaderLine: 0
Z1ITSTAT.fieldSeparator: ;
Z1ITSTAT. endSeparator: nl
Z1ITSTAT. addHeaderLine: 0
Ive tried to use the parameter beginSeparator=nl for the segments Z1ITSTAT but its not working. I havent been able to find a solution in the other forums. Can anybody help me?
Thanks in advance
Roger Allué VallCan you explain it with my example? I can't see what you mean.
<ZSYSEX01>
.<IDOC BEGIN="1">
....<EDI_DC40 SEGMENT="SEGMENT0">
........<FIELD1>HEADER</FIELD1>
....</EDI_DC40>
....<E1STATS SEGMENT="SEGMENT1">
........<FIELD2>100</MANDT>
........<Z1HDSTAT SEGMENT="SEGMENT2">
...........<FIELD3>0200000716</FIELD3>
...........<Z1ITSTAT SEGMENT="SEGMENT3">
...............<FIELD4>1000</FIELD4>
...........</Z1ITSTAT>
........</Z1HDSTAT>
........<Z1HDSTAT SEGMENT="SEGMENT2">
...........<FIELD3>0200000717</FIELD3>
...........<Z1ITSTAT SEGMENT="SEGMENT3">
...............<FIELD4>1000</FIELD4>
...........</Z1ITSTAT>
...........<Z1ITSTAT SEGMENT="SEGMENT3">
...............<FIELD4>1001</FIELD4>
...........</Z1ITSTAT>
...........<Z1ITSTAT SEGMENT="SEGMENT3">
...............<FIELD4>1002</FIELD4>
...........</Z1ITSTAT>
........</Z1HDSTAT>
....</E1STATS>
.</IDOC>
</ZSYSEX01>
Regards,
Maybe you are looking for
-
RFC Error in Webdynpro Abap...
Hi, Im Using one FM SRM_DOCUMENT_CHECKIN_VIA_FILE...Inside that Fm it is usng some RFC Connection..while debugging Im getting an internal error in the FM as 'RFC server sapftp cannot be started - 1: Program no longer started via RFC'... Can An
-
BADI to change the PDS priority in ECC
Need to change the priority of the PDS during CIF. Please suggest the BADI which can be used in ECC side.I guess BAdis /SAPAPO/CURTO_SNP and /SAPAPO/CURTO_CREATE.can be used in APO. I need to change PDS value in ECC side while doing CIF or CURTO_CREA
-
After installing LR5, I try to launch the program but I receive a message saying LR5 has unexpectedly quit. Anyone who can help with this issue? This is part of the crash report: Application Specific Information: *** Terminating app due to uncaught e
-
Since upgrading to SL I have noticed a distinct degradation in performance of my MacBook. The major problem is with the finder. It sometimes just stalls, nothing works for ages and then suddenly it just kicks back into life. The battery icon also fai
-
We are using Tuxedo 6.5/Jolt 1.2 on Sun Solaris 8 Just like to find out if there are anyone out there who had encounter the problem of JSL server simply died or crashed as more and more users connected. Thanks