System, Update, Memory & Background Debugging

[Former Member]

Hi Experts,

Can anyone of you please explain me about System, Update, Memory & Background Debugging? I have gone through the earlier posts in the forum and have got a bit ot idea like:

The System Debugging function enables the user to analyze system programs, in addition to application programs.

Update debugging is used to debug the SAP standard code that gets executed while system performs update functions like during a COMMIT WORK.

Memory debugging is used to monitor the usage of memory for any memory leaks in the program.

Could anyone please give me a bit more idea like an example situation where the update debugging or memory debugging might be exactly used by an ABAPer in realtime. One of my classmates told me that, "System debugging is rarely used in situations like when there isnt anything wrong with our code but we arent getting the desired output. We do that to try look for any bug in the SAP standard code so that we can then raise an OSS notes.." Please help me with your explanations as I need this information for an interview that I have to attend shortly.

Thanks.

[Former Member]

hi

IN SAP there is no update debugging we can debug the sap standrd programs also

and t-codes also

in monitering memory is sap required memory in developement server will go for performence tuning.

in developing application we will take so many precautions to improve the performence of the program

mainly we use internal tables to store the data tempororyly

and we use that data in different dimensions this is nothing but ABAP MEMORY

to store global varibles and constants we use global repository. called SAP MEMORY........

so the performence is good when comparing other technologies

mostly we go for system tables in usage to take the data by sap created table is easiyer than ztable ... so mostly we use system tables in sap