These Are The FAQ

Frequently Asked Questions
By
Shailesh D. Mamidwar
2
These are the FAQ’s Collected from SAPSUPERUSERS.

What is the difference b/n roles & profiles?
-> Roles are a collection of transactions and authorization objects. Profiles are the output
of generating a role.
-> More precisely, Roles are collection of authorizations to be provided, and Profiles are
generated to define uniqueness of the Role.
Every time a unique profile is generated for a new role.
Role is just a container of the authorizations and users assigned.

Actual assignment of the authorization is done by Profiles only.
-> Also role is invalid without a profile. You add role to user master record which will
automatically add profile to master record. Never do the reverse
Cannot activate a table in SAP
Syntax error in SDCC, table inconsistency between ABAP Dictionary and the database,
transport error 8 during the generation of ABAP Dictionary. When you call Transaction
SDCC, a termination occurs due to a putative syntax error because a table is not known
or active. When you check this with the ABAP dictionary (SE11), you notice, that the
table is active or inactive, however it is not possible to activate it. The activation might
terminate with the error message 'Inconsistency between ABAP Dictionary and database'.
A check of the affected object also delivers this error.
Solution
Proceed as follows:
• Log on as user DDIC

• Call Transaction SE14
• Enter the affected table name and
• select EDIT
• In the following screen, choose Table -> Reconstruct
• Confirm the execution
• Call Transaction SE11
• Enter the affected table name
• Display
• Activate
Shailesh D Mamidwar SAP Basis Consultant

3
If - after you chose EDIT -, the error message occurs that the table only exists on the
database, you need to activate the source and the runtime object.
• Call Transaction SE37:

-> Function module 'DD_TABL_ACTM' -> Single test
• Under import parameter MODE, enter the number 12 and under TABNAME the
corresponding table name
• -> Execute (F8) -> Export parameter ACT_RESULT must be 0
• Call Transaction SE14 again as described above.
• -> Extras -> Database object -> Check,
as well as
-> Extras -> Runtime object -> Check
inconsistencies should no longer be contained.
If you cannot switch to the EDIT mode in Transaction SE14, which means no
modifications are allowed in the customer system, then proceed as follows:
• Call function module 'DD_TABL_ACTM' as described above.

• Then call Transaction SE14 again and verify that the table has been activated.
• As a result, this ensures that the SDCC can be executed.
• The menu options in Transaction SE14 are
-> Extras -> Database object -> Check,
as well as
-> Extras -> Runtime object -> Check
inconsistencies should no longer be contained.
• If this is not the case, open a CSN message under the BC-DWB-DIC-ED
component.
How to apply OSS Note?
OSS notes is the old name for SAP Notes (OSS was the name of the support system at
SAP).
SAP Notes typically contain bug fixes for SAP software. In addition some name may
include corrections to guides and manuals, provide some consulting tips, or provide 'hot
news' for customers on critical information.
Depending on the correction you may apply the fix in a number of ways:
- Apply an ABAP fix via transaction SNOTE
- Apply Java fixes through the java developer tools
- Apply binary patches by downloading the fix and replacing the existing binary file
- Apply parameters via a file editor or profile editor
- the list goes on... The note typically gives you some application directions.
You can find notes via the SAP Service marketplace (SMP): http://service.sap.com/notes

