BACKGROUND WORK PROCESS
1.The Programs which are timed out due to restriction of time,i.e
long running programs,time consuming programs,periodic jobs and memory
expensive programs are defined(scheduled) to run in the background mode
during off peak hours.
Background Process handles the entire transaction in one step. it is dedicated to the user task and waits until the task is completed.The background process could not be timed out due to the process timeout parameter.it may run for minutes, hours and days.Background processes may be thrown out of the system due to memory issues.
Standard SAP House Keeping jobs are scheduled in SM36. Standard Jobs–>Default Scheduling.
Standard SAP DB House Keeping jobs are scheduled in DB13.
Customer background jobs can be defined in SE38/SA38 or from any Executable Transaction.
Background Process Flow:
1.A User Submits a Request to execute an expensive program.
2.The Dialog Process handles the Request and Stores them in the TBTC* Tables
TBTCP—Program that needs to run in the Background mode
TBTCS—Schedule
TBTCT—Time
3.A Background Scheduler sapmssy8 runs periodically for every 60 seconds in the dialog mode or the time specified in the parameter rdisp/btctime=60.
4.Scheduler Picks the Jobs with status ready and allocates a background process.
5.The background process is dedicated to the job and complete the task.
6.The Advantage of the background scheduling is monitoring can be displayed in SM37. i.e ABAP Level tasks(SAP), OS Level tasks, DB Tasks and External Tasks.
7.The background Processes are defined by using parameter rdisp/wp_no_btc. Minimum two processes are required for the entire System. it is possible to configure as many background processes as required based on available resources.
8.it is possible to Integrate the SAP Background jobs with Third Party schedulers such as TIDAL, BMC-CONTROL-M, SAP REDWOOD SCHEDULER and TIVOLI Scheduler
Defining a Background Job:
Execute SM36
Specify the Job Name(Unique Name to identify the Job).
Specify the Jobs class(A, B, C) A- HIGH, B-Medium and C-Low
Status is automatically set:
Job Statuses:
Scheduled: it is defined for execution in SM36, but date and time are not specified…it will be in the scheduled as long as Execution Condition is Specified.
Released: it is specified with execution conditions such as date,time,immediate,after job,after event,operation modes etc…
Ready: The Execution Time occurred
Active: The background process allocated and currently running
Finished : job Finished
Cancelled: job terminated/aborted
Execution Target Server: when more then one application server is configured then specify the name of the Instance where the job need to be Executed.
Spool list recipients: The output of the job will be sent to the user’s email or to the printer.(payslip print or payslip to email in pdf format)
Start Condition: Specify the job start Condition.
Immediate
Periodic
Date and Time
after an event
after a job
after factory calendar
after operation modes
save the job an entry will be displayed in SM37.
Job Step:
Job Step can be defined by using the Following
1.ABAP Program
2.External Command
3.External Program
1.ABAP Program is a standard or Customer Program/Report defined in SE38. it Requires a Variant for Execution.
Variant: it is a program selection criteria that is used to populate runtime values during program execution.These variants are defined in SA38/SE38.
2.External Command: These Commands are defined in SM49/SM69. These Commands are used to Execute at OS Level.
Ex: A Database Backup is executed at OS Level and all the database Housekeeping jobs are executed at OS Level using backup, Restore and Recovery Commands.These are scheduled in DB13 Using DBA Calender.
brconnect -f next
brconnect -f check
brconnect -f next
brconnect -f stats
brarchive
brbackup
3.External Program:These are triggered by using executable ‘sapxpg’. These are not predefined but triggered based on Requirements.
Ex: While transporting Requests(STMS),it triggers External programs as sapevents.(sapevt)
SAP Standard Background Jobs:
RSBTCDEL—–Deletes Old Batch jobs from TBTC Tables
RSSNAPDL—–Deletes Old ABAP Dumps from SNAP Table
RSPO0041/RSPO1041–Deletes the Old Spool Request from Spool Tables
RSM13002–Delete the Old Update Records from the Update Temp Tables
RSPO0043/RSPO1043—>Check the Consistency of the Spool in background
RSBDCREO——background to delete the old batch input logs.
RSCOLL00 —–is a performance collector job which schedules further Background jobs.
Note: There are various jobs that are scheduled in SM36 to collect the Performance Information and display in ST02/ST03/ST04/ST07.
WHY????
scheduled: The Job is Scheduled but time/execution conditions are not specified
Released: The job is Released with the dependency of execution.
Time, job, event, operation modes….which have not occurred.
Ready:
1.rdisp/btctime is set to 0 or higher value 43200
2.btctrns1 report pauses background jobs and resumes by btctrns2(it is set automatically by support packages/updates/upgrades)
3.There are no background work processes to allocate to the job
4.The Configured Processes are not sufficient or the processes are held with the expensive tasks.
5.Based on requirement increase the Processes to avoid the processes in the Ready state for a Longer time.
6.Schedule operation modes.
Active:
The Job is active and running for a long time.
1.Network/bandwidth Congestion
2.Required Memory, CPU, DISK I/O are not available
3.Expensive processes are running on the System
4.The Processes are waiting for a response from external system
Cancelled or sometimes they are simply in the ACTIVE state blocking the Work Process.
1.Issues on the Target System: when the background process is working to get the data from External Systems(RFC Failure, CPIC Issues, Gateway Issues) Communication with BW, CRM, SRM and SCM Systems
2.Bottleneck on the Database(due to space or any issue on the DB) ORA-1631/32 ora-1653 /1654,ora-255,272 etc…check DB17 for corrective measures.
3.File System Issues(File Could not be opened for reading and write, authorizations, virus issues)
4.Variants Issue
5.User Input Errors(Zero divides/convert number etc)
6.Authorization issues(user id, password, client does not exist or user id expired, password expiry etc)
7.The Jobs like SLCA_LCK_SYNC_OWNERS runs only on Supply Chain Management System. They are failed on ERP, SRM, CRM and Netweaver Systems
8.No Component Chosen for WP_CACHE_RELOAD Jobs.it also looks for SCM System.
Get the Knowledge transfer from the Business Process Owners.
Inform the BPO about the Error Message so that they can reschedule the Job or Reprocess or run the job from SM37.
Do not own any background job other then Sm36/db13 standard jobs. if required create a user like WF-BATCH to schedule the background jobs of the End User Community.
Use Report RSBTCDEL to delete the background jobs periodically.
Execute SM37 and repeat the scheduling of a background job provided there is a black and white request from the Users.
Note: Do not Kill any Background job unless it is warranted and approved by the management, else the system may be inconsistent if the job is related to an update.
Scheduled, released and ready can be paused (except Active).
Third Party Scheduler standard job dependencies and controls on SAP R/3 jobs. Schedule SAP R/3 jobs to run on specified days and times and in a defined order.Define inter-dependencies between SAP R/3 jobs and jobs that run on different platforms.They are used to Customize job execution return codes, Intercept jobs, Track child jobs, Raise events and Notifications.
Ex: TIDAL, Control-M, BMC, TIVOLI, SAP REDWOOD Job Scheduler.
Background Process handles the entire transaction in one step. it is dedicated to the user task and waits until the task is completed.The background process could not be timed out due to the process timeout parameter.it may run for minutes, hours and days.Background processes may be thrown out of the system due to memory issues.
Standard SAP House Keeping jobs are scheduled in SM36. Standard Jobs–>Default Scheduling.
Standard SAP DB House Keeping jobs are scheduled in DB13.
Customer background jobs can be defined in SE38/SA38 or from any Executable Transaction.
Background Process Flow:
1.A User Submits a Request to execute an expensive program.
2.The Dialog Process handles the Request and Stores them in the TBTC* Tables
TBTCP—Program that needs to run in the Background mode
TBTCS—Schedule
TBTCT—Time
3.A Background Scheduler sapmssy8 runs periodically for every 60 seconds in the dialog mode or the time specified in the parameter rdisp/btctime=60.
4.Scheduler Picks the Jobs with status ready and allocates a background process.
5.The background process is dedicated to the job and complete the task.
6.The Advantage of the background scheduling is monitoring can be displayed in SM37. i.e ABAP Level tasks(SAP), OS Level tasks, DB Tasks and External Tasks.
7.The background Processes are defined by using parameter rdisp/wp_no_btc. Minimum two processes are required for the entire System. it is possible to configure as many background processes as required based on available resources.
8.it is possible to Integrate the SAP Background jobs with Third Party schedulers such as TIDAL, BMC-CONTROL-M, SAP REDWOOD SCHEDULER and TIVOLI Scheduler
Defining a Background Job:
Execute SM36
Specify the Job Name(Unique Name to identify the Job).
Specify the Jobs class(A, B, C) A- HIGH, B-Medium and C-Low
Status is automatically set:
Job Statuses:
Scheduled: it is defined for execution in SM36, but date and time are not specified…it will be in the scheduled as long as Execution Condition is Specified.
Released: it is specified with execution conditions such as date,time,immediate,after job,after event,operation modes etc…
Ready: The Execution Time occurred
Active: The background process allocated and currently running
Finished : job Finished
Cancelled: job terminated/aborted
Execution Target Server: when more then one application server is configured then specify the name of the Instance where the job need to be Executed.
Spool list recipients: The output of the job will be sent to the user’s email or to the printer.(payslip print or payslip to email in pdf format)
Start Condition: Specify the job start Condition.
Immediate
Periodic
Date and Time
after an event
after a job
after factory calendar
after operation modes
save the job an entry will be displayed in SM37.
Job Step:
Job Step can be defined by using the Following
1.ABAP Program
2.External Command
3.External Program
1.ABAP Program is a standard or Customer Program/Report defined in SE38. it Requires a Variant for Execution.
Variant: it is a program selection criteria that is used to populate runtime values during program execution.These variants are defined in SA38/SE38.
2.External Command: These Commands are defined in SM49/SM69. These Commands are used to Execute at OS Level.
Ex: A Database Backup is executed at OS Level and all the database Housekeeping jobs are executed at OS Level using backup, Restore and Recovery Commands.These are scheduled in DB13 Using DBA Calender.
brconnect -f next
brconnect -f check
brconnect -f next
brconnect -f stats
brarchive
brbackup
3.External Program:These are triggered by using executable ‘sapxpg’. These are not predefined but triggered based on Requirements.
Ex: While transporting Requests(STMS),it triggers External programs as sapevents.(sapevt)
SAP Standard Background Jobs:
RSBTCDEL—–Deletes Old Batch jobs from TBTC Tables
RSSNAPDL—–Deletes Old ABAP Dumps from SNAP Table
RSPO0041/RSPO1041–Deletes the Old Spool Request from Spool Tables
RSM13002–Delete the Old Update Records from the Update Temp Tables
RSPO0043/RSPO1043—>Check the Consistency of the Spool in background
RSBDCREO——background to delete the old batch input logs.
RSCOLL00 —–is a performance collector job which schedules further Background jobs.
Note: There are various jobs that are scheduled in SM36 to collect the Performance Information and display in ST02/ST03/ST04/ST07.
WHY????
scheduled: The Job is Scheduled but time/execution conditions are not specified
Released: The job is Released with the dependency of execution.
Time, job, event, operation modes….which have not occurred.
Ready:
1.rdisp/btctime is set to 0 or higher value 43200
2.btctrns1 report pauses background jobs and resumes by btctrns2(it is set automatically by support packages/updates/upgrades)
3.There are no background work processes to allocate to the job
4.The Configured Processes are not sufficient or the processes are held with the expensive tasks.
5.Based on requirement increase the Processes to avoid the processes in the Ready state for a Longer time.
6.Schedule operation modes.
Active:
The Job is active and running for a long time.
1.Network/bandwidth Congestion
2.Required Memory, CPU, DISK I/O are not available
3.Expensive processes are running on the System
4.The Processes are waiting for a response from external system
Cancelled or sometimes they are simply in the ACTIVE state blocking the Work Process.
1.Issues on the Target System: when the background process is working to get the data from External Systems(RFC Failure, CPIC Issues, Gateway Issues) Communication with BW, CRM, SRM and SCM Systems
2.Bottleneck on the Database(due to space or any issue on the DB) ORA-1631/32 ora-1653 /1654,ora-255,272 etc…check DB17 for corrective measures.
3.File System Issues(File Could not be opened for reading and write, authorizations, virus issues)
4.Variants Issue
5.User Input Errors(Zero divides/convert number etc)
6.Authorization issues(user id, password, client does not exist or user id expired, password expiry etc)
7.The Jobs like SLCA_LCK_SYNC_OWNERS runs only on Supply Chain Management System. They are failed on ERP, SRM, CRM and Netweaver Systems
8.No Component Chosen for WP_CACHE_RELOAD Jobs.it also looks for SCM System.
Get the Knowledge transfer from the Business Process Owners.
Inform the BPO about the Error Message so that they can reschedule the Job or Reprocess or run the job from SM37.
Do not own any background job other then Sm36/db13 standard jobs. if required create a user like WF-BATCH to schedule the background jobs of the End User Community.
Use Report RSBTCDEL to delete the background jobs periodically.
Execute SM37 and repeat the scheduling of a background job provided there is a black and white request from the Users.
Note: Do not Kill any Background job unless it is warranted and approved by the management, else the system may be inconsistent if the job is related to an update.
Scheduled, released and ready can be paused (except Active).
Third Party Scheduler standard job dependencies and controls on SAP R/3 jobs. Schedule SAP R/3 jobs to run on specified days and times and in a defined order.Define inter-dependencies between SAP R/3 jobs and jobs that run on different platforms.They are used to Customize job execution return codes, Intercept jobs, Track child jobs, Raise events and Notifications.
Ex: TIDAL, Control-M, BMC, TIVOLI, SAP REDWOOD Job Scheduler.
Comments
Post a Comment