SAP IMPLEMENTATION QUESTIONS

1. What is Implementation? Explain the phases of implementation

Implementation : it is the Processs of the Deploying the SAP Software in an organization right from
sizing to go-live (End to End). it involves the Following Activities.
1. Hardware Sizing

2. Procuring Hardware and Software

3.Installation of SAP Systems

4.Performing Post-Installation Actions
5.Configuring the Landscape
6.Deploying Support packages ,Notes ,Add-ons ,kernel update and Languages
7.Customizing ,Development and Transportation of Objects
8. Scheduling Go-live Sessions with SAP.

9.Go-live
2. How to get the Phase-wise details for ASAP Methodology? Explain them in Detail
SAP Systems are Implemented using Solution Manager to track each phase documents of
ASAP Methodology. SAP Solution Manager is the Primary Tool Designed to support the
Implementation of SAP solutions until solution is productive. SAP Solution Manager provides the
various Tools, Methodology, and Preconfigured Content which can be used during the
Implementation of SAP solution. Preconfigured content for the Evaluation and Implementation of
Business Solutions .Tried and Tested implementation and Test Tools -- for example, the
Implementation Guide (IMG) or the Test Workbench.
The Road Maps are accessed by using Transaction RMMAIN in Solution Manager

ASAP (Version 8) Methodology Contains 6 Phases:

1. Project Preparation
2. Blue Print Phase
3. Realization
4. Final Preparation
5. Go live and Support
Run and Operations
3. Explain the reasons for implementation failures
• User Requirements are vague and not properly documented
• Understanding the Requirements and Adopting the Requirements into SAP.
• User Motivation and Employee Retention
• Risk Evaluation and Risk Mitigation
• Growth in Business Requirements(SCOPE Change)
 • Project Management Tools are not Used for tracking the Progress of the Project.
(SAP Provides Solution Manager Tool)
• Testing the Objects Before Go-Live and Training the End Users
• Lack of Competency, Talent and Project Management skills(Team Failure)
• Lack of Top Management Commitment
• Poor ERP Package Selection
• Resistance to Change/Lack of Buy-in
Miscalculation of Time and Effort
4. What is hardware sizing?
it is the process of converting the business requirements into Technical Requirements such as CPU
,Memory ,IOPS ,Network Bandwidth and Disk(storage).
The Business Requirements can be the number of Users who are working on the system or the number of
objects that are created in the system.
Sizing is Performed by Quick Sizer Tool. it is a web based tool developed by SAP with help of Hardware
vendors to determine the Hardware Independent Sizing Units.it is free of cost for the customers ,partners
,Hardware vendors etc..
Navigate to URL http://service.sap.com/sizing

5. What are the different types of sizing

Hardware Sizing based on Two Types.
1. User Based

2. Object based throughput Sizing

User Based Sizing: it is calculated based on the Numbers Users who work on the System to a different
degree .The Users are segregated as Low ,medium and High which depends on the number of Dialog steps
they perform/week.

Dialog Step is a Transactional Step which may involve a Screen Change Execute ,Mouse Click or Key
Board Functional Keys(F2,F3,F8 Enter , etc )
Low Users generates around 0-480 dialog steps/week
480 Dialog Steps-40 Hours
1 step=40*60min/480=5 min=300 sec
Medium Users generates around 480-4800 dialog steps/week
4800 Dialog Steps-40 Hours
1 step=40*60/4800=0.5 min=30 sec
High users generates around 4800-14400 dialog steps/week
14400 Dialog Steps-40 Hours
1 step=40*60/14400=1/6 min=60/6 sec=10 sec
Generally the Users are in the Ratio of 60-64(Low)30-34(Medium)and 6-10(High). This is displayed in the
Transaction ST03n (Work Load Overview)
Throughput based Sizing: it is based on the number of objects that are created in a specific period of time.
Ex: The Number of sales orders/purchase Orders/Invoices/billings/ shipping Orders/Production Orders that
are created in Average/ Peak based on Year Time Interval. Every Changes/Display are calculated as 100%.
The residence Time is the amount of time the object resides in the SAP System.(In India every object is
required for a period of 7 Years(Accounting Purpose) and for US/UK 5 Years)
6. What are the inputs of hardware sizing
 Specify the Project Name:(customer Number comes by default)
 Click on Create the project
 Select project Information
 Project Data Name of the Project new or upgrade(software
extension)
 Customer Data(customer information like name, Email, Telephone No,
Fax NO)
 Platform communication such as OS Version, Database Version,
System Type(DEV,QAS,PRD),Size of Legacy Database,
 System Availability: How long the system/business sustains without
SAP.
Mirroring, RAID, Storage Area Network, Backup
(online/offline),Standby Server, Clustering etc
Select the Modules (FI,CO, HR,SD,QM,PM) and Specify the Number of Users for Each Category Low,
Medium and High, Save the sizing Inputs
The Sizing report is only a Skeleton Sizing which needs to consider the following factors before a
Final Sizing Report is made.
1. OS and DB

2. Virtual Memory

3. Third Party Tools(weigh bridge ,biometric ,GRC,XMII)

4.Interfaces like Printers ,fax etc..

5. Future Growth of the Company

6. High Availability(Mirroring ,RAID ,Cluster etc)

7. Standby Server and Disaster Recovery Servers

8. RFC Connections with SAP CRM,SRM,SCM etc...

9. Backup and Restore

10.Additional Modules and Users

7. What is the output of sizing
The Sizing Output Contains the Following
1. CPU Category
2. No of SAPS(DB+ APPS)
3. Memory(DB+APPS)
4. Disk Category
5. Storage
6. IOPS
8. Explain about SAPS
SAPS: it is an Hardware Independent Unit that is used to measure the number of CPUS Required as per
the sizing results
SAPS Stands for SAP Standard Application Benchmark for Performance Standards.it is measured based
on the generation/creation of every 2000 Sales Order Line Items/Hour which Requires 100 SAPS.
i.e 100 SAPS are required for every 2000 sales Order Line Items/Hour or 2400 Business
Transactions/Hour or 6000 dialog Steps/Hour
9. How do you interpret the sizing results? Do you get appropriate results in sizing
The Sizing report is only a Skeleton Sizing which needs to consider the following factors before a Final
Sizing Report is made.
1. OS and DB

2. Virtual Memory

3. Third Party Tools(weigh bridge ,biometric ,GRC,XMII)

4.Interfaces like Printers ,fax etc..

5. Future Growth of the Company

6. High Availability(Mirroring ,RAID ,Cluster etc)

7. Standby Server and Disaster Recovery Servers

8. RFC Connections with SAP CRM,SRM,SCM etc...

9. Backup and Restore

10.Additional Modules and Users

10. What are the prerequisites of installation
Installation Pre-Requisites:
Download the Installation Guide from SMP
1.http://support.sap.com/ instguides
2.http://support.sap.com/sltoolset
3.http://support.sap.com/swdc
https://launchpad.support.sap.com/#/softwarecenter
4. http://support.sap.com/notes;launchpad.support.sap.com/#/notes

5.http://support.sap.com/pam
6. http://support.sap.com/platforms

Note: the URL has been changed to http://launchpad.support.sap.com

7. Install the Operating System and its patches as per the SAP Note specified in the installation guide.

8. setup the File System as per OS recommendations in the SAP Note

9. setup the File System as per DB recommendations in the SAP Note

10. setup the shared mount /sapmnt

11. Install the Java Runtime Environment if Required(SAP JVM is inbuilt in SWPM)

