The concerns I have are:
1) This may overload my network/SAP connections. Since this job runs in parallel SMP, there could be many more than 6 simultaneous connections. In my experience with connecting to remote systems, this may cause some problems due to overhead and burden.
2) The entire job is dependent on successful completion of all SAP connects. If one fails, the entire job fails and must be restarted from the beginning.
3) From a support standpoint, with all of these connections, it could be difficult to debug and diagnose failures.
![Image](http://img571.imageshack.us/img571/8656/image45e60b0301e18af5.jpg)
I would recommend having a separate job for each ABAP connection that would write its own sequential file, then save a copy to archive. I would change the existing job by replacing the ABAP stages with sequential files. This would separate the process into smaller units of work, which are easier to manage.
I would also add that, while I have 8+ years with Server edition, Parallel and SAP are brand new to me and my company.