cancel
Showing results for 
Search instead for 
Did you mean: 

Error while processing a file in PI7.3

Former Member
0 Kudos

Hi,

  Iam getting the below error while processing a file.

 

IDoc: Error before sending :
IDocException com.sap.conn.idoc.IDocParseException: (7)
IDOC_ERROR_PARSE_FAILURE: Missing required <IDOC BEGIN="1"> tag
within IDocXML for type <ACC_DOCUMENT02>:

state=READING_IDOC_STARTTAG, charPosition=56,
lineNumber=2, columnNumber=18

Attaching the file at which PI is throwing an error.

Kindly provide me the solution for not getting the above error at PI level.

Accepted Solutions (0)

Answers (4)

Answers (4)

anupam_ghosh2
Active Contributor
0 Kudos

Hi Madhuri,

                          Could you please upload the mapping where this condition is being imposed, that  is not to generate the idoc when there is zero amount value. Is this file to idoc scenario?

Regards

Anupam

Former Member
0 Kudos

Yes, this is file to idoc scenario..

Former Member
0 Kudos

Hello,

Could u generate idoc xml corresponding to below source message (i guess this message has resulted into ***idoc.parse exception?):

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

<ns:MT_Fleet_Req xmlns:ns="http://honda:finance:GLPosting">

<Data1>

  <key>1</key>

  <Doc_Date>13/10/2013</Doc_Date>

  <AC_233000>0</AC_233000>

  <AC_224000>0</AC_224000>

  <Base_tax>0</Base_tax>

  <AC_342400>0</AC_342400>

  <Post_Indi_1>C</Post_Indi_1>

  <AC_826140>0</AC_826140>

  <AC_224010></AC_224010>

  <AC2_233000></AC2_233000>

  <Post_Indi_2></Post_Indi_2>

  <AC2_826140></AC2_826140>

  <Associat_Num></Associat_Num>

  <VIN_Num></VIN_Num>

  <Customr_Amnt></Customr_Amnt>

  <AC2_224010>]</AC2_224010>

</Data1>

<Data2>

  <key>2</key>

  <Doc_Date>13/10/2013</Doc_Date>

  <AC_233000></AC_233000>

  <AC_224000></AC_224000>

  <Base_tax></Base_tax>

  <AC_342400></AC_342400>

  <Post_Indi_1></Post_Indi_1>

  <AC_826140></AC_826140>

  <AC_224010>0</AC_224010>

  <AC2_233000>0</AC2_233000>

  <Post_Indi_2>C</Post_Indi_2>

  <AC2_826140>0</AC2_826140>

  <Associat_Num></Associat_Num>

  <VIN_Num></VIN_Num>

  <Customr_Amnt></Customr_Amnt>

  <AC2_224010>]</AC2_224010>

</Data2>

</ns:MT_Fleet_Req>

Thanks

Amit Srivastava

Former Member
0 Kudos

The below is the output I got when I tested above XML

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

<ACC_DOCUMENT02></ACC_DOCUMENT02>

Former Member
0 Kudos

Hello,

Why don't u use extended receiver determination and validate the condition by checking if all the amount in the input message is zero then don't create any idoc (i.e. ignore the message)?

Thanks

Amit Srivastava

Former Member
0 Kudos

IDoc XML should start like that

<?xml version="1.0" encoding="UTF-8" ?><Name_of_IDoc_MT><IDOC BEGIN="1">.....

Your IDoc probably does not have that "header".

How did you supplied that idoc xml? By hand from test or is it coming from other system?

It is also possible, that you are supplying xml, which is not representation of IDoc.

But anyway - reason is, that your IDoc XML does not have right format. Check that.

Former Member
0 Kudos

The below is the payload which got error as mentioned above

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

<ns:MT_Fleet_Req xmlns:ns="http://honda:finance:GLPosting">

