Analyzing Job Status 
Procedure
From the CCMS initial screen, choose Jobs ® Maintenance.
All background processing jobs can be subjected to an analysis of job status. This analysis is concerned with the following criteria:
(requested/actual start time, steps, target server, job class and so on)
You can restrict the number of jobs selected on the request screen:
It is important whether or not the user who makes the selection has an administrator authorization for background processing. If a user has administrator administration, then jobs will be selected across all clients. If not then jobs will only be selected in the client onto which the user has logged on.
The system displays a list of the jobs that were found:
This overview displays information that is of particular importance for problem analysis, that is, job status. The list is usually sorted alphabetically, but you can sort it according to other criteria (by choosing Edit ® Sort). You can sort it chronologically, for example, so that you can easily see the jobs that ran over a given time period.
The following functions are especially important for problem analysis:
This contains information about any problems which occurred in the job at runtime, such as whether an ABAP program was terminated or an external program could not be started.
This also contains a list of all messages which were output either by ABAP programs with the MESSAGE statement or by external programs.
Displays all data belonging to a given job, such as the start date, steps, spool lists generated by steps, etc. The job detail information also shows on which host and in which work process the job was executed.
To change job data such as target server, start date, steps, and so on.
You can access the spool list of a job directly from here.
You can access the step data of a job directly from here.
This can be used to pause and analyze an active job which is in the middle of executing an ABAP program. An ABAP debugger window is opened, showing the ABAP program code at the point at which it is being executed. The code can now be analyzed. You exit the debugger by choosing Debugging
The ABAP program (the job) then continues to execute from the point at which it was stopped. You cannot use this function on external programs.
This immediately terminates an active job.
This allows you to check whether the status of a job as shown in the list is the same as the real status of the job. There is a database table that contains the status information of the jobs.
Situations sometimes occur (for example, a problem in the connection to the database) that prevent the background processing runtime system from entering the current status of a job in the appropriate database table. This will cause a discrepancy between the real status of a job and the status that was entered in the database.