How to increase trace file size in SAP?

How to increase trace file size in SAP?

  

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

     o    What is the parameter used to increase the size of a trace file?

     o    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 unchecked.

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

How to create RFC connection?

How to create RFC connection


This procedure should allow the Basis team to create a RFC connection in any SAP server.

1. Logon to SAP server

2. Use Transaction Code SM59

3. On SM59 screen click on “Create” button

4. On the new screen, give RFC destination name – Name by which the connection would be identified

5. Give Connection Type ( 3 for any SAP to SAP communication ) F4 Help will list down all possible types    
     of connections.

6. Give Description for the RFC Connection – Generally the purpose of the connection is mentioned here.

7. Click on SAVE

8. Give IP address/Host name and system number for destination server in Technical  Settings tab.

9. Click on SAVE

10. Use “Test Connection” to check RFC.

11. If Trusted RFC connection is required, give user credentials in “Logon/Security” tab.

Tips and Tricks

Tips and Tricks

This space is for those bits of information that can save you a lot of time and trouble and usually are hard to find in the documentation.

1. Problems with username/passwords while setting JCO's?... try with the password in UPPERCASE.

2. Going home in a hurry? Use transaction /nex to close all your sessions at the same time in    specific 

     application server you are logged-in       

3. In an R/3 screen, use %pc to download any Tcode full page in any format you want.(.htm, .txt etc). Also

    use Tcode /nSO21 to specify the default download location (this is very useful as saving all files to the 

    sapworkdir can be little annoying at times) 

   

4. Show Work Process usage over time by running SM50 -> List -> CPU. This shows CPU usage in 

    minutes since startup. If all of your DIA WP's show time, then consider adding more.

5. If you want to select text on your SAP screen and if you are not able to do it. Use Ctrl+Y and then you 

    can select text. 

6. To access history of Tcodes used, click on the Tcode command field and use UP and DOWN arrow 

     keys.

7. To display the checked object when not authorized call transaction SU53. It reports the last objects

     verified and also the respective values. Incase missing authorization through pop-up then close it (click 

     cross mark) instead of continue it. Then run SU53 immediately either in same session (/nSU53) or in new

     session (/oSU53). 

8. Use ctrl+? To go to the Tcode command field on SAP screen.

9. Enter /i on Tcode field to delete the current session.

10. Enter /nend to cancel all SAP sessions and log off.

11. Use ALT+F+W and ALT+F+U in SAP Easy Access Screen to download and upload the user

       favorites within/across systems.   

      

12. To send a SAP message to another person use Function Module TH_POPUP from transaction SE37.

13. Ctrl & + to open new SAP session

14. ctrl+shift+F8 System Administration information.

15. ctrl+shift+F8 Manual entry of Transaction Code.

16. ctrl+shift+F5 Create folder in Favorite list.

17. ctrl+shift+F7 Add additional object

18. ctrl+shift+F12 Direct go to Role maintenance

19. Change application server in SM51 by double clicking on application server you want to get in.

20. ALT + F12 Calls the menu pop up for Customizing of local layout.

21. CTRL + Shift + P Makes a Hard copy which shows no menu pop up and can also contain status texts 

      and modal pop ups.

22. CTRL + / Cursor jumps directly to the OK-Code field.

23. CTRL + I Cursor jumps to the first focusable field or control.

24. CTRL + ; Creates Sap shortcut.

The Difference between SAP_ALL and SAP_NEW profiles

The Difference between SAP_ALL and SAP_NEW profiles

Most of the times you might have question in your mind that why you give sap_all and sap_new every time we create admin user (Although some people used to give sap_all to everyone).So here i am sharing my knowledge about difference between these 2:

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.


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 except where necessary, in a controlled manner with all proper approvals from the customer. 

How to "kill" a work process

How to "kill" a work process

    Stopping Run-Away or “Bad” Work Processes

1. Log on to any client in the appropriate SAP system.

2. Go to transaction SM50.

3. On the Process Overview screen, find the process which must be stopped. Place a √ in the  □ to     the left of the process number to be stopped by pressing Space. On the top-most menu bar, click the Process → Cancel without core.

4. Click the blue arrow circle picture-icon to refresh the Process Overview screen until the stopped process has cleared from the display.

5. You may now leave the SM50 transaction.

If this does not kill the process, 

you can go to transaction SM04 and kill the user’s session. 

If this does not kill the process, 

you can log on to the server, open a Task Manager session, and End the Process. 

If this does not kill the session, there is an executable in the RUN directory on the server called sapntkill.exe. Run it providing the process ID number. If none of the above work, you have no choice but to “bounce” the SAP instance and or possibly the server.

Basic Understanding Regarding to Spool

Basic Understanding Regarding to Spool

Explain on Local Printing, Remote Printing and Front End Printing.

Concept of logical server and SAPLPD.

Tcode: SPAD

 Local Printing means that your spool server (R/3) and print manager (OS) are running on the same machine and the printer is connected locally or via network connection to the Print manager (OS).

Access Method for local printing:

C: Direct operating system call - for windows

L: connect locally via lp/lpr with signal - for UNIX

Remote Printing means that your spool server (R/3) and print manager (OS) are running on different machine and the printer may be connected locally or via network connection to the print manager (OS).

Access Method for Remote printing :

U: Print on LPDHOST via berkeley protocol - for windows and unix

S: Print on LPDHOST via SAP protocol - for windows

Front end printing means that printer is connected to the front end system. There is no need to define the printer on the SAP system.

Access method for front end printing:

F: Print on front end (locally) via SAPLPD

Logical Server is mapped to the physical server or another logical server. These servers are used for load balancing purpose.

SAPLPD daemon is an interface between Spool server (R/3) and Print Manager (OS). When using the access method U,S and F this daemon program should be running on the print manager (OS) (in case of U,S) and on the front end system (in case of F). 

SAP Solution Manager - SMSY

SAP Solution Manager - SMSY       

1. A user who has been assigned a profile SAP_ALL can work with SMSY?    (A)

           A.     True

           B.      False

2. T-code SMSY works on ECC systems as well? (A)

           A.     False        

           B.    True

3. Blue print configuration is done in? (B)

           A.      SOLUTION_MANAGER   

           B.       SOLAR02 

           C.     DSWP

           D.     SOLAR01

  

4. To generate Solution Manager key, we need to provide? (A,B & C)

           A.     Message server 

           B.     SID 

             C.     SNo 

           D.    SAP router string

5. Which of the following can be done using t-code SMSY alone? (D)

           A.     Transport change requests     

           B.     Client copy

           C.     Creating a new project

           D.     Creating a new logical component 

                

 6. The name of the server created in the video demo is? (B)

           A.     UWIN-Pro  

           B.      UWIN Pro 

           C.     UWI

           D.     UWINPro  

  

7. Non-SAP servers can be added using SMSY? (B)

          A.     False

            B.     True 

        

8. Which of the following can be created with assistant? (B)

           A.    Logical components       

           B.     Product systems        

           C.    Databases

           D.    Servers    

  

9. To create a project, which of the following t-code is used? (C)

           A.     PROJECT-ADMIN 

           B.     SOLAR01

           C.      SOLAR_PROJECT_ADMIN

           D.     SOLAR02   

10. The following can be created with SMSY? (A,C & D)  

           A.     Product systems        

           B.      Message server

           C.     Databases

           D.     Servers