<Data1>

  <key>1</key>

  <Doc_Date>13/10/2013</Doc_Date>

  <AC_233000>0</AC_233000>

  <AC_224000>0</AC_224000>

  <Base_tax>0</Base_tax>

  <AC_342400>0</AC_342400>

  <Post_Indi_1>C</Post_Indi_1>

  <AC_826140>0</AC_826140>

  <AC_224010></AC_224010>

  <AC2_233000></AC2_233000>

  <Post_Indi_2></Post_Indi_2>

  <AC2_826140></AC2_826140>

  <Associat_Num></Associat_Num>

  <VIN_Num></VIN_Num>

  <Customr_Amnt></Customr_Amnt>

  <AC2_224010>]</AC2_224010>

</Data1>

<Data2>

  <key>2</key>

  <Doc_Date>13/10/2013</Doc_Date>

  <AC_233000></AC_233000>

  <AC_224000></AC_224000>

  <Base_tax></Base_tax>

  <AC_342400></AC_342400>

  <Post_Indi_1></Post_Indi_1>

  <AC_826140></AC_826140>

  <AC_224010>0</AC_224010>

  <AC2_233000>0</AC2_233000>

  <Post_Indi_2>C</Post_Indi_2>

  <AC2_826140>0</AC2_826140>

  <Associat_Num></Associat_Num>

  <VIN_Num></VIN_Num>

  <Customr_Amnt></Customr_Amnt>

  <AC2_224010>]</AC2_224010>

</Data2>

</ns:MT_Fleet_Req>

Former Member
0 Kudos

Hi Madhuri

Go to the ECC system anc check the idoc structure. Make sure u have the current metadata in PI system.

It has to be a problem with your test data. Check all the field name and their type in idoc and see the data you passed is correct for that type or not.

Last time I got this error becasue one field was expecting value as date but I left it as blank.

Former Member
0 Kudos

This XML is not an IDoc XML.

You are pushing wrong data format into communication. You probably have input file read from FTP or something (not received as IDoc) and you need to make a mapping from input structure to the output IDoc structure.

Did you set mapping properly? Is message types set correctly?

Root of your problem is that you are trying to process non IDoc data as IDoc.

Former Member
0 Kudos

Hi,

  There is a condition at the idoc level... There are some amount fields in the file like

AC_233000,AC_224000 etc.If the file contains zero amount files, idoc should not get generated.With this requirement, file is getting into error state.

anupam_ghosh2
Active Contributor
0 Kudos

Hi Madhuri,

                      Every idoc should have  <IDOC BEGIN="1"> tag. This is missing in payload.

Are you working in single or dual stack??

Regards

Anupam

Former Member
0 Kudos

Hi Anupam,

  Iam working on single stack PI7.3.There is a condition at idoc saying, if the file contains zero amount values then idoc should not get generated.Because of this condition, it is not generating idoc but displaying error at PI level.

Regards,

Madhuri. A

ambrish_mishra
Active Contributor
0 Kudos

Hi Madhuri,

With this condition the IDoc should not get generated in ECC itself.

Ambrish

vedrankubelka
Explorer
0 Kudos

Probaly you haven't some obligatory field. You can check your outbound message in message monitoring. Can you se payload in that tab "Message content"?

Former Member
0 Kudos

Hello,

It seems that u r passing wrong data (may be wrong date format) in IDOC XML as a result it is throwing parsing error.

Paste IDOC XML over here?

Thanks

Amit Srivastava

Former Member
0 Kudos

Hi Amit,

  I dont have authorization to check the message payload in production.

Regards,

Madhuri. A

iaki_vila
Active Contributor
0 Kudos

Hi,

But, if you have the origin file, you can test in your quality or development enviroment. As Amit and Vendran said, the error is originated because your are sending an XML that the IDOC interface cant validate it.

Regards.

Former Member
0 Kudos

Hello,

To find out the exact cause of failure u need to somehow view the IDOC XML data, may be if u could get source xml then u could test mapping locally and then check the converted idoc xml.

Thanks

Amit Srivastava