1. Implementation
Implementation is an activity to deploy any new SAP Software component into an
organization. Some of the tasks which are undertaken during implementation are
Sizing, Installation, Configuration, Security, Adopting the system based on
customer requirements, Applying support packages, add-ons, languages, library
configuration, Customizing, Development, Transportation, Training ,router
setup,landscape design,connecting to SAP Germany,schedule go_live Sessions etc..
SAP Implementation is carried by using ASAP(Accelerated SAP Methodology)
it provides predefined road maps,business scenarios,templates,documents and
url's etc..
Execute Transaction RMMAIN in Solution Manager to get the roadmap for
implementation.
ASAP Methodlogy contains 5 Phases:
1.Project Preparation
2.Business Blueprint
3.Realization
4.Final Preparation
5.GO-Live and Support
The First Activity of a basis Consultant in Implementation is to identify the
relevant hardware,size the hardware considering various factors,recommend the
hardware,assist in hardware procurement,identifying software,assist in
communicating with OS/DB/SAP vendors etc.
Reasons for Implementation Failures:
1.User Requirements are vague and not properly documented
2.Lack of Competency and Project Management skills
3.User Motivation and Employee Retention
4. Risk Evaluation and Risk Mitigation
5. Growth in Business requirements(SCOPE Change)
Hardware Sizing:it is used to convert the business requirements into technical
requirements.
Sizing is performed by using Quick sizer tool which is provided by sap and
accessed by using URL http://service.sap.com/sizing.
it requires a market place userid (S0001234567) and password to access that
tool.it is a free tool provided by sap for customers/partners.
Sizing means determining the hardware requirements of an SAP System such as
network bandwidth, physical memory, CPU power, and I/O capacity. The size of the
hardware and database is influenced by both business aspects and technological
aspects. This means that the number of users using the various application
components and the data load they put on the network must be taken into account.
User-based sizing. We defined three types of active users who work with the
system to a different degree. Merely counting the users can be done quite
easily. The disadvantage is that this estimation is quite rough as it says very
little about the actual throughput(load) these users produce.
The Users are categorised as three types which are differntiated based on number
of dialog steps(inputs).
Dialog Step:it is a mouse click/key board enter or any functional key.
1.Low User : The Users who generate around 0- 480 dialog steps/week
considering 40 working hours/week
480----40 hours
each hour 480/40=12 dialog steps
each dialog step =60/12 minute=5minutes=300 seconds.
2.Medium User:The Users who generate around 480- 4800 dialog steps/week
considering 40 working hours/week
4800----40 hours

2. each hour 4800/40=120 dialog steps
each dialog step =60/120 minute=1/2minutes= 30 seconds.
3.High User:The Users who generate around 4800- 14400 dialog steps/week
considering 40 working hours/week
14400----40 hours
each hour 14400/40=360 dialog steps
each dialog step =60/360 minute=1/6 minutes= 10 seconds.
Throughput-based sizing. This model is quite thorough because it relies on
actual or on actually expected throughput. However, this model relies on a
number of assumptions in business terms (e.g. number of order line items per
year) that need to be cross-checked against the individual installation.
This is similar to user based sizing,but exact number of dialog steps are known.
Example a Sales Order Transaction may Contain around 8-12 dialog steps.
Transaction is nothing but which contains one or more LUW's.Luw Contains one or
more dialog steps which can be committed together or rolled back.
Process of sizing:
1.Specify the Project Name:(customer Number comes by default)
2.Click on create the project
3.Select project Information
a.Project Data---Name of the Project-->
b.new or upgrade(new)
c.Customer Data(customer information like name,email,telephone no,fax no)
d.Platform communication;
OS,Version,database,database version,system type(dev,qas,prd),size of legacy
database,
e.system availability:how long the system/business sustains with out SAP.
mirroring,RAID,Storage Area Network,backup(online/offline),Standby
server,clustering etc
Select the Modules (FI,CO,HR,QM,PM) specify the low,medium and high users and
save the sizing.
Click on Calculate Results. The Sizing is based on T Shirt Sizing and sizing
output is displayed with size of the CPU,Storage,SAPs,Memory,I/Ops required
etc..
if the sizing output comes in XXXL/48000 SAPS or 18000 IOPS or the storage
exceeds 1.6TB then contact sap and hardware vendors.
The Sizing Results are only a skeleton sizing,before concluding on the sizing
report the following has to be considered.
The Following has a major impact on the sizing
1.Operating system
2.database
3.virtual memory
4.email/fax/paging/printers interfaces
5.third party tools like biometric,weighbridge
6.high availability (peak/offpeak,raid levels,cluster)
7.backup devices and backup type
8.network infrastructure.
9.legacy data
10.future growth of the company
11.custom development
The CPU are displayed as SAPS Because each H/W vendor processors differs.
SAPS are SAP Application bench mark for performance standards.it is based on a
standard bench mark ie, for every 2000 sales order line items per hour/2400
business transaction or 6000 dialog steps/hour requires 100 SAPS.
SAPS is the understandable format of hardware vendor to calculate the CPU's
while considering the above factors the sizing result may vary from 30% to 200%
(example Unicode system requires 40% more resources)

