Sunday 24 February 2013

Create Username in SU01 Transaction code

Previously i posted about SU01 username creation topic with less information and now i am trying to cover it in detailed

SU01 is the tcode mostly used by user administrator(SAP Security administrator) in SAP systems and this tcode used to create users, change user authorization, name, email id validity, user type add/remove roles, parameters, default settings and profiles.

Above are the mostly used changes to any username in SAP system.
Let see how to create a username in SU01 tcode(Mass username creation done using SU10 tcode)

  1. Select the appropriate system SAP GUI and click log-on button to get into the system
  2. Enter your user id and password to login corresponding SAP system
  3. Goto T-code SU01
  4. Enter username(ex.test_user) and click create icon or press F8 to create user
  5. Enter user Last and first name, user E-Mail ID in Address tab
  6. Now goto logon data tab and select the user type by default it will be dialog user(User type will see later in detail)
  7. Enter the Initial password, user group, validity and accounting number(password is mandatory and others are optional)
  8. You can use SNC tab if you wish to add SNC if its enabled in your systems
  9. Goto Defaults tab check user decimal notation, date format, time format, output device and user time zone
  10. Goto Roles tab and enter the role name if you have it already or use search option to look for roles available
  11. Goto Profiles tab to enter the profiles directly 
  12. Now recheck the all the details of User master record(SU01 screen is called UMR) and click save or press Ctrl+s

Now we successfully created a username and hope this will help you

Saturday 23 February 2013

RFC Connection setup in SAP System

RFC(Remote function call) plays a vital role in SAP systems.

Consider you have two systems namely PRD and QAS.
RFC names will be like below
PRD -PRDCLNT100
QAS -QASCLNT200

RFC connection type R/3 ABAP connections
Above naming convention is used by most of the basis administrators <SID>CLNT<Client no#>

So PRD system will use QASCLNT200 RFC connection to communication with QAS system.
Similarly QAS system will use PRDCLNT100 RFC connection to communication with PRD system.
Let us see how to setup RFC connection in PRD to QAS system which means RFC connection is done at PRD system.


  1. Login to QAS client 200
  2. Go to tcode SU01 and create a username as your wish(consider PRD2QAS)
  3. Make sure its a communication user and has valid RFC authorization or you may assign SAP_ALL and SAP_NEW profiles if you're not sure about the roles 
  4. Now login to PRD client 100 client
  5. Go to SM59 tcode and select ABAP connections
  6. Click "Create" button or press F8
  7. Enter the RFC connection name(ie.QASCLNT200) and choose connection type as 3 which means ABAP connecions
  8. Enter the description of the RFC like "RFC connection for QAS system" and save
  9. Now Enter the Target Host as system name(Computer name) of the QAS system or enter the IP address of the system and system number of QAS(like 00)
  10. All the above settings must be carried out on "Technical Settings" tab
  11. Next go to "Logon & Security" tab
  12. Enter the Client number of the QAS system i.e. 200
  13. Also enter the username and password which is created in QAS in initial stage(ex.PRD2QAS and pwd: QASED56$%)
  14. Language is optional and similarly Unicode option in Unicode tab
  15. You can select "Unicode" option if target system is Unicode system or leave it
  16. Now save the settings and you will be prompted "Connection will be used for Remote logon"
  17. Click "OK" and Click "Connection Test" or Ctrl+F3
  18. Similarly you can test Unicode connection 
  19. But importantly you need to check Authorization test Menu bar Utilities --->Test ---> Authorization Test or press Ctrl+F4 on your Keyboard
  20. All the above test must be successful and you will get result like blow
Action                      Result
Logon                 23 msec
Transfer of 0 KB         3 msec
Transfer of 10 KB 4 msec
Transfer of 20 KB 4 msec
Transfer of 30 KB 5 msec

Now we successfully configured the RFC connection between PRD to QAS system
Similarly repeat the same steps in QAS system to setup RFC connection in QAS(PRDCLNT100) to PRD

Hope this will help you

Friday 22 February 2013

How to Create a New Client in SAP

Definition:
In commercial, organizational, and technical terms, a self-contained unit in an SAP system with separate master records and its own set of tables.

