How to Delete a Scheduled Background Job in SAP

To deleted scheduled jobs in SAP you need to go to Tcode SM37. Now you select the jobs that you want to delete. Click on the check button left side of each job name and now in the menu go to job->delete.

Precaution must be taken when dealing with dependent jobs. If the completion of job1 starts the job2 and if you delete job1 then job2 will not start.
When deleting the jobs the system will inform you of any such dependent jobs and you need to reschedule them to start again

Difference Between SAP_ALL and SAP_NEW

What is the difference between SAP_ALL and SAP_NEW

Definition of SAP_NEW:-
SAP_NEW is a SAP standard Profile which is usually assigned to system users temporarily during an upgrade to ensure that the activities and operations of SAP users is not hindered, during the Upgrade. It contains all the necessary objects and transactions for the users to continue their work during the upgrade. It should be withdrawn once all upgrade activities is completed, and replaced with the now modified Roles as it has extensive authorizations than required.

Definition of SAP_ALL:-
SAP_ALL is a SAP standard profile, which is used on need basis, to resolve particular issues which may arise during the usage of SAP. It is used by Administrators/Developers only and is applied on a need to use basis, then withdrawn. It contains all SAP system objects and Transactions. SAP_ALL is very critical and only SAP* contains SAP_ALL attached to it in the production system. No other dialog users have SAP_ALL attached to them.

SAP_NEW is used in the Production environment during a version upgrade whereas SAP_ALL shouldn't be or not allowed be used in Production (for audit purposes obviously), except where necessary, in a controlled manner with all proper approvals from the customer.

What is Heap Memory?

Heap Memory stores User Context when Extended Memory allocated to a work process gets exhausted and the work process requires more space to continue. Heap Memory stores contains same type of Data as Extended Memory. Heap Memory is allocated dynamically according to requirement and not during system startup. When the workprocess starts using heap area it enters in to PRIV mode.

Operation modes in SAP

Using the operation modes, you can adjust the type and distribution of the
work processes to the varying load distribution during the day. You can
also adjust the distribution of the work processes to business
requirements that only occur once. During the day the demand for dialog
work process is high an system response for dialog work process must be
fast. At night there are less users so system resources are not
utilized fully if a major percent of them is reserved for dialog work
process. By defining operation modes, you can change not only the total
number of work processes defined in the profiles, but also the type and
distribution of the individual work process types within this total
number. The switch between the work process types is performed
dynamically during the runtime of the SAP system. The switch is
triggered using a defined schedule. A reserved work process is not
immediately terminated, but marked for switching. This means that
certain delays may occur. This type change is logged in the system log.
During the switch of the operation modes, neither the instance nor the
affected work processes need to be restarted. This means that the
quality of the buffer of the SAP system is retained during an operation
mode switch ,and that the request that is currently being processed by
a work process is completed. The individual work processes retain their
process ID after the switch, which can be observed in the process
overview (SM50).You can trigger an operation mode switch from a program
that you have written yourself using a function module (RZL_PERFORM_BA_SWITCH)