12. Install the database and required patches.(some databases may be installed along with SAP. EX;
HANA,MAXDB,SYBASE)
13. Copy the Software to a folder[folder(subfolder Names))should not contain any spaces or special
characters etc.
14. Use the SWPM(Software Provisioning Manager) software and naviagte to the executable sapinst.exe
or script 'sapint'
double click on windows or use command ./sapinst to start the Installation Master
15. Select the SAP Product like ERP ,CRM ,SRM,SCM,Netweaver,Solution Manager etc.....

Note: SWPM is the only tool used for SAP Installations and SUM(Sofwtare Update Manager) is the only
tool Used for Upgrades.
These are downloaded using http://support.sap.com/sltoolset
16. Select SAP Systems--->Select the Database-->Select Standard,Distributed and High Availability

17. Select the Installation Type as "Typical/Custom"

Custom option can be used to configure the ports,file system,tablespaces,datafiles etc.......Default is

"Typical"
18. Provide SID,master Password(password that will be set for OS Users,DB Users and SAP Users)

19. Provide the Directory for Installation and path of the Software such as DBClient,SAP Kernel,DB
Exports etc...
20. Continue the Installation.
11. What is the software required for installation
1. Operating System and Database along with Patches and Fixes
2. SWPM: Download the latest version of software provisioning manager.it is Independent
of Components but specific to OS and Bit. SAP Installation Master drives the
installation which is based on operating system
3. SAP Kernel. it is Independent of Components like ERP, CRM, SRM, SCM, Netweaver
but 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
4. SAP Exports: These Exports or SAPDATA DVD's are Specific to Component and
Independent of OS and DB (CRM, SRM, SCM, ERP and Netweaver etc). These Exports
imports data during ABAP Import and populates the data into sap data directories
5. SAP JAVA Components: Provides the components that are installable and configurable
on Java engine
12. What is the path to download the Software in SAP Market Place
Navigate to the market place using URL launchpad.support.sap.com
Search for Tool software downloads
INSTALLATIONS & UPGRADES

IF YOU WANT DOWNLOAD ERP COFTWARE MEANS GO WITH E

