job scheduling....

[Former Member]

Hi,

I have a report, i need to run the report every day at 10.00 AM.

So, i need to schedule it...but how can i do it...

any pointers are helpful..

regards.

[Former Member]

Hi,

I have a report, i need to run the report every day at 10.00 AM.

So, i need to schedule it...but how can i do it...

any pointers are helpful..

regards.

[Former Member]

Hi,

Use transaction SM36

For step by step process refer this link...

http://help.sap.com/saphelp_bw30b/helpdata/en/c4/3a7f87505211d189550000e829fbbd/content.htm

Hope this helps!!

Regards,

Omkaram.

[Former Member]

Hi,

See the step by step procedure.

Scheduling Background Jobs:

1. Background jobs are scheduled by Basis administrators using transaction SM36.

2. To run a report in a background, a job needs to be created with a step using the report name

and a variant for selection parameters. It is recommended to create a separate variant for each

scheduled job to produce results for specific dates (e.g. previous month) or organizational units (e.g.

company codes).

3. While defining the step, the spool parameters needs to be specified

(Step-> Print Specifications->Properties) to secure the output of the report and help authorized users

to find the spool request. The following parameters needs to be maintained:

a. Time of printing: set to “Send to SAP spooler Only for now”

b. Name – abbreviated name to identify the job output

c. Title – free form description for the report output

d. Authorization – a value defined by Security in user profiles to allow those users to access

this spool request (authorization object S_SPO_ACT, value SPOAUTH). Only users with matching

authorization value in their profiles will be able to see the output.

e. Department – set to appropriate department/functional area name. This field can be used in

a search later.

f. Retention period – set to “Do not delete” if the report output needs to be retained for more

than 8 days. Once the archiving/document repository solution is in place the spool requests could

be automatically moved to the archive/repository. Storage Mode parameter on the same screen

could be used to immediately send the output to archive instead of creating a spool request.

Configuring user access:

1. To access a report output created by a background job, a user must have at

least access to SP01 (Spool requests) transaction without restriction on the user

name (however by itself it will not let the user to see all spool requests). To have

that access the user must have S_ADMI_FCD authorization object in the profile with

SPOR (or SP01) value of S_ADMI_FCD parameter (maintained by Security).

2. To access a particular job’s output in the spool, the user must have

S_SPO_ACT object in the profile with SPOAUTH parameter matching the value used

in the Print Specifications of the job (see p. 3.d above).

3. Levels of access to the spool (display, print once, reprint, download, etc) are

controlled by SPOACTION parameter of S_SPO_ACT. The user must have at least

BASE access (display).

On-line reports:

1. Exactly the same configuration can be maintained for any output produced

from R/3. If a user clicks “Parameters” button on a SAP Printer selection dialog, it

allows to specify all the parameters as described in p. 3 of

“Scheduling background jobs” section. Thus any output created by an online report

can be saved and accessed by any user authorized to access that spool request

(access restriction provided by the Authorization field of the spool request

attributes, see p. 3.d of “Scheduling background jobs” section).

Access to report’s output:

1. A user that had proper access (see Configuring user access above) can

retrieve a job/report output through transaction SP01.

2. The selection screen can be configured by clicking “Further selection

criteria…” button (e.g. to bring “Spool request name (suffix 2)” field or hide other

fields).

3. The following fields can be used to search for a specific output (Note that

Created By must be blank when searching for scheduled job’s outputs)

a. Spool request name (suffix 2) – corresponds to a spool name in p. 3.b in

“Scheduling background jobs” section above).

b. Date created – to find an output of a job that ran within a certain date range.

c. Title – corresponds to spool Title in p. 3.c in “Scheduling background jobs”

section above).

d. Department - corresponds to spool Department in p. 3.e in “Scheduling

background jobs” section above).

4. Upon entering selection criteria, the user clicks the Execute button to

retrieve the list of matching spool requests.

5. From the spool list the user can use several function such as view the

content of a spool request, print the spool request, view attributed of the spool

request, etc. (some functions may need special authorization, see p.3 in

Configuring user access)

a. Click the Print button to print the spool request with the default attributes

(usually defined with the job definition). It will print it on a printer that was

specified when a job was created.

b. Click the “Print with changed attributed” button to print the spool request

with the different attributes (e.g. changing the printer name).

c. Click the “Display contents” button to preview the spool request contents. A

Print and Download functions are available from the preview mode.

[Former Member]

Hi,

You can define and schedule background jobs in two ways from the Job Overview:

Directly from Transaction SM36. This is best for users already familiar with background job scheduling.

The Job Scheduling Wizard. This is best for users unfamiliar with SAP background job scheduling. To use the Job Wizard, start from Transaction SM36, and either select Goto ® Wizard version or simply use the Job Wizard button.

Procedure

Call Transaction SM36 or choose CCMS ® Jobs ® Definition .

Assign a job name. Decide on a name for the job you are defining and enter it in the Job Name field.

Set the job’s priority, or "Job Class":

High priority: Class A

Medium priority: Class B

Low priority: Class C

In the Target server field, indicate whether to use system load balancing.

For the system to use system load balancing to automatically select the most efficient application server to use at the moment, leave this field empty.

To use a particular application server to run the job, enter a specific target server.

If spool requests generated by this job are to be sent to someone as email, specify the email address. Choose the Spool list recipient button.

Define when the job is to start by choosing Start Condition and completing the appropriate selections. If the job is to repeat, or be periodic, check the box at the bottom of this screen.

Define the job’s steps by choosing Step, then specify the ABAP program, external command, or external program to be used for each step.

Save the fully defined job to submit it to the background processing system.

When you need to modify, reschedule, or otherwise manipulate a job after you've scheduled it the first time, you'll manage jobs from the Job Overview.

[Former Member]

Hi

This can be done easily as follows:

Goto transaction SM37, goto Extended Job Selection, click on the period tab, where you can set the job to be run the way you want, like daily, weekly etc at a particular time. Do specify the job name.

Thanks

Vijay