on 01-23-2013 1:51 PM
Hi Experts,
I have used IdocXMLtoFlat module in one of my interface, It was working fine, until we have a requirement to include Z(Custom) segment in the Custom IDOC. Then its failed and the following error occurs in Receiver Channel.
Delivering the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: com.sap.conn.idoc.IDocParseException: (7) IDOC_ERROR_PARSE_FAILURE: An IDocFieldNotFoundException occurred while parsing IDocXML for type <ZXSHPMNT05>: state=READING_FIELD_VALUE_TAG, charPosition=3519, lineNumber=2, columnNumber=3481, invalidChar=U+002F, sourceSnippet=...00635895</SLS_ORD><FLG>X</FLG><AGG_QTY>1.000</AGG_QTY><KDMAT>27205364</KDMAT><HERKL>TR</HERKL></Z1ED...
This points to the Z segment added in the IDOC. I have check the meta data its up to date, shows as same as backed system structure. Please let me know your thoughts on it.
It was working fine in development and after moving to QA, we are getting this error. I have already done the below points.
1. deleted the metadata and newly imported the idoc again in IDX2.
2.restarted the channel.
3. re transported the objects again from Dev to QA.
4. No data issue...coz, i tested the same by taking QA data in Dev and it is working fine.
but still the issue remain the same...
any valuable suggestion please.
hi, did the new field/segment transported to QAS from the ECC? are those element released (enabled the custom fields/segments of IDOC to be public, developers know it) in QAS?
also delete the entry in IDX2, then from ESR and impor the IDoc again.
can you see the new custom fields?
Also check the value provided in the field. Maybe the encodign does not suppot that value.
check this 1004368
http://scn.sap.com/thread/139233
http://scn.sap.com/thread/3220546
http://scn.sap.com/thread/2128819
http://scn.sap.com/thread/1441142
regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is clearly an IDOC content issue.
charPosition=3519, lineNumber=2, columnNumber=3481, invalidChar=U+002F, sourceSnippet=...00635895
Java IDOC won't allow some specific characters . Please check your content
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Venkat,
I did go through the above link...i did the same...the issue still exist..if i test without these extra feilds in idoc, it works fine..but with the fields,...it fails.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
HI,
Any other valuable suggestions please.
thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi ,
Please go through the below link ;might be help full for you
http://scn.sap.com/message/13564757
Regards
Venkat
Hi Smith,
Whether cache content is updated?
If not, you may have to try doing a cache refresh.
http://scn.sap.com/people/sylvia.xiong/blog/2010/03/09/hints-about-pi-runtime-cache-refresh
Regards,
Zameer
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.