13. What is Software Download Manager? How do you setup to download files from Market Place
Sap software download manager is free of charge tool that allows you to download multiple file
simultaneously or to schedule download to run at a later point in time. Software found in your download
basket is visble in sap download manager software download manager installation requires jre ( java
runtime environment means it will run using java files.
14. What are the inputs of installation?
1. select the SWPM based on os
2. click on sapinst.exe if it is windows or run ./sapinst if it is unix os
3. select the component (ERP/SRM/CRM/SCM/SOLMAN)
4. select the database
5. select ABAP/JAVA (ABAP And JAVA)
6. select installation type (central/distaributed/high availability)
9. Custom: it is used to customize the installation (Memory allocation, port
number customization, folders/data files path customization, number of process
for import etc.
10. Specify the SID (System Identifier): it should not be one among the reserved id's
refer to installation guide which specifies the ID such as
ADD, ALL,CRM,ERP,ANY,SAP are reserved. SID is unique throughout your
organization.
11. Do not use an existing <SAPSID> when installing a new SAP system.
 12. SID Consists of exactly three alphanumeric characters, and it Contains only
uppercase letters. Has a letter for the first characters(R47,R60)
13. Specify the Instance Number which is by default 00 for a new installation and it
is incremented based on installations. It consists of a two-digit number from 00
to 96 where 97 is reserved for DAA service, 98 is reserved for Solution Manager
Diagnostics and 99 is reserved for sap router.
14. Specify the master password for all the OS/DB/SAP users that are going to
setup/created (configured/installed) during installation.

15. Specify the installation drive for executables/transport directory etc..

16. Specify the path of the Kernel, Oracle client, Exports DVD's etc..
17. Review the inputs and continue the installation.
18. Each Central Instance Installation requires a Solution Manager Key. Generate
the Solution Manager Key from Solution Manager System using transaction
SMSY. From Netweaver 7.3 onwards Solution Manager Key is not required)

15. Explain various types of installations?(Central/Distributed/HA)

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 Services
are installed on the same system

Distributed System : the central instance and the database instance are installed on two
different physical machines pointing to global host where the executables are available to both
the instances the database get dedicated resources as it installed on a physical different machine
High Availability : read from book
16. Explain the Significance of Enque Replication Server
Enque Replication Servers are installed in an high availability system to replicate the locks between the
instances.(nodes)ERS is installed on all the nodes and lock replication table gets replicated from the
Central Services lock table in an highly available system.(Microsoft Cluster or IBM HA)

17. What is the process/mechanism of installation

18. Explain about the sap directory structure

19 Explain briefly about MCOD

MCOD is only used for DEMO Purposes. In the Previous Versions Database software is installed as many
times as required to support more SAP Components in this case ERP, SRM and CRM which is causing
confusion among Multiple Homes, Multiple Listeners and Multiple Services etc
20. Explain the process of sanity check of the system
Sanity Check of the Installation:
1. Check the OS Users using /etc/passwd

2. Check the OS groups using /etc/group

3. Check the User vs group assignment in /etc/group

4. Check Database Users(select * from DBA_Users);

5. Check the Installation Logs sapinst.log and sapinst_dev.log

6. Check the File System shared Mounts /usr/sap/ and /sapmnt

7. Check the Data files sapdata1,2,3,4 and other sap* directories

8. check the sap services in /usr/sap/services

9. check the SAPMMC Tool on windows and SAPMC for windows and Unix

10. Check the Profiles,exe,work,security directories.

21. Explain the process of Starting and stopping the sap system

When you start the SAP System, you simultaneously start the system database, the
application server and the respective processes of which the system consists
1. sapstartsrv is an executable(library) that starts as a service in windows or as
/usr/sap/services in Linux Environments.
2. Startsap start the Database Instance along with all the associated central and dialog
Instances.(Primary and Additional Application Servers)
3. startsap r3 starts only the Application Servers. startdb script is used to start database.
4. Database is started by using command 'startdb' and writes logs into
startdb.log,stderr0,stderr1..... Check the Database traces in
/oracle/SID/saptrace/background/alert<SID>.log
from 12C /oracle/SID/....................
5. Copy Kernel executables using command 'sapcpe'.
sapcpe is an executable/script that is used to copy the kernel from shared/Global
Directory to local directory.
i.e /sapmnt/SID/exe to /usr/sap/SID/DVEBMGS00|D01/exe
i.e /sapmnt/SID/exe to /usr/sap/SID/ASC01|SCS01/exe
it writes the log files into sapcpe.log
6. Starts the Message Server by using executable/script 'msg_server(exe)' and writes
logs into dev_ms
7. Starts the Dispatcher by using executable/script 'disp+work(exe)' and writes logs
into dev_disp
8. Starts the workprocesses by using executable/script 'disp+work(exe)' and writes logs
into dev_w0,w1,w2,w3,w4..wn-1
The Other Processes like gateway,Internet Communication
Manager,HostAgent,Internet Graphics Server,log collector,log sender are started and
writes the logs into home directory of SIDADM and work Directory.
21.A. Why to Stop the SAP Systems when they are working fine. Explain Few scenarios where you
have shutdown the system???
1. OS Update, Kernel Update,DB Update,Hardware Update

2.Parameter Changes in Rz10

3. Downtime Alignment with other down times.(Lift,Power,AC,Env,Hardware Maintenanace)

4. Day light savings

5.Configuring Disaster Recovery

Schedule a Downtime Plan and Inform all the Users,so that users are notified through Public Areas,such
as LIfts,Notice Boards,Transaction SM02,Email Etc..
Note:offline backup does not require SAP to shutdown
22. List all the Trouble shooting SAP startup problems/issues in Windows/Linux
Check the above logs if the system is not started and evaluate the following issues.
1.Permissions on the File System.Ex: to write Logs(sidadm:sapsys)
2. Firewall block of Ports and Protocols to start the services,ports are in Use by some other services

3. File System is full to write logs

4. Database is full or Database directrories are full

5. System Hardware Changed

6. Service Owners Changed password

7. Wrong kernel Update,version,database,unicode or non-unicode

8.Parameters are wrong for Buffers and work processes

9.Memory parameters are not set properly
10.dlls/lib/bin/exe are missing
11. Database could not be started(evaluate the reasons of DB)

12. Message Server Could not be started

13. SAPCPE could not copy the executables

14. Enque server could not be started

15.Dispatcher could not be started

16. work processes could not be started

17. IGS server could not be started.

Check the Developer traces Logs for each of the above Failures.
/usr/sap/SID/DVEBMGS00/work(These Logs are displayed through ST11
/usr/sap/SID/D01/work
/usr/sap/SID/ASCS01/work
23. Explain the post installation activities
1. Install the GUI (750 SP3) and define the connection entries
2. logon to the System and create admin Users other then sap* and DDIC
3. Lock the sap* User and disable the sap* logon by setting the parameter
login/no_automatic_user_sapstar=1 in RZ10.
4. Execute SICK to check the Compatability between OS/DB and SAP Kernels.if sick results in error then
OS/Patch,Update,DB/Patch, Update,SAP Kernel Update May be required
5. Run SGEN to Compile the Programs and reduce the Compilation and Runtime
6. SE06: SE06(Global Settings: it is used to set the System Change Options. The System Settings are set
to modifiable and not modifiable.
7. STMS:it is used to setup the Transport Management System.
8. Kernel Update: it is the process of replacing the existing kernel executables with a new set of
executables(downloaded from SAP Market Place)
10. Kernel Release Upgrade:it is the Process of Deleting the Current release executables and replacing
with new Kernel Release Executables.it is required to get support from SAP,get new
Enahancements,security features etc..(700 to 720)
11. SLICENSE:it is used to update the license which is downloaded from SAP Market Place.

12.SPAM/SAINT Update: it is used to Update the Tool

13. SR13:Library Configuration

14. SM36: Scheduling the Standard House Keeping Jobs.

Execute SM36-->Standard Jobs-->Default Scheduling.

15. DB13:Schedule Database House Keeping Jobs.

16. RZ10 to Import the Profiles:

17. Support Package Update using SPAM:it is used to apply support packages to ABAP,Basis,BW,ST-
PI,PIBasis,appl,hr etc..
18. SAINT-Add-ons Deployment using SAINT(GRC Virsa,ST-PI,PI-BASIS,Nakisa and other Third Party
Add-ons)
19. i18N(Internationalization to adopt the Languages)

20. Set the Profile Parameters for languages zcsa/installed_languages(based on i18n)

21. Import the Languages from SMLT

22.Activate the Business Functions using SFW5.

23.Activate the Business Sets using SCPR20(specific client)
25.SCC4(Creating Client)
Client is an Independent Business Entity which is used to Represent the Business or an Enterprise.
26.SCCL Local Client Copy
2.SM59 Define RFC Connections
28. SCC9 Perform Remote Client Copy

29. SCC8 Client Export

30. STMS and SCC7 Client Import and Client (Import)Copy Post proccesing

31. SCC3 Client Copy logs

32. SCC5 Client Deletion

33. SU25 Initialization of Profile Generator

24. What is kernel upgrade? Explain the process of kernel upgrade

Kernel Release Upgrade:it is the Process of Deleting the Current release executables and replacing with
new Kernel Release Executables.it is required to get support from SAP,get new Enahancements,security
features etc..(700 to 720)

Process of Kernel Upgrade

1. Download the Kernel from the market place.(http://service.sap.com/swdc-->
complimentary software)
2. Copy the downloaded two files into newly created folder and uncar them using
command
• sapcar -xvf SAPEXE_XXXXXXXXX.SAR
• sapcar -xvf SAPEXEDB_XXXXXXXXX.SAR.
3. Schedule Downtime and upon approval
• Stop the Application servers
 • Stop the Database(may not be required)
Stop the Services(saposcol, sap<SID>_00,sapccmsr
4. Create a directory Kernel_OLD and Copy the old kernel to rollback in case if the system
does not start and to match the size of existing kernel and copied kerne to ensure that entire
kernel is copied
5. Copy the executables from new kernel (step-2) into existing(runtime) kernel by
overwriting the executables.
6. cp -pr kernel_353/* /usr/sap/<SID>/SYS/exe/run/ or /sapmnt/SID/exe
7. Check the Permissions for dbatools and db libraries run rootpre.sh or ./saproot.sh followed
by <SID> to set the permissions for brtools, icmbind, saposcol and set the user bit.
8. Start the Database, Services and SAP application servers
9. Check the kernel version by using disp+work
10. if the sap system does not start then troubleshoot using developer traces in work directory
(stderr0,1,2,3,4),dev_ms,dev_disp,dev_w0,w1,w2,w3..... wn-1
Note: The Current Kernel Upgrades does not require immediate Down
Time of the instance as the Global Kernel Directory is Updated offline and Instances
Update their Kernel using SAPCPE during instance restart.
Kernel Version Upgrade requires Immediate Instance restart as the current executables
has to be deleted and replaced with new set of executables.
Difference between Kernel patch update and version update is one will overwrite the
executables and the other deletes and replace with new set of executables.

25. Explain the process of SPAM/SAINT update

SPAM/SAINT Update: it is used to Update the Tool. SPAM/SAINT Update is Cumulative like SAP
Kernel. Download the Latest SPAM/SAINT Update from SAP Market Place.Upload through the
Presentation Server(Front End) and Import the SPAM/SAINT Update. The SPAM/SAINT Transaction
may need to run twice or thrice to complete the Update.
Error: Load-Program-Lost(Not-Found) may Occurs because the exisiting SPAM Program is lost while
applying SPAM/SAINT Update
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 update spam.
6. Depending upon the spam version the spam restart may be required more
than once until the spam import queue is GREEN.
Monitor the spam progress in SPAM or in SM37/SM50/SM66
26. What are the prerequisites to apply Support packages
Support Packages: support packages are applied based on the Business Requirements,Security
Requirements and System Enhancements.
The Following pre-requistes need to be performed/followed while applying Support Packages/Add-
ons/Languages.
1. Download the Note 822379 from Support Market Place and 822380 for add-ons.Read the Note and
Follow the Requirements.
2. Configure STMS in client 000 and apply patches through 000 only

3. Apply through a User other then sap* and ddic

4. Perform Kernel Upgrade/Update especially tp,r3trans,sapcar etc

5. Ensure that atleast two btc are in place

6. Schedule the support packages in background mode.These can be scheduled in Dialog Mode but due to
screen lockout the dialog process may be terminated.
7. Ensure that there is enough space in Database using DB02

8. Enusre that there is enough space in the filesystem Directory

/usr/sap/trans (du -h)

9. Update SPAM/SAINT

10. The Patches should be applied in the landscape sequence such as DEV,QAS and PRD

11. The patches should be applied in the component sequence BASIS,ABAP,BW etc..

12. The patches should be applied in the number sequence such as 1,2,3,4,5,..No Jumping of patches is
allowed (patches are incremental).
13. The patches has to be binded/unbinded to avoid the runtime errors based on the note 822379( ex:
11,12,13 should be applied together.22 and 23 should not be applied together.
14. Ensure that Maintainence Certificate is applied and valid.

Maintenance Certificate is valid for every three months.

15. Ensure that saprouter connection is setup to get remote support from SAP.

16. Ensure that Functional/Development Team is available to adopt the changes from support packages.

17.Schedule RDDIMPDP/RDDNEWPP in client 000 using user DDIC

18. Record the Modifications to a change request so that manual changes are avoided in the other systems
in the landscape
19. Accelerate the support package Application by increasing the parallel processes(SPAM-->Extras--
>settings-->parallel Import-->specify one or more.
20. Ensure that there are no terminated/aborted support packages.
21. Ensure that the Objects are not Locked in SE03/in any transport requests.

22. Ensure that the Users are logged out and Downtime is scheduled to avoid the runtime errors(even
though support packages are hotpacks ie, applied when the system is online)
23. Support Package may consumes longer hours depending upon the size of the package.Monitor the
progress in /usr/sap/trans/tmp dir
24. Download the Conflict Resolution Transports and Include in Add-ons,if there are any conflicts with
basis Support packages
25. Apply the Suppport packages through front end if the size of the package is below 5mb and apply
through Application server
if the size of the package is above 5mb.
(copy to trans directory and uncar them using SAPCAR -xvf "pa.sar"
26. Do not delete any files from trans directory or from tables PAT01 and PAT03 unless recommended by
SAP.
27. Check the Support Package/Add-on Dependencies in SPAM by using the option New Support
packages.
28. Ensure that a Consistent backup is taken to restore the system in case of any runtime crash.

27. Explain the mechanism of support packages

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(A,S,U,Import,release,version
and transport logs)
10. Monitor the tmp directory during import of supportpackages.
Monitor the TPlogs,SM50,SM66 and SM37(use al11 transaction monitor the log files from GUI
28. What are the issues/problems while applying support packages
29. Explain the process of deploying ADDON’S

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.
Confirm the Add-on
30. What is the significance of I18n
To Add the new languages into SAP System
Execute RSCPINST or I18N to add new Languages into SAP System
31. Explain the mechanism of importing a languages
• Adopt the language through i18n (execute i18n/rscpinst(report in sa38))
• add the language ,save, simulate and activate.
• it will prompt the activation message and recommends to setup the language
parameter in RZ10.set the parameter "zcsa/installed_languages=12ADEFZ" and
restart the instance
• Download or copy the language import file into /usr/sap/trans/EPS/in • Add
the language in SMLT and specify the supplementary language.
• Specify the path of language (/usr/sap/trans) and import the language from
SMLT.
• The Language import is scheduled through a background job which is used to
unpack the language and the controlled is passed to STMS for import using
R3trans and TP
• The Language Pack is dissembled into around ten patch files i.e. data files and
Co-files which are displayed in STMS.
• The Language import is completed which can be displayed in STMS/SMLT.
32. Explain the process of Defining a Client? What is the need for creating a new 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 user id, password and language. sap provides
three default clients 000,001,066 with specific purpose
000 Client: it is a Template Client that provides all the templates,Business Packages that are required to
setup a Client.it is used for Standard Configuration Updates by SAP in the process of continuos
Improvement.Activities such as TMS Configuration,Patches,Support Packages,Add-ons,Langauges are
deployed using this Client.So this Client is not used for Production Purposes.No Other Customer
activities are allowed in this Client
001 Client : it is a Backup Client that provides backup to 000 Client. it is no more a backup client and it is
allowed for production purposes. Solution Manager uses 001 as Production Client
066 Client: Earlywatch Alert Client: it is a Client used by SAP for Remote Support.but in the Current
scenarios the SAP Support team is Directly Logging to the Effected Client,Hence the Significance of 066
is los
33. How to create a client? List all the client roles
Client Creation: These are created in SCC4
The Clients are stored in table T000.it is identified by a Field 'MANDT' in the database, if the table
contains field 'MANDT' then it is called as Client Specific Table and if the table does not contain field
'MANDT' then it is called as cross client table.Client Field is a data separator in the database.it is the First
Field during logon to seggregate the data based on Client.
when Client is created it does not contain anything except an User 'SAP*'with password 'pass'. it is built
at kernel level and created as many times as it is deleted.set the parameter
login/no_automatic_user_sapstar=1(1 to disable sap* logon and 0 to enable the sap* login)
The Newly Created client is able to access the Repository and Cross client Objects but does not contain
any Client Specific Objects.
34. What are client settings and protection levels
Client Specific Settings:
No Changes allowed in the Client(it is set to Production Client and no changes are allowed to client
specific Objects through this Client).
Changes Allowed but not Recorded: The changes are Allowed but not Recorded to carry the changes into
other systems in the landscape.However they can be transported using Transport of Copies.(Use Them in
Training Clients or SAND Box Clients)
Changes Allowed,W/O Recording and Transportation: The Changes are allowed,not recorded and not
transported,changes are specific to that client only.
Automatic Recording of Changes: The Changes are recorded(saved) and transported into other systems in
the landscape. it is set to development or customizing client
Changes to Repository and Cross Clients:(These Changes are overridden by SE03/SE06 System Settings).
Changes to Repository and Cross Clients are Allowed
Changes to Repository and Cross Clients are not Allowed
No Changes to Cross Client Objects(Repository Changes Allowed)
No Changes to Repository Objects(Cross Client Objects Allowed).
Protection Levels:
0- --Client Copy is allowed(External Availability and Client Overwrite is allowed)

1- --Client Copy is allowed No Overwriting

2- --No Overwriting,No External Availability.

35. How to lock, unlock and delete a client

Locking the Client : Use the Function Module in SE37
SCCR_LOCK_CLIENT -->Execute-->specify the client number and execute.(The Client is currently
locked against logon messsage is displayed
Unlocking the Client : SCCR_UNLOCK_CLIENT--->Execute-->specify the client number and execute
36. What is the process of a client copy
37. What are the various client copy methods? Explain them in Detail
Local Client Copy:
Execute SCCL
specify the Profile
schedule to run in the background mode.
Monitor SCC3 for Client Copy Logs.
Remote Client Copy
Define an RFC Connection between target Client and the Source Client
login to Target Client and Execute SCC9
Specify the Profile(default profile will be SAP_CUST)
Specify the Client for User Master
Specify the RFC Connection(to get Source System Name and Client)
Schedule to run in the background mode.
Client Copy Logs are displayed in SCC3
Client Export and Import:
it is performed between two systems when they are not reachable by using RFC.
Execute SCC8 for Client Export.
login to the Source Client and Export the Client based on Profile.
Client Export Generates Transport Request with a Prefix
KO,RO------Cross Client Objects are contained in this Request
KT,RT----- Client Specific Objects are contained in this Request
KX,RX------Client Specific Text Information
Upon Successfull Completion of Client Export,Copy the transport Requests to target System
/usr/sap/trans/cofile and /usr/sap/trans/data
Login to the Target Client and Import them using STMS.
After Succesfull Import perform the Post Client-Import Methods using SCC7.
39. What are the prerequisites of client copy
Prerequisites of Client Copy
1. Check the Size of the Client using report RSTABLESIZE/RSSPACECHECK

2. Ensure that Enough Size is available in database DB02

3. Ensure that Enough Size is available in /usr/sap/trans directory.

4. Perform Client Copy always from the target System Only.

5. Client Copy is only a Pull(Copy) method.

6. Select the profile which will specify the data that need to be copied.

7. Define RFC Connection between two client for Remote Client Copy

8. The SAP Versions and patch levels should be same to perform client Copy

9. Ensure that Client copy is performed in background mode

(support packages,client copy can be scheduled in dialog mode and will not fail in 600 seconds,but it
runs in interactive mode and presentation server(laptop,workstation could not be closed)
10. Lock the Source/Target Client Users during Client Copy.

11. Perform Remote Client Copy using SCC9

12. Check for client Copy logs in SCC3

13. Client Copy always overwrites the content,it is not possible to merge the data. Firstly it will delete the
data and secondly copies the data.
14. Use Report BTCTRNS1 to pause background jobs if any.... which can be later resumed by using
BTCTRNS2.
15. NO tables,programs or any Objects are created during client Copy.Only the Entries from the Source
tables(MANDT) are copied into the same table with a Different(target) MANDT.
16. it is recommended to delete a Client During Client Refresh becuase the Client Copy has to delete the
records and then Copy the records which consumes more time.
Note: it is recommended to perform system copy then a client refresh
17. Imports,Transports,Support packages,Add-ons,Client Copy,languages always overwrites the existing
data
40. What are the various profiles available for client copy
Profile: it specifies the type of data that need to be copied from Source
Client.(SAP_CUST is mandatory profile to setup all the new clients)
SAP_ALL--Copies the cust,application and usermaster(to setup training Client) sap_appl--
Copies cust and applicaton sap_user--only user master sap_cust-- only customizing data
Client Copy Copies only the table 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.

42. What is meant by Repository Objects? Explain with some examples

These are the standard objects in the database which are provided by sap in the name space of A-
X. and not allowed to be modified by any user except developers.These Objects are generally
locked and requires a Key from SAP for Modification or Repair. sap REPOSITORY OBJECTS
SUCH AS FILEDS, DOMAINS, DATA ELEMNTS , TABLES , PROGRAMS , FUNCTION
MODULES, SCREENS, MENUS, TRANSACTIONS , in the name space of A-X

43 What is meant by Cross Client Objects? Explain with some examples

These ae the table entries in the tables with filed MANDT is not available. Cross Client Objects:
These are table entries which are applicable to all the clients in the System
ex:T000,TBDLS,TACT, USR40

44. What is meant by client Specific Objects? Explain with some examples
Client Specific Objects: These are table entries which are specific to the Client and applicable to
that client only.
Ex: User Master,Material Master,vendor,Customer etc.

45. What is meant by development Namespace

from SAP Market Place.Customer can define their own objects in the namespace y or z or
/willsys/ (Customer Namespace )

46. What is meant by SSCR Keys

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')

47. What is meant by Development Class/Package

Transport Package or Development Class or Simply Package:
it is defined in SE80 and Used to group the Customer objects in the SAP Repository.
Every Object in the SAP System need to be grouped(assigned) into a package else the object is
orphan. Each Package needs a valid Transport layer

48. What is meant by Customizing

49. What are transactions Codes Required for Development/Modifications or Explain

about SPDD and SPAU

While Applying the Support Packages,Addon's,Enahncement Packages,Upgrades the

Modification Adjustment Window is displayed where the Transport Requests that are initiated
through SPDD/SPAU are included.
SPAU : Modification Adjustment for Repository Objects. (Programs, Screens, Transactions,
Functional Modules,Reports,Menus,etc)

SPDD :Modification Adjustment for Dictionary Objects(Data Elements, Domain, Table,

Structure,Index etc)

50. What are Prerequisites of a Transport Request Import

1. Check whether The Change requests are released in SE01

2. Check whether STMS is Configured

3. Check whether the objects are assigned to a valid development class/package 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 ,if required kill the tp using option kill.

identify the process at OS Level using ps -ef|grep tp*

9. Check the respective data/files and co-files exist with SIDADM:sapsys Permissions

10. Check the Sequence of Transport Requests

11. Check the Date and Time of Transport Requests

Check the RDDIMPDP/RDDNEWPP background Jobs are released/completed in SM37

51. What happens when an object is saved as local Object

If the development objects are saved as a local object these are not transportable

52. What is meant by Object Versioning for ABAP Objects

The developers can make use the of the development system and et the older version of the programs ,
changes, records and these are transport again SE38 --- PROGRAMS – UTILITIES – VERSION
MANAGEMENT

THIS VERSION MANAGEMENT GENERATE A CHANGE REQUEST THEN RELEASE THE CR IN

SE01 IMPORT IT AGAIN
53. What is SNOTE? What are the types of note

SNOTE:(SAP Note Assistant)

it is used to apply the small corrections to the SAP Standard programs without SSCR Key.

Execute SNOTE-->Download the Note-->Select the Note-->Implement the Note

1. Informative Note: The Note Contains the Installation,Upgrade, Support Package,Add-on,Language

Prerequisites that need to be followed before the Installation/Implementation.

ex: 822379/ 1228898 provides the support package Prerequisites

2. Manual Correction Note:Based on the Informative Note,some of the following may need to perform
manually.

Ex: 822379

You may have to carry out a SPAM/SAINT update.You May have to carry out a SAP kernel Update a
minimum patch level

3. Program Correction:The Small Program Correction(bug fixes),Program enhancements are provided

through a Note for Interim Relief which will be updated(overwritten)by a Support Package that is
released after the note.Corrective Note Brings the Program corrections by deleting or (commenting) the
faulty Code and Inserting the corrected code.The Notes and Kernel can be reverted based on requirement.

Select the Note-->Reset the Note Implementation.Notes are overwritten by Support packages after which
the changes could not be reverted.

54. What are system settings and roles? Explain briefly

Standard Installation: The System is setup based on the Export Software Provided by SAP. it resets the
Change Requests Number and Prepares the System to take part in the landscape.it reinstalls the
CTS(Change(correction))Transport System.

Database Copy or Database Migration:The System is setup(built) based on the Backup/Export taken from
the Existing System in the Landscape.It deletes all the transport routes,resets the number range,deletes
TMS Configuration so that this can take part in the landscape.

7. SE06(Global Settings: it is used to set the System Change Options. The System Settings are set to
modifiable and not modifiable.Generally the Development,sandbox and Testing are set to Modifiable and
Quality,Pre-Prod and Production Systems are set to Not-Modifiable.

55. What is System Landscape? Specify and explain the types of landscape

The Arrangement of Systems in the Order explaining their role in the Data Center is referred as System
Landscape
 Single System Landscape: There will be only one System in the landscape which will provide all the
client Roles(CUST,TEST,SAND,QTST,TRNG and PROD).It is optimal for Testing and Demonstration
Purposes. it could not be used for Production Purposes.

two System Landscape: it is the most optimal(least recommended) landscape where Development and
Testing,Quality activities are performed in one System and Production activities are performed in another
system.

Three System Landscape: it is most recommended landscape where Development,Quality and Production
activities are performed in three different physical Systems.

Multi System landscape: it is used to deploy additional Systems like

Sandbox,Training,Demo,preproduction systems in the landscape along with the three systems
DEV,QAS,and PRD

56. Explain about the ‘trans’ directory Structure

Bin: Binaries such as DOMAIN.CFG and TP_DOMAIN_SID.PFL

DOMAIN.CFG Contains Domain Configuration

TP_DOMAIN_SID.PFL Provides runtime for transports

Buffer: Contains the name of the Systems as Text file. Text Files Contains the Name of the transports
addressed as per Landscape Definition.These Entries are displayed in Import Buffer of the Target System.

Cofiles: Command Files or Control Files that Governs the Transport request it starts with 'K'.

Data: Actual Data that need to be transported or imported.it is prefixed with 'R'

EPS: Electronic Parcel Service: Used while Applying Support Packages,add-ons,languages. it contains
subdirectories 'in' and 'out'.

tmp(temporary directory): used during export and import.very important while applying support
packages,add-ons,languages.Monitor the growth of the tmp file and ensure that tmp has enough space.

sapnames:Contains the Names of the Developer as a Text File with all the owned(released) transport
requests

log: it contains the following logs:

ALog: Application Log, Slog: Job Steps Log , Ulog: Commands Log ,Vlog: Versioning , TClog : Buffer
Transmission Log , Plog: Processing Log , Qlog: Quit Log , Ilog: Import log , Elog: Export log Clog:
Connectivity log

57. What is STMS? How to configure TMS

Transport Management System (TMS)

This is used to manage, control and copy development objects and for customization of settings across
SAP systems in landscape using pre-defined transport routes configured with RFC Connections. This
includes exporting the objects from one SAP system and importing to another target system

 Log on to the SAP system, which is decided to be the Domain Controller, in

client 000 and enter the transaction code STMS.
 If there is no Domain Controller already, a system will prompt you to create
one. When the Transport Domain is created for the first time, following
activities happen in the background:
o Initiation of the Transport Domain / Landscape / Group
o Creating the user TMSADM
o Generating the RFC Destinations required for R/3 Configurations,
TMSADM is used as the target login user.
o Creating DOMAIN.CFG file in usr/sap/trans/bin directory – This file
contains the TMS configuration and is used by systems and domains for
checking existing configurations.

58. What is the Significance of virtual Systems

Virtual Systems: During the Initial Stages of Implementation all the systems may not be available
physically to include in the landscape. So Virtual Systems are defined to define the Landscape

59. Why there is a need to disable fully loaded truck

Semiloaded truck will be used to import Single transport request

Fully Loaded truck will be used to Import Mass Transports.

Fully Loaded Should be disabled in runtime to avoid import of all the Requests. if it is enabled then delete
the Imported requests from the Import Queue.

Disabling Fully Loaded Truck:

Select-->STMS-->Systems-->Overview-->select the system-->Double Click-->

-->Select Tab Transport Tool->Change-->Insert-->set the parameter NO_IMPORT_ALL=1(disable)(o for

enable)

60. What is meant by Queue Open, Move end Mark etc

61. How do you add transport requests to an import Queue

Copy the cofiles and data files to trans directory

Execute the tcode STMS_IMPORT –extras--- other request----add------ select the request (select the
request number
At Os LEVEL to add the request use command

Tp addtobuffer <tr> SID pf=/usr/sap/trans/bin/tp_domain_SID.PFL

62. What is the significance of Adjust Import Queue

THE SIGNIFICANCE OF THE ADJUST IMPORT QUEUE IS TO COPY THE COFILE & DATA FILE
FROM DOMAIN CONTROLER TO THE MEMBER SYSTEM

EXECUTE stms--- overview---import---HERE WE CAN FIND THE adjust queue

Click on the adjust queue to copy the cofile and data file

63. What is the Significance of Extended Transport Control Program

Transport “target groups “ are used to setup the landscape when more then three systems are configured

The extended transport control program is used to transport the objects to transport groups instead of
systems. This is also reffered as client specific transport mechanism

Define transport target group in STMS = STMS --- transport Routes --- hierarchical editor --- transport
target group--- create --- specify the system and client define rotes and layers—define the land scape
using extended transport control program

64. What is the significance of Domain Controller and Backup Domain Controller

Transport Domain Controller:

it is used to maintain all the systems in the landscape.The System such as DEV is configured as Domain
Controller which can be later shifted to an Highly Available Server such as QAS/PRD.

Whenever the trans port domain controller failed the backup domain controller act as a domain controller

65. What is the significance of Common Transport Directory

Common transport directory shared by all the systems in the landscape means trans directory is common
for all the systems. It may not recommended to share with other systems in the landscape in such a cases
production system can be isolated and remaining systems can be one group

66. What is the difference between change and transport request

Change Request: it Contains the Changes made to the Table ,Object ,table Entry ,Program or any
Repository Object Creation ,Change etc...

The Change requests are created by a Project Manager or team lead based on provided Authorizations
.Each Change Request Contain at least one or more tasks. Each task is assigned to a developer or
Functional consultant.
The Tasks are released by the respective consultant’s .The Change Request will be released by
Development/Functional Team.

Note: it is not the responsibility of a basis Consultant to release the Change request .l

Transport Request: Once the Change Request is Released then it is called as a Transport Request. TR
contains Cofiles and Data Files.The Transport is not editable. it is OS/DB/32/64/UC/NUC Independent
Request that contains Change at File System.

These transport Requests can be imported into as many system as possible.

67. How many types of transport requests? Explain them

Customizing Change Request: if the Changes are initiated to the tables which contains a Field 'MANDT'
then they are saved to a change request of type Customizing

The Changes are appliable to Client Only

WorkBench Request

1) if the Changes are initiated to the tables which does not contains a Field 'MANDT'(cross Client) then
they are saved to a change request of type Workbench.

If the Changes are initiated to either cusotmer repository or SAP Repository Objects such as table,table
field,report,program,screen,menu, structure,functional module and Scripts are saved to a change request
of type Workbench. The Changes are appliable to Entire System.

The Change Requests are created in SE01 and assigned to the developers and Functional Consultants by
Project Manager.
The Change Requests can be created while changing(modifying) the Objects provided the User is
authorized to create the requests
68. How do you Import a Transport Request or How do you schedule a Transport Request Import
Importing the Request:
Select transaction STMS_Import
select the transport Request
Specify the Options(immediate,start date and time or after event)
Execution should be set Asynronous(Default Option)
Select tab Options to import the request unconditionally to select Un conditional Modes
Specify the Client(Client Specific) and Click on the truck to Import the Request
When there is an issue with the request or it hangs.
1. Delete the tp at OS Level

2. Delete the Request from Import Monitor

3. Delete the Request from Import Queue

4.Extras-Add the Request again

5.Select the Request and Import again with overwrite Option
69. What is the meant by Client Refresh
Most of the customers treat client refresh as system copy which is not correct. Client refresh and
refreshes the client specific data. Cross client objects and repository objects are not copied .the client
refresh may fail if the source and target system versions are not same . client refresh depend on the sap
version.
70. Explain transport mechanism

71. Explain when command 'DICO' is used

DICO – display configuration – it will execuete only STMS transaction and it is used to delete the
existing STMS configration
72. What are the RFC Connections and users created during STMS Configuration
When a System is included in the landscape a request is sent to Domain Controller using an RFC
Connection tmsadm@controller.(This RFC Connection is Deleted after TMS Configuration).
Once the system is included in the landscape User TMSADM is created with 2N(Number of
Systems)RFC Connections.(TMSADM and TMSSUP)
One RFC is for TMSADM and the other is Super Destination.
if the RFC Connections Fails(Check File systems Permissions,/etc/hosts entries).
when the Systems are included in the landscape the DOMAIN.CFG is Updated
73. What is Transport layer?
Transport Layer:it specifies the path to move the Objects. SAP Provides a Standard Transport Layer
"SAP" to Transport SAP Objects. SAP Provides a Customizing Transport Layer "ZSID" to Transport
Customer Objects.
74. What is Transport Route? Explain the type of Routes
Transport Route:it Specifies the Source and Target System for Transporting the Objects.
There are two Predefined Routes provided by SAP
1. Consolidation Route
The Route between the Development System(Integration) and Quality System(Consolidation System) is
called as Consolidation Route
2. Delivery Route:

The Route between the Quality System(Consolidation System) and Production System(Delivery System)
is called as Delivery Route.
75. What is Transport Target group
Transport Target Groups:- When more then three Systems are part of the landscape then Systems are
grouped for Transports.(Due to restriction of three system Landscape)
Define Transport target groups in STMS->Transport Routes-->Change-->Edit-->Define Transport Target
groups in the namespace "/ZTRNAS/" using Extended Transport Control and include the Systems in the
Group.
Define the Landscape between the Groups with two standard Routes
76. What is Transport Group
Transport Group: The Location of Transport Directory is identified by GROUP_SID.
if all the systems shares the common transport directory then they are said to be one Group
77. what is common Transport Group/directory
Common Transport Directory: it is shared by all the systems,highly available,system independent,but
shared by production system(Production is sensitive,so it may not be recommended to share with other
systems in the landscape.in such cases Production can be isolated and remaining systems directories can
be in one group)
78. List all the license keys? Explain their significance
SLICENSE:- it is used to update the license which is downloaded from SAP Market Place. The License is
based on hardwarekey.
hardwarekey changes whenever OS is reinstalled.The License key is digitally signed and it could not be
reused. it contains the Installation Number,System Number,Hardware key and License key along with
Valid Date.
Hardware Key: Specific to Operating System changes when every OS changes or reinstalled.Use
Command saplicense -get to get the hardware key or from slicense transaction.
License Key: it is a digitally signed Key from SAP. it is valid until 31.12.9999. it is applied through
SLICENSE.
Maintenance Certificate: it is valid for three months. it is used to maintain the system.SPAM/SAINT gets
locked when this key is expired.it is applied through SLICENSE.
Customer Key: it is a key provided by SAP when SAP Software is Purchased
Installation Number: Each Customer key contains multiple Installation Numbers based on Products ex:
SAP ERP,SAP SCM,SAP CRM,SAP Solution Manager,SAP Netweaver etc....
System Number: it is generated during license key and specific to System.
Developer Key: Each SAP ABAP Developer Requires a Developer Key to develop Objects in the SAP
System(Y-Z).it has to be entered only once.
Object Access Key(SSCR(SAP Software Change Registration Key))
Any Object(A-X) that requires modification by the Customer need to obtain SSCR Key.There are 4
Million Object Keys. It is required to modify the sap standared objects in the name space (A-X)
Migration Key: if there is a change in OS/DB then Migration key is Required.
Solman Key: it is required for Installations and Upgrades. From Netweaver 7.3 it is not required
79. What is Preliminary Transport Request/Emergency Request
Emergency Transport Requests:
(Preliminary Transport Requests)
These are used to transport the objects directly into production system with out following the transport
landscape,but these requests remain in the queue for later import along with other requests.
Copy the Data Files and Cofiles from development system to PRD System
Add the Files to Import Queue->STMS-->Import-->Extras-->other requests--Add Select the Request and
Import.
80. What is Conflict Resolution Transport (CRT)
Conflict Resolution Transports: it is used to resolve the conflicts between Basis and Add-ons.
These are released by SAP vide note 822380.Each and every add-on has a specific note which clearly
describes the conflicts and provide that transport to that note.
Download the transport and import using STMS or Manual tp else include in the Support package Queue.
81. Explain the process of Current Customizing
Current Customizing: it is the process of making the changes to current objects directly in the production
with out having to develop,test and transport to production.
Example: Posting Periods, Exchange Rates, Payroll Parameters
V_T001B V_TCURR V_t511k
ob52 oc41
execute SOBJ transaction-->Specify the table Name-->Select the option Current(settings) Customizing--
>check the box-->Save-->Record--Release-->Transport to Production System
0002121019/0002044885/0002041819
0001168813
This Option allows to modify the Objects in Production system eventhough the System Settings are set to
not-modifiable and client settings are set to no changes allowed provided the client role is set to
Production.

82. Explain the TP mechanism

83. Explain about Manual 'tp' process? How the transports are performed at OS level
Manual TP:
The Manual TP can be initiated in the Following Circumstances
1. when the TP's are choked

2. when the System is Stuck,aborted while applying Support Packages,Add-ons,Language

3. To Import the Transports in a Defined Sequence/Order

4. To Import the Transports into Multiple Systems and Clients.

1. Copy the cofile and data file from source system to target system
2. Add the transport to buffer using command
3. tp addtobuffer SID pf=/usr/sap/trans/bin/TP_DOMAIN_SID.PFL to add the Requests to
Import Queue
4. import the request using command .tp Import <TR> SID clnt222
pf=/usr/sap/trans/bin/TP_DOMAIN_SID.PFL to Import single request into the System
5. if it is mass transport means tp Import all SID clnt222
pf=/usr/sap/trans/bin/TP_DOMAIN_SID.PFL to Import mass transport requests into the
System.
84. Explain about TP Logs(ALOG,ULOG and SLOG)
log: it contains the following logs:
ALog: Application Log
Slog: Job Steps Log
Ulog: Commands Log
Vlog: Versioning
TClog: Buffer Transmission Log
Plog: Processing Log
Qlog: Quit Log
Ilog: Import log
Elog: Export log
Clog: Connectivity log
85. Describe few commands that are executed at OS Level
1. tp addtobuffer SID pf=/usr/sap/trans/bin/TP_DOMAIN_SID.PFL

to add the Requests to Import Queue

2. tp Import <TR> SID clnt222 pf=/usr/sap/trans/bin/TP_DOMAIN_SID.PFL

to Import single request into the System

3. tp Import all SID clnt222 pf=/usr/sap/trans/bin/TP_DOMAIN_SID.PFL

to Import mass transport requests into the System.

tp commands are displayed in Ulog which can be directly used at OS Level.
86. What are unconditional modes
0- Leave transports requests in the Queue for later Import

(deselect if Fully loaded truck option is available)

1- Import Transport requests again(if the changes does not reflect)

2- Overwrite Originals(Overwrite the Objects in the Imported System)

6-Overwrite Objects in Unconfirmend Repairs

8-Overwrite Permitted(non-permitted) transport types
9-Ignore Predecessor Relations
87. What are tables used during transports
TP writes the jobs of import into TRBAT& TRJOB tables . R3trans is executable initiated by TP to
transport the objects. R3trans used to import/export. Rddimpdp/rddnewpp and other rddd* jobs reads the
job steps fromm TRBAT&TRJOB and the program generation , conversion , activation
88. Name some of the jobs steps that are used during an import

89. How the tp does imports the request when more than one request is in QUEUE

90. What are the common Transport errors and their return codes
Issues with the Transport Requests:
1. STMS is Configured

2. /usr/sap/trans is configured with read and write permissions

3. The Change Requests are Released and a Cofile and datafile is created

4. Check whether R3trans,tp are updated

5. Check stms-->overview-->systems-->select the system-->check transport system,transport
tool,transport directory
6. Use report RSTPTEST to check the tp connectivity

7. use command "tp connect SID pf=/usr/sap/trans/bin/TP_DOMAIN_SID.PFL'

8. Date and Time of the transport Request(Mandatory)

9. Sequence of the requests Proposed by developer/Functional Consultant has to be followed

10.Dependency Objects are not part of the Transport Request

11. Execute report rsbdcos0(execute command R3trans -d)

12. Check the tp profile

13. Check rddimpdp is running in client 000 with user DDIC.

14. Check the space in Database and /usr/sap/trans

15. The Component Version does not match(ECC5.0 transport on ECC6.0)

if it is table entry use unconditional mode--6,8,9 to import in a different version or product(ignore

predecessor)
0000 --- successfully completed
0004 --- completed with warnings
0006 --- program issue ( such as activation and dependent program not found )
0008 ---
0012 --- db connectivity errors
Note ; 12 and above all are related to tp errors
91. What is Mass (Monthly) Transport to Production

92 Explain the process of Roll Back a Transport

Most of the scenarios the rollback / reversion of a transport request is not possiable unless the version
management maintined in the development system . the developer can make use the dev system and get
the older version of the program , changes , records
And these all are stored in one cr and releae the cr import again
SE38 – program – utilities – version management
93. What are the issues related to Imports
Issues with the Transport Requests:
1. STMS is Configured
2. /usr/sap/trans is configured with read and write permissions

3. The Change Requests are Released and a Cofile and datafile is created

4. Check whether R3trans,tp are updated

5. Check stms-->overview-->systems-->select the system-->check transport system,transport

tool,transport directory
6. Use report RSTPTEST to check the tp connectivity

7. use command "tp connect SID pf=/usr/sap/trans/bin/TP_DOMAIN_SID.PFL'

8. Date and Time of the transport Request(Mandatory)

9. Sequence of the requests Proposed by developer/Functional Consultant has to be followed

10.Dependency Objects are not part of the Transport Request

11. Execute report rsbdcos0(execute command R3trans -d)

12. Check the tp profile

13. Check rddimpdp is running in client 000 with user DDIC.

14. Check the space in Database and /usr/sap/trans

15. The Component Version does not match(ECC5.0 transport on ECC6.0)

if it is table entry use unconditional mode--6,8,9 to import in a different version or product(ignore

predecessor)
94. What is meant by Transport Organizer

95. What is meant by a Modification? Explain about Repair

Modification : it is the process of creating custom repository objects or modify SAP repository objects is
known as modification
Repair : SAP repository objects such as fileds, domains, data elements , tables , stracuture , programs ,
functional module , memus in the name space of A-X can be modified by developer upon obtain the
SSCR key from market place . these are generally reffered as repair modifiy the objects in the non
original systems are called as repair
96. Explain the significance of change request? What do they contain
Change Request: it Contains the Changes made to the Table,Object,table Entry,Program or any
Repository Object Creation,Change etc...
whenever a Change is initiated they are recorded to a Change Request provided the system setings are set
to Modifiable and Client Settings are set to Automatic recording of Changes.
The Changes Requests are generated from the Table E070* tables.
The Change request Records only the Change made to the rows of table(select,insert,update,delete) along
with the number of reflected Tables

97. Explain the process of the change request release

Change Request Release: when Change request is released the TP is initiated,Connects to the database
and Checks the Contents of the Requests E070 and associated Tables. TP initiates R3trans to read the
content and convert them into File system specific Objects into Cofiles(Command or Control Files) and
Data Files.
TP Stands for Transport Protocol and is governed by the Profile parameter TP_DOMAIN_SID.PFL
98. Explain the process of transport of copies
Transport of Copies: These are used to transport the Entire table along with its Contents.MOstly Used
during System Copies to Copy the User Master(USR02),RFC Destinations(RFCDES) etc....
99. Explain the process of relocation of objects
Relocation of a Package:
it is used to transport the Entire Package. The package contains relative Customer Repository Objects.it is
used to move the Entire Developed Objects to any other system in the Landscape.
100. . How do you unlock the objects which are in Repair/modified state
Go to the transaction code SE03 or execute the program RSWBO099 using transaction code SE38
Double click on unlock object
Enter the object
And finally execute
101. How do you lock the System
Locking the System:

Use Command "tp locksys <SID> pf=/usr/sap/trans/bin/TP_DOMAIN_<SID>.PFL(only DDIC

user is allowed for Login,message Upgrade still running,logon not possible' message is
displayed)

Unlocking the System

Use Command "tp unlocksys <SID> pf=/usr/sap/trans/bin/TP_DOMAIN_<SID>.PFL Locking

102. . How to Interpret "R3trans –d
R3trans –d is used to check the database connectivity to the application
R3trans –d generate the trans.log
This log is used to check the errors
Trans.log is created in the same path where R3trans –d is ececuted
104. . What is the significance of RDDIMPDP/RDDNEWPP
RDDNEWPP is scheduled means automatically RDDIMPDP will be scheduled
RDDIMPDP is required fror transport to get successfully transported and also enable transport run wuth
need to schedule
Schedule RDDIMPDP/RDDNEWPP through SA38 to trgger background JOBS in client 000 using user
DDIC
105. What is the difference between Windows and Linux Installation

106. What is Software Provisioning Manager(SWPM

107. . What is Software Update Manager(SUM

The software update manager is a multi purpose tool that support various process such as performing a
release upgrade, installing enhancement packages, applying support packages, addons.
The sum include an option that combine the upgrade with the database migration
Using database migration option in sum
Sometimes it is reffered as the one-step migration procedure
108. How do you install additional Application Servers
Run ./sapinst (linux) or sapinst.exe for windows
Select the component (ERP,SCM,CRM,SRM,SOLMAN) – SELECT THE DTABASE – ADDITIONAL
APPLICAYTION SERVER INSTANCE --- ADDITIONAL APPLICATION SERVER INSTANCE—
Specify trhe installation type (typical/custom )
Specify the profile directory location
Provide the master password
Specify the kernel and DB client
Check summery
Click on continue
109. How do you install Netweaver Gateway
Download the latest version of netweaver gateway foundation from market place
Copy the .SAR files to trans directory
Give permissions and owner ship to that .SAR files
Uncar the .SAR files using SAPCAR –xvf NWGW.SAR
It will generate the .ATT & .PAT files automatically in EPS/IN directory
Go to application level execute SAINT tcode
Load the ADON from application server or frentend server
Schedule in background mode check the logs in SM37, SAINT tcodes
110. What is the significance of Go -Live Sessions? Explain them in detail
Go-Live Check Sessions:
The SAP GoingLive Check safeguards your SAP solution to a smooth start of production. This proactive
service mitigates the risks that arise from non-optimal system and business process configuration. It
ensures a technically robust operation from the beginning and therefore protects your business.
Analysis session: checks the configuration of the SAP system including the database. The session is
scheduled a minimum four weeks before your start of production.The Analysis session should be
performed at least six weeks before your planned start of production date. The prerequisites for this
session are detailed data about hardware, the number of users for each application, the expected data
volume and the interfaces within the entire system. In order SAP can deliver the Analysis session the
customer needs to complete the "Prepare" step than can be accessed via the SAP Solution Manager
"Service Engagement and Service Delivery" workcenter. The "Prepare" step should be completed
approximately one week before the Analysis session. The result of this session is a report that gives
information on the hardware resources situation and what parameter configurations need to be performed
for a successful start of production.
Verification session: verifies the smooth operation and performance of the productive environment and is
scheduled approximately four to six weeks after start of production
The Verification Session is a routine check of the system to verify the assumptions from the Analysis
Session. It looks at the following:
Implementation of the SAP recommendations listed in the report from previous GoingLive sessions
System availability and configuration
Performance of business processes
The Verification Session checks your system behavior approximately six weeks after the start of
production. The result of this session is a report similar to that received in the Analysis Session. The
difference is that now you have a productive system which contains representative data from daily
operations, and users can provide feedback on their experience with the production system. The report
confirms system configuration and provides additional recommendations for improvements
111. . How do you activate Business Extension 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.)
• 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)(Retail and manufacturing)

112. How do you activate Business Configuration Sets?(BC Sets)

BC Set is a management tool that allows user to record, save and share customization
settings. BC sets are snapshot of customization settings that can be used later as
template or customization backup. BC sets can also be used in group rollouts where the
customization settings can be compiled for pilot and passed on in a structured way to
other rollout locations. SAP also provides pre packaged BC sets for selected industry
sectors.
When BC Set is created, values from original customizing tables are copied into BC Set.
When you activate this BC set in other system the values stored in BC sets are copied to
corresponding customizing tables of the system. The settings in the BC set can be
compared with system data to check the consistency of data
Benefits of BC sets
1. Store customization settings backup
2. Useful in Template Rollouts
3. Efficient Change Management