4
You will need a support user (sometimes called a S# user) for this and your SAP system
administrator can provide this as your company gets these with their license.
One word or advise, learn how to apply the fix using the right tools before trying it
blindly. Incorrectly applying a fix can be worse than the original problem to fix.
Can i find hostname and IP address of the user using SAP ?
check table USR41 via transaction SE16
didn't realize you can also get this information via sm04, turn "on" the user's checkbox,
and click the Details button.
how to connect bw to n r/3 system ?
steps to connect BW & R/3

Please note following steps....
1. Create a logical system using tcode SPRO or SALE..Assign Logical system name to
your BW & R3 clients.
2.Now Using SPRO maintian prosoal for User id ALEREMOTE.
3.in BW system put tcode RSA1--> Source System. Here enter your R/3 System
details.& create a connection..After some ime it will show connectivity.
4. Using this method RC connections will get creates automaticlay..U can check that in
tcode SM59.
Another method is 1st create RFC connetions & then go to RSA1 & connect it..
But in bw when i run transaction rsa1 it says plz operate in client 000 n when i run in
client 000 it says sap-bw system must not be operated in client 000 plz tell me what
should be done.....
Change Client in BW
Run transaction RZ10 from BW and create following profile parameter in instance or
default profile
login/system_client -> your application client (i.e 100)
save profile and restart BW server.
Define Instance.
Answer
An instance is an administrative unit in which components of an R/3 systems
providing one or more services are grouped together.

5
The services offered by an instance are started and stopped at andom. All
components are parameterized using a joint instance profile.
A central R/3 system consists of a single instance in which all-necessary SAP

services are offered.
Each instance uses separate buffer areas.
Determining Change Documents
Use
You can use this report to determine all changes to a user (RSUSR100), profile
(RSUSR101), or an authorization (RSUSR102).
Note that changes are divided into two areas:
• Changes to authorizations: creating the user, changing, adding, or removing profiles
• Changing header data: password changes, validity, user type, user group, account
number, lock status
You can select both field to obtain all information. In this case, the left column shows the
status before the change the right column the changed entry.
Procedure
1. Start the user information system (transaction SUIM).
2. Expand the Change Documents node.
3. Choose the Execute option next to For Users (or For Profiles or For Authorizations).
4. Specify the user (or the profile, or the authorization) and other restricting values, and
choose Execute.
The result list Lists of Change Documents for Users appears.
5. You can display details for profiles and authorizations by double clicking the appropriate
object in the result list.

6
Use STAT Watch Users
An easy way to view user activity, and many other useful system statistics, without
turning on trace is to use the STAT TCode. Once you select STAT you are presented
with a selection screen where you can enter a user ID and a date and time range, the
resulting report will show everything that a user has accessed from TCodes to the
program names! Further drill downs are available that will show the number of records
that the user retreived when he ran a report. You can also use this in reverse by entering a
specific TCode and leaving an "*" in the User field to display which users are using that
transaction. This tool has many options to explore.
Client Mgt - All SAP - Copy Table Entries To Clients
SAP Provides additional reports useful for copying information between clients:
RSCLCCOP - Copy object lists between clients

RSCLXCOP - Copy client-specific tables from a client
RSDBVCOP - Copy variants between clients
RSREFILL - Copy translations between clients
RSTXFCPY - Copy forms between clients
RSTXSCPY - Copy styles between clients
RSTXTCPY - Copy texts between clients

7
1. What guarantees the integration of all application modules?
The R/3 basis system guarantees the integration of all application modules.
The R/3 basis s/w provides the run time environment for the R/3 applications
ensures optimal integration, defines a stable architectural frame for system
enhancements, and contains the administration tools for the entire system.One of
the main tasks of the basis system is to guarantee the portability of the complete
system.
2. What are the central interfaces of the R/3 system?
Presentation Interface.
Database Interface.
Operating system Interface.
3. Which interface controls what is shown on the p.c.?
Presentation Interface.
4. Which interface converts SQL requirements in the SAP development

system to those of the database?
Database Interface.
5. What is SAP dispatcher?
SAP dispatcher is the control agent that manages the resources for the R/3
applications.
6. What are the functions of dispatcher?
Equal distribution of transaction load to the work processes.
Management of buffer areas in main memory.
Integration of the presentation levels.
Organization of communication activities.
7. What is a work process?

8
A work process is where individual dialog steps are actually processed and
the work is done. Each work process handles one type of request.
8. Name various work processes of R/3 system?
Dialog or Online (processes only one request at a time).
Background (Started at a specific time)
Update (primary or secondary)
Enque (Lock mechanism).
Spool (generated online or during back ground processing for printing).
9. Explain about the two services that are used to deal with
communication.
Message Service: Used by the application servers to exchange short internal

messages, all system communications.
Gateway Service: Enables communication between R/3 and external applications

using CPI-C protocol.
10. Which work process triggers database changes?
Update work process.
11. Define service (within R/3)?
A service is a process or group of processes that perform a specific system

function and often provide an application-programming interface for other
processes to call.
12. What are the roll and page areas?
Roll and page areas are SAP R/3 buffers used to store user contexts (process
requests). The SAP dispatcher assigns process requests to work processes as
they are queued in the roll and page areas.
Paging area holds data from the application programs.
Roll area holds data from previous dialog steps and data that characterize the
user.

9
13. What are the different layers in R/3 system?
Presentation Layer.
Application Layer.
Database Layer.
14. What are the phases of background processing?
Job Scheduling.
Job Processing.
Job Overview.
15. What components of the R/e system initiate the start of background
jobs at the specified time?
The batch scheduler initiates the start of background job. The dispatcher then
sends this request to an available background work process for processing.
16. Define Instance.
An instance is an administrative unit in which components of an R/3 systems

providing one or more services are grouped together. The services offered by an
instance are started and stopped at random. All components are parameterized
using a joint instance profile. A central R/3 system consists of a single instance
in which all-necessary SAP services are offered. Each instance uses separate
buffer areas.
17. From hardware perspective, every information system can be divided

into three task areas Presentation, Application Logic and Data Storage.
The R/3 Basis software is highly suitable for use in multi-level client/server
architectures.
18. What are R/3 Basis configurations?
A central system with centrally installed presentation software.
Two-level client/server system with rolled out presentation software.
Two-level client/server system. Presentation and Application run on the same

computer.

10
Three-level client/server system. Presentation, Application and database each

run on separate computers.
19. What is a Service in SAP terminology?
A service refers to something offered by a s/w component.
20. What is Server in SAP terminology?
A component can consist of one process or a group and is then called the server
for the respective service.
21. What is a client in SAP terminology?
A S/W component that uses the service (offered by a s/w component) is called a
Client. At the same time these clients may also be servers for other services.
22.What is a SAP system?
The union of all s/w components that are assigned to the same databases is
called as a SAP system.
23. What is the means of communications between R/3 and external

applications?
The means of communication between R/2,R/3 and external applications is via

the CPI-C handler or SAP Gateway, using the CPI-C Protocol.
24. What is the protocol used by SAP Gateway process?
The SAP Gateway process communicates with the clients based on the TCP/IP
Protocol.
25. Expand CPI-C.
Common Program Interface Communication.
26. What is a Spool request?
Spool requests are generated during dialog or background processing and

placed in the spool database with information about the printer and print format.
The actual data is places in the Tem Se (Temporary Sequential objects).
27. What are different types of Log records?

11
V1 and V2. V1 must be processed before V2. But, we can have more than one
V2 logs.
28. What are the types of Update requests?
An update request can be divided into one primary (V1) and several Secondary
update components (V2). Time-critical operations are placed in V1 component
and those whose timing is less critical are placed in V2 components. If a V1
update fails, V2 components will not be processed.
29. Dialog work processes perform only one dialog step and then available
for the next request.
30. Explain what is a transaction in SAP terminology.
In SAP terminology, a transaction is series of logically connected dialog steps.
31. Explain how SAP GUI handles output screen for the user.
The SAP front-end s/w can either run on the same computer or on different
computers provided for that purpose. User terminal input is accepted by the SAP
terminal program SAP GUI, converted to SAP proprietary format and sent to the
SAP dispatcher. The dispatcher coordinates the information exchange between
the SAP GUIs and the work processes. The dispatcher first places the
processing request in request queues, which it then processes. The dispatcher
dispatches the requests one after another, to the available work process. The
actual processing takes place in the work process. When processing is
complete, the result of a work process is returned via the dispatcher to the SAP
GUI. The SAP GUI interprets the received data and generates the output screen
for the user.

12
APPLICATION SERVER
This is a diagram of an SAP Application server, showing the different work processes
that are performed. Moving the mouse over a work process reveals a more detailed
diagram of that service. SAP also consists of Message servers and Gateway servers,
which are not pictured here. Message servers handle communication between servers and
processes within the SAP system. Gateway servers deal with communication between the
SAP system and outside systems.
Dialog Work Process/Server
Each Dialog work process handles one dialog step of a user transaction, then becomes
available to process another dialog step. A Dialog server consists of a Dispatcher and a
fixed number of Dialog work processes which are available exclusively to handle dialog
requests.
Batch Server
Batch processing allows a program to be run at a scheduled time in the background. A

background scheduler is responsible for starting jobs at the requested times. Jobs are
processed as if they were entered by a user, so they must pass through the same dialog
steps; this ensures the integrity of the system.
Update Server
Since the Update server must make changes to the database, it is usually on the same
physical system as the database. When an update is requested, the job is separated into a
dialog portion and an update portion. First, the dialog portion creates a log file, which is
then used by the update work process to perform the actual changes.
Enqueue Server
Rather than relying on the database to control access to the data, SAP implements its own
system for controlling access, called the Enqueue server. The Enqueue server uses lock
tables to manage access to the data, ensuring only one user at a time has the ability to
make changes to the same data.
Spool Server
When a Spool request is generated, the data is placed in TEMporary SEquential objects,
and information related to the request is stored in the database. When the request is ready
to be printed, it is handled by the Spool work process, which formats it and passes it to
the operating system's spooler. The operating system spooler may be on the user's
workstation, or on a separate system altogether.

13
Everything about SAP Clients ....by Saroj Mohapatra
1. Overview....Click here...
2. About SAP Clients....Click here...
3. Creating a client and setting up the client attributes....Click here...
4. System-level control in transaction SE06....Click here...
5. PRE-CONFIGURED Client from SAP....Click here...
6. CLIENT COPY Procedures....Click here...
7. Creating custom PROFILES to copy Clients....Click here...
8. Client COPY within a System....Click here...
9. Client COPY from one System to another....Click here...
10. Transporting a Client....Click here...
11. Remote CLIENT Copy....Click here...
12. Deleting a CLIENT....Click here...
13. Ten golden rules for CLIENT copy....Click here...
14. Simple method for copying VARIANTS....Click here...
Overview
A client is organizational and legal entity in the SAP system. All the business
management data is protected here because other clients can not access them. The
main objective of the client is to keep the data isolated. The data in a client can be
only visible within that client; it can not be displayed or changed from another client.
In a physical SAP system there can be multiple clients. Each of these clients can
have different objective or each client represents a unique work environment. In a
development environment one client can be used as sandbox client (developers learn
how to configuration using SAP environment), one can be used as prototype client
(users do the customizing according to the company’s requirements and testing) and
another one can be used as the master development and configuration client (where
the final configuration is done). A client has its own set of tables and user data. To
know whether a table is client dependant or independent you can search for a field
MANDT. The client dependant tables always include the client field ‘MANDT’ as a part
of the primary key. There can be multiple clients in each of the system of SAP
system landscape as we have already seen in chapter 5. It is better to understand
the customizing process in the CTS pipeline before designing a good client strategy
for the SAP systems. Customizing is a method in the SAP R/3 system that helps the
user to configure the functionality from SAP, according to the customer
requirements. When the SAP objects are just used by only one client, we define
them as client dependant data. There are some objects as ABAP/4 programs, which
are used by all the clients in a SAP system. Those objects are called client
independent data. The functional changes resulting from customizing can be client
specific (client dependant) or general (client independent). You must know the fact
that client independent customizing can create problems if the authorizations and the
client strategy are not defined properly. For example if you have three clients in a
development environment then the role of each client should be defined properly.
One of these three clients should be used for client independent customizing and in

14
other clients, users will not have the authority to do any client independent
configuration.
About SAP Clients
With a standard installation, SAP delivers 000, 001 and 066 clients. Client 000 is
considered to be a SAP reference client and it should not be changed or deleted at
anytime from the system. After a SAP system is installed, you can create other
clients from 000 by using the client copy procedure. For some important
configuration you have to logon to client 000. For example, if you want to configure
your CTS system then this client must be used. Client 000 also plays a very
important role in upgrade process. Every time you do upgrade client dependant
changes will be automatically upgraded in this client and later on the changes can be
copied to other clients.
The customer uses client 001 as a SAP sample client. After a new installation both
000 and 001 clients are identical, but after an upgrade 000 will have additional
customizing data. Lot of customer sites does not use 001 client at all. Client 066 is
there for SAP Early Watch service. This client enables SAP to remotely access the
customer system. SAP provides this service to the customer to improve the system
performance. After Early Watch group goes through the checking methodology, a
system performance summery and recommendations to improve performance report
are provided to the customer. SAP recommends to go for an Early Watch session
before your project goes live and another one sometime after the go live date. Client
066 should not be changed or deleted from the system. In case this client was
deleted from the system, then you have to follow the instructions in OSS note 7312
to download the client data from sapserv3 and import this data to create 066 client.
Creating a client and setting up the client attributes
To create a client you have to maintain T000 table. From 3.0 onward, transaction
SCC4 can be used to maintain T000 table. Also you can chose Administration->
Client admin -> Client Maintenance from the initial screen to do the same. In client
table T000, SAP system displays all the clients available, their names, currency used
and when the client was changed last as shown in Figure 9.1. If the system is in
display mode then you must change it to the change mode by selecting the
display/change icon to create a new client. When you click display/change button, a
warning is displayed as “Warning: the table is client-independent”. The “New entries”
icon should be clicked to create a new client as shown in Figure 9.2.
Figure 9.1 shows Client overview in SCC4 transaction

In the new client creation screen to define a new client you must fill all the required
entries. The client number and the name are entered first. Then in the second line
the location of the SAP system is defined.
Logical system is defined next. SAP uses logical system concept in ALE (Application
Link Enabling), workflow and EDI areas. The logical system must be unique through
out the company and any other ALE system group can not use it. You must be
careful changing the logical system entry. SAP treats a logical system as a client. You
can use transaction BD54 to create a logical system and then enter that entry in the
logical system box while creating a client.

15
Next entry “standard currency” can be defined according to the country. For example
USD can be used as a standard currency for USA. To enter a category of a client you
must know the objective of that client beforehand. For example if this client will be
used as a customizing client then customizing entry should be used from the options.
In the next category “Changes and transports for client-dependent objects”, there
are four options. If you want to use this client as a sandbox client; and you do not
want to record or create a change request every time a change happens to the client
then “Changes W/O automatic recording” is the right option. If all the changes to the
client should be recorded in a change request then “Automatic recording of changes”
is the right option. You must choose this option for your master configuration client.
If “No changes allowed” is chosen, then no changes will be allowed to this client.
You must chose his option for clients in the production environment to protect your
system. “No transport” option is used when you do not want any user to create a
transport from this client.
Figure 9.2 shows the client create screen

The “Client-independent object changes” category determines if the client
independent data maintenance is allowed in this new client. You get following four
options in this category:
• Changes to Repository and client-ind. customizing allowed

• No changes to client-independent customizing objects
• No changes to Repository objects
• No changes to Repository and client-independent custom. obj.
To choose the right option from “Client-independent object changes” category, you
must know the definition of Clint independent customizing objects and repository
objects. The examples of SAP repository objects are data dictionary objects, module
pools and screens. Client independent objects apply to all the clients. The factory
calendar is an example of client independent object of customizing. For sandbox
client, where user learns how to do the customizing, you must not allow the client
independent customizing.
Changes to Repository and client-ind. customizing allowed: Both client

independent customizing objects and SAP repository objects can be maintained.
Usually this option is selected in a master-customizing client.
No changes to client-independent customizing objects: No change is allowed
for client independent customizing objects but changes to repository objects are
allowed. This option can be used for a sand box client.
No changes to Repository objects: If you select this option, then no changes are
allowed to the Repository objects but the client independent customizing is allowed.
When you want to protect the repository objects in a client, this is the right option to
use.
No changes to Repository and client-independent custom. Obj: This option
does not allow any changes to client independent customizing objects and repository
objects. You should use this option for a consolidation and production client where
the security of client independent objects and repository objects are necessary.
In the restriction category of the ‘Change View “Clients”: Details’ screen, there are
four options. You are allowed to maintain only the following three options as shown
in Figure 9.2:

16
• Protection against overwrite by copying: If you chose this option, a

client copy can not overwrite the new client. You should chose this option for
a master-customizing client or for an important client as production.
• Start of CATT processes allowed: This option determines whether you
want to allow the CATT (Computer Aided Test Tool) process in the client or
not. Computer Aided Test Tool (CATT) is tool provided by SAP to test different
functionality of the SAP system. To run the CATT tool you can execute
transaction SCAT. CATT process changes the database extensively and
requires lot of system resources. So we recommend not to chose this option if
you are in the production environment.
• Protection against SAP upgrade: If you chose this option, then this client
will be not updated in time of upgrade. You should use this option for a client
that is used for backup purposes or client 066 (Early Watch client) that is
used by SAP for customer’s SAP system performance. If you chose this option
for any client, the upgrade will not provide any data to this client and it can
not be used as a regular customizing client. You need S_CTS_ALL
authorization to maintain this option.
System-level control in transaction SE06
You can use the system change option to control the system level access to different
types of users in a SAP project. To use system change option screen you can chose
SE06 and then system change option or use SE03 and then go to “for setting the
system” category and chose “set system change options”. The option you chose here
directly affects ABAP/4 workbench, Workbench Organizer and the transport system.
You need all access to Workbench Organizer to change the system change options as
shown in Figure 9.3.
There are some TP commands that can be used to control the system level access. ·
System change option in se06 figure9.3
The following are the four system change options:
• Objects cannot be changed: If you select this option then no changes of

any kind are allowed for any objects in the SAP system. The SAP customers
use this option in the consolidation and production environment. Using this
option you can control the developers and the customizing people directly
changing any development objects and customizing objects in the
consolidation and production environment. So the users use the transport
method to move the objects from development system to other systems
instead of directly creating or maintaining them in the target systems. The tp
command “tp lock_eu <sapsid>” can be used in the operating system level to
set the system to "cannot be changed" and the command “tp
unlock_eu<sapsid>” puts the system back to where it was when the lock
command was executed.
• Only original objects (w. Workbench Organizer): If you go for this option
then only original objects those are created in this system can be changed. If
the original object exists in some other system and you have a copy of that
object in this system then you can not change that object. In special cases
you can use this option for the QA or test system. All the changes are
recorded in Workbench Organizer.

17
• All customer objects (w. Workbench Organizer): This option allows you to
edit or repair an object though it is not the original object of the current
system. Any changes to customer objects are allowed. The changes are
controlled and recorded by the Workbench Organizer. This option does not
allow changing the objects came from SAP originally. You can use this option
in a training system.
• All objects (w. Workbench Organizer): With this option you can change or
repair any objects in the system. Now the system is totally open for any
changes to all the objects. With this option also every change is recorded and
controlled by the Workbench Organizer. This option is generally selected in a
development or sandbox environment.
From 4.0 version the se06 change option looks as following:
Pre-Configured Client from SAP
The pre-configured client from SAP has pre-configured customizing objects for a
simple organizational structure. The pre-configured settings of the client help a
customer to configure a system quickly. SAP recommends the customers to install
the pre-configured client in their system if they want to go for a rapid
implementation using ASAP (Accelerated SAP) methodology. In the ASAP chapter we
are going to give you an extensive definition about this methodology. Now instead of
starting from client 001 copy, you can start from a pre-configured client that will
provide more configured features.
SAP provides the transports and help documentation to create a pre-configured
client. The pre-configured client for FI/CO, SD, AM, MM, HR and PP modules is
already available from SAP. According to SAP, customers that have used the pre-
configured client saved 4 to 6 weeks of project implementation time. The way pre-
configured client is designed; some of the small companies can run the pre-
configured client for production after the out of the box installation.
Following procedure is used to create a pre-configured client:
· A client is created in T000 table
· Copying client 000 to the new client
· Copying the data files and cofiles from SAP to your system
· Adding those change requests to the buffer and then importing them to the target
client
· We recommend to check your number ranges after the import
· Creating a user and assigning SAP_ALL and SAP_NEW profiles
· Run the SCAT transaction for CATT tool to test the pre-configured client. This tool is
a great tool for those users, who want to learn about SAP functionality and, what a
pre-configured client can do for them?
·The pre-configured client comes with non-matric units of mass, area, length and
volume and a sample factory calendar is pre-configured with the ten US government
holidays.
Client COPY Procedures
After the SAP system is installed, the client copy is a common thing to do for
creating new clients. A client copy can be done from one system to another or within
one system. A client copy can affect the database and current users in the system;

18
so you need to be aware of the following important information before scheduling a

client copy.
For the stability of the system, always schedule the client copy in the nighttime when
the users are not working in the system.
To avoid data inconsistency you should not keep on working in the source or target
clients when the client copy is going on.
For the best performance, always schedule the client copy in the background. Try to
examine the maximum online runtime parameter “max_wp_run_time” in the
instance profile. You might need to increase this for a large table copy.
You should have proper authorizations to run the client copy. As a basis system
administrator you should have SAP_ALL profile to complete a client copy
successfully. If you do not want a generic id to run the client copy; we recommend
using SAP*. The internal user SAP* has all the authorizations needed by the client
copy.
Always check the database resources before executing a client copy. You can do that
by running a "test run" client copy. The test run will provide all the information about
the necessary database table spaces that you need in the target client.
The main memory plays a significant role in the client copy. Make sure that you have
enough memory to finish the client copy without any problem. When you are
planning the hardware requirement for the SAP installation, it is always better to
install memory recommended by SAP. Version 3.X and 4.X require more memory for
memory management and client copy.
When you trying to copy a large productive client, it better to copy the cluster tables
first.
You should look for all the OSS notes that apply to the client copy in a particular
version of SAP. For example according to OSS note number 34547, SAP_USR client
copy parameter that suppose to copy only user data in the background also copies
customizing data in the background for release 3.0B.
If the client copy is locked by another client copy run, then check the log before
deleting the lock entry in SM12 to remove the lock.
In 2.2 release of SAP R3trans is used for client copy, client export and client import.
You should not do the same in 3.0 or 4.0 release of SAP. You can use R3trans to
remove a client in 3.0 and 4.0 also and we will see the procedure in the “deleting a
client” part of this chapter. R3trans can be used also for some other important jobs
as described in chapter 10.
It is very important to know that the number ranges have to be reset in the target
client if you are just copying the customizing data. Though the client copy utility has
been improved a lot still we get problems with number ranges. We recommend
checking the OSS notes about number ranges before dealing with them.

19
When you perform a client copy, it is very important to know the three levels of data
in SAP system and how they affect the client copy. The client dependent application
data is created from the master and transaction data of the system during the
application system operation. The client dependant customizing data is created
during the development process of a SAP project and this data depend upon the
client dependent application data. The client independent customizing data applies to
the entire client. The client copy procedure copies the client dependent application
data and client dependent customizing data unless you specify to copy the client
independent customizing. To maintain the consistency you should follow some SAP
rules. When you are copying the customizing data, you should copy the application
data (master and transaction data). If you just want to copy the customizing data
then remember that all the application tables are reset in the process and this reset
process can guarantee the consistency of the client
Creating custom PROFILES to copy Clients
Client copy profiles are used to copy specific data from one client to another. SAP
provides some custom profiles to perform a client copy. The following are the
example of profiles provided by SAP.
SAP_ALL: All data of a client

SAP_APPL: Customizing, master and transaction data
SAP_CUST: Customizing data
SAP_UAPP: Customizing, master&transact.data, user masters
SAP_UCUS: Customizing data, user masters
SAP_USR: Authorizations and user masters
The objective of above client copy profiles is defined clearly. What profile you are
going to use; depends on what you want to copy from one client to another. For
example you want to copy the entire data of a client then you want to choose
SAP_ALL as your copy profile. you can select a profile name from the profile input
field possible entries and then chose Profile -> Display profile from the menu. You
can create a custom profile according to your requirement. To create a custom
profile you need to chose the path Profile-> Create profile from client copy or client
export screen.
Profile: Here you define the profile name. The name should be according to the SAP
standard; so it should start with either Z or Y.
Last changed by and last changed on: These fields show the information about the
person who last changed the profile and the time it was changed.
In the data selection category we have the following three selections:
User masters: If you chose this option then the user master records will be copied
from the source client to the target client.
Customizing data: If you want to copy all customizing data then chose this option.
Appl. Data. Initialization. Cust. Data: This option copies master, transaction and
customizing data from the source client to the target client.

20
Important tips: It is very important for you to understand the data selection
procedure before the client copy. In SAP environment it is not possible to copy
selected parts of the application and customizing alone. If you want to copy
application data, we recommend doing it in batch input. With batch input consistency
is ensured.
In the copy mode category the following options are displayed:
Initialize Recreate: This option is grayed out and already selected. This option
allows the system to delete all the tables (not selected in the client copy process) in
the target client and initialize them. You can use the path Extras -> No initialization
to have an option for not choosing this option. We recommend not doing that; it
might create instability in the target client.
Copy variants: If you want to include variants in the client copy then chose this
option.
In “transport between 2 systems” category there is one option:
Client Independent data: If you chose this option then the client independent data
will be copied from one client to another. We recommend executing the client copy
remote compare program “RSCLICMP”, before choosing this option to do a client
copy. This program provides all the information regarding the differences between
the source and target systems client independent tables.
The other options are:
• Default source client: You define the default source client for the client
copy in the profile. You can change the client after choosing this profile before
starting the client copy.
• Default source client user master record: You can enter the client
number from where the user master records will be copied to the target
client. You can also change this like default source client.
Comment: You should provide a meaningful description for the profile here.
Client COPY within a system
SCC0 or RSCLICOP (SCCL as of 3.1 release)
In 3.0 SAP uses RSCLICOP program in transaction SCC0 to copy the

customizing environment from one client to another. This will copy client–
dependent tables, match codes, number ranges and resolve the logical dependencies
between tables and programs. RSCLIC01 or RSCLIC02 were used to copy clients in
2.0 release. These programs use to create command files and the basis administrator
was running R3trans utility to transport the data files. Those programs are not
supported in 3.0 anymore. For the mass data transfer and large number of table
copy, we recommend you to run the RSCLICOP program in the background.
Tips: Trace information about each client copy run is stored in table CCCFLOW.
Use program RSCCPROT to display information about the client copy. You can run

21
RDDANATB program in the background to get the information about the size of all
the tables in all the clients. If you start the RSCLICOP in restart mode then try to
check the checkentries in table CCCFLOW.
The copy procedure using SCCL
If you are planning to copy the source client to a new client then you must create a
new client in SCC4 or table T000 before starting the client copy.
Logon to the target client and chose transaction SCCL or use the path Tools -
>Administration->Choose Administration ->Client admin->Client copy ->Local copy
and you will see a initial client copy screen as shown in Figure 9.6.
The current client is your target client so it is already selected for you in the first
line. In the second line select the appropriate profile you want to use for the client
copy. You choose the source client in the third line. In fourth line you can define the
client from which you want to copy the user master records. The “Source Client User
Master” does not have to be same as source client. Then if you want to run the local
client copy to get the information about the storage requirements or a complete
table statistics then select the “test run” flag. We recommend you to run the client
copy using the “test run” mode first. In test run phase, database updates are not
performed.
You should schedule the client copy in the background after all the parameters are
selected as shown in figure Figure 9.6. You can run a client copy online if you are
just copying the user master records; because when you copy only user master
records very limited data is copied form a client and it does not take that long to
copy those data.
Figure 9.6 local copy transaction sccl
If the client copy fails for some reason then you can restart the client copy in the
restart mode after the fixing the problems. In this case the client copy will start
exactly from the same point where it failed. A pre-analysis phase requires sometime
determining the restart point. SAP recommends to set the restart flag in the
“Execute in background” screen when you plan to copy a large client.
Tips: We recommend to reset the buffers by entering "/SYNC" in the OK code on all
the application servers after executing the RSCLACOP or SCC0 for the client copy.
RSCLICOP compares the contents of each table in the source client with that in the
target client.
Client COPY from one system to another
Client copy from one system to another:

SCC1, SCC2, SCC7, SCC8, RSCLIEXP, RSCLIIMP
The client export/import and remote client copy procedures are commonly used to
copy a client from one system to another. The client can be exported from the
system using transaction SCC8 and then importing the client using SCC7 or using the
transaction SCC2 for both export and import process, the second procedure is to do

22
a remote client copy from one system to another. If you are copying a production
size client we recommend performing the client copy using the first procedure.
The following are the steps in the whole procedure:
• First the data from the client in the source system is exported from the
database to a transport file on hard disk. Before you transport a client from
the source client database, you need to know exactly what you want to
transport and you use SAP delivered profiles accordingly.
• Then the SAP delivered TP command is used for the import to the target
system client database.
• The post processing procedure is run in the target client to successfully
complete the client import.
You have to be very careful when copying the client independent data, because
client-dependent customizing objects are dependent on entries in client-independent
tables. SAP recommends that you should not copy the client independent tables if
they are not yet modified in the target system. If the customizing is being done in a
system regularly then you have to be very careful taking the client independent
customizing to that system; otherwise you might overwrite the whole client
independent customizing settings and the system will become inconsistent. We
recommend to consult the customizing team of a project before copying the client
independent customizing tables.
Transporting a Client
Procedure: To transport clients from one system to another, go to System

Administration then choose Tools -> Administration -> Client admin->Client
transport -> Client export or transaction SCC8. In the client transport screen you can
select a copy profile that matches your requirements and the target system in your
CTS pipeline as shown in figure 9.7. Then you can execute the client export in the
background or online. Before the client export starts, a popup screen shows all the
information about the command files that will be created after the client export is
done. After the process starts. You can watch the export process in client copy log
using transaction SCC3.
Figure 9.7 showing transaction SCC8
After the client export procedure is completed, if you chose the client independent
data then three transports are created in /usr/sap/trans/cofiles or there will be two
transports:
<sid>KO<no> for the client-independent data ( if selected). For example if the client
export is done from development client 100 then the file will look like DEVKO0001.
<sid>KT<no> for the client-specific data. For example DEVKT0001
<sid>KX<no> for the SAPscript objects as Texts and forms. For example
DEVKX0001

23
The data export is performed automatically. The output of the export includes the
name of the COMMFILE that has to be imported. The following data files will be
created in /usr/sap/trans/data directory using the same example given above:
For client dependent data: /usr/sap/trans/data/RT00001.DEV

/usr/sap/trans/data/DX00001.DEV
For client independent customizing data: /usr/sap/trans/data/RO00001.DEV
For SAPscript data of a client: /usr/sap/trans/data/SX00011.DEV
Tips: Make sure that all the cofiles and the datafiles exist in the data and cofile
directories before starting the import phase.
Then add all the command files to the buffer by using the TP command in
/usr/sap/trans/bin directory as following:
tp addtobuffer <cofile name> <target sid name>

Using the above example cofile: tp addtobuffer devkt00001 qas (if qas is our target
system)
tp addtobuffer devko00001 qas
tp addtobuffer devkx00001 qas
Then logon as <sid>adm to the target system and then use then import the
transports as following:
tp import devkt00001 qas client100 u148 – For the client dependent data
tp import devko00001 qas client100 u148 – For client independent data
(In the above example QAS is the target system and 100 is the target client)
After you import a client from another system, you must perform post-processing,
activities in order to adapt the runtime environment to the current state of the data.
To execute post-processing, choose Tools -> Administration- >Client admin ->Client
transport->client import or transaction SCC7. Transaction SCC7 will take you to the
client import post-processing screen . In that screen the transport from the last tp
import is proposed. Please check the transport number and if every thing is
according to the order then press enter and that will take care of the post processing
activities. You can also use SCC2 to execute the same process as in transaction
SCC7. During this process, the SAPscript texts are imported and application reports
are generated. If there are inconsistencies, you need to repeat the import after
checking the log.
If you get any problem importing the SAPscript objects then use the RSTXR3TR
program in the target client to import those. In this screen you can enter the
transport request for the SAPscript object. According to the above example
devkx00001. In the second line you need to enter the path for the SAPscript data file
as following:
/usr/sap/trans/data/<data file for the SAPscript objects>

/usr/sap/trans/SX00001.DEV (using the above example)

24
You can choose the import option from the “mode” option. Then you can continue to
execute the program and it will successfully complete the import of SAPscript objects
to the target client.
Up to release 3.0, RSCLIEXP program can be used to create the command files. The
tp command is used to do the import as we have seen before and the RSCLIIMP
program is executed for the post-processing activities and the consistency of data.
Using the transport procedure in 4.0
In 4.0 after the client is exported from the source system using transaction SCC8 as
we have seen in the client export section, the following transport files are created.
<sid>KO<no>: For the client-independent data (if the copy profile selected includes
client independent data:
<sid>KR<no>: For the client-specific data.
<sid>KX<no>: For the Texts and forms.
When all the above transports get released from the source system, the data is
exported to the data files of /usr/sap/trans/data directory automatically. The cofiles
are also created in the /usr/sap/trans/cofiles directory.
Then the command files need to be added to the buffer for the import using the
format from the cofiles as following:
• Logon to the target system as <sid>adm

• cd /usr/sap/trans/bin - Change to the transport directory
• tp addtobuffer <command file-name> <target-sys-id> - Adds to the buffer
If you are transporting to a new client then the new client should be created in the
target system. Then you can start the import into the target system as shown in the
following UNIX example:
tp import <target-sys-id> client<target-client> from /usr/sap/trans/bin directory
After the “tp import” process completes successfully, start transaction SCC2 and then
execute the import into the target client. This process imports all the SAPscript
objects and generates all the programs. After the client is imported successfully, you
should perform the post-processing activities by using the following path:
Tools ->Administration->Client admin->Client transport->Post-process import.
After the post processing is done, we recommend doing table compare between the
source client and the target client to check all the client dependent and independent
tables for consistency.
Remote CLIENT Copy
SCC9 transaction

25
Overview of a remote client copy:
Remote client copy is done using the RFC connection between two systems. You
might get errors if you do not have all the proper authorization you need including
user administration authorization.
Tips: A remote copy requires as much memory as needed by the largest table in the
system.
Upto 4.0, remote copy can not handle large volume of data. Remote client copy
reads the entire table from the source system and then copies that to the target
system using RFC connection. For big tables as BSEG, it takes more time then the
RFC wait time; so it might not copy the big table at all. For the same RFC wait time
constraint, large quantity of texts can not be copied and remote client copy might
terminate without any error. You are not going to see this problem in 4.0 release,
because the tables are copied in blocks by RFC. You should check the memory
parameters for memory and MAX_wprun_time for run time before starting the
remote client copy. Try to add the big tables to the exception list by executing
RSCCEXPT report. In 4.0 an inconsistency check is performed automatically during
the remote client copy; if any inconsistency is there then the system returns an
error.
We recommend avoiding big client copies using remote client copy procedure until
release 4.0. In the beginning of a development project upto 3.1I release you can use
remote client copy for the smaller clients; when the client gets real big it is better to
run client export/ import procedure instead.
Remote client copy procedure:
Before you perform a client copy, the RFC destination for the source system needs to
be defined using transaction SM59. In transaction SM59 screen chose “R/3
connections” under “RFC destinations”. Now you click on the create button to create
a RFC connection as shown in Figure 9.9.
Figure 9.9 picture of creating a RFC destination
After the RFC connection for the source system is created, you are ready to perform
a remote client copy.
You can chose SCC9 or the menu path Tools ->Administration->Client admin->Client
copy ->Remote copy.
First line shows the target client, which is the current client as shown in Figure 9.10.
Now you select a copy profile according your requirements. We have already seen
how to create a profile and what is their objective. In the fourth line enter the source
client (from where you are copying). If click the enter button the fifth line “Source
Client User Master” will be filled with the same number as source client. You can
change it if you want to. Enter the source system name or RFC destination name that
you created in SM59. You can execute the remote client copy in the test mode by
selecting the test run flag. After you are done with all the selection you can click on
the “Execute in backgrd.” button to start the remote client copy procedure as a
background job.

26
Figure 9.10 to show the remote client copy screen
Deleting a CLIENT
You need to perform two steps to delete a client. First you need to delete the
complete client from database and then delete it from client maintenance table T000.
To delete a client from a SAP system:
First log on to the client to be deleted with the proper authorization to delete a client.
Then choose path Tools ->Administration->Client admin->Special functions->Delete
client or transaction SCC5 and you are going to see a delete client screen as shown
in figure 9.11. In this screen you are going to find two entries; test run and also
delete from T000.
If you want to run a client delete process to find out information about all the tables
that will be deleted then test run is the right option to use. If you do not want to
copy another client to this client and get rid of this client forever then “delete from
T000” is the right option to use. You can delete the client in SCC5 by executing it
online or in the background. You can choose either one of these options and in the
verification popup screen you can check all the parameters for client deletion. After
the client deletion process starts you can use SCC3 log entries to check the client
deletion process.
Figure 9.11 to show the client delete screen of SCC5
In all the SAP releases so far you can use R3trans to delete a client. We have seen
significant timesaving in this way of deleting a client. If you use the R3trans
command in the operating system level to delete a client then the first step is to
create the command file in /usr/sap/trans/bin (it does not have to be
/use/sap/trans/bin as long as you provide the right path in the OS level) with the
following contents:
Clientremove
Client = 100
Select *
For the above example the command file name = del100 and the client we want to
delete = 100 are used
Then in /usr/sap/trans/bin directory run the following command to delete the client:
R3trans –w <log file for the deletion> -u 1 <path name and the command file>
For our example here you run: R3trans -w del100.log –u 1 del100
You can VI to the del100.log to anytime to the progress in the deletion process.
Tips: For the database performance, we recommend to do database reorganization

after you delete a production size client from the system.

27
To check the contents of the log:
Choose Tools ->Administration ->Choose Administration ->Client admin->Copy logs

then Select a client by double clicking on it and select a copy process by double-
clicking on it. The transaction for the log selection is SCC3 transaction. You also can
run the program RSCCPROT to get the same result.
You can select one of the client copy entry from “Client copy log analysis ” second
screen, following three buttons are provided as shown in figure 9.13.
Log
Monitor
Refresh
System log
Resource Analysis
Figure 9.13 for the client copy log screen
If you select a “Log” button from the “Client copy log analysis” third screen, then not
only you get the general information about the client copy but also the following
information for each of the table copied in the process.
Table name
Delivery class
Development class
Number of entries in the source client
Number of inserts necessary in the current client
Number of updates
Number of deletes
Additional space required by the copied table in bytes
The following is an example of what you will see in a log display screen.
Table Dev.cl Class nbr-all -ins -upd -del bytes sec
ANKA AA C 35 0 35 COPY 13 1
ANKP AA C 0 0 0 COPY 0 0
ANKT AA C 43 0 43 COPY 8 1
ANKV AA C 0 0 0 COPY 0 0
T009Y AA C 2 0 2 COPY 0 0
T082A AA C 16 0 16 COPY 0 0
T082H AA C 27 0 27 COPY 1 0

28
The above example shows the class “C”. The class represents the delivery class.
Through the delivery class you can know the kind of data the table has or what
environment the table belongs to. For example, all the tables shown in the above
display belongs to the customizing environment or they have customizing data. The
following are the examples of the delivery classes and their definitions.
Delivery Class Description
A Application table includes the master and transaction data

C Customizing table
L Table for storing temporary data
G Customizing table. It is protected against SAP Update
E Control table
S System table. They are only maintained by SAP
W System table. Contents transportable via separate TR objects
The table information, all the additional storage required in Kbytes, the run time for
the client copy and the end of processing time are also shown as following example
in the client copy log analysis.
• Selected tables: 5,672

• Copied tables: 5,671
• Tables deleted: 0
• Storage required (Kbytes): 260,444
• Program ran successfully
• Runtime (seconds): 10,123
• End of processing: 13:37:24
You can click on the “Monitor “ button and watch the progress of the client copy real
time.
The “Refresh” button always refreshes the screen to show you the up to date
information.
The “System log” button takes you to the system log screen to show you all the
system messages.
The next button “Resource analysis” is a very important utility to show you all the
data base resources you need to run the client copy in the table space level. In the
resource analysis utility you can get realistic picture of deletes and inserts calculation
for the database. Memory requirements can also be found out by this utility.
Tips: You should always check SM21 (the system log) for all the client copy
problems.
Ten Golden rules for CLIENT Copies

29
1. Master data can not be copied without copying transactional data and
transactional data can not be copied without copying master data.
2. Application data (transactional and master) should not be copied without
copying configuration data.
3. Client copy requires a valid client as the destination client. Make sure that the
client exists in T000 table and you can logon to that client.
4. The transport system and the transport management system of 4.0 are the
only proper tool to be use to keep multiple systems in sync by transporting
development and customizing changes to another instance.
5. When you copy a client from one system to another, client-independent
tables should only be copied if they are not yet modified in the target system.
6. We recommend the users to read all the OSS notes regarding client copy that
applies to their SAP release. It is always better to schedule the client copy job
in the background for the night run when normal work is not taking place.
7. Always check the database space before performing a client copy.
8. To avoid data inconsistencies all the users working in the source and target
clients should logoff from the system.
9. RSCLICHK program should be run in the target system remotely before doing
a client export. This program will give information about the missing
definitions from the data dictionary in the target. After executing this program
and getting successful results you can ensure that the client copy will have no
problems. In case some tables are different; you can use SE11 to compare
and adjust the table structure in both the system before the client copy. A
remote test client copy also can be executed to know the differences between
source client and target client.
10. If you are not in release 2.2 then do not use R3trans to copy a client.
Simple method for copying VARIANTS
The VARI, VARID and VARIT tables contain all the variants in the SAP system. Those
variants can be copied in the client copy time using an appropriate client copy
profile. If you just want to copy the variants then R3trans can be used to copy those
very quickly.
To copy the variants from one client to another in a system using R3trans, follow the
following procedure:
First create a control file with the following contains:
clientcopy
source client = <source client number>
target client = < target client number>
select * from VARI
select * from VARIT
select * from VARID
The second step is to logon as <sid>adm and use the controls file with R3trans as
shown in the client export and import section of this chapter. This procedure will
copy all the variants from the source client to the target client as defined in the
control file.

30
To copy all the variants between clients between two different systems:
First create a control file for R3trans with the following contents to create a data file:
export
client = <source client>
file = ‘<the path for the data file and the file name>’
select * from VARI
select * from VARIT
select * from VARID
The second step is to logon as <sid>adm in the source system and use R3trans as
shown before to execute the control file. The process will create a data file as defined
in the control file. The third step is to define a import control file for R3trans with the
following contents:
Import
client = <target client>
file = ‘<the path for the data file and the file name>’
After the control file is created, logon as <sid>admin the target system and execute
R3trans command with the control file to import all the variants to the target system.
Important client management tips
We recommend deleting the large cluster tables first from a client using R3trans
client remove command before going for the deletion of entire client. To increase the
client copy performance it is also better to copy the cluster tables first using the
R3trans command. Then use the RSCCEXPT report to exclude all the cluster tables
before doing the client copy. To get a list of cluster tables use transaction SE85, then
chose other objects -> select pooled/cluster tables. The following control files are for
both the above examples:
To copy the cluster tables:
clientcopy
source client = xxx
target client = YYY
select * from BSEG
select * from ……..
To delete the cluster table before deleting the whole client:
client remove
client = XXX
select * from BSEG
(XXX and YYY represent the client numbers)
Refer to chapter 10 to understand how to execute a R3trans command.

31
In each database, the rollback segments needs to be extended so that the largest
table in the system can be copied without any problem. In release it only applies to
client transports or copies and deleting the tables. In release 4.0 it only applies to
transports.
SAP does not support a non-numeric client.
If you get a message “The client copy is locked by another run” and you want to kill
the current process to start a new client copy then call transaction SM12 and check
the entry RSCLICOP and then delete it. Make sure to check if any clientcopy job is
running in the background before deleting the lock. If a job is still running, you
should wait till it finishes because you can not start another client copy run.
After the client export is done, the command file might not be created for the
SAPscript objects in /usr/sap/trans/cofiles directory, you only find the data file in
/usr/sap/trans/data directory. Sometimes the SAPscript objects can be locked
properly and the transport request does not get released. To release the SAPscript
change request, logon to the source client and execute SE01. Then enter the
transport number and try to release it from there. If there is a lock problem then
solve it and then release the request.
Transporting from 4.0 to 3.0:
You have to be very careful while doing the transport of a logical database in 4.0. In
release 4.0 the buffer of the logical database is changed. Always run RSLDB400 after
the import of a logical database. Before transporting the repository objects from
release 4.0 to 3.1 you need to know that the names of the repository objects in
release 4.0 are extended. Always check the current version of R3trans; you might
need for your system to transport objects from 4.0 to 3.1 releases. If your system
has SAP release other than 3.1I; you can not transport SAPscript objects from 4.0 to
3.0. The internal buffer is also changed in release 4.0, so GUI screens can not be
transported from 4.0 to 3.0.
Start Processing
1. Starting the SAP services
When the Microsoft Windows systems is booted, the SAP service (

SAP<SID>_<Instance_no.>, such as SAPC11_00) is always automatically
started. The service evaluates entries from the Microsoft Windows start profile and reads
the required environment variables from the registry.
1. Starting the SAP Processes
You can start the SAP processes using the Microsoft Management Console (MMC). To
do this, select an instance and choose Start in the context menu. For more information,
see Microsoft Management Console: Windows.

32
DCOM communication is set up with the SAP service and messages for starting the
appropriate SAP instance are sent to the service. The SAP service interprets the Microsoft
Windows start profile (see Evaluating the Start Profile below) and starts the processes of
which the instance consists. (The processes are started by the program
sapstartsrv.exe.)
The message to start the desired instance can also be issued using the command line
program sapstart.exe.
The following diagram illustrates the interaction of the individual processes during the
start process:
Evaluating the Start Profile
When you start an instance, the SAP service executes all commands in the Microsoft
Windows start profile that contain an Execute_ statement. The SAP service then starts
the processes of the SAP instance in the order in which the Start_Program_
statements are listed in the profile.
Shutdown Processing
You are stopping the SAP System with the MMC or another utility program. The SAP
service waits for a stop message from the MMC or from a command line program (such
as sapsrvkill) and then stops the SAP System. The service itself is not stopped.
The database is not stopped with this shutdown process.

33
Windows Start Profile

The start profile determines which actions the SAP service executes. The profile can start
all processes which are required by the SAP System in this Windows host system. The
start profile used by the service is specified when you install the service.
Start profiles are stored in the central profile directory of your SAP System so that they
can be called from any application server.
A start profile is generated automatically during system installation.
A distinction is made between processes started synchronously and asynchronously.
• Processes started synchronously
The next step in the start profile is not processed until the process has been completed.
The system does not check how (that is with which Exit Code) the process was
completed.
Synchronous processes can be recognized by the addition immediate in the start

profile.
Program strdbs.cmd - starts the database
Program sapcpe - copies the necessary executables to the application server.
• Processes started asynchronously
The next step in the start profile is processed as soon as the process has been started.
Program msg_server.exe - starts the message server
Program disp+work.exe - starts the dispatcher
Program gwrd.exe - starts the gateway (provided this is just a gateway instance)

34
Changing or Replacing the Windows Start Profile
You can change entries in the start profile using the CCMS, for example. Changes to the
start profile do not become effective until you have stopped and restarted the SAP
service. Note that when the SAP service is stopped, the appropriate SAP System is also
stopped but not the database.
In the Microsoft Management Console, you can activate the new profile settings by
restarting the SAP start service without stopping the SAP System. For more information
see Microsoft Management Console: Windows .
To stop an SAP service:
• Start the Windows window Services (Control Panel → Services).
• From the list of services, select the service of the SAP instance (
SAP<SAPSID>_<Instance number>, e.g. SAPC11_00) you want to stop. The
service has already been stopped if it does not have the Status Started.
SAP System on Windows: Problem Analysis

Use
If problems occur when the SAP System is started or stopped, you have a number of analysis
options.
Procedure
You can start the MMC and use the available features for system analysis to find out the problem.
Alternatively, try the following:
• Select Programs
→ Administrative Tools (Common) → Event Viewer to access the Windows event log. In
the menu bar, select Log → Application. You are shown a list of errors, warnings, and
information generated by the application software. You can display detailed information
by clicking on a particular log.
• Check that the SAP service (
SAP<SAPSID>_<Instance number>, e.g. SAPC11_00) was started.
To do this, go to the window Services (Control Panel → Services) and check the status of
the SAP service. The service has been started if it has the Status Started. If this is not the
case, select Start to start the service.

35
• Check the start log in the
MMC. To do this, select the instance involved and from the context menu choose Task →
View Developer Traces.
• Check the error files
stderr<n> (n is the number of one of the programs in the Windows start profile:
Start_Program_<0n>...). You can find the files in
USR\SAP\<SAPSID>\<Instance number>\work.
The files can also be accessed from the MMC. To do this, select the instance involved
and from the context menu choose Task → View Developer Traces.
• Check the trace files of the individual SAP processes:
o dev_ms
: Developer trace of message server
o dev_disp
: Developer trace of dispatcher
o dev_w<m>
(m number of work process): Developer trace of work processes

36
1. What is a transaction?
- A transaction is dialog program that change data objects in a
consistant way.
2. What are the requirements a dialog program must fulfill?
A dialog program must fulfil the following requirements
- A user friendly user interface.
- Format and consistancey checks for the data entered by the
user.
- Easy correction of input errors.
- Access to data by storing it in the data bases.
3. What are the basic components of dialog program?
- Screens (Dynpros)
- Each dialog in an SAP system is controlled by dynpros.A
dynpros consists of a screen
And its flow logic and controls exactly one dialog step.
- ABAP/4 module Pool.
Each dynpro refers to exactly one ABAP/4 dialog program .Such a
dialog program is also called a module pool ,since it consists of
interactive modules.
4. What is PBO and PAI events?
PBO- Process Before Output-It determines the flow logic before displaying
the screen.
PAI-Process After Input-It determines the flowlogic after the display of the
screen and after receiving inputs from the User.
5. What is dynpro? What are its components ?
- A dynpro (Dynamic Program) consists of a screen and its flow
logic and controls exactly one dialog steps.
- The different components of the dynpro are :
Flow Logic: calls of the ABAP/4 modules for a screen .

37
Screen layout: Positions of the text, fields, pushbuttons and so on

for a screen
Screen Attributes: Number of the screen, number of the
subsequent screen, and others
Fields attributes: Definition of the attributes of the individual fields
on a screen.
6. What is a ABAP/4 module pool?
-Each dynpro refers to exactly one ABAP/4 dialog program.Such a dialog
program is also called
a module pool ,since it consists on interactive modules.
7..Can we use WRITE statements in screen fields?if not how is data
transferred from field data to screen fields?
-We cannot write field data to the screen using the WRITE statement.The
system instead transfers data by comparing screen fields names with
ABAP/4 variable names.If both names are the same,it
transfers screen fields values to ABAP/4 programs fields and Vice Versa.This
happens immediately after displaying the screen.
8.Can we use flow logic control key words in ABAP/4 and vice-versa?
- The flow control of a dynpro consists os a few statements that
syntactically ressemble ABAP/4 statements .However ,we cannot
use flow control keywords in ABAP/4 and vice-versa.
9.What is GUI status? How to create /Edit GUI status?
-A GUI status is a subset of the interface elements used for a certain
screen.The status comprises
those elements that are currently needed by the transaction .The GUI status
for a transaction may be composed of the following elements:
-Title bar.
-Mneu bar.
-Application tool bar
-Push buttons.
To create and edit GUI status and GUI title,we use the Menu Painter.

38
10. How does the interection between the Dynpro and the ABAP/4
Modules takes place?
-A transaction is a collection os screens and ABAP/4 routines, controlled and
executed by a Dialog processor. The Dialog processor processes screen after
the screen, thereby triggering the appropriate
ABAP/4 processing of each screen .For each screen,the system executes the
flow logic that contains the corresponding ABAP/4 processing.The controls
passes from screen flow logic to ABAP/4 code and back.
11. How does the Dialog handle user requests?
- when an action is performed ,the system triggers the
PROCESS AFTER INPUT event.The data passed includes field
screen data data entered by the user and a function code. A
functioncode is a technical name that has been allocated in a
screen Painter or Menu Painter to a meny entry,a push button,the
ENTER key or a function Key of a screen.An internal work field(ok-
code)in the PAI module evaluates the function code,and the
appropriate action is taken.
12. What is to be defined for a push button fields in the screen attributes?
- A function code has to be defined in the screen attributes for the
push buttons in a screen.
13. How are the function code handles in Flow Logic?
- When the User selects a function in a transaction ,the system copies
the function code into a specially designated work field called
OK_CODE.This field is Global in ABAP/4 Module Pool.The OK_CODE can
then be evaluated in the corresponding PAI module. The function code is
always passed in Exactly the same way , regardless of Whether it comes
from a screen’s pushbutton,a menu option ,function key or other GUI
element.
14.What controls the screen flow?
- The SET SCREEN and LEAVE SCREEN statements controls
screen flow.

39
14. The Function code currently active is ascertained by what Variable?

- The function code currently active in a Program can be
ascertained from the SY-UCOMM Variable.
15. The function code currently active is ascertained by what variable ?
- By SY-UCOMM Variable.
16. What are the “field” and “chain” Statements?
- The FIELD and CHAIN flow logic statements let you Program
Your own checks.FIELD and CHAIN tell the system Which fields
you are checking and Whether the System should Perform Checks
in the flow logic or call an ABAP/4 Module.
17. What is an “on input filed” statements?
- ON INPUT
The ABAP/4 module is called only if a field contains the Value other
than the initial Value.This initial Value is determined by the filed’s
Dta Type: blanks for character Fields
,Zeroes for numerics. If the user changes the Fields Value back t o
its initial value,ON INPUT does not trigger a call.
18. What is an “on request Field” statement?
- ON REQUEST
The ABAP/4 Module is called only if the user has entered the value in
the field value since the last screen display .The Value counts as
changed Even if the User simply types in the value that was already
there .In general ,the ON REQUEST condition is triggered through any
Form of” MANUAL INPUT’.
19. What is an on”*-input filed” statement?
ON *-INPUT
- The ABAP/4 module is called if the user has entered the “*” in
the first character of the field, and the field has the attribute *-entry
in the screen Painter.You can use this option in Exceptional cases
where you want to check only fields with certain Kinds of Input.
20. What are conditional chain statement?

40
ON CHAIN-INPUT similar to ON INPUT.

The ABAP/4 module is called if any one of the fields in the chain contains a
value other than its initial value(blank or nulls).
ON CHAIN-REQUEST
This condition functions just like ON REQUEST, but the ABAP/4 module is
called if any one of the fields in the chain changes value.
21. What is “at exit-command:?
The flowlogic Keyword at EXIT-COMMAND is a special addition to the
MODULE statement in the Flow Logic .AT EXIT-COMMAND lets you call
a module before the system executes the automatic fields checks.
22. Which Function type has to be used for using “at exit-command” ?
- To Use AT EXIT – COMMAND ,We must assign a function
Type “E” to the relevant function in the MENU Painter OR Screen
Painter .
23. What are the different message types available in the ABAP/4 ?
- There are 5 types of message types available.
- E: ERROR
- W-WARNING
- I –INFORMATION
- A-ABNORMAL TERMINATION.
- S-SUCCESS
24. Of the two “ next screen “ attributes the attributes that has more priority is -
------------------.
Dynamic.
25. Navigation to a subsequent screen can be specified statically/dynamically.
(TRUE/FALSE).
TRUE.
26. Dynamic screen sequence for a screen can be set using ------------- and --------
--------- commands
Set Screen, Call screen.

41
27. The commands through Which an ABAP/4 Module can “branch to “

or “call” the next screen are
1.------------,2--------------,3---------------,4------------.
- Set screen<scr no>,Call screen<scr no> ,Leave screen, Leave

to screen <scr no>.
28. What is difference between SET SCREEN and CALL SCREEN ?
- With SET SCREEN the current screen simply specifies the next
screen in the chain , control branches to this next screen as sonn
as th e current screen has been processed .Return from next
screen to current screen is not automatic .It does not interrupt
processing of the current screen.If we want to branch to the next
screen without finishing the current one ,use LEAVE SCREEN.
- With CALL SCREEN , the current (calling) chain is suspended ,

and a next screen (screen chain) is called .The called can then
return to the suspended chain with the statement LEAVE SCREEN
TO SCREEN 0 .Sometime we might want to let an user call a pop
up screen from the main application screen to let him enter
secondary information.After they have completed their enteries, the
users should be able to close the popup and return directly to the
place where they left off in the main screen.Here comes CALL
SCREEN into picture .This statement lets us insert such a
sequence intp the current one.
29. Can we specify the next screen number with a variable (*Yes/No)?
- Yes
30. The field SY-DYNR refers to--------------

42
Number of the current screen.
31. What is dialog Module?

- A dialog Module is a callable sequence of screens that does not
belong to a particular transaction.Dialog modules have their module
pools , and can be called by any transaction.
32. The Syntex used to call a screen as dialog box (pop up)is-----
----
CALL SCREEN <screen number.>

STARTING AT <start column><start line>
ENDING AT <end column> <end line>
33. What is “call mode”?

- In the ABAP/4 WORLD each stackable sequence of screens is
a “call mode”, This is IMP because of the way u return from the
given sequence .To terminate a call mode and return to a
suspended chain set the “next screen” to 0 and leave to it:
LEAVE TO SCREEN 0 or (SET SCREEN 0 and LEAVE SCREEN)
.When u return to the suspended chain execution resumes with the
statement directly following the original CALL SCREEN statement.The
original sequence of screens in a transaction (that is , without having
stacked any additional call modes),you returned from the transaction
altogether.
34. The max number of calling modes stacked at one time is?
- NINE

43
35. What is LUW or Data base Transaction ?
- A “LUW”(logical unit of work) is the span of time during which

any database updates must be performed in an “all or nothing”
manner .Either they are all performed (committed),or they are all
thrown away (rolled back).In the ABAP/4 world , LUWs and
- Transactions can have several meanings:
LUW (or “database LUW” or “database transaction”)
This is the set of updates terminated by a database commit. A LUW

lasts, at most, from one screen change to the next (because the SAP
system triggers database commits automatically at every screen
change).
36. What is SAP LUW or Update Transaction?

Update transaction (or “SAP LUW”)
This is a set of updates terminated by an ABAP/4 commit. A SAP
LUW may last much longer than a database LUW, since most update
processing extends over multiple transaction screens. The
programmer terminates an update transaction by issuing a COMMIT
WORK statement.
37. What happens if only one of the commands SET SCREEN

and LEAVE SCREEN is used without using the other?
If we use SET SCREEN without LEAVE SCREEN, the program
finishes processing for the current screen before branching to <scr
no>. If we use LEAVE SCREEN without a SET SCREEN before it, the
current screen process will be terminated and branch directly to the
screen specified as the default next-screen in the screen attributes.

44
38. What is the significance of the screen number ‘0’?

In “calling mode”, the special screen number 0 (LEAVE TO SCREEN
0) causes the system to jump back to the previous call level. That is, if
you have called a screen sequence with CALL SCREEN leaving to
screen 0 terminates the sequence and returns to the calling screen. If
you have not called a screen sequence, LEAVE TO SCREEN 0
terminates the transaction.
39. What does the ‘SUPPRESS DIALOG’ do?

Suppressing of entire screens is possible with this command. This
command allows us to perform screen processing “in the background”.
Suppresing screens is useful when we are branching to list-mode from
a transaction dialog step.
40. What is the significance of the memory table ‘SCREEN’?

At runtime, attributes for each screen field are stored in the memory
table called ‘SCREEN’. We need not declare this table in our
program. The system maintains the table for us internally and updates
it with every screen change.
41. What are the fields in the memory table ‘SCREEN’?

Name Length Description
NAME 30 Name of the screen field

GROUP1 3 Field belongs to field group 1
GROUP4 3 Field belongs to field group4
ACTIVE 1 Field is visible and ready for input.
REQUIRED 1 Field input is mandatory.
INPUT 1 Field is ready for input.

45
OUTPUT 1 Field is display only.

INTENSIFIED 1 Field is highlighted
INVISIBLE 1 Field is suppressed.
LENGTH 1 Field output length is reduced.
DISPLAY_3D 1 Field is displayed with 3D frames.
VALUE_HELP 1 Field is displayed with value help.
42. Why grouping of fields is required? What is the max no of

modification groups for each field?
If the same attribute need to be changed for several fields at the same
time these fields can be grouped together. We can specify up to four
modification groups for each field.
43. What are the attributes of a field that can be activated or

deactivated during runtime?
Input, Output, Mandatory, Active, Highlighted, Invisible.
44. What is a screen group? How it is useful?

Screen group is a field in the Screen Attributes of a screen. Here we
can define a string of up to four characters which is available at the
screen runtime in the SY-DNGR field. Rather than maintaining field
selection separately for each screen of a program, we can combine
logically associated screens together in a screen group.
45. What is a Subscreen? How can we use a Subscreen?

A subscreen is an independent screen that is displayed in a n area of
another (“main”) screen. To use a subscreen we must call it in the flow
logic (both PBO and PAI) of the main screen. The CALL
SUBSCREEN stratement tells the system to execute the PBO and PAI
events for the subscreen as part of the PBO or PAI events of the main
screen. The flow logic of your main program should look as follows:

46
PROCESS BEFORE OUTPUT.

CALL SUBSCREEN <area> INCLUDING ‘<program>’ ’<screen>’.
PROCESS AFTER INPUT.
CALL SUBSCREEN <area>.
Area is the name of the subscreen area you defined in your main
screen. This name can have up to ten characters. Program is the
name of the program to which the subscreen belongs and screen is the
subscreen’s number.
46. What are the restrictions on Subscreens?

Subscreens have several restrictions. They cannot:
· Set their own GUI status
· Have a named OK code
· Call another screen
· Contain an AT EXIT-COMMAND module
· Support positioning of the cursor.
47. How can we use / display table in a screen?

ABAP/4 offers two mechanisms for displaying and using table data in a
screen. These mechanisms are TABLE CONTROLS and STEP
LOOPS.
48. What are the differences between TABLE CONTROLS and

STEP LOOPS?
TABLE CONTROLS are simply enhanced STEP LOOPS that display

with the look and feel of a table widget in a desktop application. But
from a programming standpoint, TABLE CONTROLS and STEP
LOOPS are almost exactly the same. One major difference between
STEP LOOPS and TABLE CONTROLS is in STEP LOOPS their table
rows can span more than one time on the screen. By contrast the

47
rows in a TABLE CONTROLS are always single lines, but can be very
long. (Table control rows are scrollable). The structure of table control
is different from step loops. A step loop, as a screen object, is simply a
series of field rows that appear as a repeating block. A table control,
as a screen object consists of: I) table fields (displayed in the screen )
ii) a control structure that governs the table display and what the user
can do with it.
49. What are the dynapro keywords?

