C4C to ECC IDoc interface is failing with illegal parsing error

[Former Member]

Dear All ,

I have configured an interface to send sales quote details from C4C system to ECC. Its standard SOAP to IDoc scenario.  Here i'm encountering like below error.

Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocIllegalTypeException occurred while parsing IDoc-XML for type <SALESORDER_CREATEFROMDAT202>:
state=READING_FIELD_STARTTAG, charPosition=2186, lineNumber=1, columnNumber=2187

MP: exception caught with cause com.sap.aii.af.idoc.exception.IDOCAdapterException: Error before sending due to idoc parsing error: (7) IDOC_ERROR_PARSE_FAILURE: An IDocIllegalTypeException occurred while parsing IDoc-XML for type <SALESORDER_CREATEFROMDAT202>:
state=READING_FIELD_STARTTAG, charPosition=2186, lineNumber=1, columnNumber=2187

I have checked ICO and aslo checked for the char Position also.  I tried with Message mapping testing also with the payload , Its successful . still i couldn't  find any clue to identify the error . Kindly help on this.

Thanks

Vignesh

[Former Member]

Hi.

I found a temporary solution. In my case the char position in error leads me to a field (but really there was four fiels with similar mapping) that have some conditions and if no is fulfilled the mapping assigns a xsi:nil value.

I tried by creating a custom mapping based on the standard mapping COD_ERP_CustomerQuoteFollowupBusinessTransactionDocumentReq and replaced xsi:nil value with an empty Constant and it's working now. The four fields I've modified in the mapping are:

/SALESORDER_CREATEFROMDAT202/IDOC/E1SALESORDER_CREATEFROMDAT2/E1BPPARNR[3]/TELEPHONE2 /SALESORDER_CREATEFROMDAT202/IDOC/E1SALESORDER_CREATEFROMDAT2/E1BPPARNR[3]/ADDRESS /SALESORDER_CREATEFROMDAT202/IDOC/E1SALESORDER_CREATEFROMDAT2/E1BPPARNR[3]/ADDRESS_ORIG /SALESORDER_CREATEFROMDAT202/IDOC/E1SALESORDER_CREATEFROMDAT2/E1BPADR1/FAX_NUMBER

I only changed the value xsi:nil with empty value constant in these 4 fields mapping and it's working fine now. We are in contact with SAP support and they are evaluating our solution, for now we are using this custom mapping while they give us an official solution.

Regards.

Alejandro

[former_member237645]

Hi Alejandro,

any update on this from SAP Support? We are facing the same issue on a customer project.

Thanks,

Christoph

[manoj_khavatkopp]

Try using Additional Parameter ; FieldValidationEnabled = false in your reciver IDOC_AAE channel or you can change globally in JavaIdocAdpater in nwa.

This parameter skips the data validation in PI .

[former_member237645]

Hi Manoj,

thanks for your suggestion.

Unfortunately the error remains

BR,

Christoph

[manoj_khavatkopp]

Chris,

Check this Note : https://launchpad.support.sap.com/#/notes/2023782/E

Br,

Manoj

[former_member237645]

Hi Manoj,

Note 2023782, as far as I understand is only valid until Netweaver 7.40, isn’t it?.

We are on 7.50 netweaver.

Note 2036878 proposes to include the additional parameter FieldValidationEnabled = false what we tested already without success.

Do you still have another idea?

Thx,

Christoph

[manoj_khavatkopp]

Hi Chris,

Even i am using 7.5 currently SP3 and we had faced the same issue recently IDOC_ERROR_PARSE_FAILURE due to data issue however we solved it by changing the property FieldValidationEnabled to false globally in nwa . can you put the screenshot of the error you are facing.

I am still wondering why isn't this working in your case

Br,

Manoj

[Former Member]

I'm having the same error with this standard scenario (but error points to a different char position). Anyway, I looked that character position of payload in a text editor and saw that is no data there, but the tag of a field.

This is a standard mapping, for that reason I believe that there is not a mapping error, I think it is a data error, but the error does in Message Monitor not allow me to identify exactly the data is wrong.

[Snavi]

this is not a mapping error and hence you are able to run the mapping without any issue.

the issue is data type and the value in the IDoc, as mentioned in the error you need to check the value at position 2186 to know the exact error.

most likely there is an issue with some date field,

you can check the IDoc schema definition for the data types other than string and try to check the corresponding values in your IDoc payload for the same.

[Former Member]

Hi Navdeep , Thanks for your reply, I have already checked for the character position, that not a issue.