SM37

Former Member — Mon, 17 Sep 2007 04:57:02 GMT

Hi All

could you please give me some more details for TCODE SM37.

Re: SM37

Former Member — Mon, 17 Sep 2007 04:59:48 GMT

sm37 will give the list of all background jobs.

you can select the user name, date of the job run etc..

in the list, you can see the job name, job start date, time, job status, and the job log as well..

Re: SM37

Former Member — Mon, 17 Sep 2007 05:30:52 GMT

hi Joel,

SM37 is used to select the back ground jobs which were defined in SM36 and process them in SM37.

Here we can give job starting conditions, when the job should be executed and all .

and we can know the status of the perticular job here.

<b>Reward points if useful</b>

cheers,

Chandra

Re: SM37

Former Member — Mon, 17 Sep 2007 08:57:55 GMT

Hi,

Tcode SM37 is used to check the status of background jobs Schedulling.

We can use this transaction to schedule the report in a specific time without any user interface.

Check the below link:

http://www2.warwick.ac.uk/services/finance/sap/help/howtoguides/backgroundjobs/

Hope this info will help you.

Rewards Points if Useful.

With regards,

K K V

Re: SM37

Former Member — Mon, 17 Sep 2007 09:18:37 GMT

With function module BP_JOB_MAINTENANCE (transaction SM37), you can call the full job maintenance system of the background processing system, starting with the job selection screen.

Since many users are not familiar with job maintenance and have no desire to search for their jobs, you can use the function modules BP_JOB_SELECT and BP_JOBLIST_PROCESSOR to select and display a list of jobs for the users of your program.

Use BP_JOB_SELECT to generate an internal table of jobs. Then, with BP_JOBLIST_PROCESSOR, you can display the selected jobs in the list format used by the job maintenance system.

You can also use BP_FIND_JOBS_WITH_PROGRAM to select jobs that run a particular program. Use this function module with BP_JOBLIST_PROCESSOR to display a job list to your users. Like BP_JOBLIST_SELECT; BP_FIND_JOBS_WITH_PROGRAM offers interactive and silent modes.

For an example that uses BP_FIND_JOBS_WITH_PROGRAM, please see Displaying Job Status: SHOW_JOBSTATE.

You can display a job list in three modes:

Display mode: The user can view job attributes and such job products as spool requests and job logs. He or she cannot, however, change jobs or perform such operations as releasing a job to run.

Edit mode: The user can perform all maintenance operations for which he or she is authorized.

Select mode: The user is requested to select a job from the list. When the selection is made, the list is closed and the TBTCJOB structure of the selected job is returned to your program.

Authorizations

The authorization tests for background processing are in effect for processing of job lists. These authorizations are described in the Users, Authorizations, and System Security guide and in Basis Customizing.

The following table shows for each attribute of a job:

whether the attribute applies to a job as a whole or only to a single job step

Each of the programs in a job forms a separate job step. For each job step, you can make separate specifications for attributes other than the start date and target system for running the job.

where and how the value for each attribute is assigned.

For programming examples of the attributes, please see the next section. Values for most of the attributes are predefined in the ABAP module LBTCHDEF.

Where to Specify Job Attributes

Attribute

Applies to Job

or to Job Step

Where to Specify

Job name

Job

JOB_OPEN, parameter JOBNAME

Job number

Job

JOB_OPEN (returned by system), parameter JOBCOUNT

Job priority

Job

Always set by default to class C. No other priority can be set with the background programming interface. You can set other priorities only by hand, in the job-scheduling transaction (SM36, also SM37).

Immediate start

Job

JOB_CLOSE, parameter STRTIMMED

Start and repeat specifications

Job

JOB_CLOSE, various parameters. See the programming samples in Task Overview: Full-Control Job Scheduling

Target system

for execution

Job

JOB_CLOSE, parameter TARGETSYSTEM

Automatic

deletion after

job has run

Job

JOB_OPEN, parameter DELANFREP

Recipient for mailed spool requests generated by job

Job

JOB_CLOSE, parameter RECIPIENT_OBJ

Name of

report to run

Job step

JOB_SUBMIT, ABAP SUBMIT

Variant for

report

Job step

JOB_SUBMIT, parameter VARIANT, ABAP SUBMIT, parameter USING SELECTION-SET

Values for selection variables

Job step

ABAP SUBMIT, various parameters. See The ABAP User's Guide

Name and operating-specific variant of external command to run

Job step

JOB_SUBMIT, COMMANDNAME and OPERATINGSYSTEM parameters

Name of external program to run

Job step

JOB_SUBMIT, EXTPGM_NAME parameter

Argument string

for external program

Job step

JOB_SUBMIT, EXTPGM_PARAM parameter

Target system for external program

Job step

JOB_SUBMIT, EXTPGM_SYSTEM parameter

Control options

for external program

Job step

JOB_SUBMIT, various parameters. See Sample Program: Adding a Job Step for an External Command or Program

User for job run-time authorizations

Job step

JOB_SUBMIT, AUTHCKNAM parameter.

ABAP SUBMIT

Printing and archiving specifications

Job step

JOB_SUBMIT, ABAP SUBMIT

using GET_PRINT_PARAMETERS to supply specifications

reward points if helpful....

topic Re: SM37 in Application Development and Automation Discussions

SM37

Re: SM37

Re: SM37

Re: SM37

Re: SM37