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

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


Wednesday, 30 November 2011

How to find out who are all having access to a particular tcode in SAP system?

This article answers the following queries

  •  How to find out who are all having access to a particular tcode in SAP system?
  •  How to find out which user ids are having access to a transaction in SAP system?
  • How to use SUIM tcode to identify users having access to a particular transaction in SAP system?
-----------------------------------------------------------------------------------------

In some real time scenarios, if there is an emergency like, a  change to a table to be done but particular end user doesnot have access to change the tables.  Then they may approach basis administrator/security(authorization) consultant to identify those users who are having that access so that they can request them to change the same in case of emergencies. So, you should be able to identify those users and confirm to business users.
In general, basis/authorization consultant should be able to identify all user ids who are having access to a particular tcode. This can be done in the following way.
In this example, am demonstrating how to identify all the users who are having access to SE16 in a given SAP system.
Login to the SAP system and go to transaction SUIM as shown below :




In the above screen, please navigate to user -> users by complex selection criteria -> By Transaction Authorizations (This is highlighted in the). Select that and click F8 or clock symbol (highlighted)  to execute. This results in the next screen as below :






In the above screen, type any transaction code, which you would like to find who are all the users having access for the same. In our example, it is SE16.
Once you input transaction code, click on highlighted clock button, which results in the following screen which displays the list of users who are having access for SE16 in this SAP system.








Monday, 3 October 2011

How to increase the size of a trace file in SAP?

This article answers the following queries
  • How to increase the size of a trace file in SAP?
  • What is the parameter used to increase the size of a trace file?
  • How to dynamically increase the size of a SAP parameter rstr/max_filesize_MB?
-----------------------------------------------------------------------------------------
Sometimes, it is required in SAP to increase the size of a trace file from default value so that more trace or log can be captured.  Mostly SAP requests this change to resolve an Oss message. This can be done as follows:
Login to SAP ABAP system. Go to transaction RZ11













As shown above, please provide the SAP parameter rstr/max_filesize_MB and click on display button which results in the below screen























As shown in the description, this parameter sets the maximum file size of a trace. Default value of trace file is 16MB. The maximum value is 100MB.
To view documentation related to this click on “documentation” push button.
To change the value, click on “Change Value” push button which results in following screen.






















As shown in above screen set the new value and also select “switch on all servers” checkbox if you would like to change this parameter across all the application servers of an SAP system.

However, if you would like to change this parameter in any specific application server, please make sure this checkbox is unticked.
As rstr/max_filesize_MB is a dynamic, parameter takes effect immediately without restart of the SAP system. However, the parameter lasts only till restart of the server. After restart, default value will be set again for this parameter





Enter your email address:


Delivered by FeedBurner




Friday, 30 September 2011

Transport Error – Transport Control Program tp ended with error code 0247

This article answers the following queries:
  • How to resolve the transport error “Transport Control Program tp ended with error code 0247?
  • How to resolve the transport error – Errors: addtobuffer has problems with data- and/or cofile?
  •   How to resolve transport issue  encountered while adding a transport to import queue of target       system?
--------------------------------------------------------------------------------------
Sometimes, while you are adding a transport request into import queue of target system as shown below, you might encounter error as
 “Transport Control Program tp ended with error code 0247 "?
Errors: addtobuffer has problems with data- and/or cofile? (Please refer screenshot 3)









After pressing Yes in the above screen, you may encounter below error:







Most probable reasons for this issue could be, due to transport did not get released from the source system.
Please login to the source system of the transport and goto transaction SE01 and provide the transport number as shown below and click on display pushbutton to view the release status of the transport








In the below screen, please drill down the transport and check whether all the transports under this are released ( if there is tick mark after the transport, it means it was released).
If there is no tick mark on any of the  transports below the given transport number it means the transport is not yet released. In those cases, you can even view truck symbol in the active state.







In the above screenshot, all the underlying transports were released(as there is tick mark after those transports), but the main transport is not yet released as indicated my active status of the truck. In these cases, just keep the cursor on the main transport number and click on truck symbol to release the transport.
Please note that you can release the transport only if you have access to do the same. If basis administrator do not have access, he/she should approach the respective team and get this transport released as per the process mentioned above.


Please find below another scenario, in which 2 of the 3 child requests not released. In this case, each of the individual transport to be selected and released (by clicking truck button) and finally release the main transport.








Once the main transport is released, data file and  cofiles will be generated for that transport request in the source system. Then no longer, the error mentioned above will be encountered will adding the transport request to import queue of the target system as the request was released and data and cofiles were also generated under /usr/sap/trans/data and /usr/sap/trans/cofiles directories of the system.



Related Link:






Enter your email address:


Delivered by FeedBurner






Friday, 23 September 2011

How to open Config tool ?

This article answers the following queries:

  • How to open config tool in SAP (for offline configuration) ?
  • What is the process to be followed to access config tool in SAP ?
  • How to open config tool in Microsoft windows environment?
  • How to open config tool in  Unix (AIX , HP-UX etc) environment?
