How to catch a message error for FF_5 run in Background

[Former Member]

Hello,

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

Bruno

[vinod_vemuru2]

Hi,

If it is hard coded in program, OSS note is the only option (If availbale). But I can suggest a better way to handle this.

Configure an external transaction with name UNALLOCATED. When ever there is a new external transaction comes that is not configured, system automatically picks up unallocated and post to this. Relevant G/L can be defined based on posting rule and respective account symbol. By this way, you can never miss posting of any new external transaction.

Hope this helps.

Thnaks,

Vinod.

[kishore_babu15]

Hi Bruno,

This is one of way to find out the error message.

You can debug batch jobs by going to 'SM37', type in 'JDBG' in the

command line ( no '/' ), put the cursor on the job and press enter - will

take you to the job in debug mode.

You can do this only after the job has finished execution. This will simulate the exact background scenario with the same selection screen values as used in the job also sy-batch will set to 'X'.

So type in the transaction code 'JDBG' and place your cursor on the job after It has finished. It will take you to a SAP program in debug mode. Step through this program which is about 10 lines, after this your program will be executed in the debug mode.

Hope this helps to you.

Best Regards,

Kishore

[vinod_vemuru2]

Hi,

How about setting up OBA5 message as error for batch ID?

Thanks,

Vinod.

[Former Member]

Hi Vinod,

This solution is not working. In fact it's a hardcoding in the program !

  IF x_noposting = 'X'.

    MESSAGE s773.

  ENDIF.

I look in user-Exit but I see nothing.