cancel
Showing results for 
Search instead for 
Did you mean: 

IDOC_ERROR_PARSE_FAILURE in IDoc_AAE

former_member463616
Contributor
0 Kudos

Hi experts,

   We are facing an error since we started our migration from PI 7.11 dual stack to PI 7.4 single stack. It is SOAP to IDoc scenario.This scenario

is working fine with ABAP Idoc adapter in PI 7.11 but same scenario is not working when we using Idoc_AAE adapter and giving error like

IDOC_ERROR_PARSE_FAILURE with one of the Idoc field value. The Idoc field value is 1,11,111.000

   We already found that the charPosition mentioned in the error message is comma (,) of the idoc field value. So, we changed the payload to this

number to 111111.000 (removed only comma's) then processing successfully as expected in PI 7.4. But, as per our requirement,we would like to need the data contains comma (,) should be process i.e. 1,11,111.000


we are looking into this thread, it seems to be not helpful.

 

Please through some lights on this issue and any help is highly appreciated.


  

Regards,

P.Rajesh

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Rajesh,

Please try any of below possible solutions.

  1. Handle comma(,) separation at the source side which is, source will not send separator along with value in field BSTMA to PI.
  2. Handle comma(,) separation at middleware (PI), Use standard function ‘replaceString’ along with field BSTMA or fields of type “QUAN” to replace comma.
  3. Apply SAP notes 2023782 and 2036878 in a sequence to get the functionality to disable IDOC segment field data type check.

Regards,
Nitesh Valecha.

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi

Check the data type of that field in ECC side. If the data type is numeric or integer, then it will not allow comma in the field value.

You have to change the data type as Char or String.

Thanks,

Indrajit

former_member463616
Contributor
0 Kudos

Hi Indrajit,

  Checked the standard field BSTMA data type as 'QUAN' in ECC side. We cannot change BSTMA field data type as it is standard. Is there any alternate solution for this. Thanks

Regards,

P.Rajesh

vadimklimov
Active Contributor
0 Kudos

Hello Rajesh,

Did you try to disable the field data type validation using parameter FieldValidationEnabled (locally on receiver IDoc communication channel level, or globally on Java Resource Adapter JavaIdocAdapter)? (refer to the SAP Note 2036878)

Regards,

Vadim