Doubt on SM36

Former Member — Thu, 05 Apr 2007 11:58:14 GMT

Hi Group,

Can any one explain me on Back Groud schedulling?

Where should I give my prog name in SM36 and also tell me can I write a code inside my prog where in I can start the background schedule.

Thank you for your time.

Regards,

Varun.

Re: Doubt on SM36

Former Member — Thu, 05 Apr 2007 12:01:02 GMT

HI Varun,

If you want to execute the job in background .There are 2 options.

1.Online

Goto se38-->enter program name ~~>(On menu bar) program~~>

Exceute-->Background.

2.Schedule

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

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.

If you have any selection screen parameters for your program you need to enter the values for those fields in runtime. So, if you schedule your program in background to execute then there is no one to do this job. Here comes the concept of Variant.

With variant you define what are the selection field values in the runtime. During runtime the program picks this values and runs the program.

When you execute your program which has selection fields, you enter the values and then you click on 'GO TO ' tab and 'SAVE AS VARIANT'.

When you schedule your program in background, give this variant also. Then it will run automatically.

Hope this resolves your query.

Reward all the helpful answers.

Regards

Re: Doubt on SM36

Former Member — Thu, 05 Apr 2007 12:02:26 GMT

When a program is scheduled to run at some particular time without user intervention is called background scheduling. When a job is scheduled, SY-BATCH is set to 'X'. A job can be scheduled through tcode sm36. Here you dont see the screens or the result. The result is directed to the spool.

If a job is executed directly and you will see the flow through the screens and the results are visible on your screen wither as ALV or classical report as per the design of the program.

chk this:

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

**reward if helpful

regards,

madhu

Re: Doubt on SM36

Former Member — Thu, 05 Apr 2007 12:08:38 GMT

Hi Varun,

JOB_OPEN AND JOB_SUBMIT AND JOB_CLOSE are the FMs we can use int abap code.

In sm36 enter the job name and enter the scheduling time.

Hope this helps you, reply for queries, Shall post you the updates.

Regards.

Kumar

Re: Doubt on SM36

Former Member — Thu, 05 Apr 2007 12:11:01 GMT

Hi,

In the field "jobname" in SM36 what is the name I have to enter?

Thank you.

Re: Doubt on SM36

Former Member — Thu, 05 Apr 2007 12:13:55 GMT

Hi,

give an appropirate name to identify your job in sm37.

regards,

madhu

Re: Doubt on SM36

Former Member — Thu, 05 Apr 2007 12:16:51 GMT

Hi Varun,

You can give anyname of your choice, but do remember it to check the status of the Background job at a later stage using SM37.

Hope this resolves your query.

Reward all the helpful answers.

Regards

topic Doubt on SM36 in Application Development and Automation Discussions

Doubt on SM36

Re: Doubt on SM36

Re: Doubt on SM36

Re: Doubt on SM36

Re: Doubt on SM36

Re: Doubt on SM36

Re: Doubt on SM36