EWA not getting generated due to long running /BDL/TASK_PROCESSOR in BW system

[former_member777310]

Hello Experts,

This job: /BDL/TASK_PROCESSOR which is scheduled as part of SDCCN configuration, usually runs for longer duration due to which EWA reports are not generated.

When checked in SDCCN of managed system, an EWA session is selected for execution but when checked in task log could see messages like 'Enqueue category failed' multiple times and also message with SYSLOG, PFA.

All other instances later to the long running one contains log as 'Enqueue for category failed' which results into no EWA generated.

Has anyone faced/seen such kind of behavior for this task processor job? If yes, eager to know how it was resolved.

Thanks.

[Henry-2023]

Hello,

when the bdl taskprocessor is running long, it should be checked if it is still processing (this can be done in SM50 / SM66: typically the background process is starting an RFC and the activity takes place in a dialog process processing the RFC) or whether it got stuck without stopping the job.

Typically you will find out that the job is still active. To figure out what it is doing, you can observe SM50 again, or the task log in SDCCN (on the first tab find the EWA task and open the log), or monitoring entries in BDLDTOC created for the current session.
Best Regards,

Nikolaus