FIELD, MODULE, SELECT, VALUES and CHAIN are the dynapro
keywords.
50. Why do we need to code a LOOP statement in both the PBO

and PAI events for each table in the screen?
We need to code a LOOP statement in both PBO and PAI events for
each table in the screen. This is because the LOOP statement causes
the screen fields to be copied back and forth between the ABAP/4
program and the screen field. For this reason, at least an empty
LOOP….ENDLOOP must be there.
51. The field SY-STEPL refers to the index of the screen table row
that is currently being processed. The system variable SY-stepl
only has a meaning within the confines of LOOP….ENDLOOP
processing. Outside the loop, it has no valid value.
52. How can we declare a table control in the ABAP/4 program?
Using the syntax controls <table control name> type tableview using
screen <scr no>.
53. Differentiate between static and dynamic step loops.

48
Step loops fall into two classes: Static and Dynamic. Static step loops
have a fixed size that cannot be changed at runtime. Dynamic step
loops are variable in size. If the user re-sizes the window the system
automatically increases or decreases the number of step loop blocks
displayed. In any given screen you can define any number of static
step loops but only a single dynamic one.
54. What are the two ways of producing a list within a

transaction?
By submitting a separate report.
By using leave to list-processing.
55. What is the use of the statement Leave to List-processing?

