Pages

Thursday 6 June 2013

What are the Standard jobs in SAP



SAP_CCMS_MONI_BATCH_DP : Internally this job runs
RSAL_BATCH_TOOL_DISPATCHING report. This job dispatches monitoring architecture methods

SAP_COLLECTOR_FOR_JOBSTATISTIC : Internally this job runs RSBPCOLL report. This job generates run time statistics for background jobs

SAP_COLLECTOR_FOR_PERFMONITOR : Internally this job runs RSCOLL00 report. This job collects data for the performance monitor

SAP_COLLECTOR_FOR_NONE_R3_STAT : Internally this job runs RSN3_STAT_COLLECTOR report. This job will collect non-abap statistic data (Distributed Statistic Records - DSR)


 SAP_REORG_ABAP_DUMPS : Internally this job runs RSSNAPDL report. This job cleans up old abap short dumps


SAP_REORG_BATCH_INPUT : Internally this job runs RSBDCREO report. This job cleans up old batch input sessions


SAP_REORG_JOBS : Internally this job runs RSBTCDEL report. This job cleans up old background jobs


SAP_REORG_JOBSTATIC :  Internally this job runs RSBPSTDE report. This job cleans up old data from the run time statistics of the jobs


SAP_REORG_ORPHANED_JOBLOGS : Internally this job runs RSTS0024 report. This job cleans up orphaned job logs. The logs that cannot be deleted by RSBTCDEL report (i.e SAP_REORG_JOBS), remains as orphans which will be deleted by this job.


SAP_REORG_SPOOL : This job internally runs RSPO0041 report. This job deletes old spool data


SAP_REORG_XMILOG : This job internally runs RSXMILOGREORG. This job deletes XMI logs


SAP_SOAP_RUNTIME_MANAGEMENT : This job internally runs RSWSMANAGEMENT report. This job does the SOAP runtime monitoring


SAP_REORG_UPDATERECORDS : This job internally runs RSM13002 report and this deletes old update records

What are status of background jobs in SAP

Possible status of background jobs

  1. Scheduled:- You have defined the program name and variant  but not defined start condition like Start Date, End Date , Frequency etc. That means you have not defined when job should be scheduled in system.
  2. Released:- All required criteria are fulfilled for job definition. Start condition is must for the job to be in release status.
  3. Ready:- All the required conditions are met to run the job in a background workprocess. But job scheduler has put the job in the queue because it is waiting for background workprocess to be free.
  4. Active:- Job has started running in the background. We cannot change the status of the job once it is  in Active status.
  5. Finished:- Job is executed successfully. It means desired task is competed without any error.
  6. Cancelled:- There are two possibilities for this. Administrator has forcefully cancelled the job or there might be some issue with job. You can investigate this from Job logs.

What is a background Job in SAP



Unlike Foreground jobs, Background jobs are non-interactive processes that run behind the normal interactive operations. They run in parallel and do not disturb interactive(foreground)  processes and operations.
It is scheduled from SM36. You can analyze it from SM37 by viewing its job log.
Advantages of Background Jobs
  • It reduces manual effort &  automates the task.
  •  It can be scheduled as per user’s choice.
  •  It reduces user interaction and can run seamlessly in the background without user input
  •  Once you define the variant for background job, the user doesn’t have to worry about value input in the field. Thus, user confusion is also reduced.
  •  Ideal for time- consuming/ resource intensive  programs which can be scheduled to run in the night(when system load is low).
Background jobs are classified in three categories -
  1. Class A (High/critical Priority) :-  Some tasks are urgent or critical and  must be scheduled with class A priority job. Class A priority reserves one or more background work processes. Users have to decide how many background work processes should be assigned to Class A priority job. Suppose a user chooses 2 background work processes for this category then available background work processes for class B and C = (Total number of work processes set in operation modes RZ03)- (Background work processes allowed to class A category).
  2. Class B(Medium Priority):- Once Class A jobs are completed , Class B job will start executing in the background before class C jobs.
  3. Class C(Low Priority):-It runs after both  class A and class B jobs are completed.

How to schedule the background job in SAP (SM36)

You can schedule the background job using  SM36. Planned or immediate jobs can be scheduled.

