SAP Basis/Netweaver Tutorials, Monitoring, Administration(Certification) and FAQs Headline Animator

SAP Basis/Netweaver Tutorials, Monitoring, Administration(Certification) and FAQs


Saturday, 2 June 2012

How to avoid “DEBUGGING IMPOSSIBLE” dump in ST22 of sap?


This article answers the following queries:


  • What is debugger?
  • What is debugging?
  • What is the reason for “DEBUGGING IMPOSSIBLE” dump in ST22?
  • How to avoid “DEBUGGING IMPOSSIBLE” dump in ST22 of sap?
  • What is the parameter used to increase or decrease debugged sessions in SAP?
  • Usually, in which role of sap systems, debugging can be done?
  • How many dialog work processes can be in debugging mode in SAP as per recommendation in development systems?
  • What is the reason for system performance issues, if large numbers of developers are doing debugging in an SAP system simultaneously?
  • Is it suggested to perform debugging in production systems? If not, why?
-----------------------------------------------------------------------------------------

What is debugger?
The debugger is a programming tool that can be used to execute ABAP programs line by line or section by section. With this tool, you can display data objects and check the flow logic of programs.

What is debugging?
Debugging is the process of executing ABAP programs line by line or section by section. This process will be done usually by developers to analyze the flow and issues (like performance problems etc) in the ABAP programs.

What is the reason for “DEBUGGING IMPOSSIBLE” dump in ST22?
In real time scenarios, we may see dump like “DEBUGGING IMPOSSIBLE” in ST22 transaction of SAP as part of monitoring system.  Also, developers might have complained to Basis team that they are not able to debug in SAP system and while they are trying to do debug, they are encountering “DEBUGGING IMPOSSIBLE” dump. The short text of the dump says “ABAP programs cannot be debugged currently”.


































So, it is responsibility of Basis administrator to avoid those dumps and help developers to debug in development systems.
Usually debugging will be done in development systems. It is not suggested to allow debugging in production systems as it impacts system performance because work processes that are in debugging mode cannot be used by other users.
Usually this dump occurs when the maximum number of work processes in debugging mode has already reached.

How to avoid “DEBUGGING IMPOSSIBLE” dump in ST22 of sap?

Please check the process overview (SM50 or SM66 transaction) and find out how many work processes are currently in debug mode.
The number of work processes that are available exclusively for debugging is defined by the profile parameter rdisp/wpdbug_max_no.
Please check this parameter value in a sap system and compare with the number of processes that are currently in debug mode. This dump occurs when the maximum of work processes in debugging mode has already crossed the parameter value set for rdisp/wpdbug_maxno.
So, it is suggested to increase the value of this parameter to avoid these dumps. This is dynamically switchable parameter and can be changed immediately and no need to restart SAP system for the value to take effect.

Note:  Please refer below link to understand how to increase/decrease an sap parameter value.
Details related to this parameter can be checked in Rz11 transaction which will be similar to as shown in below figure.



























However, please note setting this parameter to a very high value leads to performance issues in SAP system, as “work process multiplexing” won’t happen if debugging is being done. That is work processes that are in debugging mode cannot be used by other users.  This reduces the amount of free dialog work processes, which affects system performance.
In development systems, this parameter should be approximately half the number of dialog work processes.

Hint :
Usually, as debugging is not suggested in Production systems, the parameter value rdisp/wpdbug_max_no is set to low value. Most of the times, when a development system is refreshed with production system, the number of debug sessions will be low in the corresponding development system as those values are copied from profile parameter of a production system. So, it is responsibility of basis administrator after system refresh to cross check this parameter value and set correct value as per the recommendations in the development system to avoid these dumps.






Wednesday, 30 May 2012

How to generate SAP solution manager key for the installation or upgrade process



This article answers the following queries:


  • How to generate SAP solution manager key for the installation or upgrade process?
  • What is the process to generate solution manager key for a new installation?
  • How to generate solution manager key from SMSY transaction?
  • What is the tcode used to generate solution manager key in SAP?

---------------------------------------------------------------------------------------

In a real time scenario, a basis administrator is required to install an SAP system or upgrade an SAP system.  As of my SAP ERP 2004 ( SAP ECC 5.0), an SAP solution manager key is required for installing and upgrading SAP software.
Therefore generating SAP solution manager key is one of the most important pre-steps of an SAP installation or upgrade.