Leave to List-processing statement is used to produce a list from a
module pool. Leave to list processing statement allows to switch from
dialog-mode to list-mode within a dialog program.
56. When will the current screen processing terminates?

A current screen processing terminates when control reaches either a
Leave-screen or the end of PAI.
57. How is the command Suppress-Dialog useful?

Suppressing entire screens is possible using this command. This
command allows us to perform screen processing “in the background”.
The system carries out all PBO and PAI logic, but does not display the
screen to the user. Suppressing screens is useful when we are
branching to list-mode from a transaction dialog step.
58. What happens if we use Leave to list-processing without

using Suppress-Dialog?

49
If we don’t use Suppress-Dialog to next screen will be displayed but as

empty, when the user presses ENTER, the standard list output is
displayed.
59. How the transaction that are programmed by the user can be
protected?
By implementing an authority check.
60. What are the modes in which any update tasks work?
Synchronous and Asynchronous.
61. What is the difference between Synchronous and

Asynchronous updates?
A program asks the system to perform a certain task, and then either
waits or doesn’t wait for the task to finish. In synchronous processing,
the program waits: control returns to the program only when the task
has been completed. In asynchronous processing, the program does
not wait: the system returns control after merely logging the request for
execution.
62. SAP system configuration incluedes Dialog tasks and

