Skip to Content

FTP sender channel is getting stuck with Edifact module - "Archive Faulty Source Files" doesn't work

Dec 29, 2017 at 12:54 PM


avatar image
Former Member

Hello experts,

we're facing an issue during inbound processing of Edifact files. For the plain-to-xml conversion we're using the EdifactConverter Module of SAP's B2B Add on within the FIle/FTP adapter.

If there is any syntax error within the message, the EdifactConverter Module throws the following exception:

java.lang.RuntimeException: Error in conversion of ORDRSP/93A-Edifact-Document at character 672 to XML: java.lang.UnsupportedOperationException

To avoid a blocked inbound Queue in the adapter, we activated the option "Archive Faulty Source Files" and defined an archive directory on the FTP server. We also bound the MessageTransformBean with parameter "Transform.PermanentErrors" = true and set the advanced parameter "nullCauseModException" to true.

Unfortunately this doesn't work. The errorneous messages will not be moved to the archive folder. Does anyone have a suggestion for this? Maybe the Edifact module throws the wrong type of exception?

Help is highly appreciated!

Thanks in advance,


10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Best Answer
avatar image
Former Member Apr 09 at 09:36 AM

Hello experts,

the problem is solved, SAP note 2074009 did the trick:

The EDIFACT module throws a ja.lang.RuntimeException. Therefore this exception class has to be registered in the advanced tab of the communication channel by setting the class name with parameter "archiveOnException".screen.png

screen.png (21.2 kB)
10 |10000 characters needed characters left characters exceeded