In SM37 screen
Select the executed Job line item ( status = finished) and click on the "Spool" icon at top menu bar.
Then select the line in the spool output screen and select " view details" ( specs icon)
The ran job details will be displayed.
For example if you have run a report, then you can see the report output this way.
Message was edited by:
SM37 is used to run the some activities in background with doing any thing manually,what you understood is 100% correct.
Background jobs are different scheduled one,released one,active one,canceled....
Scheduled means this job is scheduled for particular time
Released means,it is released to run the job
Active means,schedule job is still active to run.
Canceled means job is failed due to some reasons.
Reward points pls.
In background processing, the SAP System automatically runs any report or program that you can start interactively.
When you schedule a job in the background processing system, you must specify:
The ABAP report or external program that should be started
The start time
The printing specifications
The background processing system starts your job and runs the program(s) that you specify. Afterwards, you can check whether your job was executed successfully and display a log of any system messages.
Suppose you need to run a report of customers whose bills are overdue.You can:
Start the report yourself from the ABAP Editor. If you do this, the system runs the report interactively, in a session at your PC or workstation. While the report is being processed, your computer response time may be slower.
Or, you can have the background processing system run the report. To do this, you must create a background job that tells the system what you want it to do.
The background processing system runs your "late bills" report according to your instructions. The list generated by the report is either printed directly or is waiting for you in the SAP output controller (see Using the Output Controller).You can also check in the background processing system whether the report ran correctly.
Running a report in the background does not tie up the SAP sessions you are currently working with.
When you start a report interactively, your current SAP session is blocked for further input for as long as the report runs.
When you start the report in the background, running the report does not influence your interactive work with the SAP System.
You can shift the execution of reports to the evening or other periods of low load on the SAP System.
You can schedule a report or external program to run at any time that the SAP System is active. You can also set up reports to run automatically on a regular basis (for example, on the last day of each month).
Background processing is the only way you can execute long-running jobs.
To prevent tying up system resources with interactive sessions for long reports, the SAP System has a built-in time limit on interactive sessions. If a single ABAP report runs for more than 5 minutes continuously in an interactive session, the SAP System terminates the report automatically.
The background processing system executes long-running ABAP reports more efficiently. Often, such reports are automatically scheduled for execution in the background. In this case, you do not need to schedule them for background processing yourself.
Accessing the Background Processing System
The table below shows how you can access the background processing system.
Point of Departure
To Schedule a Program
The ABAP Editor
You can start ABAP programs and reports either interactively or as background jobs.
Choose Program ® Background.
The system displays the ABAP job scheduling screen.
Elsewhere in the SAP System
You can schedule an ABAP program or external program as a background job.
Choose System ® Services ® Jobs ® Define job.
This is an alternative to job scheduling by way of the ABAP Editor.
The system displays the standard job scheduling screen.
You can schedule an internal (ABAP) or external program to run.
An SAP application
Often, long-running reports are scheduled automatically or semiautomatically for background processing.
Choose the appropriate report using the menu or a function key. The SAP application schedules the report as a background job.
Your program is scheduled to run in the background.
Scheduling Background Jobs
In many SAP applications, long-running programs are automatically scheduled as background jobs. However, you can also schedule background jobs yourself.
To schedule a program for background processing:
Start the job scheduling function.
To start the standard job scheduling function, choose Administration ® CCMS ® Jobs ® Define job.
To schedule ABAP programs, you can also use the ABAP job scheduling function. From the ABAP Editor, choose Program ® Execute ® Background.
If you are scheduling an external command or external program as a background job, you must use standard job scheduling.
Use the Job Wizard to define your job. In the application toolbar, choose the wizard icon:
The Job Wizard is available only from the standard job scheduling function.
The initial screen of the SAP Job Wizard appears:
Save the job. When you see the message Job saved, the job has been successfully scheduled.
A job that has been scheduled must also be released. This restriction applies even if you specify an immediate start for your job.
If you have the necessary authorization, your job is released automatically when you schedule it. Otherwise, your system administrator will release your job.
Check the status of your job by choosing System ® Own jobs.
For more information on your jobs than is shown in the status screen, choose Job overview. See also Checking the Status of a Background Job.
Checking the Status of a Background Job
Check the status of your background jobs by choosing System ® Own jobs from anywhere in the system.
At the top of the screen, the system displays the status of each of your jobs. The F1 field help explains each status.
In the middle of the screen, the system displays the names of your jobs that are active (that is, currently running). Unless you are sure of what you are doing, you should leave the Cancel button alone. Cancel interrupts an active job; that is, it terminates the report that was running.
At the bottom of the screen, the system displays the names of any of your jobs that have been cancelled (that is, ended unsuccessfully). To see the background processing log, choose Log. The log indicates what went wrong with the job.
For more information on your jobs, you can access the management functions of the background processing system by choosing Job overview.
Reward if useful to u