While there are 7 different states an SAP job can have in batch job table tbtco, there are many more possible job status a job can show in CPS/BPA. This document tries to provide additional explanation about the CPS/BPA job status’s and the corresponding status the job in SAP should have.
The following table lists the possible status a job can have in SAP:
| SAP Job Status |
|---|
| SCHEDULED tbtco-status ‘P’ |
| RELEASED tbtco-status ‘S’ |
| READY tbtco-status ‘Y’ |
| ACTIVE tbtco-status ‘Z’ |
| RUNNING tbtco-status ‘R’ |
| CANCELED/ABORTED tbtco-status ‘A’ |
| FINISHED tbtco-status ‘F’ |
- A job can exist in CPS/BPA before it is created in SAP.
- A job can have a different status in CPS/BPA to the status in SAP or perhaps no job exists in SAP.
- A job must reach a ‘final status’ such as completed or killed (See list below) before it can be deleted from CPS/BPA.
When a job/process is selected in the process monitor (job monitor), the remote information of the job/process is displayed in the lower frame of the UI where the job details are displayed. Here you can see the Remote status, the SAP job name, the SAP jobID, remote start and finish times and SAP user. (See screenshot)
The following table maps SAP jobs status to CPS/BPA job status and gives more detailed description about the status meaning.
| Possible SAP jobstatus | SAP CPS/BPA jobstatus | Description of CPS/BPA job status |
|---|---|---|
| Initial Job states | ||
| (No job exists in SAP) | New | The job/process has been submitted bit it has not been validated to run. Under normal conditions a job should only be in new status for a brief moment. |
| (No job exists in SAP) | Chained | A job chain has been submitted and the child jobs in the chain are awaiting their start condition to occur. |
| (No job exists in SAP) | Disabled | When a job chain is submitted, job chain steps and job chain jobs will remain in status Chained or Disabled until they are started. Disabled jobs will immediately reach status Ignored when the process server processes them. |
| Pre-Running Job States | ||
|
RELEASED, SCHEDULED, (No job exists in SAP) |
Scheduled | Scheduled status means that the job/process start condition has been validated and is waiting for its start condition to occur. Normally when a job is in Scheduled status in CPS/BPA, a job does not yet exist in SAP. However, when interception is configured with action “Schedule Intercepted”, then when a job is ‘caught’ in SAP, a job in Scheduled status is created in CPS/BPA. |
| (No job exists in SAP) | QueueHeld | The queue was held before the job was sent |
|
SCHEDULED, (No job exists in SAP) |
Held | (Admin guide: The execution of the process has been manually paused.) Intercepted jobs can be in HELD status in CPS/BPA and SCHEDULED status in SAP. But a CPS/BPA job can also be held before the job is created in SAP. |
| (No job exists in SAP) | EventWait | The job/process is waiting for a CPS/BPA event to be raised. The CPS/BPA event may or may not be synchronised to an SAP event. |
| (No job exists in SAP) | LockWait | The job/process is waiting for a lock to be released. Locks are objects in CPS/BPA the prevent simultaneous execution of jobs/processes. |
| (No job exists in SAP) | Queued | The start condition of the job/process has been met, but the job/process cannot be executed yet. Right-clicking on the job/process and choosing ‘Explain job status’ will provide additional information about why the job/process is in QUEUED status. There may be an ‘Execution size limit’ set on the queue or there may be no free batch work processes in SAP. |
| (No job exists in SAP) | Dispatched | (Admin guide: The process has been dispatched to a service, but the service has not yet started the process.) This status is before any communication is sent to SAP to create the job. DISPATCHED is a transitional status and normally a job/process should only be in DISPATCHCED status for a brief moment. |
|
RELEASED, READY, RUNNING, (No job exists in SAP) |
Assigned | (Admin guide: The process has been accepted by the service, but it has not been started yet.) When a job is in ASSIGNED status the call has been made to create and start the job in SAP. It is possible that the SAP job can have the status RELEASED, READY or RUNNING during the brief time a job/process is in ASSIGNED status in CPS/BPA. |
| Running job states | ||
|
RELEASED, READY, RUNNING. |
RUNNING | (Admin guide: The process is being executed by the service. Once it has entered this state, the JobService that is running this job no longer needs any access to the JobParameters of this job.) The job/process has started execution. A running job will have the status RELEASED and READY in SAP only for a brief moment before the job goes to RUNNING in SAP. |
|
RUNNING, (No job exists in SAP) |
WAITING | (Admin guide: The process is waiting for the result of the execution of another process.) A parent job chain can have the status WAITING but no job exists in SAP but the chid jobs/process of the chain are in RUNNING or other status. |
|
RUNNING, CANCELED |
KILLING | (Admin guide: The process was terminated while it was running, the process status was RUNNING, WAITING or CONSOLE) If a batch work process is killed or a job is canceled manually in SAP or killed manually in the CPS/BPA UI, then a job will show as KILLED status. The option to ‘Kill’ a job is normally only available in the context menu of the job monitor while the job is in RUNNING status. |
| (No job exists in SAP) | CANCELING | A request came from a user action or the CPS/BPA application to cancel the job/process. Normally when a cancel request is sent for a CPS/BPA job, no job exists in SAP at this point. The option to ‘Cancel’ a job/process is only available in the context menu in the job monitor, after a job is submitted but before it’s start condition occurs. |
| SCHEDULED, RUNNING, CANCELED, FINISHED. | CONSOLE | (Admin guide: The process has issues an OperatorMessage to the message monitor and is waiting a reply) A job/process is CONSOLE status will always have an attached ‘Operator message’. A job/process is CPS/BPA in CONSOLE status can have a corresponding job in SAP, possibly in one of the status’ SCHEDULED, RUNNING, CANCELED or FINISHED. |
| FINAL JOB STATES | ||
| CANCELED, FINISHED | COMPLETED | Normally when a job reaches FINISHED status in SAP it will go to COMPLETED status in CPS/BPA. ‘Final status handlers’ allow you to set the status of a chain or step to a different status to the initial final status of the chain. |
| CANCELED, FINISHED | ERROR | (Admin guide: The execution of the process failed.) An error occurred during the execution of the ABAP program or BW process chain. CPS/BPA reads the information in the job log or return code of the ABAP program and sets the job/process in CPS/BPA to ERROR status. |
| CANCELED, FINISHED | KILLED | (Admin guide: The process was terminate while it was running, the process status was RUNNING, WAITING or CONSOLE.) If a batch work process is killed or a job is canceled manually in SAP or KILLED manually in the CPS/BPA UI, then a job will show KILLED status. |
| (No job exists in SAP) | CANCELED | (Admin guide: The process was terminated before execution commenced.) If a job/process in CPS/BPA has the status CANCELED, this means no job should exist in SA and the job was canceled in CPS/BPA before the job is sent to SAP. |
| (No job exists in SAP) | SKIPPED | (Admin guide: The process server has not executed the job chain job due to a precondition or the usage of the ‘Start at specified step’ scheduling parameter. When the job chain is restarted, the process server will re-evaluate job chain jobs with the status SKIPPED.) |
| (No job exists in SAP) | IGNORED | (Admin guide: The process was ignored as a result of being disabled when the job chain was submitted.) If a step in a job chain is DISABLED then the status of the step will show IGNORED when the chain runs. |
|
FINISHED, (Or job could be deleted in SAP) |
UNKNOWN | (Admin guide: The service was terminated while the process was running. The process status was RUNNING, WAITING or CONSOLE). Also the job definition named System_ForceJobStatusUnknown can be used to force a running job, which should not or cannot be killed, into the status UNKNOWN. Jobs/processes in non-final states cannot be deleted so forcing a job/process to UNKNOWN status allows you to delete a job that never reached a final state in the normal way. |
| SPECIAL JOB STATES | ||
| (No job exists in SAP) | MODIFIED | (Admin guide: A resubmit or restart has failed and the job has been put into status MODIFIED, the job will not start without intervention.) Normally no job exists in SAP when a job/process in in MODIFIED status in CPS/BPA |
| (No job exists in SAP) | NEVER | (Admin guide: Due to conflicting time windows, time window elements or a shutdown process server, the process shall not execute for at least 2 years.) A job/process will be set to NEVER status in CPS/BPA before it is sent to SAP so no job should exist in SAP when a job is in NEVER status in CPS/BPA. |
| (No job exists in SAP) | OVERDUE | (Admin guide: The process did not run in the first time window opened after the process start time.) When a job definition has missed its window of execution, it is set to OVERDUE. It is possible to configure the reaction with the job definition option ‘Act when jobs are overdue’ – When a job has missed its time window, you can choose to change the job status and/or raise an ‘Event’. |
New NetWeaver Information at SAP.com
Very Helpfull
