- To schedule/create a background job, use the menu path: Tools CCMS Jobs definition (or transaction SM36).
- When creating a background job, you must specify a job name and a job class (priority level A, B, or C with A being the highest priority- data transfer form external system. B – important periodic jobs performance statistics. C – non-critical jobs: list and queries.
- The target host is not required. Normally, you will just leave this field blank. However, if you are using an SAP system that has multiple application servers (and each of these servers has background work processes), you can specify the specific application server on which the background job should be processed.
- Next, you should enter the steps (i.e., programs) to be included in the background job
To include an ABAP/4 program in a background job, you must specify the program name and, if necessary, its variant. A variant is a set of parameter values needed for the execution of aparticular program.
External programs may only be executed by users having the same authorization as the system administrator The name of the server where the external program is executed must be specified.
External commands can be executed via background jobs defined with transaction SM36 as shown above These commands are defined by the administrator and protected with authorizations.
Use transaction SM69 to define and maintain external commands. External commands that defined by SAP can not be changed
- Logical command name
- External commands are uniquely identified by a logical name and the assignment of an operating system
- Operating system (CASE SENSITIVE FIELD)
- External commands can be restricted to execute on a particular operating system (AIX) or any operating system (ANYOS)
- Operating system command (PATH NAME)
- Name of an operating system program
- Parameters for operating system command
- Check module
- Optional function module to further check a user’s authorization to execute this command. Then maintaining external commands (SM69), you can specify the name of a check module, which is a function module that is executed immediately before the command, and can decide whether the command will be executed.