IDOCXmlToFlatConvertor + Z IDOC Extension

[Former Member]

Hi Experts,

We are getting the following error message while trying to use the IDOCXmlToFlatConvertor standard module with Z IDOC extension. The IDOC standard works perfectly.

The our scenario is IDOC >> SAP PI 7.11 (IDOCXmlToFlatConvertor) >> SFTP

Basic type: ACCONF01

Extension: ZP10FINACCONF01_EXT

--Error message---

Message processing failed. Cause: com.sap.conn.idoc.IDocParseException: (7) IDOC_ERROR_PARSE_FAILURE: An IDocConversionException occurred while parsing IDocXML for type <ZP10FINACCONF01_EXT>: state=READING_FIELD_VALUE_TAG, charPosition=926, lineNumber=2, columnNumber=888

Once the Z1P1DCIW_BLOCKDATA segment is removed from the XML, it works fine (using the RWB to send it)

We alredy tried to delete & remove the metadata from IDX2, update the cache.

Is there any place to set up the Z extension in the configuration steps?

Thanks in advance,

Leandro Silva

[former_member182412 · Accepted solution]

Hi Leandro,

This error happen in segment data type validation process of module execution.

Identify the char position or column in IDOC XML and see what is the data type defined in the IDOC definition, you need to pass the values according to the definition of the field data type. If the field is numeric you have to pass only numbers, if you pass string you will get an error.

Check below SAP Note, the note only applicable to 7.31 and above but it will give you the reason for failure.

2094460 - IDOCFlatToXmlConvertor and IDOCXmlToFlatConvertor modules: Disable field datatype validation during conversion

Regards,

Praveen.

[engswee · Accepted solution]

Another nice SAP Note find, Praveen!

Leandro, try putting 00001 in the EBELP field. It is a NUMC field in the backend, so it is normally filled with leading zeroes.

[rcsegovia]

Hi Folks,

Any way to use Segment type instead of segment definitions? I am migrating and the old abapmapping was using segment type.

Thanks in advance,

Rober.

[engswee]

Hi Leandro

The module converter does not use the metadata in IDX2. It uses the RFC destination in the JCO configuration in NWA to retrieve the segment definitions.

Adding IDOCXmlToFlatConvertor in the Module Processor - Adding Modules to the Module Processor - SAP...

Can you check a couple of things?

1) Can you give a screenshot on what is the content at the position mentioned in the error "charPosition=926, lineNumber=2, columnNumber=888"?

2) Can you provide a screenshot of your module configuration? In particular, what value are you using for the parameter SAPRelease?

3) Can you provide a screenshot of the definitions available for your Z1P1DCIW_BLOCKDATA segment in WE31 of the backend system that is configured in the NWA RFC destination? In particular, what are the releases available and is there any that corresponds to the value in SAPRelease.

4) Can you also provide the field definition in the segment mentioned above?

5) Check WE82 for the IDoc/Message Type combination that uses the Z extension, and check what is the value of the Release.

Rgds

Eng Swee