Sap Basis
ERP Enterprise Resource Planning
3.1H Older Version
4.6 C
4.7 E (Present Version) 620
ECC (Latest Version)
There is no Database in SAP R/3.It is linked to any of the data base like SQL, ORACLE etc
ARCHITECTURE( Chapter2 )
DVEMBGS
DàDialog Work process
VàVerbose( Update Workprocess)
Eà Enque
Mà Message Service
BàBackground Work Process
Gà Gateway Service
SàSpool
Dialog Work process: To interact with SAP, users session of login of users (for band Work process) Minimum 2 work process Max Depends on H/W compatibility.
Verbose (Update Work process): There are two types of Update Work process
1 .Asynronous updates (Non Time Critical) Default in SAP R/3
2 .Synchronous update (Time Critical)
Updating Database Minimim 1 updates.
Enque: Lock Mechanism It is lock for the table by the user .If one user is updating one table then other user can not access the particular table as it will be locked by the user using it.The lock will be automatically released once the work is done from the existing user who is using it.
Message Server: Communication between Application Servicesand load balancing is done from the message server.
Central Instance: When message server is resides is called the central instance
Dialog Instance: When ordinary instance is running on other Application servers with out Message Server is called dialog Instance.
Background Work process (BTC): For long running jobs like backup etc this process will come to the picture. While specifying it self we can use BTC option for the job process.
Gateway: Communication between the different R/3 system in the network.
Spool: Printing the SAP jobs in the network.
Layers Used in SAP are
1 Presentation Layer
Dispatcher (Assigns Work process to users Request)
2 Application Layer
3 Databases.
Dispatcher it stores the dispatcher queues to check with the permissions assigned to the users who is trying to access the Database.
Dispatcher first checks with the Task Handler then with ABAP Process, Database interface and then with SQL related this is called role in
What is Central Instance, Role in Role Out?
What is the function of Dispatcher?
Who will communicate between Application Server?
Sap on Solaris.
A user by default called Sid adm is created while installing the SAP server he is the super user of the SAP Basis,
To start SAP on UNIX platforms
1 start SAP R3à only Sap will start.
2 Start SAP DBà Only DB will Start
3 Start SAP AllàSAP+DB
To Stop SAP on UNIX platforms.
1 Stop SAP R3
2 Stop DB
3 Stop SAP ALL
To check the SAP Service is running or not is
Ps –ef grep SAP
To start a database Listener of Oracle to be started.
Login as
Su – orasid
Lsnrctl start
Exit
Then log in to
Su – sidadm
Start SAP R3
Ps –ef grep ora (to check the oracle services) to check the instances in the SAP we use dpmon instance name.
Profile Management (RZ10)( Pg No 96)
The default path of the profile is usr\sap\sid\sys\profile
Start Profile: It will start SAPR3 services in OS .The file existing is start_DEVMBGS00_sid
Default Profile: It contains common settings for R3 system like message server name, gateway services. The file that contains this profile is default_PFl
Instance Profile: It contains the parameter which is existing in the particular instance. The file that contains this profile is sid_DVEMBGS00_sid
Only one default profile exists in the R3 system. If any stand by system is also available.
Editing Profiles:-
1 By using RZ10
2 By using the VI editor command like vi
3 SAP pad utility.
We need to import the profiles from OS level SAP level by using RZ10
RZ10 Utilities Import Profiles Of active Servers
Modifying of Profiles
Editing profiles is having 3 modes
1 Administration data
2Basic Maintenance
3External Maintenance
Administration data: - In administration data the path of profile, last modified, modified on which date, profile activated by which user
Basic Maintenance: Update server name, gateway
Extended maintenance: To add any parameters
To increase the dialog work process, need to change the parameter
Parameter Parameter Value
Rdisp/wp_no_dia 5 to 6
Rdisp/wp_n0_btc 2
Reports are run on SE38
Rsparam àto display the parameters available in SAP R3 àExecuted
Rspfpar
To add a new parameter
RZ10à Select the profile which needs to be modified à Extended Malignance àand click on change
Click on create button parameter
Mention the parameter name
Parameter value
Click on copy
Click on Back
Save the changes
Back
Save change
Activate the profiles
1 What ever modifications we do by using RZ10 we need to restart the SAP server
2 Version number is the number which will change according to the modifications made on the profile.
3 The parameter value of the instance profile overwrites default profile value.
4 If any changes are made in R3 server the changes must be made on standby server.
RZ 11 Maintain profile Parameter.
Parameter Name display.
Monitoring Tcodes (Daily System Check)
SM 50 àWork process overview
SM51 à Sap server
SM 66 à Global work process Services
SM21 à System logs
/n à To display the new sessions
/o à To open a new sessions with out closing present application.
SM 37 à To monitor the background jobs
SM36 à To create the background jobs
ST22à ABAP dump analysis
SM 12à Lock entries
SM13 à Updates
DB 02à Table and Indexes ( Database Performance)
ST 02 à Tune Buffers
ST 03 àWorkload analysis
ST04 à.Database performance monitor
ST06àOperating System monitor.
OPERATION MODES (RZ04) (403)
Redistribution the work process among the instances, dynamically. We can distribute the peak and off peak
Advantages:-
1 zero down time
2 Buffers will not be refreshed, performance will not be affected
3 If any work process is busy, it will not affect the work process. Once the job is completed it will shift to other mode of operations.
Tcodes .
RZ04à Operation Modes
SM63 àTime Table
RZ03à Control Panel
By default dummy (Operation Mode) will be existing.
1>Creating Operations Mode
RZ04
Click on Create button
Operation Mode Day
Short Description
Click on Save
2>Assigning Work process to operation modes
Click on instance operation mode
Click create new instances button
Mention host name
System number
Select start profile
Select Instance Profile
Click on Save.
3>Assign Operation Modes to Time Table
SM 36 (Time Table)
Operation mode set
Select Normal Operations (24 Hours)
Click on change
Double click on time interval (Select the time intervals from which the operations must be started.)
Click on assign
Select operation mode
Save
In SM21 we can see the job changes on operation mode switching.
Total Number of work process will be the same. Variation of the dialog and background process can be changed according to the peak and off-peak hours.
We cannot edit the spool work process
How to change operations mode manually.
RZ03
Control
Switch to operation modes
Select Servers
Yes to save
To check all the servers in the Network
Is RZ03
In SM 51 we can see only the active servers
SM13 to check weather updates is active or not
SM 13
Administration
SM12
List the locks
Select particular user
Lock entry
Delete (If more than 2 days then we can delete)
ST22 (ABAP Dump Analysis)
RZ10
If we get run time error in SAP we need to change the parameter value
Rdisp/max_wprun_time
Default = 300 seconds.
Background Jobs(SM 36) (446)
SM 36 To define the Background Jobs
SM37 To monitor Background jobs
SE38 ABAP editor
There are 3 types of Background jobs
1 ABAP Programme
2 External Programme àOS Programme
3 External Commands à OS Commands
There are 3 job classes
a. High Priority
b. Middle Priority
c. Low priority (Default)
Exec Target: - If nothing is monitored then it will occupy which ever are free instances.
If we mention any target server for particular Background job that job will be bounded for that particular application server.
If application server goes down. It will wait until it comes up.
A batch user should be provided in the user name
S_BTCH_ADM à Admin for batch jobs
S_BTCH_NAMà Specifying the user name
S_BTCH_JOBà Authorization to run the batch jobs
Start Conditions.
Immediate: - It will run batch jobs immediately
Date/Time:-Specify the date/Time to run the Batch Jobs
After Job: - Dependent on other job which should be run
After Event:-
At Operation Mode:-
Job Status
1 Schedule,
2, Release
3, Ready
4, Active,
5, Finished
6, Cancelled.
Schedule: The step of the background job is saved. No start condition.
Released: The step is saved with start condition
Ready: The start time has reached and waiting for resources.
Active: The process is being running
Finished: Completed successfully.
Cancelled: Terminated with errors
1 Rerun the old batch jobs
2 Start from failure steps
Reasons to fail the batch jobs
1 User is not having the authorization to run the batch jobs.
2Varient does not exist
3 Duplicate records existing in the database
4 Resources are not available
5. Application server is down
6 If it’s in the loop of ABAP programme the batch jobs keep on active status.
7 To analyze the ABAP programme we can put active job in capture mode.
Job Capture
Capturing jobs is only for ABAP programmes not for external commands or external programme.
To cancel the active job we need to go to job details there we get the pid and application securename.Then we go to SM51 and double click on the application server and cancel the process by selecting the pid.
BTCTRn(delta)1
SE38 àbtctrns1 Scheduled to upgrade (This will hold the released jobs)
SE38 àbtctrns2 Rescheduled to upgrade (This will release the hold jobs)
Were we can see all standard jobs
SM36
RSBtcdel
Practical
1> SM36
Job Name àStart with Z or Y
Job ClassàA or B or c (Default) Low priority
Status àSchedule
Exec Target àTarget Server (Not mandatory it will run on any free application server)
Step
2>Click on ABAP Programme
Name àABAP Programme name (like RSBTCdel)
Variant àCan select the ABAP Programme
Check
Save
3>Start Condition
Immediate (It will start immediately)
Date/Time (To specify the date)
Scheduled Start
Start Afterwards
Period Values
Hourly
Daily
Weekly
Monthly
Other Period
Save.
To Monitor (SM37) Batch Jobs
Job Name(*)
User name(*)
Job status
Scheduled, Released, Ready, Active, Finished, Cancelled
Select the step and click on job change to edit to immediate.
SPOOL ADMINISTRATION (SPAD) (471)
To start with command prompt
D:\usr\sap\sid\sys\exe\run
Starts OS name : NA: sap dia host:
Document
:
\/
Administration data Temse (Temporary Sequential)
:
\/
0/P RequestsàR3 Spool ServeràOS Spoolàprinteràdocument
When in R3 application server is configured for running at least one spool w/p is called spool server .Spool server consists of two parts
1) Administrative data (origin, data, author name)
2) The data to be printed (Temse (spool data))
Rspol/store_location : (db) Temse can be stored inside the R3 database or at file system level by (G)
Default is db or G(global) by selecting globally
/usr/sap/sid/sys/global: in the OS level the spool job is saved.
The preparation of spool request for printing is an o/p request .Which printer understands. It is given to the R3 spool server from this the data is shifted to the OS spooler from this it will be given to the print queue.
Types of Printing:-
1)Local Printing 2)Remote Printing 3)Front end printing
1) Local Printing:-If the spool server and the OS spooler on in the same system it is called the local printing.
2) Remote Printing:-If the spool server and the OS spooler are in different system
3) Front end Printing:- The printing with the SAP GUI
Tcode for printing
SPAD
Output Devices::- The logical printer name at SAP level
Short Name:-The name the system user to access the printer
Device Type:-Type of printer
Spool Server:-Application server with at least single spool work process
Host Printer:-The name of the printer defined at OS level
Host Name:-OS level system name.
Configured Printer in SAP level:-
SPAD
Click on output device
Click on change
Click on create
Select server type
Select spool server
Select Device class
Model
Location.
Go To Access Methods:
It is communication between OS spooler and real server for local printing L
C (NT)
Local
L (UNIX)
S (NT)
Remote
U (UNIX)
(NT)
Front end F
(UNIX)
Double Click on spool server
Logical Server:
Logical server is mapped directly or indirectly to the real spool server
Advantages:
1) Spool server switch over
2) Load balancing
To Monitor Spool Jobs
Tcode
SP01:-Spool request searching tool
SP02:-Displays all spool request.
Status:-
- : No o/p request for spool request
Proc : Spool w/p is processing the corresponding o/p request
Waiting : A spool work process is waiting for a written code from the OS spool
Compl : Completed successfully
Err : Error in Printing
Trouble shooting Printer:
1)Ping the printer
2) Fire the test print from SAP
Lpstart –a
Eg :-lpstart –a zgam
Lpstart –o zgam (Will get the print jobs are accessing)
Hpnadmin (ip address of printer)
Rsp0041:- To delete the old spool requests
SM36 (All standard jobs)
Sp12 Temse :- Administration of temporary sequential data
SP11 Temse :- Temse request screen
TST01 TST03 (When db is selected the spool jobs are saved in TST01,TST03)
TST01 :- Temse Objects
TST03:-Temse data
TST02:-Temse Protection rules.
Client Directory
Usr
Sap
Trans (SID)
Bin
Data DVEMBGS SYS
Cofiles Work exe global profile
Log Log run
Buffer KernalDirectories
Etc
Client Administration (364)
(000)
(001) Default Profiles
(066)
000 àMaster Clients
001àcopy of 000
066 àEarly watches which is used by the SAP Organization to monitor
Client Data Categorization
Custom data User Application data User data
Client Tools
1 Local client copy 2. Remote client copy 3.Client import/Export copy.
Local Client Copy: Creating a brand new user in the same R3 server and copying 000 to the new user.
Remote Client copy: It is used to copy the client from one R3 server to other R3 Server by using the RFC
(Network)
Client import/export copy: It is used to copy the client from one R3 server to the other R3 server, were as a dump is created in the OS level and can be exported to many R3 servers at a time.
Tcodes for client creation
SCC4: To create the client
SCCL: Local client copy
SCC9: Remote client copy
SCC8: Client export
SCC7: Client post import
SCC5: To delete the client
SCC3: Client logs
SM02: To sent system messages
SE06: Post installation Actions for Transport Organizer.
Local
Creating a brand new user in the same R3 server and copying 000 to new user.
Local Client Copy
1 Create client by using scc4 (In the target system)
2 Log on to the target client with the user
Sap*/pass(Password)
3 Run the Tcode SCCL (SCC9 for Remote Client copy)
4 Select the profile
5 Select the source client (in remote client copy select the remote server)
6 Before copying run the test run
7 Schedule as background
Remote Client Copy
1 In remote client copy the data is transformed directly b/w the source and target client using RFC s(Remote Function Call) in n/w connection
2 Single step Process
Export:
In client transport data is exported file at OS level (Trans/data).At some further time the client is imported from the file system to the target system by using the management system.
2 Two step process
Important Points
1 R3 repositry objects such as ABAP programme are not transported with the client copy
2 Development objects can only be transported using change request
3system messages to be passed to clients from SM02 beford copying client.
4The space on the system should be checked.
5If the client copy is terminated abnormally we can re execute the same copy process. The system allows you to restart the copy at the point were it was terminated previously.
6 The client copy programes use the client copy control flow table i.e ccc flow
To lock the particular sid
Tp locksys pf : tp profile (Path of configuration profile)
Tp unlock sys pf: tp profile (path of configuration profile)
Changes and Transports for client-specific objects
1 Changes with out automatic recording:-with this option customizing changes allowed but the changes will not be recorded in the transport request.
Eg: we can set it as SAN box client
2Automatic recording of changes
Changes to customizing data are automatically recorded in the transport request
Eg :Development
3No Changes Allowed:
We cannot do any changes allowed
Eg: Production system.
4No Transport allowed:
We can modify the data but we cannot transport
Eg:Training system
Restrictions
For Import Export
1 SCC4
To create the client in the target
SCC8 (To export the client copy)
SCC7 ( To import the Client copy)
SCC9(To Remote Client copy)
What is the difference between T000 and SCC4
In T000 the structure will be deleated but the data will be existing
If we use SCC5 the structure and the data will be completely deleated.
SECURITY (SU01) (309)
Security
User creation User deletion user Modify Roles Profiles
User Administration
000)
001) Three Default Clients
066)
Ddic) Default Users
Sap*)
000) user àddic
001) Passà19920706
000) user àsap*
001) Passà06071992
066) user àEarly watch
Passàsupport
Users are client dependent
SU01:- To create the user address, logon data, defaults, Parameters, Roles, Profiles, Groups
SU01
User Name
Click on create
Adress Title
Last Name
Logon data : password
User group
User type Dialouge(Dialouge users will be default users)
Communication (In RFC usage)
System(Background jobs)
Service
Reference (Template were we can copy)
Defaults: Start menu
O/p device
A user can change the password once in a day
But administrator can change the password any number of times.
For creating bulk users SU10
Client Refresh
We will deleate the sap* from the target client we will exit form the user and we can log in to the sap*/pass
ROLES (PCFG)
1 Creation of roles
2 Assigning to users.
Roles
1 Single Roles 2 Composite Roles 3 Derived Roles
Single Role
Authorizations Class
Authorization Objects
Authorizations
Fields
Field Values
Single Role: (default Role) :-A role which contains the authorization objects like tcode permission etc
PFCG
1 Description: - (Description of the role)
2 Menu àAssigning Transaction codes.
3 Authentications
4 Users
Menu Transaction
Assign transaction which user can access
2 Reports:-To run the report which is added in the authorizations
3 Other:-Adding the web address which user can access directly from the SAP.
Red Mark Red :- Organization levels are not maintained
Yellow:-Field values are partially maintained
Green:-All are maintained properly
We can import the following in the Authentications:
1 From SAP menu
2 From other Role which is already created
3 From area menu
4 Import from file.
Composite Roles:- In which two or more roles are added and create a new role. In this derived role we can compare the authorizations assigned to the roles in the compositerole.
Derived Roles:- It will inherite the parent role permissions, except organization level.
Composite Roles:-
Description
Roles
Menu
User
Personalization
Authorizations are not mentioned in composite role. We need to maintain in the individual roles which are maintained in the single role.
We cannot assign composite role to composite role.
Activity Groups are called roles in the newer version.
Transport:
To transport the derived role the system also transports all roles from which this role is derived .To avoid the inconsistency in the target system.
Upload:- When loads uploading all role data (including the authorization data) is uploaded from a file in to the R/3 system. The user assignment for the role and the generated profiles for the role are not uploaded.
This means authorization profiles must be regenerated after the upload.
Transport:-When roles are transported the associated authorization profiles and transported as well,but we need to perform user master comparision for all imported roles, after completing the import in to the target system.
PFCG
Role.
/nsupc:- To mass generation of profiles,
/npfud:-Mass user comparision.
/nsuim:-User information system.
For single role creation
PFCG
Click on create role
Description (Give description)
Menu
Click on Transaction (To add Tcodes to the roles)
(From Sap Menu; From Other etc)
Click on authorization
Click on change authorizations data
(Need to maintain the authorization)
Make all the fields green
Click on save
Click on generate (To generate the profiles)
Click on back
Click on users (add the users accordingly)
Click on user comparison
Click on complete comparison.
(It will adjust the user master record)
Click on save
Change authorization data:-It will not show the authorization roles on fields.
Expert mode for profile generation:
It will show the authorization roles on fields.
To do manually
Profiles
SU02 àCreation of profiles
SU03àObject class
SU24/SU22àMaintain Assignment of authorization objects of transactions
Transactions Give the tcode
Click on execute
Click on check indicator
Eg S- Data set
S-Develop Which are checked and maintained
S-Programme
SU03àInformation System
SUIM
Click on authorization objects
Click on by object name,text
Give the authorization object eg like s_dataset
Click on execute
SU03
Select the object class
Double click on object class
Double click on object eg:- Dataset
Click on create
Give Authorization name
Check mark
To maintain field value
Double click on fields and select field
Click on save
Click on activate button twice
Su02
Click on generate work area
Click on create button
Give the profile name
Select the profile type
Click on save
Give the authorization object
Press enter
Add authorizations to the authorization tab
Click on save
Click on activate twice
SU01
Click on profile tab
Select the profile
And click on save
Steps to Create Manually the Roles
We need to check the authorization objects for the particular tcode (SE38)
Need to find out the object classes for this authorization objects (SUIM or SU03)
Need to create the Authorization
Create the profile
Arranging this authorization to profiles
Assign this profile to the users
( To add tcodes we use s_tcode)
Security Tcodes
SU01àUser Creation
SU02à Create profiles
SU03àObject Classes
SU10àBulk user creation
PFCGàProfile generator
SUPCàMass generation of profiles
PFUDàUser comparison
SUIMàUser information system
SU53àDisplay authorization data
SU22àMaintain Assignment of authorization
SU24àObjects through transaction
SUGRàUser group creation
SE38
Rsusr003àTo check the password s
Sap* and ddic
Restriction on password.
SM30
SM31 Maintain table use
USR40
We will add the passwords which can be set to the user.
Authorization data stores in USR02 table
How to unlock the user in OS level
C:>svrngrl
Svrmgrl>Connect internal
Svrmgrl>desc usr 02
Which are existing in the USR 02
Svrmgrl>desc*sapsid.usr02
Describes the users in sapsid
Svermgrl>mandt,bname,uflag,from sapsid
(Client Name),(User name)
If Uflag is zero then user is not locked.
Svrmgrl>update sapsai.usr02 set uflag=’64’ where mandt=’800’ and bname=’babu1’,
SE38
Rsusr003 To check the passwords of sap* and ddic of all clients
Rsusr200 List of users according to logon date and password change
Tstct: all tcodes with text
Tstc all the tcodes.
TransportManageSystems (STMS) 156
To make a system as a domain controller we will and the STMS tcode on the newly configured system
STMS
System overview
SAP System
Create
1)Virtual
2)Externally
3)Domain link
STMS
Transport routes
Configuration
Standard Configurations
Three System configuration
Devà(Consolidation path)àTestà(Delivery Path)à Prod (Delivery system /Recipient system)
(Consolidation System)
Request Types
1 Customization,
2 Workbench
3 Transport of copies
4 Relocations
Request Status
1 Modification
2 Released
Display ( To check the displays)
Gobal Information
Transport
Repairs.
When TMS is configured by default the
TMS.ADM user; domain.cfg à ( Bin directory);rfc configuration.
Double click on the domain controller and we can create the backup server on communication.
SE09/SE10
Check customization requests
Or Work bench Requests
Click on create
Select customization/Work bench
Select the short description
User name and save it
Then select the tasks and click on release.
How to import the released jobs
STMS
Click on Import overview
Double click on target server
Adding an request in to the import queue
Click on extras
Click on other requests
Add
We will add the request number
Select the transport require
And click on import request
(This is used for importing one request)
Select the target client
If bulk requests to be imported then click on import all befpre this we want to select all the requests by using F6 key)
We can schedule the import date and time accordingly.
( Work bench requests are imported immediately were as customization requests are imported in weekends only)
Execution
1Synchronous 2 Asynchronous
Asynchronous
1 )If import is executed asynchronous the dialog or batch process is released after import was started
2) Synchronous
If import is executed synchronously dialog or w/p is blocked until import has ended
Click on continuous
Select the particular request
Click on logs
If we get any errors then we will reassign to development
And the request will be imported successfully
Written codes after releasing and importing
(0) means successful
(4)With warnings
(8)Errors
(12)Fatal Errors
SE01 Transport organizer request
Transports From OS level
Tp add to buffer request number
Tp import(Client 800)U
Tp import all(to import all the requests)
Go to
Usr/sap/trans/bin
To execute the tp command (Transport requests are stored in E070 table)
If the import has been hung then we run the batch jobs
SE38 àRDDIMPDPàRDDNEWDP to activate
SE01:- Extended overview of transport organizer
STMSàTransport requests
SE01àExtended transport
SE09/SE10àExport transports
SE06àPost installation actions for transport organizer
SE03àTransport Organization tools
SE06
System change option
And we change modified or non modifiable
Before this option we require to perform client setting(SCC4)
SE03
Transport Organization tool.
Transport Domain Management:
1>If the R/3 system acting as the Domain controller fails no changes can be made to the TMA configuration. So SAP recommends
To configure back up domain controller that can assume the function of the domain controller when required
2>To move the domain controller the another R/3 system you must active the backup controller.Now the backup controller becomes the domain controller and vice versa.
To check the status of the transport Domain configuration
Overviewàsystems
Configure TP
1>Transport control programme (Tp) requires a transport profile that contain info about establishing the db connection for all R/3 system in the transport domain.
2>TMS generates and manages this transport profile
TP-.pf1
3>To display the tp parameters of an R/3 systems
Overviewsystems
Click on transport tool tab
Goto tp parameters
It displays the parameters in tp-.pf1
TMS Authorizations:
To perform TMS on each R/3 system using client 000 and user authorizations S_CTS_ADMIN.
TMSADM user profile S_A.TMSCFG
Configure TMS
1 Configure the Tramsports Domain and assign R/3 systems to this domain ad specify one R/3 system as the transport domain controller .
2 Configure transport routes
3 Configure QAS.
Domain Controller is normally configured on a PROD)on QAS.R/3 system selected to be domain controller should have
1 high availability
2 high level securities
3 high level maintenance
Initializing the transport Domain Controller
To use STMS the user authorization is S_STS_ADMIN
1>If the R/3 system is already assigned to transport domain, the TMS screen shows the system status. Either domain controller or as an R/3 system with in a domain.
2>If R/3 system not yet assigned to a transport domain,R/3 tries to locate the existing transport domain with in the current transport group by reading file Default.cfg in the bin directory.
If no transport domain is exists a new transport domain is created and the current R/3 system is assigned as the transport Domain controller
3> when transport domain controller first created, the TMS generates
1A transport domain ad transport group
2 User TMSADM
3 RFC destination s for TMS
Domain.CFG file in bin directory for storing TMS configuration.
Default transport domain name (Domain name_)
Cofiles:à Command or change request information files that includes information on the transport type, object classes, required import steps and post-processing exit codes.
Sap name:-Info, pertaining to transport requests for each SAP user.
EPS:-download directory for advanced corrections and support packages
Tmp:-Temporary date and log files
Buffer:-Transports buffer for each system, indicating which transports to be imported.
Sub Directories:-
Bin: - Configuration files for tp (Tp- .pfl) and
Data:-exported data
Old data:-Old exported data (to be archived (or) deleted)
Log:-Transport logs, trace files and statistics
Act log:-Action logs for all tastes and requests
Trans(sub Directories)
Cofiles log tmp buffers sapnames data bin
Bin:- Contains configuration file TP_.PFl of transport programme TP and configuration file DOMAIN>CFG of the domain.
Data:-Data files of transport requests
Sapnames:-A log for each user of the CTS.It contains the transport activities for usesrs transport requests.
Buffer:- One import buffer for each system. It contains the requests planned for import into this system, including all the work steps required for the import.
Tmp:-Temporary log files and semaphores
Log:-General and request –specific log files.
Cofiles:-Control files for the transport requests, the files record the object classes, the required import steps and return values.
The system from which the transport domain is created is defined as the Domain controller. All the configuration work must be performed from 000 client.
Daily Tasks
1 Check the R/3 system is up or not (log in to the SAPR/3 system)
2 Check the daily backups executed with out errors (DB12)
3 Application server are up and running (SM51)
4 CCMS alert monitor (RZ20)-Computer center management system)
5 Work process Overview (SM50) or SM66 àfor Global
6 System log (SM21)
7 Update records (SM13)
8 Lock entries (SM12)
9 Cancelled Background jobs (SM37)
10 Check the logon users (SM04)
Alog à Global
11 Spool Problems (SP01)
12 Abap Dump (ST22)
13 Workload analyses (ST03)
14 buffer statistics (ST02)
15 DB Performance monitor (ST04)
16 Exclusive Lock waits (DB01)
17 Table / Index (DB02)
18 dba logs (DB14)
19 Local Transaction statistics (STAT)
20 OS Monitor(ST06)
21 Application Monitor (ST07)
22 N/W monitor (ST08)
23 Performance Monitor (STUN)
Support Packages (SPAM)
SPAM:-Support Package Manager
To install the packs
Types of S/W components
SAP_BASIS àSAPKB (number)
SAP_ABAà SAPKA (number) àCross application
SAP_APPLà SAPKH (Number) àlogistics and accounting
SAP_HRàSAPKE (Number)àHuman resources
ST_PI à à Plug ins
www.service.sap.com here we get the support packs of SAP
it will ask for user id and password
user name (S000------)
Password
Procedures to install Support Packs
1 Download the required .CAR file from sap net i.e. (Service.sap.com)
2 Change the directory
/usr/sap/trans>SAPCAR (Case sensitive) - xvf (Downloaded file names) (To uncompress the CAR file)
The above command will decompress the CAR file and generated the two files (.ATT,.PAT) in
/usr/sap/trans/EPS/in directory
3 Log in 000 client with ddic user
4 And execute SPAM
Support packages
Load packages
From application server
We will get a popup box with list of patches in the queue
Both applied Patches and new patches will be listed
5 Click the back button to get the main screen
6 and click on display /define button.
We get a popup box with unapplied patches
7 Select the particular patch which needs to apply
Go to support Package
Click on import queues
8 After Patch is successfully applied you have to confirm the patch application
Support packages
Confirm
Run the tcode
SPAU
(This will check the changes made by the patches)
SPDD
(This will check the data dictionary objects)
PAT01 The patches are stored on Tables
PAT03
SAINT (Add on installation)
SDCC(To get the add ons and plug ins of the system)
Information
Pre-download checks
Notes and collectors
Possible errors while installing support packages application
1 Cannot_Create_Cofiles
We will delete the concerned file of patch in cofile directory and data directory and restart the process
2 EPS IN is in old format
We will delete the concerned files i.e. .ATT and .PAT from the /usr/sap/trans/EPS/IN
And we will decompress the packages and restart the process
3 Objects_Locked
There are also times when a patch will fail because an object i.e. trying to modify is locked by changed requests. In such cases identify the objects and the change request of using SE03 tcodes search for objects and unlock that and restart the process
KERNEL UPGRADATION
How to check kernel status
From SAP level à
System
Status
(Click on other kernel info (It will show all the information of SAP, Oracle, and System))
From OS Level
àusr/sap/sid/sys/exe/Run
Disp+work –V
From Sap level SM51
Click on release notes
How to apply kernel patch:-
1 Download the kernel patch from www.service.sap.com
Eg:- du_117_20018c.SAR.
2 Download this patch from net to the folder
3 Uncar this patch
SAPCAR –xvf dw_117_200--.SAR
4.Change the ownership toadm to all these extracted files
Chown –Radm : sapsys
5 login as adm
6 Goto /usr/sap//sys/exe/run
disp+work -Vpg
7 Now copy the run folder
Cp –R run
8 Copy all extraxted file to run folder
9 again check disp+work – V pg
10 login ora <>Sid
11 Start the listener lsnrctl start
12 start sap go to status (Check the kernel version)
change the ownergroup
How to upgrade kernel up gradation
Same as above steps
But need to delete Saposcol.exe from the run directory
Run root.sh à It will create the more saposcol.exe
LOAD BALANCING (SMLG)
SMLG
Click on create button
Give logon group name
And Select the Instance
In attributes select the ip address
And we can restrict the users
Click on copy
How to check the load balancing
SMLG
Goto
Load distribution data
RFC( SM59)
SM59
Select the type of connections
RFC destinations Destination ip address
Logon /Security
We will the user name a\of destination system and password to get authentication
Click on save
And test connection
SAPCAR _XVF dw_2210_1000 25 sg.CAR
R/3 APO
Btdlb.o
Disp+work
Dpmon
Enq
Gwmon
Gurd
Icmar
Icman
Mss_server
Rspo0lib.o
10 files while applying the application packages to be checked
Bw/crd 20 files
FRFCLIB32.SAR
Disp+Work
Dbjzee
Dpmon
Dw_gui.o
Dw_mdm.o
Dw_stl.o
Dw_xml.0
Dw_xtc.o
Enqt
Gwmon
Gwrd
Icmadmin.SAR
Icman
Icmbnd
Icmon
Msg_server
Respo0lib.o
Sa.ppfper
Sepwebdisp
SM01 à to lock tcodes
ERP Enterprise Resource Planning
3.1H Older Version
4.6 C
4.7 E (Present Version) 620
ECC (Latest Version)
There is no Database in SAP R/3.It is linked to any of the data base like SQL, ORACLE etc
ARCHITECTURE( Chapter2 )
DVEMBGS
DàDialog Work process
VàVerbose( Update Workprocess)
Eà Enque
Mà Message Service
BàBackground Work Process
Gà Gateway Service
SàSpool
Dialog Work process: To interact with SAP, users session of login of users (for band Work process) Minimum 2 work process Max Depends on H/W compatibility.
Verbose (Update Work process): There are two types of Update Work process
1 .Asynronous updates (Non Time Critical) Default in SAP R/3
2 .Synchronous update (Time Critical)
Updating Database Minimim 1 updates.
Enque: Lock Mechanism It is lock for the table by the user .If one user is updating one table then other user can not access the particular table as it will be locked by the user using it.The lock will be automatically released once the work is done from the existing user who is using it.
Message Server: Communication between Application Servicesand load balancing is done from the message server.
Central Instance: When message server is resides is called the central instance
Dialog Instance: When ordinary instance is running on other Application servers with out Message Server is called dialog Instance.
Background Work process (BTC): For long running jobs like backup etc this process will come to the picture. While specifying it self we can use BTC option for the job process.
Gateway: Communication between the different R/3 system in the network.
Spool: Printing the SAP jobs in the network.
Layers Used in SAP are
1 Presentation Layer
Dispatcher (Assigns Work process to users Request)
2 Application Layer
3 Databases.
Dispatcher it stores the dispatcher queues to check with the permissions assigned to the users who is trying to access the Database.
Dispatcher first checks with the Task Handler then with ABAP Process, Database interface and then with SQL related this is called role in
What is Central Instance, Role in Role Out?
What is the function of Dispatcher?
Who will communicate between Application Server?
Sap on Solaris.
A user by default called Sid adm is created while installing the SAP server he is the super user of the SAP Basis,
To start SAP on UNIX platforms
1 start SAP R3à only Sap will start.
2 Start SAP DBà Only DB will Start
3 Start SAP AllàSAP+DB
To Stop SAP on UNIX platforms.
1 Stop SAP R3
2 Stop DB
3 Stop SAP ALL
To check the SAP Service is running or not is
Ps –ef grep SAP
To start a database Listener of Oracle to be started.
Login as
Su – orasid
Lsnrctl start
Exit
Then log in to
Su – sidadm
Start SAP R3
Ps –ef grep ora (to check the oracle services) to check the instances in the SAP we use dpmon instance name.
Profile Management (RZ10)( Pg No 96)
The default path of the profile is usr\sap\sid\sys\profile
Start Profile: It will start SAPR3 services in OS .The file existing is start_DEVMBGS00_sid
Default Profile: It contains common settings for R3 system like message server name, gateway services. The file that contains this profile is default_PFl
Instance Profile: It contains the parameter which is existing in the particular instance. The file that contains this profile is sid_DVEMBGS00_sid
Only one default profile exists in the R3 system. If any stand by system is also available.
Editing Profiles:-
1 By using RZ10
2 By using the VI editor command like vi
3 SAP pad utility.
We need to import the profiles from OS level SAP level by using RZ10
RZ10 Utilities Import Profiles Of active Servers
Modifying of Profiles
Editing profiles is having 3 modes
1 Administration data
2Basic Maintenance
3External Maintenance
Administration data: - In administration data the path of profile, last modified, modified on which date, profile activated by which user
Basic Maintenance: Update server name, gateway
Extended maintenance: To add any parameters
To increase the dialog work process, need to change the parameter
Parameter Parameter Value
Rdisp/wp_no_dia 5 to 6
Rdisp/wp_n0_btc 2
Reports are run on SE38
Rsparam àto display the parameters available in SAP R3 àExecuted
Rspfpar
To add a new parameter
RZ10à Select the profile which needs to be modified à Extended Malignance àand click on change
Click on create button parameter
Mention the parameter name
Parameter value
Click on copy
Click on Back
Save the changes
Back
Save change
Activate the profiles
1 What ever modifications we do by using RZ10 we need to restart the SAP server
2 Version number is the number which will change according to the modifications made on the profile.
3 The parameter value of the instance profile overwrites default profile value.
4 If any changes are made in R3 server the changes must be made on standby server.
RZ 11 Maintain profile Parameter.
Parameter Name display.
Monitoring Tcodes (Daily System Check)
SM 50 àWork process overview
SM51 à Sap server
SM 66 à Global work process Services
SM21 à System logs
/n à To display the new sessions
/o à To open a new sessions with out closing present application.
SM 37 à To monitor the background jobs
SM36 à To create the background jobs
ST22à ABAP dump analysis
SM 12à Lock entries
SM13 à Updates
DB 02à Table and Indexes ( Database Performance)
ST 02 à Tune Buffers
ST 03 àWorkload analysis
ST04 à.Database performance monitor
ST06àOperating System monitor.
OPERATION MODES (RZ04) (403)
Redistribution the work process among the instances, dynamically. We can distribute the peak and off peak
Advantages:-
1 zero down time
2 Buffers will not be refreshed, performance will not be affected
3 If any work process is busy, it will not affect the work process. Once the job is completed it will shift to other mode of operations.
Tcodes .
RZ04à Operation Modes
SM63 àTime Table
RZ03à Control Panel
By default dummy (Operation Mode) will be existing.
1>Creating Operations Mode
RZ04
Click on Create button
Operation Mode Day
Short Description
Click on Save
2>Assigning Work process to operation modes
Click on instance operation mode
Click create new instances button
Mention host name
System number
Select start profile
Select Instance Profile
Click on Save.
3>Assign Operation Modes to Time Table
SM 36 (Time Table)
Operation mode set
Select Normal Operations (24 Hours)
Click on change
Double click on time interval (Select the time intervals from which the operations must be started.)
Click on assign
Select operation mode
Save
In SM21 we can see the job changes on operation mode switching.
Total Number of work process will be the same. Variation of the dialog and background process can be changed according to the peak and off-peak hours.
We cannot edit the spool work process
How to change operations mode manually.
RZ03
Control
Switch to operation modes
Select Servers
Yes to save
To check all the servers in the Network
Is RZ03
In SM 51 we can see only the active servers
SM13 to check weather updates is active or not
SM 13
Administration
SM12
List the locks
Select particular user
Lock entry
Delete (If more than 2 days then we can delete)
ST22 (ABAP Dump Analysis)
RZ10
If we get run time error in SAP we need to change the parameter value
Rdisp/max_wprun_time
Default = 300 seconds.
Background Jobs(SM 36) (446)
SM 36 To define the Background Jobs
SM37 To monitor Background jobs
SE38 ABAP editor
There are 3 types of Background jobs
1 ABAP Programme
2 External Programme àOS Programme
3 External Commands à OS Commands
There are 3 job classes
a. High Priority
b. Middle Priority
c. Low priority (Default)
Exec Target: - If nothing is monitored then it will occupy which ever are free instances.
If we mention any target server for particular Background job that job will be bounded for that particular application server.
If application server goes down. It will wait until it comes up.
A batch user should be provided in the user name
S_BTCH_ADM à Admin for batch jobs
S_BTCH_NAMà Specifying the user name
S_BTCH_JOBà Authorization to run the batch jobs
Start Conditions.
Immediate: - It will run batch jobs immediately
Date/Time:-Specify the date/Time to run the Batch Jobs
After Job: - Dependent on other job which should be run
After Event:-
At Operation Mode:-
Job Status
1 Schedule,
2, Release
3, Ready
4, Active,
5, Finished
6, Cancelled.
Schedule: The step of the background job is saved. No start condition.
Released: The step is saved with start condition
Ready: The start time has reached and waiting for resources.
Active: The process is being running
Finished: Completed successfully.
Cancelled: Terminated with errors
1 Rerun the old batch jobs
2 Start from failure steps
Reasons to fail the batch jobs
1 User is not having the authorization to run the batch jobs.
2Varient does not exist
3 Duplicate records existing in the database
4 Resources are not available
5. Application server is down
6 If it’s in the loop of ABAP programme the batch jobs keep on active status.
7 To analyze the ABAP programme we can put active job in capture mode.
Job Capture
Capturing jobs is only for ABAP programmes not for external commands or external programme.
To cancel the active job we need to go to job details there we get the pid and application securename.Then we go to SM51 and double click on the application server and cancel the process by selecting the pid.
BTCTRn(delta)1
SE38 àbtctrns1 Scheduled to upgrade (This will hold the released jobs)
SE38 àbtctrns2 Rescheduled to upgrade (This will release the hold jobs)
Were we can see all standard jobs
SM36
RSBtcdel
Practical
1> SM36
Job Name àStart with Z or Y
Job ClassàA or B or c (Default) Low priority
Status àSchedule
Exec Target àTarget Server (Not mandatory it will run on any free application server)
Step
2>Click on ABAP Programme
Name àABAP Programme name (like RSBTCdel)
Variant àCan select the ABAP Programme
Check
Save
3>Start Condition
Immediate (It will start immediately)
Date/Time (To specify the date)
Scheduled Start
Start Afterwards
Period Values
Hourly
Daily
Weekly
Monthly
Other Period
Save.
To Monitor (SM37) Batch Jobs
Job Name(*)
User name(*)
Job status
Scheduled, Released, Ready, Active, Finished, Cancelled
Select the step and click on job change to edit to immediate.
SPOOL ADMINISTRATION (SPAD) (471)
To start with command prompt
D:\usr\sap\sid\sys\exe\run
Starts OS name :
Document
:
\/
Administration data Temse (Temporary Sequential)
:
\/
0/P RequestsàR3 Spool ServeràOS Spoolàprinteràdocument
When in R3 application server is configured for running at least one spool w/p is called spool server .Spool server consists of two parts
1) Administrative data (origin, data, author name)
2) The data to be printed (Temse (spool data))
Rspol/store_location : (db) Temse can be stored inside the R3 database or at file system level by (G)
Default is db or G(global) by selecting globally
/usr/sap/sid/sys/global: in the OS level the spool job is saved.
The preparation of spool request for printing is an o/p request .Which printer understands. It is given to the R3 spool server from this the data is shifted to the OS spooler from this it will be given to the print queue.
Types of Printing:-
1)Local Printing 2)Remote Printing 3)Front end printing
1) Local Printing:-If the spool server and the OS spooler on in the same system it is called the local printing.
2) Remote Printing:-If the spool server and the OS spooler are in different system
3) Front end Printing:- The printing with the SAP GUI
Tcode for printing
SPAD
Output Devices::- The logical printer name at SAP level
Short Name:-The name the system user to access the printer
Device Type:-Type of printer
Spool Server:-Application server with at least single spool work process
Host Printer:-The name of the printer defined at OS level
Host Name:-OS level system name.
Configured Printer in SAP level:-
SPAD
Click on output device
Click on change
Click on create
Select server type
Select spool server
Select Device class
Model
Location.
Go To Access Methods:
It is communication between OS spooler and real server for local printing L
C (NT)
Local
L (UNIX)
S (NT)
Remote
U (UNIX)
(NT)
Front end F
(UNIX)
Double Click on spool server
Logical Server:
Logical server is mapped directly or indirectly to the real spool server
Advantages:
1) Spool server switch over
2) Load balancing
To Monitor Spool Jobs
Tcode
SP01:-Spool request searching tool
SP02:-Displays all spool request.
Status:-
- : No o/p request for spool request
Proc : Spool w/p is processing the corresponding o/p request
Waiting : A spool work process is waiting for a written code from the OS spool
Compl : Completed successfully
Err : Error in Printing
Trouble shooting Printer:
1)Ping the printer
2) Fire the test print from SAP
Lpstart –a
Eg :-lpstart –a zgam
Lpstart –o zgam (Will get the print jobs are accessing)
Hpnadmin (ip address of printer)
Rsp0041:- To delete the old spool requests
SM36 (All standard jobs)
Sp12 Temse :- Administration of temporary sequential data
SP11 Temse :- Temse request screen
TST01 TST03 (When db is selected the spool jobs are saved in TST01,TST03)
TST01 :- Temse Objects
TST03:-Temse data
TST02:-Temse Protection rules.
Client Directory
Usr
Sap
Trans (SID)
Bin
Data DVEMBGS SYS
Cofiles Work exe global profile
Log Log run
Buffer KernalDirectories
Etc
Client Administration (364)
(000)
(001) Default Profiles
(066)
000 àMaster Clients
001àcopy of 000
066 àEarly watches which is used by the SAP Organization to monitor
Client Data Categorization
Custom data User Application data User data
Client Tools
1 Local client copy 2. Remote client copy 3.Client import/Export copy.
Local Client Copy: Creating a brand new user in the same R3 server and copying 000 to the new user.
Remote Client copy: It is used to copy the client from one R3 server to other R3 Server by using the RFC
(Network)
Client import/export copy: It is used to copy the client from one R3 server to the other R3 server, were as a dump is created in the OS level and can be exported to many R3 servers at a time.
Tcodes for client creation
SCC4: To create the client
SCCL: Local client copy
SCC9: Remote client copy
SCC8: Client export
SCC7: Client post import
SCC5: To delete the client
SCC3: Client logs
SM02: To sent system messages
SE06: Post installation Actions for Transport Organizer.
Local
Creating a brand new user in the same R3 server and copying 000 to new user.
Local Client Copy
1 Create client by using scc4 (In the target system)
2 Log on to the target client with the user
Sap*/pass(Password)
3 Run the Tcode SCCL (SCC9 for Remote Client copy)
4 Select the profile
5 Select the source client (in remote client copy select the remote server)
6 Before copying run the test run
7 Schedule as background
Remote Client Copy
1 In remote client copy the data is transformed directly b/w the source and target client using RFC s(Remote Function Call) in n/w connection
2 Single step Process
Export:
In client transport data is exported file at OS level (Trans/data).At some further time the client is imported from the file system to the target system by using the management system.
2 Two step process
Important Points
1 R3 repositry objects such as ABAP programme are not transported with the client copy
2 Development objects can only be transported using change request
3system messages to be passed to clients from SM02 beford copying client.
4The space on the system should be checked.
5If the client copy is terminated abnormally we can re execute the same copy process. The system allows you to restart the copy at the point were it was terminated previously.
6 The client copy programes use the client copy control flow table i.e ccc flow
To lock the particular sid
Tp locksys
Tp unlock sys
Changes and Transports for client-specific objects
1 Changes with out automatic recording:-with this option customizing changes allowed but the changes will not be recorded in the transport request.
Eg: we can set it as SAN box client
2Automatic recording of changes
Changes to customizing data are automatically recorded in the transport request
Eg :Development
3No Changes Allowed:
We cannot do any changes allowed
Eg: Production system.
4No Transport allowed:
We can modify the data but we cannot transport
Eg:Training system
Restrictions
For Import Export
1 SCC4
To create the client in the target
SCC8 (To export the client copy)
SCC7 ( To import the Client copy)
SCC9(To Remote Client copy)
What is the difference between T000 and SCC4
In T000 the structure will be deleated but the data will be existing
If we use SCC5 the structure and the data will be completely deleated.
SECURITY (SU01) (309)
Security
User creation User deletion user Modify Roles Profiles
User Administration
000)
001) Three Default Clients
066)
Ddic) Default Users
Sap*)
000) user àddic
001) Passà19920706
000) user àsap*
001) Passà06071992
066) user àEarly watch
Passàsupport
Users are client dependent
SU01:- To create the user address, logon data, defaults, Parameters, Roles, Profiles, Groups
SU01
User Name
Click on create
Adress Title
Last Name
Logon data : password
User group
User type Dialouge(Dialouge users will be default users)
Communication (In RFC usage)
System(Background jobs)
Service
Reference (Template were we can copy)
Defaults: Start menu
O/p device
A user can change the password once in a day
But administrator can change the password any number of times.
For creating bulk users SU10
Client Refresh
We will deleate the sap* from the target client we will exit form the user and we can log in to the sap*/pass
ROLES (PCFG)
1 Creation of roles
2 Assigning to users.
Roles
1 Single Roles 2 Composite Roles 3 Derived Roles
Single Role
Authorizations Class
Authorization Objects
Authorizations
Fields
Field Values
Single Role: (default Role) :-A role which contains the authorization objects like tcode permission etc
PFCG
1 Description: - (Description of the role)
2 Menu àAssigning Transaction codes.
3 Authentications
4 Users
Menu Transaction
Assign transaction which user can access
2 Reports:-To run the report which is added in the authorizations
3 Other:-Adding the web address which user can access directly from the SAP.
Red Mark Red :- Organization levels are not maintained
Yellow:-Field values are partially maintained
Green:-All are maintained properly
We can import the following in the Authentications:
1 From SAP menu
2 From other Role which is already created
3 From area menu
4 Import from file.
Composite Roles:- In which two or more roles are added and create a new role. In this derived role we can compare the authorizations assigned to the roles in the compositerole.
Derived Roles:- It will inherite the parent role permissions, except organization level.
Composite Roles:-
Description
Roles
Menu
User
Personalization
Authorizations are not mentioned in composite role. We need to maintain in the individual roles which are maintained in the single role.
We cannot assign composite role to composite role.
Activity Groups are called roles in the newer version.
Transport:
To transport the derived role the system also transports all roles from which this role is derived .To avoid the inconsistency in the target system.
Upload:- When loads uploading all role data (including the authorization data) is uploaded from a file in to the R/3 system. The user assignment for the role and the generated profiles for the role are not uploaded.
This means authorization profiles must be regenerated after the upload.
Transport:-When roles are transported the associated authorization profiles and transported as well,but we need to perform user master comparision for all imported roles, after completing the import in to the target system.
PFCG
Role.
/nsupc:- To mass generation of profiles,
/npfud:-Mass user comparision.
/nsuim:-User information system.
For single role creation
PFCG
Click on create role
Description (Give description)
Menu
Click on Transaction (To add Tcodes to the roles)
(From Sap Menu; From Other etc)
Click on authorization
Click on change authorizations data
(Need to maintain the authorization)
Make all the fields green
Click on save
Click on generate (To generate the profiles)
Click on back
Click on users (add the users accordingly)
Click on user comparison
Click on complete comparison.
(It will adjust the user master record)
Click on save
Change authorization data:-It will not show the authorization roles on fields.
Expert mode for profile generation:
It will show the authorization roles on fields.
To do manually
Profiles
SU02 àCreation of profiles
SU03àObject class
SU24/SU22àMaintain Assignment of authorization objects of transactions
Transactions Give the tcode
Click on execute
Click on check indicator
Eg S- Data set
S-Develop Which are checked and maintained
S-Programme
SU03àInformation System
SUIM
Click on authorization objects
Click on by object name,text
Give the authorization object eg like s_dataset
Click on execute
SU03
Select the object class
Double click on object class
Double click on object eg:- Dataset
Click on create
Give Authorization name
Check mark
To maintain field value
Double click on fields and select field
Click on save
Click on activate button twice
Su02
Click on generate work area
Click on create button
Give the profile name
Select the profile type
Click on save
Give the authorization object
Press enter
Add authorizations to the authorization tab
Click on save
Click on activate twice
SU01
Click on profile tab
Select the profile
And click on save
Steps to Create Manually the Roles
We need to check the authorization objects for the particular tcode (SE38)
Need to find out the object classes for this authorization objects (SUIM or SU03)
Need to create the Authorization
Create the profile
Arranging this authorization to profiles
Assign this profile to the users
( To add tcodes we use s_tcode)
Security Tcodes
SU01àUser Creation
SU02à Create profiles
SU03àObject Classes
SU10àBulk user creation
PFCGàProfile generator
SUPCàMass generation of profiles
PFUDàUser comparison
SUIMàUser information system
SU53àDisplay authorization data
SU22àMaintain Assignment of authorization
SU24àObjects through transaction
SUGRàUser group creation
SE38
Rsusr003àTo check the password s
Sap* and ddic
Restriction on password.
SM30
SM31 Maintain table use
USR40
We will add the passwords which can be set to the user.
Authorization data stores in USR02 table
How to unlock the user in OS level
C:>svrngrl
Svrmgrl>Connect internal
Svrmgrl>desc usr 02
Which are existing in the USR 02
Svrmgrl>desc*sapsid.usr02
Describes the users in sapsid
Svermgrl>mandt,bname,uflag,from sapsid
(Client Name),(User name)
If Uflag is zero then user is not locked.
Svrmgrl>update sapsai.usr02 set uflag=’64’ where mandt=’800’ and bname=’babu1’,
SE38
Rsusr003 To check the passwords of sap* and ddic of all clients
Rsusr200 List of users according to logon date and password change
Tstct: all tcodes with text
Tstc all the tcodes.
TransportManageSystems (STMS) 156
To make a system as a domain controller we will and the STMS tcode on the newly configured system
STMS
System overview
SAP System
Create
1)Virtual
2)Externally
3)Domain link
STMS
Transport routes
Configuration
Standard Configurations
Three System configuration
Devà(Consolidation path)àTestà(Delivery Path)à Prod (Delivery system /Recipient system)
(Consolidation System)
Request Types
1 Customization,
2 Workbench
3 Transport of copies
4 Relocations
Request Status
1 Modification
2 Released
Display ( To check the displays)
Gobal Information
Transport
Repairs.
When TMS is configured by default the
TMS.ADM user; domain.cfg à ( Bin directory);rfc configuration.
Double click on the domain controller and we can create the backup server on communication.
SE09/SE10
Check customization requests
Or Work bench Requests
Click on create
Select customization/Work bench
Select the short description
User name and save it
Then select the tasks and click on release.
How to import the released jobs
STMS
Click on Import overview
Double click on target server
Adding an request in to the import queue
Click on extras
Click on other requests
Add
We will add the request number
Select the transport require
And click on import request
(This is used for importing one request)
Select the target client
If bulk requests to be imported then click on import all befpre this we want to select all the requests by using F6 key)
We can schedule the import date and time accordingly.
( Work bench requests are imported immediately were as customization requests are imported in weekends only)
Execution
1Synchronous 2 Asynchronous
Asynchronous
1 )If import is executed asynchronous the dialog or batch process is released after import was started
2) Synchronous
If import is executed synchronously dialog or w/p is blocked until import has ended
Click on continuous
Select the particular request
Click on logs
If we get any errors then we will reassign to development
And the request will be imported successfully
Written codes after releasing and importing
(0) means successful
(4)With warnings
(8)Errors
(12)Fatal Errors
SE01 Transport organizer request
Transports From OS level
Tp add to buffer request number
Tp import
Tp import all(to import all the requests)
Go to
Usr/sap/trans/bin
To execute the tp command (Transport requests are stored in E070 table)
If the import has been hung then we run the batch jobs
SE38 àRDDIMPDPàRDDNEWDP to activate
SE01:- Extended overview of transport organizer
STMSàTransport requests
SE01àExtended transport
SE09/SE10àExport transports
SE06àPost installation actions for transport organizer
SE03àTransport Organization tools
SE06
System change option
And we change modified or non modifiable
Before this option we require to perform client setting(SCC4)
SE03
Transport Organization tool.
Transport Domain Management:
1>If the R/3 system acting as the Domain controller fails no changes can be made to the TMA configuration. So SAP recommends
To configure back up domain controller that can assume the function of the domain controller when required
2>To move the domain controller the another R/3 system you must active the backup controller.Now the backup controller becomes the domain controller and vice versa.
To check the status of the transport Domain configuration
Overviewàsystems
Configure TP
1>Transport control programme (Tp) requires a transport profile that contain info about establishing the db connection for all R/3 system in the transport domain.
2>TMS generates and manages this transport profile
TP-
3>To display the tp parameters of an R/3 systems
Overviewsystems
Click on transport tool tab
Goto tp parameters
It displays the parameters in tp-
TMS Authorizations:
To perform TMS on each R/3 system using client 000 and user authorizations S_CTS_ADMIN.
TMSADM user profile S_A.TMSCFG
Configure TMS
1 Configure the Tramsports Domain and assign R/3 systems to this domain ad specify one R/3 system as the transport domain controller .
2 Configure transport routes
3 Configure QAS.
Domain Controller is normally configured on a PROD)on QAS.R/3 system selected to be domain controller should have
1 high availability
2 high level securities
3 high level maintenance
Initializing the transport Domain Controller
To use STMS the user authorization is S_STS_ADMIN
1>If the R/3 system is already assigned to transport domain, the TMS screen shows the system status. Either domain controller or as an R/3 system with in a domain.
2>If R/3 system not yet assigned to a transport domain,R/3 tries to locate the existing transport domain with in the current transport group by reading file Default.cfg in the bin directory.
If no transport domain is exists a new transport domain is created and the current R/3 system is assigned as the transport Domain controller
3> when transport domain controller first created, the TMS generates
1A transport domain ad transport group
2 User TMSADM
3 RFC destination s for TMS
Domain.CFG file in bin directory for storing TMS configuration.
Default transport domain name (Domain name_
Cofiles:à Command or change request information files that includes information on the transport type, object classes, required import steps and post-processing exit codes.
Sap name:-Info, pertaining to transport requests for each SAP user.
EPS:-download directory for advanced corrections and support packages
Tmp:-Temporary date and log files
Buffer:-Transports buffer for each system, indicating which transports to be imported.
Sub Directories:-
Bin: - Configuration files for tp (Tp-
Data:-exported data
Old data:-Old exported data (to be archived (or) deleted)
Log:-Transport logs, trace files and statistics
Act log:-Action logs for all tastes and requests
Trans(sub Directories)
Cofiles log tmp buffers sapnames data bin
Bin:- Contains configuration file TP_
Data:-Data files of transport requests
Sapnames:-A log for each user of the CTS.It contains the transport activities for usesrs transport requests.
Buffer:- One import buffer for each system. It contains the requests planned for import into this system, including all the work steps required for the import.
Tmp:-Temporary log files and semaphores
Log:-General and request –specific log files.
Cofiles:-Control files for the transport requests, the files record the object classes, the required import steps and return values.
The system from which the transport domain is created is defined as the Domain controller. All the configuration work must be performed from 000 client.
Daily Tasks
1 Check the R/3 system is up or not (log in to the SAPR/3 system)
2 Check the daily backups executed with out errors (DB12)
3 Application server are up and running (SM51)
4 CCMS alert monitor (RZ20)-Computer center management system)
5 Work process Overview (SM50) or SM66 àfor Global
6 System log (SM21)
7 Update records (SM13)
8 Lock entries (SM12)
9 Cancelled Background jobs (SM37)
10 Check the logon users (SM04)
Alog à Global
11 Spool Problems (SP01)
12 Abap Dump (ST22)
13 Workload analyses (ST03)
14 buffer statistics (ST02)
15 DB Performance monitor (ST04)
16 Exclusive Lock waits (DB01)
17 Table / Index (DB02)
18 dba logs (DB14)
19 Local Transaction statistics (STAT)
20 OS Monitor(ST06)
21 Application Monitor (ST07)
22 N/W monitor (ST08)
23 Performance Monitor (STUN)
Support Packages (SPAM)
SPAM:-Support Package Manager
To install the packs
Types of S/W components
SAP_BASIS àSAPKB (number)
SAP_ABAà SAPKA (number) àCross application
SAP_APPLà SAPKH (Number) àlogistics and accounting
SAP_HRàSAPKE (Number)àHuman resources
ST_PI à à Plug ins
www.service.sap.com here we get the support packs of SAP
it will ask for user id and password
user name (S000------)
Password
Procedures to install Support Packs
1 Download the required .CAR file from sap net i.e. (Service.sap.com)
2 Change the directory
/usr/sap/trans>SAPCAR (Case sensitive) - xvf (Downloaded file names) (To uncompress the CAR file)
The above command will decompress the CAR file and generated the two files (.ATT,.PAT) in
/usr/sap/trans/EPS/in directory
3 Log in 000 client with ddic user
4 And execute SPAM
Support packages
Load packages
From application server
We will get a popup box with list of patches in the queue
Both applied Patches and new patches will be listed
5 Click the back button to get the main screen
6 and click on display /define button.
We get a popup box with unapplied patches
7 Select the particular patch which needs to apply
Go to support Package
Click on import queues
8 After Patch is successfully applied you have to confirm the patch application
Support packages
Confirm
Run the tcode
SPAU
(This will check the changes made by the patches)
SPDD
(This will check the data dictionary objects)
PAT01 The patches are stored on Tables
PAT03
SAINT (Add on installation)
SDCC(To get the add ons and plug ins of the system)
Information
Pre-download checks
Notes and collectors
Possible errors while installing support packages application
1 Cannot_Create_Cofiles
We will delete the concerned file of patch in cofile directory and data directory and restart the process
2 EPS IN is in old format
We will delete the concerned files i.e. .ATT and .PAT from the /usr/sap/trans/EPS/IN
And we will decompress the packages and restart the process
3 Objects_Locked
There are also times when a patch will fail because an object i.e. trying to modify is locked by changed requests. In such cases identify the objects and the change request of using SE03 tcodes search for objects and unlock that and restart the process
KERNEL UPGRADATION
How to check kernel status
From SAP level à
System
Status
(Click on other kernel info (It will show all the information of SAP, Oracle, and System))
From OS Level
àusr/sap/sid/sys/exe/Run
Disp+work –V
From Sap level SM51
Click on release notes
How to apply kernel patch:-
1 Download the kernel patch from www.service.sap.com
Eg:- du_117_20018c.SAR.
2 Download this patch from net to the folder
3 Uncar this patch
SAPCAR –xvf dw_117_200--.SAR
4.Change the ownership to
Chown –R
5 login as
6 Goto /usr/sap/
disp+work -Vpg
7 Now copy the run folder
Cp –R run
8 Copy all extraxted file to run folder
9 again check disp+work – V pg
10 login ora <>Sid
11 Start the listener lsnrctl start
12 start sap go to status (Check the kernel version)
change the ownergroup
How to upgrade kernel up gradation
Same as above steps
But need to delete Saposcol.exe from the run directory
Run root.sh à It will create the more saposcol.exe
LOAD BALANCING (SMLG)
SMLG
Click on create button
Give logon group name
And Select the Instance
In attributes select the ip address
And we can restrict the users
Click on copy
How to check the load balancing
SMLG
Goto
Load distribution data
RFC( SM59)
SM59
Select the type of connections
RFC destinations Destination ip address
Logon /Security
We will the user name a\of destination system and password to get authentication
Click on save
And test connection
SAPCAR _XVF dw_2210_1000 25 sg.CAR
R/3 APO
Btdlb.o
Disp+work
Dpmon
Enq
Gwmon
Gurd
Icmar
Icman
Mss_server
Rspo0lib.o
10 files while applying the application packages to be checked
Bw/crd 20 files
FRFCLIB32.SAR
Disp+Work
Dbjzee
Dpmon
Dw_gui.o
Dw_mdm.o
Dw_stl.o
Dw_xml.0
Dw_xtc.o
Enqt
Gwmon
Gwrd
Icmadmin.SAR
Icman
Icmbnd
Icmon
Msg_server
Respo0lib.o
Sa.ppfper
Sepwebdisp
SM01 à to lock tcodes
No comments:
Post a Comment