3. General Recommendation:
1.OS on Raid 1 Level(1:1)-->Mirroring
2.Transaction logs/redologs on raid 1 level(1:1)-->Mirroring
3.Database on Raid 5 or on SAN(storage area network)(1:4,1:5)
4.Memory setup in different slots
5.Processors to handle load balancing/failover.
6.The Space required should be requested as NET Size(gross includes
raid,firmware,parity etc..)
Most user sizings follow the standard pattern of low, medium, and high activity
users
Think times between screen changes of 5 minutes, 30 seconds, and 10 seconds
The usual distribution is 60-70%(64%) low, 30%(30) medium, 5-10%(6) high
If in doubt, take medium activity users
The above sizing is based on average response time of 600 ms to 1 second.
Changes to SAP SD Bench Mark
on January 1, 2009, the SAP SD Benchmark was updated. Alongside the upgrade to
SAP Business Suite 7 and the SAP enhancement package 4 for SAP ERP 6.0, a number
of additional, necessary updates were implemented. Business changes constantly,
for example, Unicode and the use of the new general ledger /credit limit check
are now common practice for SAP customers across all industries, and the SAP
standard application benchmarks need to reflect this change.
The above sizing is based on average response time of 1second to 2 seconds
Hardware procurement:The Hardware is ordered to the preferred vendor and
hardware dispatch may take around 1 to 2 months.
Software Procurement:The Software need to be ordered well in advance to comply
with the statutory requirments of the conutry which may take around 2 to 3
months.
Prerequistes of Installation:
1.Download the installation guide from http://service.sap.com/instguides
2.Check the product availability matrix from http://service.sap.com/pam and
platforms
3.Download and check the known issues from http://service.sap.com/notes
4.Ensure that hardware is sized and sizing output is determined using
http://service.sap.com/sizing
5.Download the software from http://service.sap.com/swdc
6.Prepare a mile stone list to implement the sap software.(it should include the
responsibilities of OS Administrator,software,internet, dependencies,
risks,start date,processing(installation) status updates etc...)
7.Install the operating system and define the file system as per installation
Guide.
8.Ensure that hostname should not be longer then 13 characters and it should not
contain any special characters like(-,_)
9.Define the Virtual Memory(for 32 bit machines-->3 times of Physical Ram plus
500mb to 1000mb,for 64 bit machines the minimum virtual memory is 20GB.on top of
it add three times to physical ram(if it is more then 7 GB)
check the operating system command "memlimits" which will allocate memory to
processes.
10.Install Java runtime environment and setup environment variables(set path and
class path).Install the recommended JRE Version only(lower/higer may be
incompatible.)
11. Install the Database (based on Operating System) and apply patches.
Example: oracle 10.2.0.1/11.2.0.1 are not supported(not certified by SAP)
oracle 10.2.0.1 need to be patched to 10.2.0.2/4 or 11.2.0.1 to 11.2.0.2/3
12.Ensure that installation ports /21210/21211/21212/21213 are not blocked or
not in use.(netstat -a or -p)
13.Assign IP Address(A Static IP Address is Required so that the GUI Entries are
not Required to change) The Range of IP Addresses are 192/172/10.These are
called as private IP Addresses.127 is called as loop back/self ping which not
assigned to any system.(update etc/hosts)

4. Remaining all the IP addresses are public iP addresses.
14.Check used ports in etc/services(Use command netstat -p to display the used
ports).ensure that these Ports 3200,3300,3600,3900,4700, 4800,8000,8001 are not
in use.
15.Run prerequisite checker using sapinstallation master DVD.
16.Create Required file system(tmp directory for staging oracle| sapmnt
directory,sapdata1...n)
17.Check Remote connection to SAP(Internet) to get remote support from SAP in
case of any issues during installation
www.service.sap.com/notes-->help and support--<connect to sap>open the
connection
18.Copy the SAP Software into a temporary Folder and the folder name should not
contain space or any special characters).
19.Internet Connection to get support from other team members(download
notes/google for runtime issues)
20.On windows 2008 SR2 Disable the antivirus software/switch of the firewall.
21.Installation User should have previlages to create users/groups and asssign
groups to users.
when SAP Systems are installed using Domain Server then use Domain Admin ID or
user should be assigned with Domain Admin Rights(do not install with <SID>ADM
User).THE USER SHOULD HAVE PREVILAGES TO CREATE USERS/GROUPS/SERVICES/RUN
SERVICES/ASSIGN USERS TO GROUPS/CREATE FILE SYSTEM/DIRECTORIES/SHARED MOUNTS
ETC....
Software:
1.Operating System and Database.(installation along with Patches)
2.SAP Installation Master(independent of Components) (specific to OS).
intsllation master drives the installation which is based on operating system.in
earlier versions there are too many installation masters,but from netweaver 7.0
onwards there is only one installation master which contains
ERP/SCM/SRM/CRM/Netweaver and other components installation.it also provides an
option to select the available databases for that operating system along with
option to select Unicode.
3.SAP Kernel (Independent of Components) (Specific to OS|DB|32|64|Unicode
and non Unicode).it provides runtime executables,libraries,binaries which are
specific to Operating system/database/32bit/64bit/Unicode/non-unicode
it populates the kernel directory
/sapmnt/SID/exe
/usr/sap/SID/sys/exe/run
/usr/sap/SID/sys/exe/uc/NTAMD64
/usr/sap/SID/sys/exe/nuc/NTI386
4.SAP Exports(SAPDATA DVD's)--specific to Component and independent of OS and
DB(CRM,SRM,SCM,ERP, Netweaver etc). These Exports import data or populates the
data into sapdata*(sapdata1,sapdata2,sapdata3,sapdata4) directory
5.SAP JAVA Components:
Provides the components that are installable and configurable on java engine.
6.SAP GUI:Provides Presentation Server GUI Executables/binaries/libraries
in the PRES1(Win GUI) and PRES2(JAVA GUI)

5. 32bit and 64 bit architecture:
32 bit operating system provide 2^32 bit of memory for each process and 64 bit
operating system provides 2^64 bit memory for each process.it is displayed by
using command "memlimits"
SAP discontinued supporting 32 bit operating systems for productive systems.
Supply Chain Management is not supported on 32 bit machines.
32 bit machines provide a maximum of 2gb memory and 64 bit machines handles
memory requirement more then 4GB
Microsoft and other operating systems provides an option of 3GB in the current
versions of 32 bit hardware
Unicode/Non Unicode:
SAP Provides Support only for two options
1.Unicode
2.Non-Unicode
Unicode provides supports for all the Code Pages ie,4300 all the languages are
supported by Unicode.
Non Unicode supports only one code page example 1100 supports around 10-11
languages.
Non_Unicode to Unicode Conversion takes more downtime and need to be performed
by certified consultants.
Unicode Consumes more resources ie. 40% more then non-unicode.
MCOD:(Multiple Components on One Database):
in earlier cases the database software is installed as many times as required to
support more SAP Components,but causing a confusion of Multiple homes,multiple
listeners,mulitple services etc...
SAP Supports MCOD i.e installing all the Components in one Database Software on
SAME SID(system identifier) but differed by different schema owners.
Example:
SAPERP is installed on SID--PRD but schema owner for PRD is SAPSR3
SAPSCM is Installed on SID--SCM but schema owner for PRD is SAPSR4
SAPSRM is Installed on SID--SRM but schema owner for PRD is SAPSR5
SAPCRM is Installed on SID--CRM but schema owner for PRD is SAPSR6
SAPBI is Installed on SID---BIW but schema owner for PRD is SAPSR7
SAPJAVA is is Installed on SID--- but schema owner for PRD is SAPSR3DB
Schema Owner is the owner of the Database who owns all the tables related to the
specific component
Application Components cannot have same SID,each application requires a unique
SID(system Identifier)but can point to the same SID of database.
Instances are differed by instance numbers and Instance SID, but pointing to
SAME DB<SID> differed by different schema ID.
SAP Recommends not to install the SAP Systems on MCOD due to the following
Reasons.
1.OLTP and OLAP are installed together i,e(ERP and BI should not installed
together)
2.if one Database is dead then all the MCOD systems are not accesible.
3.it is not possible to restore a single system and hence system/DB Refresh is
not possible.

6. *************************************************************************
Installation Inputs:
1.Select the Installation Master(specific to OS/Bit)
2.Click on sapinst.exe(windows)--if it is linux(Unix) then use(./sapinst)--login
as root user
3.select the component
4.Select the database
5.select ABAP or JAVA or (ABAP and JAVA)
6.Select the Installation type(Central System|Distributed|High Availability
System)
Central System Installation:
it will install both the Central Instance and Database Instance on a Single
System.
it is recommended for small companies with users around 100-500.
(Database and DVEBMGS are installed on the same system)
Central Instance: if an instance provides
DVEBMGS(DIALOG,UPDATE,ENQUEUE,BATCH,MESSAGE,GATEWAY, SPOOL and ICM) then it is
referred as Central Instance.or precisely the instance which provides message
server is called as Central Instance.
Dialog Instance:The Instance which provides the services other then message
server are referred as Dialog Instance
ASCS Instance: ABAP SAP Central Services: it is installed as part of the high
availability cluster.
it contains message server and enqueue server.They are installed on separate
instance numbers
From Netwaver 7.3 onwards ASCS is mandatory for all installations(Central
System/Distributed)
Enque Replication Server(ERS):it is installed on all the instances(nodes) to
replicate the enqueue locks between the Enqueue Server and Dialog Instances.it
needs a separate instance number.
No Separate ERS Installation is required in netweaver 7.3 systems.
Note all the above instances are installed on different instance numbers.
ASCS00,DVEBMGS01,ERS05,D07
Database Instance: it is an instance where database is installed and SAP Data is
imported,it contains the entire repository of SAP System.(it contains
sapdata1,sapdata2,sapdata3 and sapdata4)
Distributed System:
The Central Instance and Database instance are installed on two different
physical machines pointing to global host where the executbles are available to
both the instances.
High Availability(Microsoft Cluster System)
These instances are installed as part of the MSCS
1.ASCS
2.CI
3.DBI
4.ERS
5.DI
Central services instance for ABAP (ASCS) installed as part of the First Cluster

7. Node along with ERS.
Additional Modes are installed with Dialog Instance and ERS
Database instance
Central instance
Dialog instance
-----------------------
select the installation type:(typical or custom)
Typical: it is installed with default values and minimal inputs.
Custom: it is used to customise the installation(memory allocation,portnumber
customization,folders/data files path customization etc.
Specify the SID(System Idenitifier): it should not be one among the reserved
id's(refer to installation guide)such as ADD,ALL,CRM etc
Is unique throughout your organization.
Do not use an existing <SAPSID> when installing a new SAP system.
Consists of exactly three alphanumeric characters
Contains only uppercase letters
Has a letter for the first characters(r47,e60)
Specify the Instance Number:(by default for 00 for a new installation)
It consists of a two-digit number from 00 to 96 where 97 is resevred for DAA
service ,98 is reserved for Solution Manager Diagonostics and 99 is reserved for
saprouter.
specify the master password for all the OS/DB/SAP users that are going to
setup(configured/installed) during installation.
sepcify the installation drive for executbales/transport directory etc..
specify the path of the Kernel,Oracle client,Exports DVD's etc..
review the inputs and continue the installation.
each Central Instance Installation requires a Solution Manager Key.
Generate the Solution Manager key from Solution Manager System using transaction
SMSY.
Installation Inputs:
1.Typical : it provide the default values for instance number,memory
allocation,file system,datafile location,trans directory,number of R3loads
2.Custom: it is used to provide the custom values such as instanc
number,memory,file sizes,Location of Directories to be created,....
2.Specify the SID (System Identifier).it is 3 alpha numeric characters which
should not be from the reserved key words like SAP,EPS,ADD,ALL,SID.it should
contain only uppercase letters and Has a letter for the first character
3.Instance Number: it is represents a two digit number ranges between 00-97
4.Master Password: password for all the users that are created during
installation.
5.Provide the path of Kernel Software,Export Software Locations

8. 6.Provide the Path for the SAP Data Files.
7.Review the inputs and Continue the Installation.
Solution Manager Key is not required in Netweaver 7.3 Systems.
***********************InstallationLogs**********************************
The Installation Logs are logged in sapinst_instdir which is located in
C:/program files/sapinst_instdir
/tmp/sapinst_instdir logs on Linux Operating systems.
1.sapinst_dev.log and sapinst.log are used to provide the installation progress
logs.
2.ABAP Loads logs are stored in SAP*.log(sapddic,sapappl0.log,sapappl1.log) the
TASK(*.tsk) specifies what table /view/strucutre/index/key need to be created
R3load is an executable which imports the data into database during
installation
Check the keydb.xml and control.xml which are required to start the aborted
installations.
These files ensure to start from the point where it has been stopped.
keydb.xml stores the inputs provided during the installation
Control.xml stores the installation process
*.tpl -->templates are provided for creating database
objects(table/view/index/key)
*.sql -->sql commands
*.cmd--->command file governs the data import from export Software location(it
contains Taskfile,database templates,database structure file,datafiles (.nnn)
and table of contents(TOC).it commands to build the database and load the
database.
*.tsk--->task files specifies which table/index/key need to be created and data
need to be imported(T,D,P,I)
it is very difficult to load the sap database as one task/process.So it is split
into multiple packages based on the
functionality(Executbales,DDIC,application(appl0,appl1,appl2)view and
structures)
*.log specifies the task log(specifes which of the tables created/data
imported,primary key created,index created)
*DBSIZE.XML-->size of the database
SAPAPP*(package logs specifies the status of the package import)
***************************Installation Mechanism/Process****
1.it checks the environment(OS/DB/Environment variables) and request you to
input solution manager key
Solution Manager Key is Mandatory to install any SAP Component,so that the
system will get runtime support from SAP. The Solution Manager system has to be
installed before installing any other component in the landscape.(solution
Manager does not require any solman key during installation).it checks only on
central instance installation
from Netweaver 7.3 onwards solman is not required.
2.Update the Required Dll's and install common files(os specific)
3.Creates users,groups and assign groups to users
4.Unpack(uncar) the Kernel Executables
5.create Services,create database,create filesystem to load the database,
6.Import the abap database (it is more time consuming process)
7.Update Statistics(it is also time consuming phase)
8.create SAPMMC and Start SAP
9.Run ABAP Reports
Environment Variables:it specifies where the software home is located(java

9. home,oracle home).The Software is called in the application by using home path
because the physical path differs from system to system.
JAVA_HOME /opt/java/jre1.4_12
ORACLE_HOME /oracle/DEV/102_32
Environment path: it specifies the path of the executables where the software
executables are installed.
path /oracle/DEV/102_32/lib;/oracle/DEV/102_32/bin
LD_LIBRARY_PATH /sapmnt/SID/exe
************Checking/Verify/sanity check of the System:
1.Check the Users---> (SIDADM,SAPSERVICE<SID>(win) and on unix <SID>adm and
ora<SID>) (cat /etc/passwd)
2.Check the Groups--> groups provide Authorizations on OS and DB
(ora_dba,ora_sid_dba,ora_sid_oper, sap_localadmin, SAP_globalAdmin-->cat
/etc/group
3.Check the users Vs Groups (click on the group to see the assigned
members(users)
4.Check the Services(SAPOSCOL,SAPSID_00(instance number),sapccmsr)
5.Check the File System(C/D/E/F/ /usr /opt/ oracle and /sapmnt
6.Check the profiles/executables(kernel)/work/log
(usr/sap/SID/SYS/profile
/sapmnt/SID/exe
/usr/sap/SID/SYS/exe/uc/NTAMD64
/usr/sap/SID/DVEBMGS00/work
/usr/sap/SID/DVEBMGS00/log
7.Check the trans directory(bin,data,buffer,cofiles,tmp,EPS,sapnames,log)
/usr/sap/trans
8.Check the Database Users:(select username from dba_users;)
9.Check the Database tables(select owner,count(*) from dba_tables group by
owner;)
SQL SERVER (select table_schema,count(*) from INFORMATION_SCHEMA.TABLES.tables
group by table_schema)
10.check the Database File System and its size (df -h ) or du-h)
11.Check the Installed ports(etc/services)
12.Check the Startup/sapmmc etc
*************************************************************************
Starting and Stopping the SAP System:
SAP System is started by using sapmmc console or using command "startsap"
SAP System is stopped by using sapmmc console or using command "stopsap"
Stopping the System:
1.Planned downtime is required to stop the system for the following reasons:
(Prior Approval and notification to all the business users is required)
Kernel Upgrade(SAP)
OS Upgrade and Patches
Database Upgrade and Patches
Parameter Changes using RZ10(occasionally)
Offline Backup(daily)(only database)
Align down time to other breakdowns(network,lift,UPS,generator,power,Hardware
maintenance,Building Maintenance)
Manual(Accidental or Incidental or wilfull) errors
Natural or Physical Disasters
Changes to exe,profile,listener,work,database,port
block,ipblock,hostblock,change profiles,change parameters etc may requires the
instance restart..
Starting the SAP System:
it is started by using startsap or windows sapmmc console

10. 1.it is started by reading the StartUp Profile
"START_DVEBMGS00_HOSTNAME.PFL"(central Instance)
2.Default parameters are provided from DEFAULT.PFL
3.Instance specific parameters are provided by Instance profile
SID_DVEBMGS00_HOSTNAME.pfl(instance profile)
Startup Profile
a.)copy sap executbales using executable "sapcpe" from kernel to executable
directory
/usr/sap/SID/sys/exe/UC/OS&BIT(NTI386)// to /sapmnt/SID/exe or
/usr/sap/SID/DVEBMGS00/exe
Note: In earlier version kernel is located in run directory and the system is
started using executables from run directory.Now the Kernel is setup based on
32|64 bit,Unicode|non-Unicode,OS and DB.
So the kernel is copied from the kernel directory to shared mount
//sapmnt/SID/exe or Instance Directory /usr/sap/SID/DVEBMGS00/exe
while starting it writes logfile into /usr/sap/SID/DVEBMGS00/work/sapcpe.log
b.)starts the database by using executable(batch) strdbs and writes log into
stderr0(standard error) logs
on unix environment the database is started by using command startdb and writes
the logs into sidadm home directory(startdb.log)
c.)starts the message server by using msg_server.exe and writes into stderr1 and
dev_ms
d.)start the dispatcher by using disp+work and writes into stderr2 and dev_disp
e.)start the work processes by using disp+work and writes into dev_w0,dev_wn-
1....
f.)start the internet graphic server by using igswd.exe
Note:Standard Errors(stderr) are filled to granular level when the trace
parameter rdisp/TRACE =0,1,2,3 (increase trace level) is activated..
The parameter rdisp/TRACE is set in any of the profile in RZ10 and restart the
instance.
The Work Directory is filled with the enormous log files so, ensure that the
above parameter is reset to '0',else the system will be very slow and finally
gets halted...
The Trace files are written to work directory.
Instance Profile:(<SID>_DVEBMGS00_HOSTNAME)
it provides work process configuration,memory configuration,buffers
configuration etc...
These Logs are displayed in work directory and known as developer traces which
can be displayed through ST11.
.......
The SAP System has to be started after a kernel Upgrade but it could not be
started??
How do you start evaluating the SAP startup issues?????
*********************************************************************
Troubleshooting SAP startup problems in Windows/Unix

