Documente Academic
Documente Profesional
Documente Cultură
SAP BASIS
By Surya
2
Summary:
T-CODE DESCRIPTION
SM01 Lock & Un-Lock T-codes
SM02 System Message Send
SM04 User Activities / User Overview
SM12 Monitoring Lock Entries
SM13 Monitoring Update Process
SM21 Monitoring System Logs
SM36 Background Job’s Design / Standard Background Job’s Design
SM37 Background Job’s Monitoring / Background Job’s Deletion
SM38 Background Job’s are Running or not
SM50 Work Process Overview for Individual Instances
SM51 Active Servers
SM59 Remote Function Call (RFC)
SM66 Work Process Overview for System wide (Globally(Multiple Instances))
SMLG Create Log On Load Balance
SCC1 Transport Role / Import Role
SCC3 Copy Logs / Transport Log Analysis
SCC4 Client Creation
SCC5 Client Deletion
SCC7 Client Import
SCC8 Client Export
SCC9 Remote Client Copy
SCCL Local Client Copy
BD54 Logical System Creation & Deletion
PFCG Profile Creation & Generation (Single, Derived & Composite Roles)
SE10 Releasing Request
SE37 Lock & Un-Lock Clients
SE38 Background Job’s Pause / Client Size
RZ03 Check Status of Server
RZ04 Operational Mode Creation & Deletion
RZ10 Static Parameter Creation / SAP* Enable
RZ11 Dynamic Parameter Creation
SU01 Single User Creation / Lock & Un-Lock Users
SU10 Mass User Creation (Multiple Users)
SU24 Relation b/w T-codes & Authorization Objects
SU53 Missing Authorizations
SUIM Overview of Users Data
EWZ5 Overview of Lock & Un-Lock Users
ST01 System Trace
ST05 SQL Trace
ST22 ABAP Dumps
STMS Create TMS Configuration (Transport Management System)
DICO Delete TMS Configuration
5
T-CODE DESCRIPTION
SM04 / Monitoring Application Users
AL08
SM12 Monitoring Lock Entries
SM13 Monitoring Update Process
SM21 Monitoring System Logs
SM37 Monitoring Background Job’s (Batch Job’s)
SM50 Monitoring Active Servers
SM51 Monitoring Work Process for Instance wise
SM66 Monitoring Work Process for System wide (Globally(Multiple Instances))
ST02 Monitoring Buffer Statistics (Tune Summary)
ST06 Monitoring CPU Utilization
ST22 Monitoring ABAP Dumps
SP01 Monitoring Spool Request
DB02 Monitoring DB Space
Tables:
T-CODE DESCRIPTION
T000 Client Data Stores
TST01 TEMSE Objects
TST02 TEMSE Protection Rules
TST03 TEMSE Data
6
SAP (System Application Product for Data Processing)is a Business Software Tool.
SAP is Developed ERP Software (Enterprise Resource Planet).
In 1972 Four Ex-Employees of IBM Company have started SAP.
They have Developed ABAP module which is Combination of “C++, COBAL”.
SAP Supports 24/7 by 365 Days through “service.sap.com”.
SAP is OS Independent & also it can Support any OS.
R/1 System:
R- Real Time PC-1
1- 1 Tire
Note: Presentation Layer
Here in Application
Layer Work Process
Application Layer
Are going on.
DB Layer
Drawback:
If we Lost Power in Presentation Layer we can’t able to Login
Remaining Systems.
R/2 System:
R- Real Time
2- 2 Tire
PC-2
Application Layer
PC-1
Presentation Layer
DB Layer
Drawback:
If we Lost Power in Presentation Layer we can’t able to Login
Remaining 2 Layers.
There is No Q-Mechanism.
7
Client-Server Architecture:
Tickets (Bugs/Errors)
User Id Dispatcher
Screen Interpreter
Buffer
User DB
Context Client
Application Layer:
What are the Requests comes from Presentation Layer those All Requests are
Received by Dispatcher & those Requests Insert into Dispatcher Queue in the
Form of FIFO (First In First Out).
It will Assign the Request to Available Work Process in the Form of FIFO.
Task Handler:
It Receives the Request from Dispatcher.
ABAP Interpreter:
Used for to Convert ABAP Code into SAP understandable
Language.
SQL Interpreter:
Used for to Convert SQL statements into SAP understandable
Language.
Screen Interpreter:
Used for to Convert Screens into SAP understandable
Language.
User Context:
Stores the User Information details.
Eg:
User Id, Password, Authorization, Parameters etc,.
9
Buffers:
It is nothing but Frequently Accessed Data & Rarely Modify Data.
DB Client:
Act as Informer of DB.
If the User Request is not in Buffer by using DB Layer we can Fetch
the Data .
At the Time DB Client Fetch Data from DB Layer one Copy Stores in
Buffers & another Copy Send to User.
DB Layer:
Used for Insert Data & Fetch Data Information which are Stored in
Tables in DB.
Instance:
It is nothing but R/3 Services which are Started & Stopped together.
It contains Work Process.
Eg:
OS Services, SAP Services.
2 types of Instances.
Central Instance
Dialog Instance
Based on RAM Increases Instances will be Increases.
Message Sever:
CI (00)
Dispatcher-1
WP- WP- WP-
1 2 n
Dispatcher-2
Message Sever
WP- WP- WP-
1 2 n
Dispatcher-3
WP- WP- WP-
1 2 n
Note:
Here Dispatcher Range from 00 to 99 Only.
WP- Work Process.
Used for Load Balance on Dispatchers.
It is looking for 1st Dispatcher (CI) if 1st Dispatcher Busy Message Sever Assign
the Request to 2nd Dispatcher likewise Cycle will going on.
SAP Versions:
Note:
ERP - Enterprise Resource Planning System.
SCM - Supplier Chain Management System.
SRM - Supplier Relationship Management System.
CRM - Customer Relationship Management System.
13
Startup Process:
Double Click on,
SAP MMCSelect Our ServerRight Click on ServerAll TasksStart.
Eg:
Server is, ECC, DM0 etc,.
Central Instance (CI)
OS DB
Collector
Message
ServerDispatch +
Work Process
Dialog
Instance
Stop Process:
Double Click on,
SAP MMCSelect Our ServerRight Click on ServerAll TasksStop.
Eg:
Server is, ECC, DM0 etc,.
Central Instance (CI)
OS DB
Collector
Message
ServerDispatch +
Work Process
Dialog
Instance
SAP Stopping in Real Time Procedure:
Note:
/n – For Back Page.
/o – For New Page.
14
Client Administration:
Client:
Individual Unit in the R/3 System.
Eg:
One Branch (One Client)
Data:
In SAP Command line enter the T-code as RZ10 (Static i.e,If we done
any changes then we need to Restart Server to effect the changes . )
16
Click on change
18
Click on Copy.
Click on back
One pop-up will be come
Click on Yes
22
Click on Yes
Click on Continue
25
After Restart the Server login with SAP* and the password is pass(or)
06071992
26
NOTE:
OS Level:
A) NOTE: Whenever you create New Client you should have to Login
With Default Client (Eg: 800)
SAP* user can be used when you will be create New Client
Login with Default Client-800 with the User of SAPUSER and
Password is india123 .
In SAP command line enter the T-code as SCC4
Click on Change/Display
28
Click on Continue
31
We can also run Background also with the help of Schedule as Background
Job.
Then click on Continue.
40
If you can use T-code as AL08 we can see the below col’s .
44
Note: While Login with Newly created User system will through the one pop-up
Message which is Change the Password.
A) In SAP command line enter the SU10 for Mass User Creation.
Give Multiple Users.
Click on Create.
46
Click on Lock
48
Note: If you want to Lock Client,1st you have to logion Different Client
then Lock the Client.
If you have already gave the Remote Connection then you can’t able
to Un-Lock.
52
Now Check the Authorization Check box & then click on Trace On tab
Now In SAP command line enter the ST01 & then click on Trace Off tab
56
Click on Analysis
57
Here Change the TO Col Time as System Time & then Click on Start Reporting
Now Open one New Session, In that SAP command line enter the T-code as PFCG
Select Role as below & then click on Change Icon
Here we need to enter System Time to the End Time & click on Enter
67
If SWAPS Col having any Red color values Double Click on that.
69
Now Note it down the Profile Parameter and Value in above mentioned screenshot.
70
Check the Check box of Delete Entry from T000 and Start Immediately or
Delete Background.
For Checking Status of Local Client Copy Log, We have to using the
T-code as SCC3
Pre-Requirements:
We have to check whether User was existing or not for which we are
going to assign Role.
In SAP command line enter the T-code as PFCG
Here fill all the fields as per below screenshots and Save it.
Click on Profile Name Browser then data will be automatically fetched and Save it.
79
Click on Last Circle Symbol of Single Role in above screenshot i.e Missing Values.
Then click on Execute.
80
Now all the fields will be come into Green color then Save it.
Pre-Requirements:
One Parent Role & another one Child Role
Eg: Parent Role rakhi_single_role
T-codes SU01, SCC4
Child Role teja_single_role
T-codes SCC5, SCC3
Click on Menu tab and Enter the Derived from Role then Save it.
Here one Link was enable i.e, Delete Inheritance Relationship
86
Click on Authorizations
Composite Role:
Pre-Requisites:
Click on Roles tab & fill the Role’s as below then Save it.
90
Fill the details as below & then click on Save and Logon
Click on last circle symbol of Single Role to change the Yellow color to Green color
Save it and Generate.
99
User Window:
Now Expand Authorization Object & Copy the Highlighted Authorization Object.
101
Now one screen will be open in that past the Authorization Object.
Then again go to User Window Copy the T-code.
Then again go to SAP Consultancy Window Click on Empty T-code
area & then one screen will be open in that past the Copied T-code.
Now all the Circle Symbol’s will be Convert as Green color.
Save it and Generate.
NOTE:
Pre-Requirements:
Roles:
Profiles:
Step:1 Create Central & Child Clients and Users with Roles & Profiles:
Profiles are,
SAP_NEW
SAP_ALL (Optional)
Here we can use T-codes are, BD54 (For Creating), SCC4 (For Checking).
001- DEVCLNT001
800- T90CLNT090
Click on Save.
In below Screenshot if you have any Red color Symbol we need to follow few Steps.
107
Step:5
Create CUA & Distribution Model in Source Client.
In SAP command line enter T-code as SCUM & as per our requirement we can change
the Radiant button.
110
Assign the Job Name as below & according our Requirement we can
Change the Job Class.
Then click on Step Icon or hit the enter.
121
Schedule:
Background Job was Defined but not Assign Start condition.
Released:
Background Job was Defined with Start condition.
Ready:
Background Job was Defined & Waiting for Process.
Active:
Background Job was Defined & Processing.
Finished:
Background Job was Defined & Successfully Completed.
Cancelled:
Background Job was Defined & Cancelled due to Errors.
Note:
If you enter T-code as SM36 Background Jobs Automatically Running.
127
Default Profile:
Startup Profile:
It is used to Start DB, Message Server, Dispatcher & Work process (App.Server)
Naming Convention, START_INSTANCE NAME_HOST NAME
Eg: START_DVEBMGS01_SAPSERVER
It contains Instance Specific Profile Data & the Changes will be effect
within Instance only.
Naming Convention is, SID_INSTANCE NAME_HOST NAME
Eg: DM0_DVEBMGS01_SAPSERVER
T-code as RZ10:
It is Static. We need to Restart the SAP Server to Effect the
Changes.
Few Static Parameters,
RDISP/WP_NO_DIA
RDISP/WP_NO_BTC etc,.
T-code as RZ11:
It is Dynamic. We no need to Restart the SAP Server to
Effect the Changes.
Few Dynamic Parameters,
RDISP/MAX_WPRUN_TIME
RDISP/TRACE
RDISP/MAX_PRIV_TIME etc,.
Note:
We can Change the Work Process (DIA & BTC) no’s.
129
Note:
If Operational Modes are already Existing in Instance, 1st we have to Delete those
Operational Modes.
Click on Change.
131
Now Double click on Start Time & End Time as per our requirement.
Click on Change.
Now Double Click on Time of Start (Operational Mode). Now Color will be Change to
Black Color.
Eg: 08:00am to 08:00pm (Day Shift)
Click on Assign
Now again Double Click on Time of Start (Operational Mode). Now Color will be
Change to Black Color.
Eg: 08:00pm to 08:00am (Night Shift)
137
Click on Assign
Click on Yes
Here we can Change the Dialog Work Process & Background Work Process.
142
Click on Execute.
148
Click TEMSE Data Storage, Consistency Check, & then Delete all.
149
Here we can see the Today Errors, Yesterday Errors & also we can see the Back
Month Errors.
If you click on Particular Error you will get Explanation of Error.
Physical Memory:
Memory Configured in System (RAM)
Virtual Memory:
Memory that is configured Physical Memory & Some Part of
the Hard disk.
Note:
For SAP Installation we need to assign 3 Times of
Physical Memory.
Shared Memory:
Memory that is used by SAP App & OS App
Extended Memory:
Memory that is used by SAP All Work Process.
Local Memory:
Memory that is used by SAP 1 Work Process only.
Heap Memory:
Memory that is Exactly (Totally) used by Private Memory.
Note:
Whenever we find out Work Process in Private (PRIV) Mode no one
Can Access SAP.
Q.48) What is Transport Management System (TMS) & How to Delete It?
A)
Used to Transport Data from One System to Another System.
TMS Configuration should be Done in 000 Client.
Domain Controller:
Transport Group:
Transport Route:
2 Types.
Consolidation Route:
Route b/w Development System & Quality System.
Delivery Route:
Route b/w Quality System & Production System.
Change Request:
Whenever we Create the Request.
Transport Request:
Whenever we Release Change Request.
Trans
Bin:
It Consist of Domain Configuration Files & Transport Profile
Parameter.
TP_DOMAIN.<SID>.PFL, DOMAIN.CFG
Buffer:
It Contains Transport Request Ready to Import.
(2 Transport Request).
Co files:
It Contains Control Information of Transport Request.
It Starts with “K”.
Data Files:
It Contains Data Information of Transport Request.
It Start with “R”.
Log Files:
This is used to Store the Log Files during the Change Request.
SAP Names:
Who are Change the Request those User Names Stored
Here.
Written Codes:
0Import with Successfully.
4Import with Warnings.
8Some Objects are not Transformed.
12Critical Transport Errors.
Note:
Deleting Existing TMS in both SAP level & OS level.
Double Click on all the Folders one by one & then Delete all.
157
In SAP command line enter the T-code as DICO & then Delete it.
158
Click on Change
169
Click on Continue.
Click on Save.
172
Q.50) How to Transport Role from one Client to another Client in Different
System?
A) Logged on Source Client.
Eg: 800
In SAP command line enter the T-code as PFCG.
Assign Existing Role as.
Eg: z:rakesh_single_role
Click on Display
Fill the details as below & Click on Start Immediately or Schedule as Background.
180
Click on Continue
For Checking Client Export Copy we need to logged in any Client & give the
T-code as SCC3 for Client Copy/Transport Analysis.
182
Click on Yes
188
Click on Enter
Click on Continue.
191
.
192