Question on a SAP R3 scenario and Control-M Enterprise

JoPoCME · Post by **JoPoCME** » 23 Sep 2010 5:02

Our SAP team has an SAP R3 ABAP program they wish to schedule in Control-M Enterprise. That isn't a problem but the ABAP program then kicks off about 300 other jobs. They would like to be able to have Control-M Enterprise monitor the full job stream but I don't believe it can in this case. We were able to for SAP BW jobs because the job that Control-M Enterprise schedules does not end until the stream completes.

Anyone with experience with this scenario?

Below link describes the SAP program:

http://help.sap.com/saphelp_46c/helpdat ... ontent.htm

philmalmaison · Post by **philmalmaison** » 24 Sep 2010 4:39

don't anderstand
you must at least have the Controlm option for R3 installed on a agent, or CM for SAP to schedule to SAP/R3 system.

regards,
Philmalmaison

Ross_T_Boss · Post by **Ross_T_Boss** » 24 Sep 2010 7:04

Are you using the SAP CM?

It sounds like a 'parent' job in SAP that spawns a multitude of 'child' jobs for mass parallel processing. You will be need to configure the extractor process on Control-M side and have BASIS check it is enabled in SAP.

Be aware that if there are 300-odd child jobs it will extract them all to Control-M and you will have to license accordingly. If it a mass-parallel job then the parent job should not finish until al chid jobs have completed, so maybe it is something different.. something to check with your BASIS guys.

JoPoCME · Post by **JoPoCME** » 01 Oct 2010 3:37

The SAP R3 module is available on the agent. The issue is that the SAP R3 mass parallel job typically runs, kicks off the 300 jobs and then ends.

Our SAP team decided to wrap the mass parallel job around the 300 jobs so that it does not end until the 300 jobs have all run their course. This way we can monitor the status of the whole process via Control-M Enterprise and also consolidate this to the one job.