Please follow the below steps to create a new client SAP.
  1. Go to tcode SCC4 which is used to maintain defined clients(T000 tables stores all these values and we can check this information in Data Browser)
  2. Click to Change mode or Ctrl+F1
  3. Now the table is changed to edit mode and you will be altered "Caution: The table is cross-client" because it's a cross client table and it will be reflected to all other clients which are available in the system if you do any changes(will see in details about client changes)
  4. Now click "OK" button 
  5. Click "New Entries" button in the top or press F5 button
  6. Now you will be asked to enter the Client number(3 digit unique) and Description
  7. Then you need to enter the following details the screen City, Logical System, standard currency, and Client role(Production, Test, Customizing, Demo, Training/Education and SAP Reference)
  8. You need to assign a logical system to this client(Will see later how to create a logical system)
  9. Once you have done all the above details click save
  10. Now you can see the new client is listed in the initial screen of the SCC4 tcode and the same value is stored in the table T000
  11. Once we done with all the above steps we should do a client copy with default client 001, existing client available in our system or from other system
  12. For client copy you need to set the profile parameter "Login/No_automatic_user_sapstar" value to 0
  13. Then only you will be able to log-in to newly create client with username SAP* and password as PASS
I will post in detail about client copy

Let me know if you have any comments or clarifications and your suggestions are most welcome

How to Avoid Filters In Transport Import Queue

The biggest headache for an SAP Basis administrator is small system settings changes which was unknowingly done by a user in our SAP system.

So like that i faced an issue in STMS_IMPORT tcode screen and i dont know who was done this changes.
There is an issue like when an a filter settings are changed in STMS import requests it will not show the TP import status or it will not appear after import of the request.
so the developer or who ever is importing a TP in the corresponding system might complain about the issue.

Please follow the below steps to avoid such a filter issue in TP


  1. Login to the corresponding system
  2. Go to STMS tcode
  3. Click Import overview or F5 
  4. You will get the list of systems select the system which you have the issue or which system we logged in for issue.
  5. Double click on it and you will be directed into STMS_IMPORT tcode screen
  6. Go to EDIT Menu
  7. Now you can see there is an option called "Delete All Filters"
  8. It will be in Dark color if there is any filter settings are present for the system
  9. Delete the filter by choosing this option and it will be changed to Gray color
  10. Now you can see all the requests are displayed in the import queue of the system without any filters
  11. The Delete all filters option will be grayed once the filters removed for the import queue
  12. You can do it in the DC(Domain controller too)

How to Make a Good Video Resume

How to make a Good Video Resume In Tamil.
Below video is about how to create a video resume from Karki a famous twitter, freelance recruiter and Blogger.


Thanks To Karki

Thursday 14 February 2013

SAP BASIS Interview Questions and Answers

Below are set of SAP Basis interview questions which is created/collected with my experience and from different web pages.

1. Where you can check system log at OS level?
Check /usr/sap/<SID>/system/logs directory or goto SAP MMC console look for "system logs" Under SID.

2. How do you check whether a system is UNICODE system or not?
Go to ->SM51 tcode and click "Release Notes" button 
or click System->Status->check UNICODE values is YES or NO under SYSTEM DATA in SAP Easy Access page or execute command "disp+work-version" at command prompt.

3. What is LUW(logical unit of work)?
A list of steps within a tcode called logical LUW.

4.What are the common transport errors?
Return code 4 --> Imported with warnings
   -Generation of program, colomns or row missing
Return code 8 --> Imported with errors
  -Syntax error
  -Program generation error
  -Dictionary activation error or method execution error
Return code 12 --> Indicates Import Cancelled
  -Program cancelled due to job
  -Import cancelled due to object missing
  -Import cancellled due to object not active
Return code 18 --> Indicates Import Cancelled
  -Due to system down while import
  -Due to user expired during import
  -Due to insufficient roles or authorization

5. How to transport users from one client to another client?
To transport users within a system(same SID) go to tcode-->SCC1 -->give source and target client -->select profile SAP_USER --> schedule in background job execution.

Note: if you want to transport from different system(SID) means we can use SCC9 or SCC8 tcode by selecting SAP_USER profile in other terms called client copy or client refresh.

6. What is "OK" code and Tcode?
OK code is used within a program to execute a function.
Tcode is "Shortcut" which helps to run a program.

7. How to check list of tcodes within a SAP system and where to look for tcode names and program values.
  -Use tcode ST11 to view table TSTC
  -Go to SE93 tcode to view or Define a tcode

