This is then bypassing any ChaRM transport methodologies - technically and transport perspective is the same, but tracking and reporting updates might suffer and you need to open project status switches.
Solution is to create an own report to call the task on the task list via FM /TMWFLOW/TASK_START.
This report can be scheduled as any other report, executes imports via schedule manager and provides logging. No need to open status switches and thus jeopardizing security and traceability in ChaRM.
Regards,
Hannes