SAP Gateway exception handling logging to the SLG1 Application Log object /IWBEP/ and /IWFND/

[wouter_peeters]

Hello Gateway experts,

I have a question regarding to best practices of Gateway exception handling and the logging towards SLG1 Application log, I'm specifically talking about 2 use cases:
1. Gateway service to process a request and raise a business exception when there's an error, e.g. saving of a Payment
2. Gateway service to validate data entry on the User Interface by raising a business or technical exception, e.g. is the IBAN entered correct

Do note, difference in business (expected possible errors 400) and technical exception (unexpected 500) is the status code.

From what I see, all exceptions that are raised are being logged to in the Application log ( /IWBEP/, /IWFND/ ), which is absolutely great. But we are seeing a lot of users entering wrong data (case 2), causing our application log to fill up with things we do not want to followup on.

Question: Does anyone have the same 'problem' as described above? How do you tackle it?

Code references in SAP standard:
/IWBEP/CL_MGW_LOCAL_HANDLER->EXECUTE_OPERATION( )
/IWBEP/CL_MGW_HANDLER_UTIL->HANDLE_EXCEPTION( )

Regards,
Wouter

[wouter_peeters]

andre.fischer, any thoughts on the above?

We also see CDS based Odata services (SADL) log errors when no record was found.

Many thanks,
Wouter