...
- Refer to "Governance ReadMe" sheet for details on how to fill up the register.
- Job owners will need to define a 5-6 character long Job ID: <2-3 Character Identifier><3 digit sequence number>
- First 2-3 character is used to identify which process or functionality the job belongs to. E.g., POD (A2D, S2S etc.) or functionality (GTS, FIN, AFC, PI etc.).
- Next 3 digits will be in running order (001, 002, etc.).
- Duplicate job IDs will be highlighted in red using conditional formatting.
- Please update the next empty row and do not leave empty rows.
...
- Development & Sandbox - System owners can request the respective system administrators to schedule the jobs after:
- Batch jobs register is updated with the required information.
- Program and variants have been created.
- Other systems
- Batch job confluence page is approved and batch jobs register is updated with the required information.
- Before
- Before the start of the different test cycle (integration test, UAT etc.), an email reminder will be sent out to review will review columns X to ADby the basis team to ask job owners to review which jobs are to be schedule for the start of the test cycle.
- Respective PIC will schedule the jobs marked need to set the status as "Ready to be Scheduled" for the respective systems before the start of the test cycle.(Column T to Z) and basis team will schedule the jobs.
- Please raise a tasks to basis team if the job is to be schedule after the initial configuration periodupdate, stop or start the batch schedule during the test cycle.
Teams responsible to setup batch jobs
...
- Teams managing the respective SaaS applications will be responsible to schedule batch jobs in their respective systems. For example Ariba team will configure Ariba job.
- Batch Jobs in S/4HANA will be managed by different teams depending on the type of batch jobs. Following is a guideline:
- Basis team - SM36 Jobs, SAP Application Jobs
- Development Team - Process Chain
...