We have a question and would like to see if CA has a stance on the subject either way. When setting up SAP jobs to run in ESP - is it better to set up a single ABAP program and variant per SAP job, and run each job in sequence in the ESP application? Or set up the SAP job to run numerous programs and variants, and have ESP run a single SAP job in the application? We are currently doing it both ways and would like to pick one or the other.
CA WA ESP Edition 11.4 Z/OS
Each of the methods have their own pros and cons, and we don't have official best practice suggestion:
- Set up a single ABAP program and variant per SAP job:
Pros: the ABAP programs can have different/flexible relationships with each other. And when one fails, ESP can resubmit only the failed one.
Cons: More SAP_JOB definitions in ESP. Note: to reduce the redundant work, you can set up a TEMPLATE and then use it for the job definitions.
- Set up the SAP job to run numerous programs and variants, and have ESP run a single SAP job in the application
Pros: very simple SAP_JOB definition in ESP
Cons: Can't change the sequence or relationship between the ABAP programs in ESP. And when one ABAP program fails, ESP will rerun it from the very first ABAP.