11. 1. Check whether the Database is up and running. Check the database traces in
E:oracleSIDsaptracebackgroundalert<SID>.log, startsap.log, v9start.sql,
stderr0,1,2,3,4 in work directory
startdb.log in home directory of <sid>adm
2. Check whether Listener service is running, if not there may be an issue
with listener (port and hostname) ora-12541(Listener not started or listener is
running on different port/host
• cmd>lsnrctl status -->to know the status of listener
• cmd>lsnrctl start --> to start the listener
• cmd>lsnrctl stop --> to stop the listener
if the listener is not started then the error ora-12541 occrus with an error
message listener not started.
3. Userid and password mis-match for schema user id (ora -1017) (SAPSR3,
SAPSID, SAPR3 based on versions
• Check the Environment Variables are properly set
Example Oracle_home, db_ora_tnsname =SID
• User has sufficient privileges like sapconn role, sapdba role
• Schema Owner Locked with error ora-28000 will be unlocked by using
command
• Sqlplus>ALTER USER SAPSR3 ACCOUNT UNLOCK;
These Errors are found in the trans.log (execute R3trans •d) to check whether
database is reachable to work processes
R3trans -d should result (0000) or (0004) if it is (0012) then there is an error
connecting to database.
4. Wrong entries are maintained in tnsnames.ora, listener.ora or sqlnet.ora.
In the current version of SAP the above entries are maintained in
usr/sap/SID/sys/profile/oracle along with /oracle/SID/102_64/network/admin
Modify the entries based on hostname, port number, protocol and oracle Home
5. Check for Ora-600(internal hardware Error) and escalate to hardware, SAP
and Oracle where restore and recovery may be required
oracleSIDsaptracebackgroundalert<SID>.log
6. Check for ora-1578(Data Block Corruption) and restore and recover that
block from valid database backup(oracleSIDsaptracebackgroundalert<SID>.log)
7.Message Server is not started (check dev_ms, startsap.log, stderr0, 1, 2, 3,
4).Hardware changes, IP Address Changes, hostname change will reflect in message
server log. Check for customer key in the dev_ms log. Ensure that ports
3600,3900 and 8100 are not blocked.
if the log dev_ms does not contain hardware/customer key then assume that
message server is failed.
8.Profiles are not available to start the database, dispatcher and message
Server (If there is a file system change or the respective directory is not
mounted on UNIX (/usr/sap/SID/SYS/exe/profile)). if the profiles are corrupted
then Copy the profiles from an active system and modify the entries accordingly
and start with minimal parameters or restore from the valid backup
9.Kernel is upgraded but not related to the database/Unicode/32/64 bit operating
system.(select the right kernel before upgrade)
10.Execute script "rootpre.sh or saproot.sh " to set the permissions for kernel
executables on Unix after kernel Upgrade
11. Dispatcher could not start with error message DISPATCHER EMERGENCY
SHUTDOWN .Analyze the dev_disp Dispatcher developer trace
Check for the logs in Event Viewer (EVENTVWR.exe) and check for disp+work in
task manager

12. The "services" file, which contains TCP and UDP services and their respective
port numbers. This plain-text configuration file is located under
winnt/system32/drivers/etc.(Ensure that dispacther ports(3200) are not blocked.
12.Check Dispatcher Monitor (DPMON.exe), which is located under
/usr/sap/SID/sys/exe/run (dpmon pf=instance profile)m-menu
13.Dispatcher dies due to a database connection problem or A connection to the
database could not be established because either the SQL login specified in
parameter is valid or there is a problem with environment variables or database
might be down.(R3trans -d results trans.log which gives detailled information
about connecting to database
14.Work processes could not connect to Database (evaluate dev_w0, dev_wn-1,
dev_wn-2 etc).This Log will explain the complete process of Connecting to the
Database along with the status of each step.
15.Too Many work process are configured (Processes should configure as per
formula i.e atleast 75mb should be allocated to each process).Or too many
processes are configured or the number is more then 100.
16.Buffer Areas Could not created (Program Buffers, Table Buffers) PXA (Program
Execution Area) Initialization Failed . Shared Memory is not sufficient to start
the dispatcher (errors with shm in dev_disp) An ABAP dump saying
"PXA_NO_SHARED_MEMORY" is generated as soon as a user logs in.
17.Identify the error that starts with Ora-1017,600,1555,1578,255,272 etc
18.SAP does not start at all: no message server and no dispatcher
19.The message server and the dispatcher do not start at all in the SAP MMC. The
following error when trying to view the developer traces within the SAP MMC: The
network path was not found. No new developer traces written to disk (under the
"work" directory.)The network shares "saploc" and "sapmnt" do not exist. Re-
create the "saploc" and "sapmnt" network shares. Both need to be created on
the /usr/sap directory, Check whether the Drive is mounted.
20.Users get "No logon possible" messages. Work processes start but no logins
are possible. Users get the login screen but the system does not log them in.
Instead, they get this error: No logon possible (no hw ID received by mssg
server). The reason is because the "services" file is missing. Example: SAPmsTST
3600/tcp. Edit the "services" file and add the entry.(/etc/services).check
whether offline backup is scheduled and running
21.SAP MMC Entries are missing to start the sap System. It was happened due to
abnormal termination or due to virus or change in the <SID>ADM password. Use
sapstartsrv.exe to create the SAP MMC Entries.
22.Check whether the services saposcol and SAP<SID>_NN are running. If not check
the user permissions and run them manually.
1.sapcpe
kernel outdated
permission on cpe
permissions on /sapmnt/SID/DVEBMGS00/exe
2.Database --.startdb.log,stderr0,startsap.log,alter_sid.log
ora-600,ora-1578,ora1017,ora-12541,ora-28000,ora 1146,1034(oracle not available)
check whether database is terminated abruptly and asking for media
recovery,control files are lost,redolog files are lost------>read the
alert_sid.log for dberrors

13. 3.Start message server stderr1,dev_ms
hostname change,hardware change,ipchange,(the Customer key should be logged in
dev_ms file)
portsblocked---3600,3900,8100,file system change or if profiles are deleted or
not available
4.Start Dispatcher
shared memory/virtual memory is not available,too many processes configured then
available resources,buffer areas are configured beyond the allowable
limit/resources
refer to dev_disp,stderr2,if any of the work processes are not started/if it
could not connect to message server then dispatcher fails.
5.Start Work processes-->Memory is not sufficient to start,connectivity to
database failed,shared memory realm does not exist,memory is not released(ipcrm)
cleanipc <instance number>
JRE is not available
Environment variables are not available
display path is not set
free space not availble to write logs/no free space in database
Check windows event viewer
virus deletes the files,so restore from backup or recreate them from an existing
system
use top command in linux to check the memory usage
execute R3trans -d to check the connectivity from instance to Database. it
writes trans.log into the directory where command is executed.
Note: if the error could not be traced then use parameter rdisp/TRACE in
instance profile.
use command cleanipc or ipcrm to clean the shared memory.
*************************************************************************
Logging to the SAP System:
Provide Userid and Password along with logon Client and Language.
the two users sap* and ddic are provided by default with master password
provided during installation.
user sap* is built at kernel and does not contain any user master record,so it
is created as many times as it is deleted at database level with default
password "pass".
to enable sap* login set the parameter login/no_automatic_user_sapstar=0
by default it is set to 1.
1.Execute transaction sick/sm28 (initial consistency check).
it is used to check the consistency between OS,DB and SAP Kernels.
it also checks whether the processes are configured as per the instance(minimum
one enque/one btc/one update and message server)
Example; oracle 10.2.0.1/11.2.0.1 are not supported,
windows 2008 sr2 does not support base version of SAP Kernel which needs a sap
kernel upgrade to 111 .
2.SE06(initialize the correction(Change/correction Transport System)
it contains two radio button options(standard Installation) System/DBCopy
it is used to initialize the system and to adopt the changes and also to add to
the landscape.it resets the System ID to the current SID(system Copy).This
transaction prompts to configure the landscape in STMS in client 000.

14. System Change Options:
There are two settings
Modifiable:The Development system is set to modifiable where are as QAS is also
to set to modifiable(can be set to restricted modifiability).
Not Modifiable:The production system is set to not modifiable.(no changes
allowed in the entire system)
No changes are allowed by developer or functional consultant.
3.Configure STMS in client 000 client.(SAP Transport Management System)
STMS contains two configurations for systems:
1.Domain Controller
2.Member of the Domain
1.Domain Controller: it is used to manage all the systems in the
landscape,generally this should be configured in an highly availbale system,but
due to non-availbility of Quality and Production systems during the day one of
implementation,it is configured on Development System.DC can be moved to any
other system in the landscape.
2.Member System. All the other systems except Domain controller are referred as
member systems.
Execute STMS, A pop-up window is prompted to configure a domain or include in a
domain.
specify the domain as DOMAIN_SID(DOMAIN_DEV) and specify the instance and save
to configure the domain or include in the domain.
3.virtual Systems: These systems are created to configure the landscape.
These are used to address the change requests that are created in development
system.these systems does not exist and all the change requests are addressed to
these virtual system ID's.The virtual systems are replaced by real systems and
gets all the requests into import queue.
if the virtual system name changes then all the requests need to be added to the
buffer manually.
4.Slicense: it is used to apply the license to the sap system to get runtime
support.The license key is generated in the market place based on hardware
key,installation number,system number and valid until 31.12.9999
sap also provides a maintenance certificate that is valid for 3 months which
need to be renewed for every 3 months.(this is to ensure that customer pays
their AMC(Annual Maintenance Contract) regularly.
5.SM36: Define the sap standard background jobs(delete old abap dumps,delete ols
spool requests,old updates,old btc jobs,old batch input logs.
6.DB13: Define the database specific background jobs.(backup,redo backup,update
stats,adapt next extents).perform a full backup using DB13
7.RZ10: import profiles of the active servers into database(Execute RZ10-
utilities->import profiles of active servers).
configure the parameters such as number of processes,buffers,memory areas)
8.SU01 : Create master users in SU01 and change password of sap* and ddic.
sap* is the only user which does not contain user master records and is
built(created) as many times as it is deleted with password "PASS".
9.SR13 Configure Library to get the application context help

15. execute SR13-->new entries-->
variant-Internet
Platform--win32
Area--Documentation(IWBHELP)
ServerName: help.sap.com
path :erp2005_ehp_06/helpdata
language :en
check the default and save
Navigate to the screen using transaction and use Help Menu-->aaplication help
10.SPAM/SAINT are the tools used to update the system with support
packages/pacthes/add-ons etc(Update the spam and apply the relevant packages)
11.I18N(ADOPT LANAGUGES): To Add the new languages into SAP System
12.SMLT(LANGUAGE TRANSPORT):it is required to provide MNLS Support to customers
for which the additional languages can be imported using SMLT
13.Create client in SCC4: SAP provides three clients(000,001,066) by default
which could not be used for customer runtime.So it is required to create clients
in SCC4
14.Perform client copy(Local,remote and client export and import)
15.SFW5(Activating Business Sets).
SAP provides various inbuilt business functions(sets) which can be activated
based on the customer requirement.Each activation requires additional license
fees(oil,gas,mining,textile,utilities etc.)
Execute Transaction SFW5:
Select the Business Set/functions save and activate.once activated these
business sets could not be deactivated..(take a backup before activating the
system)
Do not activate the conflicting Business Sets(ex:Banking and Insurance)
*************************************************************************
Kernel Upgrade: Kernel Provides runtime executables for SAP System.
kernel upgrade is the process of replacing the existing executables with a new
set of executables.Kernel Upgrade is required in the following scenarios.
1.To Ensure that SAP Systems are compatible with OS and database.
2.While applying support packages,patches,add-on, languages and transports
3.During SAP Upgrade or OS/DB Migration,OS/DB Patches,OS/DB Upgrade etc
4.SAP Recommends as part of the EWA (Early Watch Alert)
5.To fix the runtime issues that are cropped up during runtime.
(example: Update failures,enque lock failures,deadlocks,functionality issues
etc...)
6.SAP Servers Routine/periodical Maintenance
7.SAP Recommendation as part of the security threats
Kernel is based on operating system,database,32/64 bit,unicode/non-unicode etc..

16. (because of SAP Kernel,SAP System is said to be OS/DB Independent.
Third party executables like sapgenpse,sapcrypto.dll,dbatools,igs,igshelper and
saprouter may also need to be updated during kernel Upgrade.
SAP Provides two sar
files(sapexe_version,sapexedb_version,dbatools,igs,igshelper) one is db
dependent and db independent(OS dependent)
Process of Kernel Upgrade:
1.Download the Kernel from the market place.
(http://service.sap.com/swdc-----.complimentary software)
2.Create a folder kernel_Timestamp(Date and Time) ex: Kernel_23092012
or Kernel_333(kernel version)
3.Copy the downloaded files into newly created folder.
4.schedule downtime-->upon approval
1.Stop the application servers
2.Stop the database
3.Stop the services(saposcol,sap<SID>_00,sapccmsr)
5.Create a directory Kernel_OLD_Version and Copy the old kernel(to rollback in
case if the system does not start)(match the size of existing kernel and copied
kernel-->to ensure that entire kernel is copied.
6.Copy the executables from newkernel (step-2) into existing(runtime) kernel by
overwriting the executables.
cp -pr kernel_333/* /usr/sap/<SID>/SYS/exe/run/
7.Check the Permissions for dbatools and db libraries
8.run rootpre.sh or ./saproot.sh to set the permissions for brtools,saposcol
and set the userbit.
9.start the database,services and sap application servers.
10.check the kernel version by using disp+work
if the sap system does not start then troubleshoot using developer
traces(stderr0,1,2,3,4),dev_ms,dev_disp,dev_w0,w1,w2,w3....wn-1
*************************************************************************
SPAM/SAINT Update:
SPAM/SAINT tool is used to apply support packages and add-ons.This tool has to
be updated to current version to comply with sp/add-on's
SPAM/SAINT update does not require any sequence.Update from Lower version 21 to
42 or 45 or 47 is possible.
spam/saint is based on WEBAS Version(620,700,701,730)
1.Download spam/saint from market place(using option complimentary software)
2.Login to 000 client and load the packages from front end.The .sar/.car file is
decompressed and loaded to /usr/sap/trans/EPS/in in the .pat format
3.Use the option "import spam/saint update" to update the SPAM/SAINT.
4.The spam/saint screen disappears(empty screen) and the error
LOAD_Program_not_found occurs.Restart spam and continue to update spam.
5.The SPAM/SAINT Update may abort in EPILOGUE Phase,Restart spam and continue to

17. update spam.
Depending upon the spam version the spam restart may be required more then once
until the spam import queue is GREEN
*************************************************************************
Client: it is an independent business Unit which is represented by three
digits(ranges from 000 to 999).it is a data separator and it is the first field
to login along with userid,password and language.
sap provides three default clients 000,001,066 with specific purpose.
000 client provides default templates for creating other clients.it is also used
to apply support packages,patches,add-ons,languages etc...
001 is backup client for 000(now 001 can be used for production purposes:
Ex:Solution manager and Dual Stack Java Engines)
066 is an early watch alert client which is used by SAP to generate EWA Reports
for every six (one)months.
what is the Need for Creating a New Client????????
As the sap standrard clients(000,001 and 066) cannot be used for customizing and
development,there is a need to create new clients based on the customer
requirment.
Client is a 3 digit number in the database Table (T000) which is represented by
a field 'MANDT'.Client is a data separator in the database tables.
The tables with field MANDT are called as client specific tables.(only exception
is table T000 because it maintains client information).The Tables with out field
MANDT are called as cross client tables.
Clients are created in Transaction SCC4.
Specify the Number of the Client Unique no(000-999) as 000,001,066 are reserved
the remaining available client numbers can be used..
1.Client Number :(Three digit number)
2.Client Description(specify text)
3.Client Location(location of the client)
4.Currency:(currency to be used in client)
5.Client Role:
SAP Provides 6 predefined Client Roles: CUST|TEST|SAND|QTST|TRNG|PROD
Client Specific Options:These are used to specify whether changes are allowed in
the specific client.
a.No Changes allowed: No Changes are allowed in this Client for
development/customizing
TEST(ING) Client is only used for Unit Testing so no changes are allowed.
QTST(Quality Testing) is used for Integration Testing,so no changes are allowed.
TRNG(Training Client) is used for training to end users,so no changes are
allowed.
PROD(Production Client) is used by end users for business,so no changes are
allowed.
b.Changes allowed but not recorded:(customizing client specific is allowed)
SAND(BOX)Changes are allowed but not recorded in this Client(facilitate
functional team to work on this client before they work on Cust Client.
C.Automatic Recording of changes:
CUST(Customizing): There will be only one client which is set with ARC in the
SAP System Landscape.
The Changes are allowed and recorded to change request for transporting the

18. changes from one system to another system in the landscape.
d.Changes Allowed but not recorded/nor transported:
The Changes are allowed but not recorded nor transported(some times TEST client
may have this option)
changes to Repository Objects and cross client objects are allowed
changes to repository objects allowed (ccc not allowed)
changes to cross client objects allowed(rep not allowed)
No changes to Repository Objects and cross client objects are allowed
(Production Systems are set with this option)
Protection Level:it is used to protect the client information from copying and
overwriting.
Level 0 : Client Copy is allowed(external availability)/Overwriting is allowed
Level 1 : Client Copy is allowed(external availability)/no Overwriting
Level 2: Client Copy is not allowed(no external availability)/no Overwriting
Production systems are set with this options.
Ecatt:(Extended electronic Computer aided Test Tool)
SECATT(is allowed to run /no run in production systems they are not allowed
after Go_live.
This is used to massively transfer the data using transaction SECATT
Logical System: To identify the client uniquely in the landscape.it is in the
naming convention <SID>CLNT<CLNT NUMBER>
it is defined in transaction SALE.it is mandatory in BW Systems as the Data
transfer between clients is performed by using logical systems.
When the Clients are created in SCC4 only an entry in Table T000 is created with
out any data.it is inbuilt with a user sap* which is available at kernel level
and created as many times as it is deleted with default password "PASS".
sap* default password is 06071992 and ddic default password is 19920706 which
is overridden by master password provided during installation.
Client has access to the cross client information and repository objects,but it
does not contain any client specific data.
So inorder to get the client specific data a client copy is required from
default template client i,e either from '000' or '001'.
Netweaver systems like BI a client copy from 001 is recommended,or 001 can be
used as production client.
********************************************************************************
*********************************************************
Client Copy: it is used to copy the client specific data between clients.
There are three types of clients copy methods
1.Local Client Copy
2.Remote Client Copy
3.Client Export and Import(Transport)
1.Client Copy Local(SCCL): it is used to copy the data between two clients in
the same system.
2.Remote Client Copy(SCC9): it is used to copy the data between two clients from
two different systems(the systems are in the landscape and reachable through
RFC)
3.Client Export/Import: it is used to Export the client data from one system and
transport it to other systems which are not in the landscape.(not reachable
through RFC)
Prerequisites of Client Copy:
1.It is performed always on the target client

19. 2.it always copies/pulls the data from source client
3.check the space in DB02 and ensure that enough space is available for client
copy
4.Users should not be logged on the source client(lock the users in source
client)
5.client copy should be performed in the background mode only and ensure that
atleast two btc processes are available.
6.Ensure that all the lanaguages/support packages/add-ons are applied before
client copy.
7.identify the space required for client copy using
RSTABLESIZE/RSSPACECHECK(report gives size of current client)
8.Define RFC Connection between two clients during Remote Client Copy
9.Ensure that /usr/sap/trans directory has enough space to perform client export
and write client copy logs
10.select the profile to specify the data to be copied from Source client to
target client.
11.Ensure that STMS is Configured in 000 Client
12.Client Copy always overwrites the data and data merging is not possible.
13.it is recommended to delete a client during client refresh In SCC5 and copy
from the source client.Client Deletion Consumes more time in hours|days.(example
a copy from PRD Client to QAS client)
14.Client Copy logs are displayed in SM37/SCC3/SM50
15.The source system and target system version and patch levels should be same
to perform client copy. (it effects in remote client copy and client export and
import)
********************************************************************************
***************************************************
Local Client Copy:
Execute SCCL on target System.
Target Client is Displayed
Select the Profile
specify the Source Client
schedule as a background job/or start immediately in the dialog mode.
Profile: it specifies the type of data that need to be copied from Source
Client.(SAP_CUST is mandatory profile to setup all the clients)
SAP_ALL--Copies the cust,application and usermaster(to setup training Client)
sap_appl--Copies cust and applicaton
sap_user--only user master
Client Copy Copies only the entries from the source client and paste(copy) them
in the same table with target client.(different MANDT).
The Number of tables will not increase due to a client copy.The entries are
copied with a target client number.
Test run is used to check the resources that are required for client copy.
Remote Client Copy :
1.Define RFC Connection between Target Client and Source Client
2.Execute SCC9
3.Select the proflie
4.select destination RFC(source system and source client are displayed)
5.schedule as a background job or run in the dialog mode.
Note:The Source System and Target System should contain the same version and
patch levels)
***********************************************************************
Note Assistant:SNOTE is used to fix the runtime issues,bugfixes,program
corrections.
Notes are of three types
1. SAP Notes provide informative Notes such as 822379/822380/669669.it provides

20. known problems in support packages,addons, installations, upgrades and other
technical/release information.
2. SAP Provides Manual Correction notes such as table creation,table
entries,uploading data,upload images etc.it provides step by step information to
perform the changes to the tables entries manually.
3. SAP Provides notes for program corrections which can be applied through
transaction SNOTE.
SNote is used to modify the sap standard repository programs with out any object
access key.SAP provides SSCR(SAP Software Change Registration Keys to modify the
standard Objects where as snote does not require sscr keys.
if there are any bugs,fixes which are identified by SAP are fixed through SAP
Notes.
Sap Notes provides the program corrections by commenting the faulty code and
inserting the corrected code.
Execute SNOTE:
menu goto-download note-specify the note number and execute to download-
The Status of the Note is
New--when downloaded into SAP System
obsolete--it is overwritten by support package or no more in use.
cannot be implemented---it cannot be implemented.(Informative/manual note)
completely implemented----implemented when it is a corrective note
can be implemented----note is ready for implementation
Corrective Note: Comments the faulty code and inserts the corrected code.due to
this reason notes can be reverted until it is overwritten by a support package.
select the note and click on execute to implement the note.
(note: saposs connection is required to download the note)
The Note is applied in development system and recorded to a change request and
transported to other systems in the landscape.
Snote is introduced in SAP R3 46C version and the changes are applied with out
any SSCR key.
Reverting the Note: Select the Note in SNote and select the option reset sap
note implementation
(Note: Except kernel and sapnotes other sap objects could not be
reverted(Supportpackages,support stacks,Languages,add-ons)
***********************************************************************
Support packages:
The group of Notes,bugfixes,program corrections,enhancements are grouped into a
support package.
Support packages are released by sap from time to time.
Group of support packages are referred as Support Stacks.(ABAP 12,13 basis 12,13
etc)
Group of Support Stacks/support packages are referred as Service
Releases(SR1,SR2,SR3...etc)
ECC6.0 base version is patch level 3 SAPKB70003
ECC6.0 SR1 is on patch level 6 SAPKB70006
ECC6.0 SR2 is on patch level 9 SAPKB70009
ECC6.0 SR3 is on patch level 14 SAPKB70014
until above only the patch level changes(example: SAPKB70001 to SAPKB70024)
Note: Support Packages,Add-ons,Languages are also transport requests
initiated/generated from SAP.They can also be imported from STMS instead of
SPAM/SAINT/SMLT
Enhancement Package:

21. it is used to provide enhancements to the current system and to avoid frequent
SAP Upgrades.
it changes the version/kernel and release(SAPKB70021 to SAP 70101,70203,
73101).-
Pre-Requisites for Applying Support Packages/Add-ons/Languages:
1.Ensure that stms is configured in client 000
2.depending upon the size of package apply through front end if it <5mb
and use the option application server if it >5mb
3.Ensure that 2 free btc processes are available
4.perform a backup before applying support packs
5.always apply in btc mode(so that it runs even the user is logged out)
6.Perform Kernel Upgrade especially three executables tp,r3trans and sapcar
7.apply patches in the number sequence.(1,2,3,4,5,6),no number jumping is
allowed. i.e, 10 to 12 it is not allowed.(patches are incremental)
8.apply patches in the sequence of landscape(DEV,TRN,SAN,QAS....PRD)
9.apply patches in the sequence of patches(BASIS,ABA,BW,PI,.....)
10.Read note 822379 for known problems that are populated by patches
11.bind the patches or individual(combined or individual)
group the patches like 12,13,14 to apply together
12.perform spam/saint update
13.ensure that enough space is available in /usr/sap/trans
14.ensure that enough space is available in database space through DB02
15.configure Router(TO GET REMOTE SUPPORT FROM sap)
16.schedule rddimpdp/rddnewpp background jobs in client 000 using user ddic
17.ensure that functional/development team is available to adopt changes
18.lock the users(EWz5 transaction)
19.as the support packages are hot packages no downtime is required(no system
shutdown)
20.support packages cannot be reverted
21.There should not be any aborted packages(resolve the aborted package before
continuing with new one
22.Record the modifications to a transport request and include them while
applying support packages in the other systems of the landscape.
23.check the dependencies from note 822379 before applying support packages.
Modification Adjustment:
The Patches brings some new functionality into sap system which may require
adjustment with the exisiting objects.
Example: A+B=20 is the object provided by installation
A+B=30 is the object modified by customer(manually using sscr key or
through a Note)
A+B=28 is the object status after patch(SP) application.
SPDD(Data Dictionary Adjustment):when ever the objects related to Data
Dictionary are modified then the changes need to be adopted in
SPDD(domain,dataelement,table,index,view,structure etc)
The Functional/Development Teams assistance is required whether to go with
old,remain with current or adopt the new (proposed) Changes.
The adoption/decision is recorded into a change request,released and
subsequently transported to other systems while applying support packages.These
Transport requests are included in the modification adjustment phase as manual
changes are not allowed in other systems except DEV(even if allowed it consumes
more time)
SPAU(repository Objects)when ever the objects related to repository like
transactions/programs/reports/menus/screens/functional modules then the changes
need to be adopted in SPAU.The adoption/decision is recorded into a change
request,released and subsequently transported to other systems while applying
support packages.These Transport requests are included in the modification
adjustment phase as manual changes are not allowed in other systems except DEV

22. All the above prerequistes turns into error if they are not checked properly.
Support package Mechanism:
The Support Packages are applied using SPAM/SAINT.
1.The ".car" or ".sar" files are decompressed into EPS/in directory using
SAPCAR.
2.tp connects to the database and checks writability to trans dir
3.sapcar decompreses(uncar) into .att(attributes) and .pat(patch files).
4.tp creates cofiles and datafiles based on .att and .pat files.
5.tp writes the job steps of import into TRBAT and TRJOB tables.
6.R3trans is the executable initiated by tp to transport the objects(run the job
steps)
7.R3trans is used to import/export(test,ddic import,main import,import of
tables).
8.Rddimpdp/rddnewpp and other rdd* job reads the job steps from TRBAT and TRJOB
and run the programs to generation,conversion,activation,etc...
9.The Complete logs are written to Log directory
10.Monitor the tmp directory during import
11.Monitor the TPlogs,sm50,sm66 and sm37(use al11 transaction monitor the log
files from GUI).
Add-on/plug-in's:
These are used to provide the additional functionality to the existing system.
add-ons like BW,VIRSA,PIBASIS,STPI are applied through SAINT.
Read the note 822380 for known issues related to add-on's.
Process:
1.Download the add-on from the market place.
2.copy the add-on to /usr/sap/trans directory.
3.uncar the file using commands 'SAPCAR -xvf Addon.sar'
4.it will create .att/.pat files into /usr/sap/trans/EPS/in directory.
5.load the add-on from the application server.
6.select the add-on and continue to apply the addon.
7.Most of the addon's requires a password which is provided in the add-on
specific note to ensure that all the dependencies/conflicts are checked.
8.Enter the password from the note and continue to apply the add-on.
9.Add-on displays the package and suggest to select the packages(addon packages)
or recommends for the minimum package.
10.select the recommended packages if available and then continue to apply the
add-on.
11.The logs which are specified for support packages are applicable to addon's
and languages.
12.confirm the add-on.
Language Import:
SAP Provides by default english and German languages(EN and DE).
The additional languages can be imported into sap system based on customer
requirement.
1.Adopt the language through i18n (execute i18n/rscpinst(report in sa38))
add the language,save and activate.
2.it will prompt the activation message and recommends to setup the language
parameter in RZ10.(zcsa/installed_languages=E,D,Z,)

23. 3.Download or copy the language import file into /usr/sap/trans
4.Add the language in SMLT and specify the supplementary language.
5.Specify the path of language (/usr/sap/trans) and import the language from
SMLT.
6.The Language import is scheduled through a background job which can be
monitored in SM37.
7.The Language Pack is dissembled into around ten pat files which are displayed
in STMS.
8.The Langauge import is completed which can be displayed in STMS/SMLT.
9.The same logs of support packs/add-on's are used to troubleshoot the runtime
issues.
*************************************************************************
Systems Role:
Development/Quality/Production/preprod/sandbox/migration/payroll/testing/trainin
g--sap allows to have upto 8 systems in landscape.
(DEV/QAS/TRN/PPD/PRD/MIG/PYR/SAN)
Change Management:
SE06: As part of the post installation the correction(change) transport system
settings are set.
i,e The System is adapatable to changes based on System Settings and Client
Settings.
System Settings:(SE06/Se03)
There are two settings (modifiable and not modifiable).
Modifiable: The System is allowed to make changes to the repository objects in
the SAP namespace/customer namespace.it is also possible to restrict the objects
partially modifiable.
This is set in Development and SAND BOX Systems Only.
Not Modifiable: The System is not allowed to make changes to the repository
objects in the SAP namespace/customer namespace.
This is set in all the other systems except DEV/SAN/TRN Systems ie QAS,PPD and
PRD systems
Client Settings:These are set in SCC4.
Automatic Recording of Changes:allowed in DEV system
No Changes are allowed is set in QAS/PRD Systems.
So the Required changes are performed in the development systems/recorded into a
change request,released and transported to other systems.
Application Data,Transaction Data,User Master Data,This is live(runtime data)
data which is modifibale in QAS/PRD Systems irrespective of system/client
settings.
Repository Data,Cross Client Data,Client Specific Data
ecatt(electronic/extended computer aided test tool(SCAT)(SECAT) are the settings
which are used to protect the data.This is System Data which is modifible based
on System/Client Settings
Transport Domain Controller:There will be only one Transport Domain Contoller in
the Landscape.it is used to maintain the information of all the systems in the
landscape.
initially the development system is configured as Transport Domain but later it

24. can be moved to other systems like QAS/PRD(but mostly remains in DEV only)
Login to 000 Client of development system as user like DDIC.
execute STMS to configure STMS.
execute 'dico' in the stms screen to delete STMS Configuration to move the
domain controller to any other system)
when stms is executed in 000 client apop-up window is prompted to configure
domain contoller or member of the transport domain.
provide the details in the pop-up window like (domain host,domain instance
number,Domain_SID etc and save the configuration.
Defining virtual systems:
During the implementation the development system is configured and other systems
like QAS and PRD are not available/procured(due to cost/warranty for earlier
procurement as they will not be in use until development is finalized).
The Systems which does not exist and likely to be replaced with real systems(in
future) are referred as Virutal Systems.These are used for addressing the
transport requests.
Defining the Transport Landscape
Execute STMS-->Transport Routes-->change mode-->Configuration-->standard
Configuration-->Three Systems in Group.(select Development/Quality and
production system).
Single System Landscape:
There will be only one system in the landscape which needs to provide all the
client roles(CUST,TEST,SAND,QTST,TRNG and PROD).There is no consistent
environment for produciton and quality clients as the repository and cross-
client objects are shared between all the clients.
This system is not recommended for production use and can be used for test and
demo purposes.The Objects which are modified in CUST Client Could not be used in
PROD Client
Two System landscape:
There will be two systems in the landscape where DEV and QAS are installed in
one Box(i.e 5 clients in one box) and the PROD Client in another system
The Quality system and Development objects share the repository and cross client
objects and so the quality is not consistent and stable.
This is the least recommended landscape by SAP.
Three System landscape:
This is the optimal landscape where three systems are installed separately in
the landscape and they are consistent and stable.
***********************************************************
Multi system landscape:The Above landscape does not provide an environment for
sandbox to play around with repository and cross client objects.
So the sandbox,preprod and payroll may be installed on separate systems.
Transport Group:Each system is assigned with a transport group when it is
included in Landscape it is GROUP_DEV,GROUP_QAS,GROUP_PRD.
i.e these three systems are having their own transport directories.
if all the systems are sharing the same transport directory then it is called as
common transport direcotry.(GROUP_DEV).
CTD should be on higly avaiable shared drive.(preferably on SAN)
configuring Transport Groups
Execute STMS-->overview systems-->select the system-->Communication tab-->change
the transport Group;
Use tab transport tool-->set the parameter transdir=/usr/sap/trans

25. similarly set environment varibale on all the systems DIR_TRANS=/usr/sap/trans
Transport "Target Groups":These are used to setup the landscape when more then
three systems are configured.The Extended Transport Control mechanism is used to
transport the objects to transport groups instead of systems.
Define Transport target Groups in STMS(stms-transport routes-->hierarchical
editor-->transport target groups create--->specify the systems-->define
transport routes using extedned transport control program.
******************************************************************
Adopting the SAP System
The SAP System is Installed and Updated to get the current functionality(Support
Packages,patches,add-on,languages)
The System is ready to be used by the Functional Team to Adopt according to the
customer requirements.
SAP Provides various predefined templates which are industry specific and can be
used directly with out any modifications.
Customizing: it is the process of keying entries into the predefined tables.
Client Specific Customizing:if the tables contains a Field 'MANDT' then it is
referred as client specific Customizing and the changes made reflects only in
that specific Client.
Example: Company Code,Chart of Accounts,sales organizations, divisions,
plants,warehouses, etc.......
Cross-Client Customizing:if the tables does not contains a Field 'MANDT' then it
is referred as cross-client Customizing and the changes made reflects in the
entire system.
Example:Client table 'T000',Logical Systems table TBDLS,Password Restriction
Table USR40;
Development:when ever a new field,table,program,report,screen,menu, function
module,transactions are created or modified then it is referred as
Development/Modifications.
Repair: Modifying the objects in the non-original system
*************************************************************************
Transport Mechanism:
In a traditional SDLC(Software Development Cycle) the Objects are developed in
Development System and Compiled into Packages and copied to
staging/testing/training/production System at File System Level.
In SAP System the object changes takes place in database(all the objects/tables
resides in database except Kernel/profiles/trans directory).
when the Changes are performed(initiated) they are recorded to a change Request.
The Change requests are stored in table E070. The Change Request Point to the
objects which are modified and gets released to convert the Database specific
changes to OS/DB Independent Transport requests.Once released the Change request
releases the locks and the transport requests are generated at OS Level in trans
dir.No Changes can be made to transport requests as they are compiled into
machine Code.(sap is required to inerpret this machine code)
The Transport Requests can be imported into as many systems as possible to adopt
the changes.
Change Request: it contains the changes intitiated by Developer/Functional
Consultant
The Change Requests resides in Table E070 and created by a project Lead/Manager
and assigned to the team members as Change Request tasks.

26. The Team Members changes the Objects and record to the assigned change Request
tasks and releases them.
once all the associated tasks are released then the change request is released.
if the change requests are related to client specific objects then it is
referred as Customizing change Request.
if the change requests are related to cross-client objects or development
(repository) then it is referred as workbench change Request.
The Requests are created in Transaction SE01(earlier SE09/SE10) by a Project
Manager/Team Lead. The User Should have necessary authorizations to create
change requests.
The Development Team/Functional Team can save the changes only to the allocated
change request(task) and similarly they are only authorizsed to release them.
Customizing:it is the process of keying/editing entries into the tables.
Example: T000,T001,TBDLS,USR40,Chart of Accounts,sales organizations,sales areas
etc...
Execute SE01 and Create Change Request.
Execute SPRO and Create Entries into Client Specific Tables.A pop-up box is
prompted to save the changes to change request. The User has the option to
create a change request(provided user has necessary authorizations)or save them
to assigned request.
Development:
it is the process of creating custom repository objects or modifying SAP
Repository Objects.
SAP Repository Objects such as Fields,Domain,Tables,Programs,Functional
Modules,Screens,Menus,Transactions in the namespace of A to X can be modified by
a Developer upon obtaining SSCR Key (SAP Software Change Registration Key) from
SAP Market Place
These are generally referred as repairs.
it requires the Valid Developer Key(Table DEVACCESS)
it requires the Valid SSCR Key(Object Access Key).Every SAP Object Requires a
SSCR Key for Modification.(ADIRACCESS)
Customer Defines the objects in the namespace(Y-Z) where a valid Developer key
is required.
SE11 is used to define Data Dictionary Objects(Fields,Domain,Tables)
SE37 is used to define Functional modules
SE38 is used to define Programs/Reports
SE41 is used to define Menus
SE51 is used to define Screens
SE71 is used to define Forms
SE93 is used to define Transactions
Se80 is used to define the repository objects
when any of the above object is created or modified it prompts for a change
request of type work bench.These object also requires a Development class or
package with out which the objects could not be transported.THe Objects saved to
$tmp class or saved as local object are not transported.
These Objects are grouped into a Package (packages are defined in SE80).
Each Package requires a Transport Layer(Transport layers are defined in STMS)
Transport Layer specifies the path to move the objects between the systems.
Transport Layers are assigned to Transport Routes(transport layers are defined
in STMS)

27. These Transport Routes are assigned to Systems to form the System Landscape.
Transport Routes are used to transport the objects between the systems.
There are two types of transport routes.
Consolidation Route: the Route between the Integration(DEV) system and
Consolidation System.
Delivery Route: The Route between the Consolidation(QAS) System and Delivery
System(PRD) is Delivery Route.
Systems are defined in STMS:
Developer key: it is used to authorize the developer "ex:sapuser" to
develop/create/modify/delete the objects in the SAP Namespace(a-x) or customer
namespace(y-z) or reserved namespace(/willsys/).
Example:
Modifying a sap standard Object A-x are referred as repairs where SAP Software
Change Registration key is required along with developer key.
Example a Customer requirement is to display the daily/weekly/monthly sales
report.
a Report with in naming convention (y -z ) has to develop where a developer key
is required.
Developer keys are stored in table DEVACCESS.
The Object Access keys (SSCR)are stored in table ADIRACCESS.These are also
referred as SAP Software Change Registration Keys(SSCR Keys)
Note:One time Data Access Key is required,subsequently all the developers are
allowed to modify that standard Object(a-x).
********************************************************************************
***********************************
Change Requests Release:
when a change requests is released it checks for the valid target system.if the
system landscape is not defined then the transport requests(local transports)
are not generated.
if the repository objects are assigned to a $tmp class or saved as local objects
then the transport requests are not generated.
So assigning a Valid Development package/class to the Objects is required
The Package is assigned to transport layer--->layer is assigned to Transport
Route and route is assigned to systems--systems forms the landscape.
when a request is released,transport requests are created and target system
buffer is filled with transport request number,cofile is created "K" and
datafile is created "R" and sapnames are updated with username who owns the
change request(username file gets updated with change request numbers)
sapnames directory is also used to identify the requests owned by
developers/functional consultants.(after Import)
Log directory gets filled with Alog(application Log),SLOG(Steps Log) and
Ulog(commands log).it also generates a transport request specific log.These four
logs has significance in identifying the issues/errors.
Transport layers are defined in STMS,by default SAP Transport Layer is created
to move the 'sap' standard Objects and Z<SID> is created to move the custom
Objects(y-z,/company/)
The support packages/patches/add-ons/languages etc...are the compressed
transport requests sent by SAP in the form of .CAR/.SAR when these are
decompressed (uncarred)patches like .att/.pat files are generated.
when these are imported through SPAM/SAINT/SMLT the respective

28. data/cofile/sapnames are created and filled in trans directory
tmp directory is used during the runtime of transports. if any content is choked
in tmp directory then assume that there is an issue with the transport request.
do not delete any contents from tmp directory unless recommended by SAP.
Importing the Requests:
Execute STMS/STMS_IMPORT
Select the Transport Request and Import using semi loaded truck.
Disable the fully loaded truck to avoid accidental usage and accidental import
of all requests that are in Queue.
it is recommended to delete the requests after import.
Execute-->STMS--Overview--Systems-->doubleclick system--set the parameter
No_IMPORT_ALL=1(set it in domain controller)
Check the logs in /usr/sap/trans/log or use the tp logs.
tp: (transport protocol);it is used to export and import the objects From
database to file system(export) and file system to database (import).
tp calls R3trans to export and import the objects(execute R3trans -d)to check
the tp connectivity to database.
tp is specific to OS/DB/32/64/UC/NUC.
Preliminary Transport Requests:(Emergency Requests)
These are transported directly to the production with out following the
Transport Queue/Approvals in an emergency.These requests remains in the queue
for later import along with other requests.
Execute STMS_Import-->select the menu Extras-->other Requests Add--select the
request and import..
The Requests requires an approval and need to copy the associated cofiles and
data files.
CRT(conflict Resolution Transports):
when the add-on's are applied read the composite note 822380 and add-on specific
note.
if there is a conflict sap releases conflict resolution Transport requests which
has to be manually imported at OS Level.
Example: when banking add-on is applied it conflicts with existing BW and basis
component then a CRT which is released by sap has to be imported through(at) OS
Level or using STMS
********************************************************************************
********************************************************
Current Customizing:it is the process of allowing the production system to
modify the changes to certain tables even the system settings are set to not
modifiable/no changes allowed in client settings and the Client role should be
set to production.
SOBJ Transaction is used to set the current settings option;
execute SOBJ-->select the table-modify--check the current settings option and
save.The tables which are checked with current settings options are editable
only in production system.
example is OB52 transaction
Manual TP
while stms is specific to a single or mass transports ,tp can also be initiated
at OS Level with various options.
when support packages/add-ons/languages are applied,if the system is aborted due
to any reason and if the system does not allow login (logon screen is in
modified state--i.e it is modified by the support packs),then the remaining part
of the support package can be applied (initiated)through manual tp.
go to ULOG and the get the tp commands to execute at OS Level.
check connectivity of TP to database :
tp connect <SID> pf=/usr/sap/trans/bin/tp_domain_SID.pfl

29. Check R3trans Connectivity "R3trans -d" and analyse trans.log(trans.log is
created in the same path where R3trans -d is executed)
Add the requests to buffer :
if the systems are not in the landscape then the requests need to be added to
buffer else they are not displayed in import Queue
tp addtobuffer <TR> SID pf=/usr/sap/trans/bin/tp_domain_SID.pfl
import single requests
tp import <TR> <SID> client001 pf=/usr/sap/trans/bin/tp_domain_SID.pfl
import massive requests
tp import ALL <TR> <SID> clnt001 pf=/usr/sap/trans/bin/tp_domain_SID.pfl
Manual Transports:
tp addtobuffer DEVK900208 PRD pf=/usr/sap/trans/bin/TP_DOMAIN_DEV.pfl
tp IMPORT DEVK900208 PRD client001 U012689
tp IMPORT DEVK900208 PRD client001 U012689
pf=/usr/sap/trans/bin/TP_DOMAIN_DEV.pfl
tp IMPORT DEVK900297 DEV client001 U012 pf=/usr/sap/trans/bin/TP_DOMAIN_DEV.PFL
Transport Logs:These are displayed in
/usr/sap/trans/log(alog,ulog,slog,Transport Log).
A Transport request is failed when return code is more then '4'
tp return codes are important to resolve the run time issues of transports.
(0000)----succesfully completed
(0004)----completed with warnings
(0006)---Programs issue(such as activation/dependent programs not found)
(0008)-and above---Completed with errors.
(0012)---db connectivity errors
12 and above are related to Tp errors
execute R3trans -d to check whether tp could connect to database.
R3trans -d generates trans.log in the current directory.
Execute STMS-Overview-Systems-select system check-->transport tool-->directory--
>connection test
tp connect <SID> pf=/usr/sap/trans/bin/TP_DOMAIN_<SID>.PFL
execute report RSTPTEST in SA38
generally above "8" are related to tp,r3trans,tms, file system,/trans,tp profile
parameter errors.
********************************************************************************
****
TP Mechanism:
tp converts the database changes (change requests) into OS Independent format
during the export(change request release)using the truck in SE01
Most of the transport requests are sap release dependent.(620,640,700)
tp converts db specific changes to OS Independent Data Files/cofiles and import
them into DB Dependent format during the Import using the truck in STMS
Transport Request Import:
1.check whether The Change requests are released in SE01

30. 2.Check whether STMS is Configured
3.Check whether the objects are assigned to a valid development class and class
is assigned to a valid transport layer.objects assigned to local and $tmp are
not transportable.
4.Check whether transport directory is readable/writable(permissions) etc in
STMS.
5.Check whether the transport profile is readbale
6.if required upgrade tp and R3trans
7.check whether tp is connecting to Database(use R3trans -d)
8.check for any hanging tp(at OS level)
9.check the respective data/files and co-files exist with SIDADM Permissions
Execute STMS or STMS_Import
select the transport request and select import truck.
specify the client to transport/date and time
specify the Unconditional Modes.
1--Leave the request for later import in the queue.
2--Overwrite Originals
6--Overwrite repaired objects
8--Ignore the restrictions
These are prefixed with 'U'
Semiloaded truck is used import a single requests
Fully loaded truck is used to import mass transport requests.
Stms displays the tp monitor and tp logs.Before confirming that the transport
is succesfull check the tp logs and tp return codes or check from transport
Logs.
Mass(monthly)Transports to Production
The Transports are moved into production system periodically either
daily/weekly/monthly during off peak hours.
Frequent Transports overwrite the (programs)buffers and frequent swaps occurs
which will degrade the performance of the system.
Transport(window) Life Cycle is followed in most of the environments(generally
daily,weekly,monthly during offpeak hours)
1.Schedule MTP with date and time
2.Notify the Users
3.Lock the Users using transaction EWZ5
4.Transport(Import) the Objects using STMS/STMS_IMPOrt
5.Release(unlock in EWZ5/Su01) the Business Process Owners(users) to test the
imported objects.
6.Test the Objects
7.Decision to go or no-go
8.if 'no' revert the changes using another transport requests(reverse)
9.unlock the users.
Note: There is no option to revert the Transport Requests(TR,SPAM/SAINT,Language
etc) because they overwrite the objects and it reflects in various
tables/programs.So they cannot be reverted..
Process of ROLL BACK
The Developers can make use of the development system and get the older version
of the programs,change/record/release/transport again.
Note: Disable the fully loaded truck,so that the mass transport option are not
used.
if Mass Transport option is required then delete the requests from the queue
after import.
if these are not deleted then multiple versions are available in the STMS and
using fully loaded truck will make the system inconsistent.
it is also possible to select group of transports by closing the transport queue
and move the end mark and if required open the queue.

31. Transport Requests Deletion:
Execute STMS
select the request and delete and if required add the request.
Transport hangs:
check tp,r3trans processes(os) along with background processes-SM50/SM37).
some times too many tp are running.delete them at OS Level,
delete tp import monitor logs and reimport the requests.
batch jobs(rddimpdp/rddnewpp)could not be started..
check user tmsadm/DDIC are not locked
check rfc connection tmsadm,tmsup
check whether btc job rddnewpp/rddimpdp are scheduled in client 000 with user
like ddic
Issues related to Imports.
1.trans dir file system space/permissions
2.tp connectivity errors(R3trans -d)
3.tp and r3trans version compatability
4.database table spaces overflow
5.no sufficient background jobs/user ddic locked
6.memory issues such as TSV_TNEW_PAGE_ALLOCATION etc
when the support packages are terminated they can be reinitiated by
Re-run the support package to start from the point where it is failed.
Note: During SPDD/SPAU rerun the package in dialog mode to take a decision to
adopt the changes
Note: Do not delete the pat01/pat03 tables and tmp/log file unless recommended
by sap.
********************************************************************************
**********************************************************
Starting and stopping of SAP System.(Kernel upgrade/Rz10 Parameters)
1.stopsap at OS Level
2.use sapmmc on windows environment.
Starting the sap system:
1.startsap at Os Level
2.use sapmmc on windows environment.
startscript reads the startup profile and starts the engine
startup mechansim.
1.it reads startup profile with naming convention START_DVEBMGS00_HOSTNAME.PFL
it contains the following executables/scripts to start the sap system
a)copy execuatbles from kernel directory to runtime kernel /sapmnt/SID/exe using
sapcpe.exe and writes log into sapcpe.log
b)start database by using strdbs and writes the logs into stderr(standard error
logs and startdb.log)
c)starts message server using msg_server.exe and writes log into dev_ms.log
d)starts the dispatcher using disp+work.exe and writes log into dev_disp log
e)starts the work processes using disp+work and writes log into
dev_w0,dev_w1,dev_w2,dev_w3,dev_w4...............

32. f)starts the Internet Graphics Server using igswd.exe and writes into
igs logs
These logs are written to work directory.The available.log specifies the
availability of the instance.
Tracing:
To root cause the startup issues set the trace level using parameter
rdisp/TRACE=0,1,2,3,4....
This trace will write the logs enormously into stderr0,1,2,3,4.......
subsequently the developer traces are also updated.
Analyse the logs in the sequence to root cause the startup issues.
1. Check whether the Database is up and running. Check the database traces in
E:oracleSIDsaptrace/background/alert<SID>.log, startsap.log, v9start.sql,
stderr0,1,2,3,4 in work directory
2. Check whether Listener service is running, if not there may be an issue
with listener (port and hostname) ora-12541(Listener not started or listener is
running on different port/host
• cmd>lsnrctl status to know the status of listener
• cmd>lsnrctl start to start the listener
• cmd>lsnrctl stop to stop the listener
3. Userid and password mis-match for schema user id (ora -1017) (SAPSR3,
SAPSID, SAPR3 based on versions
• Check the Environment Variables are properly set
Example Oracle_home, db_ora_tnsname =SID
• User has in sufficient privileges where the sql statements like
sapconn_role, sapdba_role has to be executed.
• Schema Owner Locked with error ora-28000 will be unlocked by using
command
• Sqlplus>ALTER USER SAPSR3 ACCOUNT UNLOCK;
These Errors are found in the trans.log (execute R3trans •d) to check whether
database is reachable to work processes
4. Wrong entries are maintained in tnsnames.ora, listener.ora or sqlnet.ora.
In the current version of SAP the above entries are maintained in
usr/sap/SID/sys/profile/oracle along with /oracle/SID/102_64/network/admin
Modify the entries based on hostname, port number, protocol and oracle Home
5. Check for Ora-600(internal hardware Error) and escalate to hardware, SAP
and Oracle where restore and recovery may be required
6. Check for ora-1578(Data Block Corruption) and restore and recover that
block from valid database backup
7.Message Server is not started (check dev_ms, startsap.log, stderr0, 1, 2, 3,
4) Hardware changes, IP Address Changes, hostname change will reflect in message
server log. Check for customer key in the dev_ms log. Ensure that ports
3600,3900 and 8100 are not blocked
8. Profiles are not available to start the database, dispatcher and message
Server (If there is a file system change or the respective directory is not
mounted on UNIX (/usr/sap/SID/SYS/exe/profile)).
Copy the profiles from an active system and modify the entries accordingly and
start with minimal parameters or restore from the valid backup
9. Kernel is upgraded but not related to the database/Unicode/32/64 bit
operating system.(select the right kernel before upgrade)
10. Execute script "rootpre.sh or saproot.sh " to set the permissions for
kernel executables on Unix after kernel Upgrade
11. Dispatcher could not start with error message DISPATCHER EMERGENCY
SHUTDOWN .Analyze the dev_disp Dispatcher developer trace
The "services" file, which contains TCP and UDP services and their respective
port numbers. This plain-text configuration file is located under
winnt/system32/drivers/etc. check for the logs in Event Viewer (EVENTVWR.exe)
and check for disp+work in task manager
12. Check Dispatcher Monitor (DPMON.exe), which is located under

33. /usr/sap//sys/exe/run (dpmon pf=instance profile)m-menu
13. Dispatcher dies due to a database connection problem or A connection to
the database could not be established because either the SQL login specified in
parameter is valid or there is a problem with environment variables
14. Work processes could not connect to Database (evaluate dev_w0, dev_wn-1,
dev_wn-2 etc).This Log will explain the complete process of Connecting to the
Database along with the status of each step.
15. Too Many work process are configured (Processes should configure as per
formula i.e at least 75mb should be allocated to each process).Or too many
processes are configured or the number is more then 100.
16. Buffer Areas Could not created (Program Buffers, Table Buffers) PXA
(Program Execution Area) Initialization Failed . Shared Memory is not sufficient
to start the dispatcher (errors with shm in dev_disp) An ABAP dump saying
"PXA_NO_SHARED_MEMORY" is generated as soon as a user logs in.
17. The message server and the dispatcher do not start at all in the SAP MMC.
The following error when trying to view the developer traces within the SAP MMC:
The network path was not found. No new developer traces written to disk (under
the "work" directory.)The network shares "saploc" and "sapmnt" do not exist. Re-
create the "saploc" and "sapmnt" network shares. Both need to be created on
the /usr/sap directory, Check whether the Drive is mounted.
18. Users get "No logon possible" messages. Work processes start but no logins
are possible. Users get the login screen but the system does not log them in.
Instead, they get this error: No logon possible (no hw ID received by mssg
server). The reason is because the "services" file is missing. Example: SAPmsTST
3600/tcp. Edit the "services" file and add the entry.(/etc/services)
19. SAP MMC Entries are missing to start the sap System. It was happened due
to abnormal termination or due to virus. Use sapstartsrv.exe to create the SAP
MMC Entries.
20. Check whether the services saposcol and SAP<SID>_NN are running>. If not
check the user permissions and run them manually
Tracing:
If the instance could not be started then switch on the trace by using parameter
rdisp/TRACE=0,1,2,3,4 (default Profile)
This Trace writes granular log files into work directory. Ensure that we have
enough space in the work directory. Due to this parameter the running system may
be stopped.
**************************************************************
client export and import:
1. client export is performed using scc8 in the source Client.
2. The Data Files and Cofiles are generated in /usr/sap/trans directory.Based on
the profile The Tranport Requests like
KO-Cross Client Data
KT -Client Specific data
and KX- client specific text are created
select the profile sap_user
3.Copy these files to the Target System.
4.Add these files to the import Queue in STMS
5.Import these requests using STMS
6.perform post-client copy activities in scc7.
when The new Clients are created they will not allow to login with sap* as it
was deactivated at system level.
set the paramter
login/no_automatic_user_sapstar = 0(default it is set to 1) and restart the
instance

34. Client Refresh:it is the process of setting up a client with live data from
production system.
Periodically it is required to set up clients for preproduction/quality
assurance/training clients.
Most of the scenarios the Remote client copy is the best method then the local
client copy on the production system(to avoid client settings/accidental client
copies in Production).
However in some of the environments the preproduction client will exist in
Production system but it is only possible to test client specific scenarios
because the Rep and CCC are shared between clients(set to not modifiable)
It it also recommended to perform DB/System Refresh instead of Client Refresh.
Note: There will be only one client in the production system apart from 000,001
and 066.
1.Kernel Upgrade:
2.SICK
3.SE06
4.STMS
5.Slicense(based on hardware key)
6.SM36-----Schedule Standard Background jobs
7.DB13-----Schedule Database Specific Standard background Jobs.
8.SU25-----Initialize the Profile Generator(execute SU25->click on initially
fill the cutomer tables.
9.SPAM/SAINT
10.I18N
11.RZ10-Import Profiles of active servers
12.SMLT-Import Languages.
13.SR13--Library Configuration
it is used to configure the library for run time/screen context help
Select the tab PlainhtmlHttp
Specify the Variant as HELP
Platform as WIN32
Area as IWBHELP is for documentation and IWBTRAIN for Training.
Server Name:help.sap.com
path:erp2005_ehp_06/helpdata(without 'en')
Lanaguage: EN
Select-->Mark the Default Tab.
The Above Information is obtained from help.sap.com
14.SU01--Change User Master Passwords/Create a Super User like sap* and Lock
sap*
15.SICF--Internet Communication Framework:
Execute SICF and activate the service based on the
requirement(webgui,bi,xi,srm,srm etc...)

35. 16.SCC4---Create a Client
17.Copy Client Local(SCCL)
18.Remote Client Copy(SCC9)
19.SCC3 Client Copy Logs
20.SCC5 Delete Client
21.SCC8-Client Export
22.SCC7-Client Import
23.SGEN--To compile the programs in the background mode which will improves the
performance as compilation is not required during runtime.(it is required after
installation,supportpacks and upgrade)
Preparing the Production System:
1.Develop the Objects in Development System(Cust Client)
2.Copy the objects between the client for Unit Testing using SCC1
3.Transport the Objects to Quality System for Testing
4.Upon Approval move the transports related to objects,roles,customizing etc to
production system
5.Establish the Router Connection to SAP
6.Schedule Go-Live Sessions with sap
(go-live analysis and go-live verification.
1.Solman Key:specific to hostname and instance number;mandatory for installation
and upgrades.
2.S UserID: SAP User id Required to login to SAP Market Place
3.Installation Number: Specific to the Installation Product(ERP,Solution
Manager,Netweaver,Business Objects,CRM,SRM etc..)and customer
4.System Number:Specific to the System comes along with sap license.
5.Hardware Key: Specific to the Installation Host(which may differs based on OS
installation(if OS is reinstalled the hardware key may change)
6.License Key :specific to hostname and hardware key(generated on sap market
place)
7.DEVELOPER Key: Specific to the Developer Name to develop programs on the
system in the customer name space 'Y' and 'Z'.
8.SSCR Key(SAP Software Change Registration Key or referred as Object Access
Key).it is required to modify the sap standard objects in the name space
('A'-'X')
9.Maintenance Certificate: it is valid for three months and mandaotry for
applying support packages released after Basis 7.0
SP14