8. How we can disable the "IMPORT ALL" button on STMS tcode?
Login to DC(Domain controller) STMS-->System overview -->double click on corresponding system -->go to Transport Tool tab --> add/change parameter "NO_IMPORT_ALL" set its values 1.

9. What is different between client refresh and client copy?
Copying or over writing to existing client called as client refresh.
Copying to newly created client called client copy.

10. What is the purpose of table T000?
This table contains a list of defined clients within a system where we can maintain tcode SCC4.

11. How do you create a exceptional password list?
Use USR40 table to maintain exceptional password list.

12. What is the purpose of table USR02?
USR02 table stores user logon data like usernames, encrypted password, creation date...etc

13. How can you check/tell if a transport entry is in the process of being imported?
Check table TRBAT.

Unlock DDIC and SAP* at DB level

Some time we(Basis administrator) may need to unlock or lock DDIC and SAP* at database level.

Please use the following query.


  1. Login to the corresponding DB with username and password or windows authentication if its windows system.
  2. Start a new query or use sql command prompt
  3. Update <SID> .USR02 set UFLAG ='00' where MANDT = '000' and BNAME = 'DDIC';
  4. To display all usernames in the client use the below query
  5. SELECT * FROM <SID>.USR02 where MANDT = '000';
Above procedure is applicable for SAP* too.

Sunday 10 February 2013

SAP Test System Refresh

Please follow the below steps for SAP test box refresh from production box


1. Take the relevant screenshot of system

STMS,SCC4,SM59,SAP standard jobs,DB13,SLICENSE,CCMS settings,SPAD

2. Import the SPAD settings


3. Take the offline backup of production system


4. Take the backup of backSID.log,*.aft and initSID.ora of production and test server


5. Lock users in Test system


6. Take offline backup of test system


7. Open client in test server : SCC4


8. Export the client for profile SAP_USER in test server. Keep test system as target server

SCC8


9. Take the trace of control file on both the Test and production server


10. Stop the SAP instance and sap services


11. Note down the Schema users existing presently in the system

SQL> select user name from dba_users;


12. Shutdown the database


13. Copy last offline backup log file(*.aft) from production system to test server


14. edit the *.aft log file as per test server

change SID from prdoduction to test server SID, check ORA-HOME directory

15. Now restore the backup 

brrestore –c –m full –b XXX.aft

16. Connect to oracle as sqlplus /nolog, connect /as sysdba and type startup Nomount


17. Edit the controlfile of Prod. Change all production SID to test SID and  NORESETLOGS TO RESETLOGS


17. Use the edited controlfile of Prod to recreate the control file of Test

SQL> @Cntrl.sql
SQL>shutdown immediate;

18. SQL> Alter database open RESETLOGS


19. Create new OPS$ADM  using the below command.

I:\scripts>sqlplus /nolog @ORADBUSER.sql SAPSID NT DOMAIN SID  (IF SIDADM is local user then give the host name in the place of Domain Name)

20. After this run the script sapdba_role to set proper right for OPS$ user IDs.

>sqlplus /nolog @sapdba_role.sql

21. Check whether SAPSR3P (schema owner) account has been locked or not:

select username,account_status from dba_users where username=”SAPPCE”;

22. If it is locked use this command to unlock it:

alter user SAPPCE account unlock;

23. Start the SAP application



POST Processing Steps:


24. Update the license

Logon to SAP with DDIC-client 000; update the license key through the transaction SLICENSE

25. check the consistency

Go to transaction SICK for checking the consistency of the system.

26. check the local host entry

Go to transaction SE37 and execute BPT_LOCAL_HOSTNAME_CHECK to check for the hostname entry

27. Change the STMS configuration and perform post installation activity

Now go to transaction SE06 to perform post installation activities

28. Reconfiguring STMS 


29. Login into DCE client 000 with DDIC , goto transaction STMS


30. Schedule the standard jobs


Go to transaction SM36 and click on the button “Standard jobs” to schedule the standard jobs defined for the system


31. Import the user master of test server

Goto the STMS and import the user master request

32. Close the client


33. Changing the client description. 


34. Import profiles of active Server using RZ10


35. Delete incorrect instances defined in RZ04, create correct instances and assign Operation modes for the same 


36. Change the logical system name


37. Take an OFFLINE backup of the Test system and release the system to the users