Z IDocs on PI 731 IDoc_AAE

[DG]

Hi,

I do have a receiver IDoc_AAE Adapter on 731.

I have been processing other types of idoc. I have with the same setup processed INVOIC01 without any problems. 

But now when I need to process our custom idoc ZPOD01.DELVRY03. The IDOC adapter does not seems like it is working.

I do get the following error:

IDOC_ERROR_PARSE_FAILURE: Invalid character encountered within IDocXML for type <DELVRY03>:

state=READING_CONTROLRECORD_STARTTAG, charPosition=89, lineNumber=1, columnNumber=90, invalidChar=U+003E,

sourceSnippet=...UTF-8" standalone="no"?><DELVRY03><IDOC BEGIN="1"><EDI_DC40><IDOCTYP>DELVRY03</IDOCTYP><SNDPRT>LI</S...

The idoc looks like the following

<?xml version="1.0" encoding="UTF-8"?>
<DELVRY03>
          <IDOC BEGIN="1">
                    <EDI_DC40>
                              <IDOCTYP>DELVRY03</IDOCTYP>
                              <SNDPRT>LI</SNDPRT>
                              <SNDPRN>9999999999</SNDPRN>
                              <RCVPRT>KU</RCVPRT>
                              <RCVPRN>0000000901</RCVPRN>
                    </EDI_DC40>
                    <E1EDL20 SEGMENT="1">
                              <VBELN>5232080110</VBELN>
                              <LIFEX>23124033608</LIFEX>
                              <PODAT>20111115</PODAT>
                              <POTIM>1119</POTIM>
                    </E1EDL20>
          </IDOC>
</DELVRY03>

Any ideas on how I can find the > which is the invalid car U+003E.

Daniel

http://figaf.com

[MichalKrawczyk · Accepted solution]

hi,

can you compare the sp level with oss notes on this issue?

Note 1736292 - Idoc_error_parse_failure Java IDoc_AAE

Regards,

Michal Krawczyk

[DG · Accepted solution]

Hi

I did have a look at the note, we are not on that support pack. So I'll ask the basis to install that patch.

For the Invoice I have been able to fill in data to the  <IDOCTYP>DELVRY03 to make sure that the adapter reconized the file as being of the correct type.

[vk_k3 · Accepted solution]

HI Michael,

I have asked basis to install that patch for the same Issue we are facing,

but it still doesnt work.

Do you have any other suggestion ?

Regards,

Vkjoat

[DG · Accepted solution]

Interesting. Let me now if you are getting any information on a OSS.

[Former Member · Accepted solution]

Hi Daniel,

Just as a sanity check & it almost appears as though there is some sort of XSD validation taking place but I wouldn't want to assume 🙂

Check the values you have populated (e.g. SEGMENT) against the IDOC XSD & possible enumerations. I'm really interested in the outcome and if it is actually enforcing XSD validation. If it is, the error messaging should have been a bit more descriptive I thought...

Regards, Trevor

[DG · Accepted solution]

The add XML validation was good.

I was missing the SEGMENT in EDIC record.

[DG · Accepted solution]

The validation helped.

Making sure that EDI_DC40 has to have the segment.

then also my time <POTIM>1119 also need to be 6 chars long.