Update tasks.
63. Dialog-task updates are Synchronous updates.
64. Update –task updates are Asynchronous updates.
65. What is the difference between Commit-work and Rollback-
Work tasks?
Commit-Work statement “performs” many functions relevant to
synchronized execution of tasks. Rollback-work statement “cancels:
all reuests relevant to synchronized execution of tasks.
66. What are the different database integrities?

50
· Semantic Integrity.
· Relational Integrity.
· Primary Key Integrity.
· Value Set Integrity.
· Foreign Key integrity and
· Operational integrity.
67. All SAP Databases are Relational Databases.

68. What is SAP locking?
It is a mechanism for defining and applying logical locks to database
objects.
69. What does a lock object involve?

The tables.
The lock argument.
70. What are the different kinds of lock modes?

Shared lock
Exclusive lock.
Extended exclusive list.
71. How can a lock object be called in the transaction?

By calling Enqueue<lock object> and Dequeue<lock object> in the
transaction.
72. What are the events by which we can program “help texts”
and display “possible value lists”?
-PROCESS ON HELP-REQUEST (POH).
-PROCESS ON VALUE-REQUEST (POV).
73. What is a matchcode?

51
A matchcode is an aid to finding records stored in the system

whenever an object key is required in an input field but the user only
knows other (non-key) information about the object.
74. In what ways we can get the context sensitive F1 help on a