---------------------------------------------------------------------------------------
Config tool is mainly used to set JVM parameters in SAP.
In this article, am covering on how to open config tool (with screenshots)  in Microsoft windows environment :
Goto respective drive and navigate as follows
usr  -> sap  ->  <SID>  -> DVEBMGS**  ->  j2ee  ->  configtool    (shown in below figure)
and double click on configtool.bat file.







This run a batch file and opens up another screen as follows and prompts you to confirm whether you want to use default DB settings.






































Click on Yes and confirm the same.
This opens up  config tool, where various parameters can be viewed/maintained





 
Procedure of opening config tool  in Unix is same as above.
i)              To be navigated to /usr/sap/<SID>/DVEBM*/J2ee/Configtool
ii)            Execute ./configtool.sh script
This opens up the config tool as above.
Note : Only difference is here, script need to be run instead of a bat file in windows.


Related Link :


Enter your email address:


Delivered by FeedBurner





Thursday, 22 September 2011

CCMS – Availability and Performance Overview in SAP

This article answers the following queries:
  • How to check system availability in SAP using RZ20?
  • What is the use of CCMS – Availability and Perform Overview ?
--------------------------------------------------------------------------------------
If your landscape is very big and contains more than 50 servers, it would be tough to manually monitor all those systems. So, it is better to get CCMS configured in Solman system and all other satellite systems that are to be monitored to be connected to that.
If in your landscape, CCMS monitoring is configured properly in Solution manager, then you can configure receipt of CCMS alerts in case of any non-availability/performance issue of any SAP system based on the thresholds set.
However, those alerts are not descriptive enough to understand the issue. To troubleshoot the issue and to figure out the exact issue, you will need to follow the below process:
Goto RZ20 transaction of Solution manager and navigate to  “SAP CCMS Monitor Templates” as shown below







































As highlighted above, please click on “Availability and Performance Overview” to proceed to below screen :




You will have 2 nodes as shown in the above figure :

  • Availability
  • GRMG-Tested Availability
Drill down in both of these nodes and figure out if any sub-node (i.e. SAP system) is in red color. It means that there is some issue with that system.
Please find screenshot below :





















We can further drill down these red systems to understand the issue in detail.























If you are able to capture SID of the affected system from the CCMS alert, then you can directly go to that respective SID in the above screen and drill that node down to figure out the issue as shown above.







Enter your email address:


Delivered by FeedBurner

How to view OSS messages based on their various criteria?

This article answers the following queries:
a)    How can we  check OSS messages   owned by us?
b)    How to check OSS messages of other users ?
c)     How to spool a report on the oss messages created between any 2 intervals?
d)    How to view all Oss messages based on their status for any given period?
e)    How to export Oss messages list to an excel?
------------------------------------------------------------------------------------

How to check Oss messages owned by us

Login to Service Market Place and navigate to  “ my Inbox” as shown below :


It displays all the customer messages that are owned by you.
(However in the example above there are no messages displayed, as I haven’t created any)

How to check Oss messages owned by others

Please select Customer Messages from the drop down of Search for (highlighted  in the above screen) and click on Go button , to proceed to the following screen


As shown in the basic search of above screen, Oss messages can be filtered and viewed based on:
  • Customer Number
  • Installation Number (based on particular system)
  • Reporter Name ( User who has created the message)
  • Status ( based on status of message)
  • Create date ( based on create date interval)
  • Changed within last days  (based on last change)
  • Priority
  • Component
  • Message Number
How to spool a report on the OSS messages created between any 2 intervals
Advanced search tab will have much more options than basis search as shown below
For example : If I have to view all Oss messages, which are in Status “In Processing by SAP” and “Customer Action” and whose priority is Very high/High/Low and messages which were created between 15.09.2011 to 22.09.2011, I can select as shown in the above screen.
After selecting all these, click on Search push button which displays all the Oss messages which meets these criteria as shown below:




Click on Down All pushbutton (highlighted) in the above screen, to download these oss messages into an excel sheet for further processing/reporting






Enter your email address:


Delivered by FeedBurner

Wednesday, 21 September 2011

How to identify various ports of an SAP system?

This article answers the following queries:

  • How to identify various ports of an SAP system?
  • What are the various protocols of an SAP system?
  • How to identify http and https ports of an SAP system?
  • How to identify telnet port of an SAP system?
  • How to identify P4 port of an SAP system?
  • How to open java stack if http(s) port is not known for an SAP system?
--------------------------------------------------------------------------
There are various protocols that are used in an SAP system. Each of these protocols is associated with a sap port. Sometimes we need to know these ports to specify in some configurations etc. These ports of an SAP system can be found out as mentioned below:
1)    Login to SAP system ABAP stack
2)    Goto SMICM transaction
It displays screen as shown below


























3)    Click the highlighted services button in the above screen, which displays the below screen




     As listed in the above screen, there will be various services running in SAP system like

  •          HTTP
  •          HTTPS
  •          P4
  •          IIOP
  •          SMTP
  •          TELNET