SMSY is the transaction code used to generate a solution manager key for installing a new SAP system or upgrading an SAP system.

Login to ABAP stack of solution manager system and choose SMSY transaction. It results in below screen.







































In the above screen, right click on “Product systems” tab and choose “Create New product System”. A screen similar to below will appear








































In the above screen, please provide SID of the system and select Product type from drop down list . Depending on the SAP system being installed, please select the product type like SAP ECC or SAP CRM or SAP PI etc. Also select the product version and installation number of the product from the drop down list.
Once this is done, please click on save button. This creates a new product system as shown below.

















In the above example, I have created a product system KT3, whose product version is SAP ECC 6.0.
In the above screen, please tick on the relevant products and click on save. After this, again choose SMSY transaction and navigate  to System Landscape -> Select object as shown below:

Once select object is clicked, a screen similar to below one will appear.




























I the above screen, please click on key icon ( highlighted in the above screen).This results in the below screen



































Please provide system number (i.e instance number) and message server hostname in the above screen and click on “Generate Key” pushbutton to generate the Installation/Upgrade key as shown in the above screen.
This particular key should be noted and specified in the installation or upgrade tool.








Tuesday, 29 May 2012

sap netweaver interview questions - set 7


This article covers some of the most important basis/net weaver theoretical interview questions

--------------------------------------------------------------------------------------------------
1)    What is SAP Business Suite?
Answer: The SAP Business Suite is a comprehensive integrated suite of business applications that help companies, institutions, and other organizations run their business better.
SAP Business suite consists of
v  SAP ERP
v  SAP Industry Suite
v  SAP Net weaver
SAP ERP is an application within SAP Business Suite. All the applications from the SAP Business Suite are powered by SAP Net weaver

2)    What does SAP GRC stands for?
Answer: GRC stands for Governance, Risk and Compliance

3)    What is SAP’s Release and Maintenance Strategy?
Answer: As of now, SAP follows 2 release and maintenance strategies. They are
             I) 5-1-2 release and maintenance strategy and
             ii) 7-2 release and maintenance strategy


 5-1-2 release and maintenance strategy is introduced in 2004. It means for duration of 5 years, SAP does a mainstream maintenance for a software release. Thereafter, extended maintenance is available for 1 year at an additional fee of 2%. Thereafter, extended maintenance is available for 2 years at an additional fee of 4%. Thereafter customer specific maintenance will be offered case to case basis. 


It applies to core applications based on SAP Netweaver 2004 and higher, as well for addons.



§  SAP NetWeaver 2004 and add-ons
§  SAP ERP 2004 and add-ons
§  SAP CRM 2005, SAP CRM 2007 and add-ons
§  SAP SCM 2004, SAP SCM 2005, SAP SCM 2007 and add-ons
§  SAP SRM 2004, SAP SRM 2005, SAP SRM 2007 and add-ons

7-2 maintenance strategy was introduced in 2008. It applies to new releases of core applications of SAP Business Suite as of November 2008, as well as add-ons and enhancement packages.

§  SAP ERP 6.0 and add-ons
§  SAP NetWeaver 7.0 and add-ons
§  SAP CRM 7.0 and add-ons
§  SAP SCM 7.0 and add-ons
§  SAP SRM 7.0 and add-ons

4)    How does connectivity between SAP Net weaver AS ABAP and SAP Net weaver AS Java will happen?
Answer: Connectivity between SAP Net weaver AS ABAP and SAP Net weaver AS Java will happen via SAP Java Connector (SAP JCo)

5)    What are Usage Types in SAP? Name some of the usage types in SAP?
Answer:  Usage types determine the intended purpose of an SAP system. They are structuring element for SAP software on a technical level. Usage types are realized by installing and configuring a collection of software components. Some usage types also require other usage types in the SAP system to operate.

Please find below the usage types present in SAP
ü  Application server ABAP (AS ABAP)
ü  Application server Java (AS Java)
ü  Enterprise Portal Core (EPC)
ü  Enterprise Portal (EP)
ü  Business Intelligence (BI)
ü  Business Intelligence Java components (BI Java)
ü  Development Infrastructure (DI)
ü  Mobile Infrastructure (MI)
ü  Process Integration (PI)