field?
- Data element documentation.
- Data element additional text in screen painter.
- Using the process on help request event.
75. What is roll area?

A roll area contains the program’s runtime context. In addition to the
runtime stack and other structures, all local variables and any data
known to the program are stored here.
76. How does the system handle roll areas for external program
components?
- Transactions run in their own roll areas.
- Reports run in their own roll areas.
- Dialog modules run in their own roll areas
- Function modules run in the roll area of their callers.
77. Does the external program run in the same SAP LUW as the
caller, or in a separate one?
- Transactions run with a separate SAP LUW
- Reports run with a separate SAP LUW.
- Dialog modules run in the same SAP LUW as the caller
- Function modules run in the same SAP LUW as the caller.
The only exceptions to the above rules are function modules called
with IN UPDATE TASK (V2 function only) or IN BACKGROUND

52
TASK (ALE applications). These always run in their own (separate)

update transactions.
78. What are function modules?

Function modules are general-purpose library routines that are
available system-wide.
79. What are the types of parameters in the function modules?

In general, function module can have four types of parameters:
- EXPORTING: for passing data to the called function.
- IMPORTING: for receiving data returned from the function
module.
- TABLES: for passing internal tables only, by reference (that is,
by address).
- CHANGING: for passing parameters to and from the function.
80. What is the difference between Leave Transaction and Call

