Scribd
Upload
3 views5 pages

Sap Background Workprocess

The document outlines various SAP transaction codes related to work processes, including SM50 for local work process overview, SM51 for application server checks, and SM60 for global work process overview. It also details how to manage update records with SM13, check update statuses with SM14, lock entries with SM12, and create background jobs using SM36. Finally, it mentions monitoring background jobs through SM37.

Uploaded by

karanvq76789
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
3 views5 pages

Sap Background Workprocess

The document outlines various SAP transaction codes related to work processes, including SM50 for local work process overview, SM51 for application server checks, and SM60 for global work process overview. It also details how to manage update records with SM13, check update statuses with SM14, lock entries with SM12, and create background jobs using SM36. Finally, it mentions monitoring background jobs through SM37.

Uploaded by

karanvq76789
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

SAP BACKGROUND WORKPROCESS

 Dialog work process takes the user request and process the user request.
 SM50 is the transaction code for local work process overview. Only one application server
related information is shown here.
 Via SM51 transaction code, we can check how many application servers are there in the
system.
 SM60 is the transaction code for global work process overview.
 One dialog work process (10/9) is up and running.

 Go to SM13 transaction code.


 SM13 is the transaction code to check if there are any failed update records or not.
 Update work process will update the records in the database table level.

 SM14 is the transaction code used to check the status of the update.
 Whether the update is active or not.
 If the update is active then the records will be updated in the database table level otherwise
the records will not be updated in the database table level.

 SM12 is the transaction code used to lock the entries.


 Same person cannot execute the same transaction codes.
 One of the users got locked by doing so.
 SM36 is the transaction code for background job creation.

 Enter the job name and job class (A – High priority).


 Go to job step and enter the program name.
 Enter the program name which is to be executed as a background job and then click on save
button.
 Click on job startup and then choose the startup conditions.
 Go to SM37 transaction code for background job monitoring.

You might also like