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

XML IDoc conversion: No known segments identified

<pre>

Hi All,

I am doing a JDBC to IDOC Scenario. When I done this I am getting following Error when I checked in SXMB_MONI

XML IDoc conversion: No known segments identified

Here is my JDBC Structure

Occurences Type

&#61656;MURTHY_JDBCSENDER_MT 1..1 MURTHY_JDBCSENDER_DT

&#61656; Row 1..1

o Name 1..1 xsd:String

o City 1..1 xsd:String

o District 1..1 xsd:String

Here is my IDOC Structure Mapping is Like this

&#61656;ADRMAS02

&#61656;IDOC

BEGIN -


&#61664;Constant(1)

&#61656;EDI_DC40

SEGMENT -


&#61664;Constant(1)

TABNAM -


&#61664;Constant(EDI_DC40)

DIRECT

IDOCTYP -


&#61664;Constant(ADRMAS02)

MESTYP -


&#61664;Constant(ADRMAS)

SNDPOR -


&#61664;Constant(NA)

SNDPRT -


&#61664;Constant(NA)

SNDPRN -


&#61664;Constant(NA)

RCVPOR -


&#61664;Constant(NA)

RCVPRN -


&#61664;Constant(NA)

&#61656;E1ADRMAS

SEGMENT -


&#61664;Constant(1)

OBJ_TYPE

OBJ_ID

--

--

--

&#61656; E1BPAD1VL

SEGMENT -


&#61664;Constant(1)

NAME -


&#61664;Mapped to Name from JDBC structure

CITY -


&#61664;Mapped to City from JDBC structure

DISTRICT---&#61664;Mapped to District from JDBC structure

---

---

-


&#61656; E1BPAD1VL1

&#61656; E1BPADTEL

&#61656; E1BPADFAX

&#61656; E1BPADTTX

&#61656; E1BPADTLX

&#61656; E1BPADSMTP

&#61656; E1BPADRML

&#61656; E1BPADX400

&#61656; E1BPADRFC

&#61656; -


&#61656; --

&#61656; --

&#61656; --

For all the remaining segments I have given Constant Value 1

When I checked in SXMB_MONI I found the error message as

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!--

Call Adapter

-->

- 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:ApplicationFaultMessage namespace="" />

<SAP:Stack>Error: XML IDoc conversion: No known segments identified</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

Message in SXMB_MONI in Payloads from Inbound Messges

Resultant message is like this..

<?xml version="1.0" encoding="utf-8" ?>

- http://murthy.com/JDBC2IDOC">

- <row>

<Name>AA</Name>

<City>AA</City>

<District>A</District>

<Flag>1</Flag>

</row>

- <row>

<Name>AAC</Name>

<City>CC</City>

<District>B</District>

<Flag>1</Flag>

</row>

</ns:MURTHY_JDBCSENDER_MT>

Message in payloads from Request message mapping .....

<?xml version="1.0" encoding="UTF-8" ?>

- <ADRMAS02>

- <IDOC BEGIN="1">

- <EDI_DC40 SEGMENT="1">

<TABNAM>EDI_DC40</TABNAM>

<DIRECT>2</DIRECT>

<IDOCTYP>ADRMAS02</IDOCTYP>

<MESTYP>ADRMAS</MESTYP>

<SNDPOR>NA</SNDPOR>

<SNDPRT>N</SNDPRT>

<SNDPRN>NA</SNDPRN>

<RCVPOR>NA</RCVPOR>

<RCVPRN>N</RCVPRN>

</EDI_DC40>

</IDOC>

</ADRMAS02>

</pre>

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    Posted on May 25, 2007 at 05:46 AM

    Your mapping is the issue here,

    Map the ROW from the JDBC source to E1ADRMAS and E1BPAD1VL .

    Regards

    Bhavesh

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Bhavesh Kantilal

      Bhavesh,

      Here in we20 Inbound options I have given the Process Code -- APLI(Inbound IDoc: Individual Processing)

      and checked the Cancel processing After Syntax Error check box.

      I could not found the option "Process Immediately" here...

      Could you please tell me where it would be..

      Thanks

      Murthy

  • Posted on May 25, 2007 at 06:02 AM

    Check the IDX1 entry , RFC destination entry. I think, it is not pointing correctly . in XI system

    Also delete the Idoc metadata from the in Transaction IDX2 and reimport the same.

    Have a look into this SAP Note- 742093

    Regards,

    Prateek

    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.