Transaction?
In contrast to LEAVE TO TRANSACTION, the CALL TRANSACTION
statement causes the system to start a new SAP LUW. This second
SAP LUW runs parallel to the SAP LUW for the calling transaction.
81. How can we pass selection and parameter data to a report?

There are three options for passing selection and parameter data to
the report.
- Using SUBMIT…WITH
- Using a report variant.
- Using a range table.
82. How to send a report to the printer instead of displaying it

on the screen?

53
We can send a report to the printer instead of diplaying it on the

screen. To do this, use the keywords TO SAP-SPOOL:
SUBMIT RSFLFIND…TO SAP-SPOOL DESTINATION ‘LT50’.
83. How can we send data to external programs?

Using SPA/GPA parameters(SAP memory).
Using EXPORT/IMPORT data (ABAP/4 memory)
84. What are SPA/GPA parameters (SAP memory)

SPA/GPA parameters are field values saved globally in memory.
There are two ways to use SPA/GPA parmeters:
By setting field attributes in the Screen Painter.
By using the SET PARAMETER or GET PARAMETER statements.

54

These Are The FAQ

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

These Are The FAQ

Caricato da

Copyright:

Formati disponibili

Frequently Asked Questions

These are the FAQ’s Collected from SAPSUPERUSERS.

Every time a unique profile is generated for a new role.