Step 1) Execute T-code SM36.
SAP Background Job Processing SM36: Create, Schedule, Reschedule 
Step 2) Fill the job name, priority(A/B/C) and the target server. Background jobs once scheduled on a target server run on that server. Main purpose of defining target server is the workload balancing.
SAP Background Job Processing SM36: Create, Schedule, Reschedule 
Step 3) Click on "spool list recipient". You will get output in your mailbox. You can check email from SBWP.
SAP Background Job Processing SM36: Create, Schedule, Reschedule 
Step 4) Insert your SAP username and click the copy button.
SAP Background Job Processing SM36: Create, Schedule, Reschedule 
Step 5) Click Step button to define ABAP program, variant's details, etc.
SAP Background Job Processing SM36: Create, Schedule, Reschedule 
Step 6) Define program name, variant details. 
  1. Enter your program name, Variant name in the field. If you have not created variant as per your requirement, then leave it blank.
  2. Press save button.

SAP Background Job Processing SM36: Create, Schedule, Reschedule 
Step 7) Once you schedule the job you will get the following screen.
SAP Background Job Processing SM36: Create, Schedule, Reschedule 
Step 8) Click Start conditions to fill start date, end date, frequency, etc for job. If you do not specify start condition then job will always remain in scheduled status. A  job in scheduled status will never run. 
  1. Click on Date/Time(For periodic jobs). If you click "Immediate" then job will start running right away. But it will not be set as periodic job. It's like "press and run."
  2. Define job's start date/time, end date/time. The job will be released only once it meets its Scheduled start date/time.
  3. Press periodic values.

SAP Background Job Processing SM36: Create, Schedule, Reschedule 
Step 9) Click on Hourly/Daily/Weekly period to define the frequency of the job as per your requirement.We will select Other Period
SAP Background Job Processing SM36: Create, Schedule, Reschedule

Step 10) Here you specify the recurring criteria of the job.For example, You can have the Job run after every 5 days from the Start Date. Here we select job to run every 10 minutes
SAP Background Job Processing SM36: Create, Schedule, Reschedule 
Step 11) Click on save button.
SAP Background Job Processing SM36: Create, Schedule, Reschedule 
Step 12) Click on save again.
SAP Background Job Processing SM36: Create, Schedule, Reschedule 
Step 13) Click save again
SAP Background Job Processing SM36: Create, Schedule, Reschedule 
Step 14) Once Job step and start conditions are defined the following window will appear.
SAP Background Job Processing SM36: Create, Schedule, Reschedule 
Step 15) Press save.
SAP Background Job Processing SM36: Create, Schedule, Reschedule 
Step 16) Goto SM37 to know the status of the job.
SAP Background Job Processing SM36: Create, Schedule, Reschedule 
Step 17) Select your criteria for the job which you want to monitor. 
  1. Put your job name and username who scheduled the job.
  2. Select the status of the job.
  3. Specify the date range. In our scenario, we just specify the end date while keeping From Date Open.
SAP Background Job Processing SM36: Create, Schedule, Reschedule
Step 18) You will get the following screen. Look at the status, it's a released means start conditions are met, and the job is in the queue is waiting for background work process to be free.
SAP Background Job Processing SM36: Create, Schedule, Reschedule


How to Download/Upload Roles from PFCG in SAP

Download Role Authorization from PFCG 

1.Goto PFCG
2.Enter role name( which you want to download)
3.Click on Role & Click on Download


clip_image004

clip_image006




Upload Role Authorization from PFCG 

1.Goto PFCG
2.Enter role name( which you want to upload
3.Click on Role & Click on Upload


clip_image008
clip_image010
clip_image012
clip_image014


Next activity for generate role and assign to user or role

How to creat User Group IN SAP ( SUGR )


Transaction code SUGR is used to create and maintain user groups in SAP system. The user groups commonly used to to categorize user into a common denominator, sort users into logical groups and allow segregation of user maintenance, this is especially useful in a large organization. User groups can categorized as two types,
Authorization user group : In conjunction with S_USER_GROUP authorization object. It allows to create security management authorization by user group. e.g. you can have a local security administrator only able to manage users in his groups, Help-Desk to reset password for all users except users in some group.
General user group : In conjunction with SUIM and SU10, to select all the users in a specific group. User can only be member of one authorization user group but several general user group.


enter the name of New User Group in SUGR and click on create






then enter to user id of people which you want to add in group