Site icon ExpressGRC | SAP Cyber Security Software for SAP Compliance

What do you need to Understand regarding the SAP Batch Jobs

[vc_row][vc_column width=”2/3″][vc_column_text]You’ve Just joined the customer with SAP ECC System and you are the SAP Auditor / SAP Security

You think it’s going to be the next hot shot consultant in your company.

But you are not aware of some of the SAP Basis related activities

Two weeks later, you are still struggling to figure out why some of the roles are not properly synched.

No matter how much research you do, you are not able to figure out why the role tab is red.

Here are some of the skills you need have.

How to create a Batch Job in the SAP System

Identify the program which must run the background

Figure out the frequency which the job must run in the SAP ECC System

What is the variant which must be used for running the program?

What is the user ID which must be used for running the program?

Figure out the time it must run, preferably late night or early morning?

Make sure someone is monitoring the Batch job so when there is error it

can be fixed.

Always involve an SAP basis person to help so the job can be properly

scheduled and the right application server can be selected

 

A batch job in SAP is a scheduled background program that usually runs on a regular basis without any user intervention. Batch jobs are provided with more allocated memory than the ones that are done in the foreground. They are used to process high volumes of data that would normally consume long-term memory if run in the foreground, as well as for running programs that require less user interaction.

One of the advantages of running large programs as the batch job is that more servers can dedicate more work processes in night mode when there are few interactive users. The number of batch jobs during the day could be restricted to fewer servers and numbers as needed.

If a batch job creates an output that is to be printed, faxed or emailed, the output is transferred to the spool management in the R/3 system.

To create a new batch job, one can use transaction SM36. This involves defining the job name, job class, and target server if needed. However, it is recommended that users avoid choosing the target server when creating the batch job, and allow the background system to determine the server as and when needed instead. Batch jobs can also start processing based on specific events and results. SM36 also provides a batch job wizard.[/vc_column_text][/vc_column][vc_column width=”1/3″][stm_sidebar sidebar=”527″][/vc_column][/vc_row]

Exit mobile version