Error in CC while using SAP_XI_IDOC/IDOCXmlToFlatConvertor module

[Former Member]

Dear Experts,

We are getting an error in Receiver CC monitoring while using IDOC--> XI -->IDOCXmlToFlatConvertor module for converting IDoc XML to flat file.

I am get the output as xml.AS I required the IDOC text file , I am using Module " SAP_XI_IDOC/IDOCXmlToFlatConvertor" .  While converting it is showing the error CC as

Error in CC:

Message processing failed. Cause: com.sap.conn.idoc.IDocParseException: (7) IDOC_ERROR_PARSE_FAILURE: An IDocFieldNotFoundException occurred while parsing IDocXML for type <ZWP_PLU03>: state=READING_FIELD_VALUE_TAG, charPosition=1614, lineNumber=1, columnNumber=1615, invalidChar=U+002F, sourceSnippet=..._N><ZCLASS_ID>AC</ZCLASS_ID><ZSUBCLASS_ID>BL</ZSUBCLASS_ID><ZATTYP>02</ZATTYP><ZOLDMAT>DMRACBL013919... ^

Please help me how to resolve the same.

Thanks & Regards

Rakesh

[Former Member · Accepted solution]

Hi Rakesh,

As you change the Idoc structures, you need to reimport the idocs into the repository else

Re-import the Idoc into Transaction IDX2 in XI system.

I think this will solve your issue.

Best Regards,

Sagarika

[Former Member · Accepted solution]

HI Sagarika,

Thanks For your input, Here I am not using the mapping. Using ID I am converting IDOC xml generated in ECC to the text file (Idoc Text).

I have deleted the metadata, and while processing Idoc again ,  it is automatically generating the Metadata in IDX2. But still facing the same issue.

Thanks & Regards

Rakesh

[Former Member · Accepted solution]

Dear All,

Now, I have generated the IDOC with out that customized segment in ECC and this scenario get successful and able to generate the Idoc text file.

I mean , without customized segment , I am able to generate the Text file from Idoc xml . But If I am adding the customized segment, it is showing the same error.

Please advice me to over come this with customized segment.

Thanks & Regards

Rakesh

[Former Member · Accepted solution]

Hi Rakesh,

There is no automatic refresh, If IDoc metadata is changed, you must force a manual refresh. To clear the cache, you can use transaction IDX2 or the report "IDX_RESET_METADATA."

If the above process is not working then please try one thing, go to IDX2 transaction and delete the entry corresponding to the idoc.The new idoc metadata, will be imported automatically when the scenario is re-run.

Best Regards,

Sagarika

[Former Member · Accepted solution]

Hi Sagarika,

I got it , I mean to say the same, "The new idoc metadata, will be imported automatically when the scenario is re-run" . And I did the same.

Thanks & Regards

Rakesh  

[Former Member · Accepted solution]

Thank you one and all for your helpful inputs. The Problem get resolved by maintaining the metadata again.

Thanks & Regards

Rakesh

[Former Member]

HI Rakesh,

As per the error message, there is a field coming with invalidChar=U+002F. try to find out the field and the value expected.

Check this and reply back.

[Former Member]

HI Hanumantha Rao,

I am unable to find that Invalid Char. My scenario is ECC --> XI --> Thirdpart1 (as XML)  & Third Party2 (as Idoc Text).

Here I am able to generate the xml for thirdparty1. but I am facing problem to generate the  Idoc text from the respective xml .

Thanks & Regards

Rakesh

[zameerf]

Hi Rakesh,

Did you already follow the steps mentioned in the below blog to configure the meta data information before using this module in channel?

http://scn.sap.com/community/pi-and-soa-middleware/blog/2009/04/01/how-to-use-user-module-for-conver...

Regards,

Zameer

[Former Member]

Hi Zameer,

Thanks for your input. I already followed the steps mentioned in the link and earlier

it is working , but I am facing this problem after enhancing the structure with two more fields.

Thanks & Regards

Rakesh

[udo_martens]

Hi Rakesh,

you have to configure a destination inside the adapter which is used to fetch meta data for the conversion. I think the meta data are not synchronous with your send IDoc message. This can happen if the IDoc structure was changed (it is a Z-IDoc). Usually the meta data are fetched only once during the first message processing.

There is no "Button" refresh meta data for a channel, therefore try:

1. start and stop the channel and test again

2. change short text of the channel in IB Directory, activate and test again

3. delete and recreate the channel (take a screenshot before)

Regards,

Udo

[Former Member]

HI Udo,

Thanks for your input, And your assumption is exactly right. Previously it is working , but I am facing this problem after enhancing the structure with two more fields. Now I have tried all the three options suggested by you. But, Still getting the same error.

Thanks & Regards

Rakesh

[udo_martens]

Hi Rakesh,

you can try to recreate the channel with a different name (if the meta data are stored with correlation to channel name).

In addition Hanumantha's answer looks good. Can you check character no 1615? If you download the message from monitoring and open it in serveral tools like IE, XML Spy or nodepad you get may be a hint, may be the character looks corrupt.

Regards,

Udo