Skip to Content
author's profile photo Former Member
Former Member

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.

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

4 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Jun 25, 2008 at 11:57 AM

    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

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jun 25, 2008 at 10:03 AM

    check with Idoc metadata

    IDX2 transaction

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jun 25, 2008 at 10:06 AM
    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Jun 25, 2008 at 10:08 AM

    Hi,

    Take the Inbound Payload from MONI and Test it in MApping

    Regards

    Seshagiri

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.