Skip to Content
Former Member
Oct 24, 2013 at 12:28 PM

How to catch a message error for FF_5 run in Background



I work with the ETEBAC format file for Electronic Bank Statement. Recently we decided to automatize the upload of the EBS with a morning batch. Due to the arrival of SEPA some new code in the external transaction appears in France. The new code are not yet implemented and during integration the message FB773 (Account statement was not updated) is generated by the batch (message type "S") but the batch was not break and finish by a return code 0. So we can’t catch the message in our scheduler and the files are not integrated.

We search how to cancel the job when the message appears to have the message in our scheduler or have a return code different from 0.

Did somebody have the same subject and solve it.

Thanks & regards