SAP R/3 Document : Background Processing

Transcription

1 BACKGROUND PROCESSING All the non-dialog and time consuming programs can be executed in the background. For background processing, R/3 system provides the backgorund service with its background work processes, also referred to simply as background processes. Unlike dialog processing, during which each logical Unit of work (LUW) is assigned by the dispatcher to the next free dialog process, in the background processing one process is assigned to a background job for the duration of processing. You set the time at which the background job should start. You can trigger the job using either a set time or an event. A background scheduler is active within the instances of the R/3 system. At specified intervals, the background scheduler checks if there are any background jobs to be processed. The background scheduler is program that is interpreted and processed within a specified dialog process. The background scheduler automatically selects the dialog process when the R/3 system is started By default, the time interval for the background scheduler to become active is 60 seconds. The administrator can change this time in the instance profile by setting the parameter rdisp/btctime. One event scheduler is active on the application layer of the R/3 system. You can select the instance for the event scheduler by setting the parameter rdisp/btcname = <computer name> in the default profile (DEFAULT.PFL). The R/3 system is delivered with a set of events. Follow the path Tools CCMS Jobs Define Events System Event Names Display

2 After you click the Enter icon, you get a list of system events You can also define your own events. Follow the same path and select the user events name section To define an event, you need to create an entry in a table.

3 Events can be triggered by following the path Tools CCMS Jobs Raise Event Or by using the function module BP_EVENT_RAISE from an ABAP program Or by using the external program sapevt The program sapevt can found in the directory \usr\sap\<sid>\sys\exe\run. You can use it as follows : Sapevt <event name> [-p <parameter>] [-t] [pf=<instance profile>] name=<sid> nr=<instance number>

4 Following the path Tools CCMS Jobs Definition or by executing the transaction code SE36 background jobs can be defined. To schedule a background job, you basically need to provide with the job name, job class, Target host name, start date and time and processing step information. The job class entry decides the job execution priority : Class A jobs have the highest priorities. These jobs ensure the functioning of R/3 and are time critical Class B jobs have medium priority. These are periodic jobs. Class C jobs have normal priority. Job class is used to assign system resources.

5 You can set the start time and date by clicking on the Start date button on the application toolbar. Here you can also set periodic values to execute the job To execute a ABAP program in background an variant has to be defined. You can define a variant by following the path Tools ABAP Workbench Goto Variants Create. You enter a variant name and a parameter value and then save it. You should also define the steps to process the background jobs. A background job should have at least one step defined.

6 External commands consists of a logical name and an assigned external program with selected parameter values, which can vary depending on the operating system You can define an external command from the CCMS menus. Follow the path Configuration External Commands Change Command Create. The R/3 system already contains many external commands. You can also create additional external commands.

7 Let us create a external command Click on the Create icon. Enter the external command name, OS command and the parameter with which the OS command should be executed. The OS command lies below the external command name. A command defined in such a way can be used both when you define background jobs and from the CCMS Choose Jobs External commands, or use the trasaction code SM49, select a command, and then choose Command Execute

8 You can monitor and analyze the background via the menu path CCMS Jobs Maintenance. Alternatively you can also use the transaction code SM37 Depending on the selection made, a list of background jobs is generated alone with their status

9 To display the job log, double click on a job. These job logs give you some very valuable information such start time, date, job status like whether the job finished successfully or was cancelled etc. You can increase / decrease the number of background processes available in the system using the parameter rdisp/wp_no_btc in the instance profile. You can use authorizations to control the actions that are performed by a user in background processing. Some of the important authorizations for background processing are : Authorization S_BTCH_ADM S_BTCH_JOB Meaning Administrator for background processing, client-independent Operations with background jobs, client dependent DELE : Deletes jobs of other users LIST : Display spool list of other users PROT : Display logs of other users RELE : Schedule your own and release them for execution SHOW : Display job details of other users Use the field Job group to restrict the authorization specific to job names S_BTCH_NAM S_RZL_ADM Use a background user explicitly CCMS system administration

10 For an R/3 system to function to satisfaction there are certain jobs that need to carried out at regular intervals. It is the systems administrators responsibility to schedule and monitor these jobs. Program Meaning Time RSCOLL00 RSBPCOLL RSBTCDEL RSBPSTDE RSDBCREO RSPO0041 RSPO0043 Collects the general statistical data for R/3 system perfomance analysis. Schedule in Client 000 as user DDIC Normally scheduled at delivery under the name COLLECTOR_FOR_PERFORMANCEMONITOR Collects the statistical data to analyze the average run time of periodically executed jobs Deletes all logs successfully completed jobs The system administrator can use variants to define the number of days after which a log is deleted. Cleans up the run-time statistics of the background jobs. All the objects older than the specified date are deleted Deletes the logs of background input processes Log BI<SID><instance name> in the directory \usr\sap\<sid>\sys\global is minimized by deleting processed entries Client-dependent Deletes obsolete spool objects Client-dependent Deletes spool lists, which are remnants of canceled background programs Hourly Daily Daily Monthly When needed Daily, depending on the print activities Daily Checks the consistency of the spool tables RSSNAPDL If the maximum number of entries is exceeded, deletes Daily run-time errors entries (short dumps) that are older than six days RDDIMPDP Converts transport requests Event-Driven SAPRSLOG SAPRSEUT Administration job that updates the object lists and navigation indexes, normally active under the name EU_PUT Administration job that updates the object lists and navigation indexes, normally active under the name EU_REORG Daily Daily If you need further information on these programs then goto SE38 and have a look at the programs documentation.