Role is just a container of the authorizations and users assigned.

Cannot activate a table in SAP

• Log on as user DDIC

Shailesh D Mamidwar SAP Basis Consultant

• Call Transaction SE37:

• Call function module 'DD_TABL_ACTM' as described above.

How to apply OSS Note?

Shailesh D Mamidwar SAP Basis Consultant

Can i find hostname and IP address of the user using SAP ?

check table USR41 via transaction SE16

how to connect bw to n r/3 system ?

steps to connect BW & R/3

login/system_client -> your application client (i.e 100)

save profile and restart BW server.

Shailesh D Mamidwar SAP Basis Consultant

A central R/3 system consists of a single instance in which all-necessary SAP

Each instance uses separate buffer areas.

Determining Change Documents

Note that changes are divided into two areas:

• Changes to authorizations: creating the user, changing, adding, or removing profiles

1. Start the user information system (transaction SUIM).

2. Expand the Change Documents node.

The result list Lists of Change Documents for Users appears.

Shailesh D Mamidwar SAP Basis Consultant

Use STAT Watch Users

Client Mgt - All SAP - Copy Table Entries To Clients

RSCLCCOP - Copy object lists between clients

Shailesh D Mamidwar SAP Basis Consultant

1. What guarantees the integration of all application modules?

2. What are the central interfaces of the R/3 system?

Operating system Interface.

3. Which interface controls what is shown on the p.c.?

4. Which interface converts SQL requirements in the SAP development

5. What is SAP dispatcher?

6. What are the functions of dispatcher?

Equal distribution of transaction load to the work processes.

Management of buffer areas in main memory.

Integration of the presentation levels.

Organization of communication activities.

7. What is a work process?

Shailesh D Mamidwar SAP Basis Consultant

8. Name various work processes of R/3 system?

Dialog or Online (processes only one request at a time).

Background (Started at a specific time)

Update (primary or secondary)

Enque (Lock mechanism).

Spool (generated online or during back ground processing for printing).

Message Service: Used by the application servers to exchange short internal

Gateway Service: Enables communication between R/3 and external applications

10. Which work process triggers database changes?

Update work process.

11. Define service (within R/3)?

A service is a process or group of processes that perform a specific system

12. What are the roll and page areas?

Paging area holds data from the application programs.

Shailesh D Mamidwar SAP Basis Consultant

13. What are the different layers in R/3 system?

14. What are the phases of background processing?

16. Define Instance.