A Custom Event on Customer Order Release, meant to block release with an error when a custom field is blank, works exactly as expected when tested directly in PL/SQL Developer, but in the actual application the order just releases normally with no error shown and nothing visible in the debugger. What's causing the event to silently do nothing in the app?

All FAQ questions / Platform, Aurena, and customization

Answer

Check whether the Customer Order's Order Type has 'Online Processing' ticked in Sales Basic Data — this setting determines whether Release runs synchronously (online, in the same session, so the event fires and any error displays immediately) or asynchronously as a background job instead. For an Order Type without Online Processing ticked, Release runs as a background job, and the event's Error_SYS-triggered failure happens silently within that background job — visible only if you go looking at the failed background job's own log — rather than surfacing as an on-screen error to the user in real time. Ticking Online Processing for the relevant Order Type makes the event's error message display synchronously to the user as originally intended.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Platform, Aurena, and customization questions