...
Debugging | The System Task runs in the background. To debug it, you can run the event in the foreground by executing the report /IQX/FAB_SYSTEM_TASK and enter the following parameters: Form Name - FAB App Name Instance - FAB Instance (Form ID) Status - Status of the Instance at the time of processing Task ID - Process Task ID (Example: Update SAP) |
Troubleshooting | Check the Logs in transaction /n/IQX/FAB_DATA. The logs should contain this message Starting Event Handler for Background Task. Otherwise, check the transaction SWETYPV if Event Type Linkages are configured. Object Category - BOR Object Type Object Type - /IQX/FAB Event - BACKGROUND_TASK_START Receiver Type - BACKGROUND_TASK |
Troubleshooting - Authorization issueWorkflow runtime is not configured properly | In an event if the Event Type linkages are configured and activate, but no background job/system task is created/released should have been found in SM37 then authorization is an issue should be considered. Check authorization issue log in SU53 as below example: , then please check if the Workflow runtime is configured properly in transaction SWU3 as below screenshot: In TS4 environment, there is no RFC destination configured as well as no WF-BATCH user is created for the workflow runtime. |