From the above screen, we can make out what are the various services running in that SAP system and the ports on which they are running.
Please find below interesting aspects of port numbers on how they were derived :
HTTP port is 50100 (It means 5<instance_ num>00)
HTTPS port is 50101  (It means 5<instance_num>01 )
Always HTTPS port ends with 1. It is nothing but HTTP port + 1
P4 port is 50104  ( It means 5<instance_num>04)
As the name indicates, P4 port always ends with 4
Telnet Port is 50108 ( It means 5<instance_num>08)
Most of the cases, telnet port ends with 8.

How to open java stack if http(s) port is not known for an SAP system?
In some cases, if you donot know the java link of a particular server,  you can figure out the same & open following below process :
1)    Goto SMICM and identify http(s) ports
2)    Identify hostname of the server
Then follow  the below convention to open nwa of  java stack
http://<hostname>:5<instance_num>00/nwa 
eg: http://sapserv12:50100/nwa
or
https://<hostname>:5<instance_num>01/nwa  
eg: https://sapserv12:50101/nwa


Enter your email address:


Delivered by FeedBurner





How to set the PI SOAP Adapter 7.1 components trace level to debug?

This article answers the following queries

  • How to set the PI SOAP Adapter 7.1 components trace level to debug?
  • How to change the trace level of PI SOAP Adapter 7.1?
------------------------------------------------------------------------
Sometimes, to troubleshoot an issue related to SOAP Adapter, SAP might request you to change the trace level of SOAP adapter in a PI system. This is required because much more log can be captured if trace level is set to debug.
Here is the process to perform the same in the java stack of PI system.
1)    Open  NWA of java system
Eg: https://hostname :port/nwa
2)    Navigate to  Problem Management -> Logs and Traces -> Log Configuration
3)    Select show -> tracing locations
4)    Go to Tracing location  com -> sap -> aii -> adapter -> soap
5)    Set severity of this location to Debug and click “Copy to Sub tree”
6)    Go to Tracing location com -> sap -> aii -> af -> sdk -> xi
7)    Set severity of this location to Debug and click “Copy to Sub tree”


Enter your email address:


Delivered by FeedBurner



Tuesday, 20 September 2011

How to create an Oss message

This article answers following queries :

  • How to create an Oss message in SAP?
  • What are the different priorities of tickets/message that can be created ?
  • In what cases Very high priority message to be raised?
-----------------------------------------------------------------------------
In real time scenarios, there might be situations, where local basis administrators could not resolve the issue. In those cases, a message can be raised to SAP so that SAP consultants can resolve the issue based on priority of the ticket.
Please follow below steps to raise an Oss message:
Step1:  Goto Service Market Place. Navigate to Help & Support ->  Report a Product Error




As shown in the above screen, there will be 4 steps to raise an Oss message.
They are
i)  Choose system (Select system on which issue to be reported )
ii) Prepare Solution Search (Solution search can be performed here by using 
    keywords of the issue)
iii) Find Solution (System displays some notes which are relevant to the issue. 
     If any of the notes suits your requirement, they can be reviewed and 
     applied and message creation can be deferred.
iv) Enter message ( If note of the listed notes are applicable, you can go ahead 
     and create an Oss message)

Step 2 : Please refer below screen. Please provide SID of the system regarding which you would like to report an issue and click on search button. It displays the system details.




Click on SID, which opens up the following screen.



Step 3: In the above screen, provide the keyword of the issue and conduct a search.
System displays all the notes that are relevant to this issue as shown below


Step 4: Please review the notes listed and try if you can apply any of these to resolve your issue. If none of the notes suits, you can proceed further to create a message to SAP.





















As shown in the above screen, select the Language, Component and Priority of the message.
By default English language will be selected. If you would like to change, you can do the same by selecting from the dropdown.
Afterwards, the relevant component of the SAP system for which you would like to report needs to be selected.  A click on component button, opens up screen as below from which component of the SAP system can be selected.  Please note this is very important to raise a ticket in correct component for faster resolution of issue. Otherwise, it delays because an SAP consultant will have to go through the issue and he has to in turn forward this message to correct component(In other words, to correct team – As each component will be supported by a separate expert team)































Next, priority of the message to be selected.
There are 4 types of priorities

  • Very high
  • High
  • Medium
  • Low

Depending on the priority of the issue  this  is to be selected. SAP responds to you based on the priority selected.
In case you have selected very high priority to create an Oss message, you will need to provide some extra details to SAP like Business Impact, Revenue Loss, Number of users impacted etc. In these cases, an SAP consultant will call you within 15mins to understand the issue and lowers the priority if it does not suit to Very high priority call. If they consider it as very high priority call, they start working on the issue immediately, requesting further details in case of any required.
Hence, Please note,  In case you are selecting very high priority, please make sure you have valid business reason for the same like production system is down and lots of users are unable to work and huge amount of revenue loss to the company.

Next as shown in below screen enter problem details like short text (subject of the issue) and long text (description of the issue)

















Below this, any attachments related to the issue like screenshots, dump files etc can be uploaded in the Attachments section



In Contacts & Notifications section name , email id, contact number of the reporter to be provided so that SAP can contact you in case of emergencies related to this issue.



Once all these details are provided, please click on save message push button to save the Oss message. It provides an Oss message number. Please note the same. After that, please click on send message push button which actually sends the message to SAP.
Generated Oss number can be used for further correspondence with SAP.