cancel
Showing results for 
Search instead for 
Did you mean: 

New : (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred

Former Member
0 Kudos

Hello,

Production message failed with below error : System : PI 7.31 SP 06, scenario BPM to IDoc.

I had gone through the similar threads in SCN,

1. Searched for any special characters, wrong date formats, whitespaces in the IDoc - xml ,  its not there

2. At position 20834 character is correct.

What is the issue here? Kindly share any other way to find the reason for this issue.

reg, avinash

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hello all,

I have found the reason for this issue.

Value ‘def’ is appearing in the payload (after mapping).

there is a mapping for this field:

At runtime, def is coming in the field RECITEM which is pretty strange.

Do you know any OSS note / solution.

thanks in advance.

reg, avinash

Answers (2)

Answers (2)

vicky20691
Active Contributor
0 Kudos

Hi,

It is data issue, some field doesn't match the IDOC definition as per the metadata of IDOC.

To find the exact field for which error is there search the error in NWA logs it, those logs dispay the field which couldn't be parsed

Regards,

Vikas

Former Member
0 Kudos

Hello Vikas,

This message failed on 29 Dec 2015, Log is not available in nwa.

Seems its impossible to find the bad data here.

reg, avinash

vicky20691
Active Contributor
0 Kudos

Hi Avinash,

try to see if the logs of 29 dec are persisted or not. Filter NWA logs with date and only error status.

If not found, only if it reoccurs.

Regards,

Vikas

former_member186851
Active Contributor
0 Kudos

Hello Avinash,

Its data issue,Did you check the message after BPM step?

Former Member
0 Kudos

Hello Raghu,

Yes, I have checked the payload in BPM step, around 330 records , I didnt find any special char or etc.

reg, avinash

former_member186851
Active Contributor
0 Kudos

Avinash,

Do a metadata refresh and check