Sap Basis

IBM Global Business Services
Day 2: Module map
Module 5: SAP Installations and JAVA SCF
Module 6: SAP System Landscape and SAP Kernel
3 Module 7: Operation Modes and SAP Web Dispatcher
Module 8: Client Concepts and Administration
1 SAP Basis FastTrak WAS 700 © Copyright IBM Corporation 2009

Course Title
SAP Installations and JAVA SCF

Module 5
© Copyright IBM Corporation 2009

Module 5: Objectives
On completion of this module, you should be

able to:
 Identify the different types of SAP
installation
 Describe the Java Startup process

Module 5: Agenda
 Topic 1: Different types of SAP installation

 Topic 2: Java Startup process

Different types of SAP installation
 SAP ERP (ABAP/ABAP+JAVA)

 SAP Enterprise Portal
 SAP Solution Manager
 SAP Netweaver (AS JAVA)
 SAP SCM
 SAP APO
 SAP NWDI
 SAP SRM
 SAP MDM
 SAP DMS

JAVA startup and control framework
 SAP provides a separate Startup and Control

Framework for SAP Web Application Server
Java. This Framework is used to start, stop, and
monitor the Java stack processes within the SAP
system instances - but not, however, the Central
Services. It consists of the following processes:
– JControl
– JLaunch

JControl
 JControl starts, stops, and monitors the processes of a Java instance

primarily the server and dispatcher processes.
 SAP Signal Handling is implemented with JControl, to forward the start and
stop commands to the processes of the Java stack.
 JControl restarts terminated processes, ends hanging processes, and sends a
shutdown signal to the processes of the Java stack.
 It reads the description of the instance from profile files.
 It starts the JLaunch processes, which in turn start Java nodes such as
dispatchers or servers.
 It creates a shared memory segment for the internal administration data of all
JLaunch processes.

JLaunch
 JLaunch starts a Java program, loads a Java VM (JVM) in its own address
space and assumes the function of the corresponding cluster element.
 The parameterizing of the JVM is read before the loading.
 JLaunch receives commands from the JControl process (through named
pipes) to stop cluster elements such as dispatchers or servers.
 The JLaunch process ends itself if its parent process JControl is no longer
running.

Start process of a JAVA instance
 JControl is started.
 JControl starts a Java instance bootstrap process with parameters that are
defined in the file bootstrap.properties
(/usr/sap/<SID>/<instance>/j2ee/cluster/bootstrap).
 The bootstrap process synchronizes all required binaries for the Java nodes
from the database with the file system. This is necessary, since the Class
Loading is performed using the file system in the Java environment.
 The database always contains the current (deployed) binaries and properties
and distributes these to every Java node when starting.
 The Java instance bootstrap process reads the instance description from the
Java schema of the database.
 The Java instance bootstrap process stores a file instance.properties,
containing the instance description, at operating system level.

Start process of a JAVA instance (continued)
 JControl reads the instance description from the file system.

 JControl starts the bootstrap processes which are specific to Java nodes and
which read the descriptions for the nodes from the database and store them in
the file system.
 JControl creates a connection to the Central Services message server. If this
connection is established successfully, the operation continues with the next
step. If no connection is established to the message server, JControl initiates
an Emergency Shutdown.
 In the final step, JControl starts all the Java nodes such as dispatchers and
servers as JLaunch processes and, when doing so, loads a JVM in the
JLaunch process.

Start process of a JAVA instance (continued)
Source: SAP

Module takeaways
 SAP has different flavors.

 JAVA instance is started by JControl and JLaunch
processes.
 While some parameters are read from database,
others are read from the file system.

Questions and Answers

Module 5: Summary
Having completed this module, you should now

be able to:
 Identify the different types of SAP installation
 Describe the Java Startup process

Course Title
SAP System Landscape and SAP Kernel

Module 6


able to:
 Identify and understand an SAP landscape
 Explain the basics of Change and Transport
System
 Explain the importance of kernel files

Module 6: Agenda
 Topic 1: SAP landscape

 Topic 2: Basics of Change and Transport System.
 Topic 3: Kernel files

SAP landscape
 A collection of SAP systems required to support a SAP project lifecycle.

 Standard SAP landscape consists of three distinct environments:
– An environment for development & customizing (Integration system).
– A environment for testing the customizing & development changes using
real life-like data (consolidation system).
– A stand alone environment for production (delivery system)
 A collection of SAP systems required to support a SAP project lifecycle.
– A prototyping environment (Sandbox)
– Training environment
– Regression testing environment

SAP landscape (continued)
The system landscape should enable you to:

 Protect application data using:
– Client roles
– Authorization concepts
 Perform development, quality assurance, and production activities in separate
environments to ensure:
– Consistency of repository objects
– A secure and stable production environment

System landscape definition
 Definition: A set of SAP system with unique SIDs which has the same set of
client specific customizing data , the cross client customizing data and the
ABAP repository.
 An SAP system landscape is basically used to tailor the generic SAP
software through business specific customizing and customer ABAP
developments for productive use.
 This entire tailoring of the software to suit the business need in realized
through various phases of configuration, development and testing.
These phases are realized through the different systems of the landscape.

Typical systems in a landscape
Sandbox / Playground Training / Education
Development / Build Migration /

Regression testing
System Test / QA Production

Sandbox
 An isolated environment, i.e. changes made in the sandbox would never flow
to the implementation landscape
 Used to carry out preliminary analysis.
– Can be used to prototype design & build.
– Will be re-created several times during a SAP project life.
– The sandbox system will mostly be re-build from Development System.
– Since this system can be recreated any time no changes are taken out from
this system to any other systems in the landscape.

Development system
 All Design and Build will be carried out in this system.

– First round of testing of all designed and built objects will be carried out in this
system.
– This system will always be the “Original System” for all the changes introduced
during the implementation.
– All changes introduced during implementation will be distributed from this system
to other SAP system in landscape.
– No Design and Build is normally permitted in any system in the Landscape other
than the Development system.
– This system may, in certain cases, serve as the Sandbox as well as QA system
(though this is not the SAP recommended strategy).

Quality assurance system
 Testing and validation of all changes introduced in the development system

during the design and build phase.
– All correction necessitated by the testing need to be done in the development
environment and rested in the system test environment.
– No changes can be permitted in the system test/qa environment.
– The testing carried out can be functional test, integration test, user acceptance
testing.
– This system can also serve as the training environment.

Training
 The training of the business users are carried out in this environment.
 The system is ideally prepared from the system Test/QA system after all the
changes have been tested and approved.
 No changes can be permitted in the training environment.

Regression / migration
 Copied from Production (on request) to support regression testing with

productive data.
 Make Regression testing secure a s well as thorough and meaningful by using
production end-user profiles and production representative data.
 Supports testing of conversion in this environment.
 No changes are permitted in this environment.
 This system can serve as a System Test / QA environment.

Production
 A secured environment for execution of productive operational business

transactions of the company.
 Absolutely zero changes are permitted in this environment
 The hardware used for the production system would have high scalability &
availability.

Types of system landscape
 A system landscape can made of one

SAP system ,two SAP systems, three
SAP systems or even more .
 SAP recommends a system landscape
to have three systems although a two
system landscape is a must.
 SAP does not recommended a single
system landscape.

Single system landscape
PROD
DEV TEST
1-System Changes
Cross-Client Customizing
Landscape
Repository threaten
No Stable runtime environment Production system
 A single system landscape will have 3 clients 1 each for development , quality
and production in the same single SAP system.

Two system landscape
DEV TEST PROD
2-System
Landscape
No Stable runtime environment Stable runtime environment
 A two system landscape is the least which can support a small uncomplicated
SAP implementation with standard business functionality and limited customer
developments.

Three system landscape
DEV TEST PROD
3-System
Landscape
DEV QAS PROD
 A three system landscape is the standard landscape recommended by SAP.

 The three systems comprise of the development , the quality assurance and
the production system.
 The development system has the client for customizing and development

Four system landscape
DEV QAS PRD
TRG

Complex system landscape
 In addition to the landscape types discussed , there are some complex

landscape types as follow:
PR1
DEV QAS PR2
PR3
Multiple production system landscape

Complex system landscape (continued)
DV1 QS1 DEV QAS PRD
Phase N+1 Phase N
Phased system landscape

Complex system landscape (continued)
D11 Q11 P11

Asian implementation
DEV QAS D22 Q22 P22
American implementation
D33 Q33 P33

European implementation
Global System Landscape

Types of system landscape (continued)
 SAP provides the tools for creation, documentation and distribution of

changes within a system landscape.
 To set up the system landscape so that it supports the management,
verification, and testing of all changes:
– A single client is recommended for all customizing work. Set client change options
appropriately before using clients.
– A single SAP system (development system) is recommended for all development
work. Set the system change options appropriately.
– To create and assign appropriate user authorizations to developers and
customizers, use the sample profiles included in the SAP system. These
authorizations control whether a user can create, modify, or release change tasks
and requests.
– Record and document all changes to a client or system.

Change and transport system (CTS)
CTS
Change and Transport Organizers (CTO)
Transport
Transport management System
Transport (TMS)
Organizer
Organizer STMS
(extended view)
SE09/SE10
SE01
Transport Tools
tp and R3trans

Change and Transport System (CTS) tools
In SAP Release 4.0, SAP has introduced a revised version of the Change and
Transport System (CTS), compromising following tools:
 The change and transport organizer (CTO) provides functions for organizing
software development projects. It is designed to support projects of all sizes,
whether they are carried out centrally or in a distributed environment.
 The transport management system (TMS) organizes, monitors, and performs
transports for all SAP systems within a system landscape. In addition, TMS is
used to configure and mange the setting up of SAP systems and transport
routes within a system landscape,.
 Operating system transport tools are executables that communicate with the
SAP system, the database, and files generated during the export process.

SAP Kernel
 The kernel is the central program that is essential to the SAP system
applications. From SAP Release 3.0C, you can upgrade the kernel to a higher
release while keeping the applications at the original release. Therefore, the
kernel is said to be "downward-compatible."
 The advantage is that you gain the latest kernel, incorporating the most up-to-
date program patches and other improvements, while avoiding the extra effort
of a full application upgrade.
 For example, this is very useful if you plan to do a full upgrade at a later date
but still want to benefit from the latest kernel immediately.
 Kernels are only downward-compatible within the same release sequence. For
example, you cannot install a 4.X kernel when you are still running SAP
Release 3.X.

SAP Kernel (continued)
 Integration
– The downward compatibility of SAP kernels is supplemented by the downward
compatibility of the database and operating system (OS).
– This means that you can normally update the database and OS at the same time as
you update the kernel, without affecting your applications.
– For example, suppose that you are running SAP Release 3.0F and you want to
update the kernel to 3.1I. At the same time, you could also update the database or
the OS.
– The higher database or OS release does not need to have been explicitly approved
for SAP Release 3.0F.

SAP Kernel (continued)
Source: SAP
List of interesting SAP executables
 dipgntab - Activation and adjustment of the nametabs with the ABAP

Dictionary.
 dw - disp+work - "Dispatcher & Workprocess" - "The complete Kernel" - Here
the complete ABAP is processed ...
 librfc - The RFC (Remote Function Call) Library, that is available for any
platform to develop and run a RFC Server or RFC Client.
 r3ldctl - The tool for exporting all table structures to the file system during a
OS/DB-Migration.
 r3load - The table import & export tool of SAP during Installation, Upgrade
and Migration.
 r3setup - The Installation (and Migration) Tool for all SAP systems up to
Release 6.10.

List of interesting SAP executables (continued)
 r3szchk - The tool for determing the sizes of the different tables in the target
database during the import in an OS/DB-Migration.
 r3trans - This is the tool, that does the real work for tp. tp controls the import
and export of changes and r3trans does them using scripts, that were
generated from tp.
 tp - "The" Transport Tool. This program coordinates the complete import and
export of program and table changes made within the SAP system in order to
transport them through the complete System Landscape.

SM51 transactions
 SM51 is the transaction used to view server details:
Server Details
OS Details
Patch Number
Database Details

Module takeaways
 The SAP system landscape generally consists

of a complex system landscape in large
enterprises.
 The kernel consists of many important
executables inside the directory.
 The transport management system (TMS)
organizes, monitors, and performs transports
for all sap systems within a system landscape.


Module 6: Summary

be able to
 Identify and understand an SAP landscape.
 Explain the basics of Change and Transport
System.
 Understand the important kernel files.

Course Title
Operation Modes and SAP Web Dispatcher

Module 7


able to:
 Interpret the importance of operation
modes
 Identify the application of SAP Web
Dispatcher for load balancing

Module 7: Agenda
 Topic 1: Operational modes

 Topic 2: Application of SAP web dispatcher

Concept of operation modes
Day
Dialog
Processing Background
Processing
Night

Adjusting instances to the load distribution
Source: SAP

Setting up operation mode
Source: SAP

Work processes and changeability

The time table (SM63)

Schedule for Normal Operation 08:00 – 21:00 Operation mode: DAY
21:00 – 08:00 Operation Mode: NIGHT
Schedule for Exception Operation 15:00 – 17:00 Operation Mode: Exception

Monitoring and consistency check

Inconsistencies in the SAP system
Source: SAP
Load balancing
 When you log on to the AS ABAP using the SAP

GUI for Windows or the SAP GUI for Java using
logon groups, the message server performs a load
distribution of users to the available instances.
 This load distribution, which takes place during the
logon procedure, is also known as logon load
balancing. After the load distribution by the
message server, the SAP GUI communicates
directly with the dispatcher.
 The user remains logged on to this instance until he
logs off again.
 An overview of users who are logged on the
instance to which you are also logged on, is
available using transaction SM04

SAP WebDispatcher
Source: SAP
WhySAP WebDispatcher
 The Web applications are also to be used from the Internet.

 The company network is protected by a Demilitarized Zone (DMZ) and the
critical business processes run on servers that are not recognized on the
Internet. How can you avoid the need to place an SAP application server
within the DMZ?
 The SAP system in question consists of multiple application servers
(instances) that are distributed across multiple hosts.
 However, the Web applications provided should run under a descriptive
address; technical details such as server name and port number are to remain
hidden to users.
 What form can a sensible load distribution take? All application servers may
not provide all services (ICF or J2EE Engine).

Functioning
An HTTP request (or unpacked HTTPS

request) is assigned to a server in two
stages:
 First, the SAP Web Dispatcher
determines whether the incoming HTTP
request is to be forwarded to an ABAP
or Java server. It then finds a group of
servers in the SAP system that can
execute the request.
 Load balancing is then carried out within
this group. After the SAP Web
Dispatcher has identified a server, it
forwards the request to the ICM of the
relevant application server.

Module takeaways
 Operation Modes enable work process

optimization during non-business hours.
 Except the spool work process all other work
processes are similar.
 SAP Web Dispatcher is used for abstraction and
load-balancing.


Module 7: Summary

be able to:
 Interpret the importance of operation modes
 Identify the application of SAP Web
Dispatcher for load balancing

Clients
Module 8


able to:
 Define a client from SAP perspective
 Interpret client roles
 Identify client copy
 Describe the system change option

Module 8: Agenda
 Topic 1: Definition of client

 Topic 2: Client roles
 Topic 3: Client copy
 Topic 4: System change option

Clients in an SAP system
 A client:
– Is a unit of the SAP system that is technically, organizationally, and commercially
self- contained.
– Has its own set of user master data, application data, and customizing based on
table key ranges.
– A client can, for example, can be a corporate group.
Client 100 XYZ cement

Client 100
Client 100 XYZ chemical

Application
User data
data
Client 200 XYZ pharmacy
Client-
dependent
customizing

Technical implementation of clients
 Technically the data of a client is stored in client dependent tables which

has a field “MANDT” as the primary key field that stores the client number
as shown in the tables.
 All SAP tables in database are broadly classified as being client dependent
tables and client independent tables. The tables with field MANDT being the
primary key are the client dependent tables.
Mandt Field 1 Field 2 Field 3
100
200
300
 Tables without MANDT are the client independent tables except for table T000
which has field MANDT but is not the primary key for the table.
 All users must log into a specific client within a SAP system.
 Application data (master and transaction data) belongs only to one specific
client
Data in an SAP system
 Data in SAP system can be divided into two categories: client-specific data
and cross-client data.
– Client-specific data: It includes user master and application data, which affects
only one client.
– Cross- Client data: It includes cross client customizing data and all repository
objects, which affects the whole system environment.

Data types in an SAP system
Client 100 Client 200
Application Application
Data Data
User
User
Data
Data
Client- Client-
Dependent Dependent
Customizing Customizing
Cross-Client Customizing
Repository Objects
(such as table definitions, programs, transactions, function modules)
In-house
development in the
customer
Technology CO HR PP MM SD …. namespace
FI

Standard client roles
Development and For configuring client

customizing settings and creating new
functionality
CUST
Quality assurance For testing functionality and

verifying configuration
QTST
For productive activities and

Production business data
PROD
Additional client roles
Sandbox For experimenting with customizing

transactions and settings
SAND
Test For testing configuration settings

using data
TEST
For end- user training

Training
TRNG
Roles of a client

Standard SAP ECC clients

Creating a logical system

Creating a client

Creating a client (continued)

Changes and transports for client-specific objects
Start
Do
Is
customizing
customizing
YES changes need to be YES Automatic recording of
required
promoted changes
in the
to other
client?
clients?
NO NO
No Changes allowed No Transports allowed

Cross-client object changes

No changes to repository and
Start client-independent customizing objects
NO
Is
Are
client-independent No changes to
NO development efforts YES
customizing required client-independent customizing
required in the
in the objects
client?
client?
No changes to repository
YES objects
Is Is
NO
Are
client-independent client-dependent YES
customizing allowed
NO customizing allowed
development efforts
required in the
in other in the
client?
clients? client?
YES
Changes to repository
and client-independent customizing
Rethink your decision !!!
objects allowed.

Client copy and transport tools
 The client copy and client transport tools:

– Are designed to replace the data of one client with the data from another client
– Are not designed to combine the data of different clients
 Client data is categorized a either:
– Customizing data
– User master data
– Application data as defined by the data table’s delivery class
 Application data can only be copied with the corresponding customizing data.
Application
Data
User Data
Client-
Dependent
Customizing

Copy profile
 Copy profile overview

Copy Profile Meaning
SAP_USER Users, user roles and authorization profiles are
copied. The client is not reset.
SAP_UONL User without authorization profile and role
SAP_PROF Only authorization profile and roles
SAP_CUST Client-specific customizing including authorization
profile is copied. The application data is deleted, the
user data is retained.
SAP_CUSV SAP_CUST with variants
SAP_UCUS SAP_CUST with user master data
SAP_UCSV SAP_UCUS with variants
SAP_ALL All client data except change documents (see note
180949) and local data is copied.
SAP_APPL SAP_ALL without user master data
SAP_APX SAP_ALL without authorization profile and roles

Authorizations
General authorization objects for client copy
Authorization objects Action

S_TABU_CLI Maintain cross-client tables
S_TABU_DIS Maintain system tables
S_CLNT_IMP Import data in client copy
S_DATASET Access the file system
Copy user profiles and user master records

Authorization objects Action
S_USER_AGR Copy roles
S_USER_PRO Copy authorization profiles
S_USER_GRP Copy user master records

Client copy and transport tools (continued)
Remote client copy

Local client copy
and client transport
Applic Applic
Applic
ation ation
ation
Data Data
Data
User
Data
User
Data
User
Data
Client- Client-
Client- Dependent
Dependent
Dependent
Customizing
Customizing Remote client Customizing
Copy (RFC)
Cross- client customizing Cross- client customizing
SAP system repository SAP system repository

Client Target system
Source system
Transport
(Export/import)
Transport directory

Testing customizing change requests
 Transaction SCC1: Copy based on a transport request
Change
Request
Task

Local client copy (SCCL)
Select an appropriate
profile for Client copy
Select a relevant “Source Client” and “Source

Client User Masters”
Schedule the client copy as a

Background Job and
schedule it “Immediately” or
with a scheduled Date/Time.
Watch log/status of the Client

Copy process from SCC3.

Remote client copy
ADOs
Appl.
Use
Data
r
Customizing
Consistency
check using RFC
Cross- client customizing
Copy of data ADOs
SAP system repository using RFC Appl.
remote copy
Use
Data
r
Customizing
SAP
System
Cross- client customizing
Repository structures
must be identical in
source and target clients
SAP system repository

Client copy using parallel processing
Client Tables Tables Tables Tables Tables

copy 1..10 11..20 21..30 31..40 41..50
RFC group
Application Application Application

server server server
Legend
Dialog process for parallel processing:
QAS Free dialog
Dialog process:
process for parallel processing:
QAS Free Dialog process:

Client transport
1. Export processing
(Transaction SCC8)
SAPscript
Data files Command files
Appl.
Data RX<no> KK<no>
User
RT<no> KT<no>
Customizing
RO<no> KO<no>
Cross- Client Customizing
SAP System Repository

Source system <S-SID>
• Export the client in

Background processing
with SCC8
Client Transport :Import Process

Client transport: Import process
Source: SAP
Client protection
 When we select the option, Protection: Client copier and comparison

tool, on the client maintenance screen, the client is protected against being
overwritten by a client copy.
 This option ensures that sensitive data can not be viewed from another client
during client compares, an activity performed during customizing cross-
system viewer (Transaction: SCU0).The levels of overwrite-protection you
can select are as follows:
– Protection level 0 : No restrictions.
– Protection level 1 : No overwriting.
– Protection level 2 : No overwriting and no external availability.

Client protection (continued)

Client restrictions
 Start of CATT and eCATT processes allowed

– Select this option for a client such as the quality assurance test client where you
wish to run the Computer Aided Test Tool (CATT) or the enhanced Computer
Aided Test Tool (eCATT) to perform scripted validity tests of application
functionality. Since CATT scripts generate application data, they should not be run
in every client.
 Currently locked due to client copy
– This option is automatically set by the SAP system when you use the client copy
tool. You can not select it manually.
 Protection against SAP upgrade
– You can assign this option only to a client whose role is set to TEST. This option
prevents the introduction of new client-dependent customizing changes into a
client during a release upgrade, thereby preserving the settings that existed prior
to the upgrade. After an upgrade, the test client can be used in conjunction with
the cross-system viewer to compare the client-dependent differences between the
two releases.
Setting the system change option
Software Component
Modifiable Restricted Modifiability Not Modifiable
Not Modifiable
Existing objects can Existing objects can be

be changed. repaired.
NameSpace
New objects have the

same system ID as the New objects have SAP as
original system. the original system.
Modifiable

Setting the system change option (continued)
Maintain System Change options

from tcode SE06 and then
selecting “System Change
Option”.

Restarting a client copy process
 If for any reason (such as database storage problems) the copying process
has been canceled, when trying to re-execute the same copy process, the
system allows you to restart the copy at the point where it was previously
terminated, using the same parameters as before.
 The client copy programs use the client copy control flow table, CCCFLOW,
which includes checkpoints.
 When you are presented with the option of restarting the copy process but
you don't want to use the restart option, select the NEWSTART option.

Client copy profiles

Table delivery classes

Monitoring
 Select target
client
Transport Directory
logs  Select run
 Monitor copy
Target Client
process
Client Client Copy Log Analysis  Show control

status
Copy Target Runs Last date Status info
100 5 112304 ok
 Show full table
details
Copy Logs and Control Information

Source Client
Client copy profiles vs copied data

Client-
Client-dependent Application User independent WARNING: Before data is
Copy profile Variants
customizing data data data customizing copied from the source client,
data the contents of the target client
SAP_ALL X X X X are deleted ! This is true for all
client copy profiles except the
SAP_APPL X X X profile SAP_USER. In
SAP_CUST X addition, if Central User
Administration is active, you
SAP_CUSV X X
will not be able to copy user
SAP_EXBC* X X X X data, regardless of the client
SAP_EXPA* X X X X X copy profile you select.
SAP_EXPC* X X X
SAP_UAPP X X X X
SAP_UCUS X X
SAP_UCSV X X X
SAP_USER X
SAP_RMBC** X X X X
SAP_RMPA** X X X X X
SAP_RMPC** X X X
* These profiles can be selected only for a client transport (SCC8).
** These profiles can be selected for a Remote client copy only (SCC9)
Profile SAP_RECO
 This client copy profile to be used for recovering a client that has been
accidentally deleted It contains local tables of delivery classes L and W and
the change documents, as well as SAP_ALL.
Deleting a client (SCC5)
To delete in Background To delete Online
To delete the client ID from

Client Maintenance (SCC4)
To simulate the deletion

process and see what table
entries will be deleted Schedule the client deletion
process in the Background
“Immediately” or schedule it
at some later Date/Time.
Client copy: Monitoring and troubleshooting
 Verify the database resources are sufficient

 Monitor a Client Copy with SCC3
 Restart a terminated run if necessary
 Check table using database utility or SQL tools
 Tables not in development class $TMP?
Client copy: Monitoring and troubleshooting (continued)
Client compare
Reference client Logon client Comparison client
Applic Applic Applic

ation ation ation
Data Data Data
User Data
User Data
User Data
Compare Client- Compare Client-

Client- Dependent Dependent
Customizing
Dependent RFC RFC Customizing
Customizing
Cross- client customizing RFC Cross- client customizing

Compare
SAP system repository SAP system repository
Logon system Comparison system
Transaction SCU0
 Transaction SCU0 lists:

– Objects
– Differences
 Client Compare: Selection Options
– Table Entries
Client compare: Difference list
Source: SAP
Using client maintenance tools
 Adjustment of individual objects with SCU0
 Generates detailed information in work list.

 For certain records that can be maintained in SM30.
 Displays a comparison status for each record in work list.
 To understand the comparison status, choose the legend icon.
 Adjustment Customizing Objects.
Client administration
 BDLS Tool: Conversion of logical system names

 SCC1 Copy by transport request
 SCC3 Client copy / transport log analysis
 SCC4 Display view “Clients"
 SCC7 Post-client import methods
 SCC8 Client export
 SCC9 Remote client copy
 SCCL Local client copy
 SCMP View / table comparison
 SCU0 Customizing cross-system viewer
 SE01 Transport organizer (extended view)
 STMS Transport management system
Module takeaways
 There are reasons behind clients being

necessary for a SAP system
 Different clients of different SAP systems can be
copied into the same landscape
 The system change option is necessary to
perform certain tasks like importing a transport
into a client.
 There are different profiles which could be used
for a client copy. The most used profile is
SAP_ALL.
Module 8: Summary

be able to:
 Define a client from SAP perspective
 Interpret client roles
 Identify client copy
 Describe the system change option

Sap Basis

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Sap Basis

Uploaded by

Copyright:

Available Formats

IBM Global Business Services

Day 2: Module map

Module 5: SAP Installations and JAVA SCF

Module 6: SAP System Landscape and SAP Kernel

3 Module 7: Operation Modes and SAP Web Dispatcher

Module 8: Client Concepts and Administration

1 SAP Basis FastTrak WAS 700 © Copyright IBM Corporation 2009

IBM Global Business Services

SAP Installations and JAVA SCF

© Copyright IBM Corporation 2009

On completion of this module, you should be

3 SAP Basis FastTrak WAS 700 © Copyright IBM Corporation 2009

 Topic 1: Different types of SAP installation

4 SAP Basis FastTrak WAS 700 © Copyright IBM Corporation 2009

Different types of SAP installation

 SAP ERP (ABAP/ABAP+JAVA)

5 SAP Basis FastTrak WAS 700 © Copyright IBM Corporation 2009

JAVA startup and control framework

 SAP provides a separate Startup and Control

6 SAP Basis FastTrak WAS 700 © Copyright IBM Corporation 2009

 JControl starts, stops, and monitors the processes of a Java instance

7 SAP Basis FastTrak WAS 700 © Copyright IBM Corporation 2009

8 SAP Basis FastTrak WAS 700 © Copyright IBM Corporation 2009

Start process of a JAVA instance

9 SAP Basis FastTrak WAS 700 © Copyright IBM Corporation 2009

Start process of a JAVA instance (continued)

 JControl reads the instance description from the file system.

10 SAP Basis FastTrak WAS 700 © Copyright IBM Corporation 2009

Start process of a JAVA instance (continued)

11 SAP Basis FastTrak WAS 700 © Copyright IBM Corporation 2009

 SAP has different flavors.

12 SAP Basis FastTrak WAS 700 © Copyright IBM Corporation 2009

Questions and Answers

13 SAP Basis FastTrak WAS 700 © Copyright IBM Corporation 2009

Having completed this module, you should now

14 SAP Basis FastTrak WAS 700 © Copyright IBM Corporation 2009

IBM Global Business Services

SAP System Landscape and SAP Kernel

© Copyright IBM Corporation 2009

On completion of this module, you should be

16 SAP Basis FastTrak WAS 700 © Copyright IBM Corporation 2009

 Topic 1: SAP landscape

17 SAP Basis FastTrak WAS 700 © Copyright IBM Corporation 2009

 A collection of SAP systems required to support a SAP project lifecycle.

18 SAP Basis FastTrak WAS 700 © Copyright IBM Corporation 2009

SAP landscape (continued)

The system landscape should enable you to:

19 SAP Basis FastTrak WAS 700 © Copyright IBM Corporation 2009

System landscape definition

20 SAP Basis FastTrak WAS 700 © Copyright IBM Corporation 2009

Typical systems in a landscape

Sandbox / Playground Training / Education

Development / Build Migration /

System Test / QA Production

21 SAP Basis FastTrak WAS 700 © Copyright IBM Corporation 2009

22 SAP Basis FastTrak WAS 700 © Copyright IBM Corporation 2009

 All Design and Build will be carried out in this system.

23 SAP Basis FastTrak WAS 700 © Copyright IBM Corporation 2009

Quality assurance system

 Testing and validation of all changes introduced in the development system

24 SAP Basis FastTrak WAS 700 © Copyright IBM Corporation 2009

25 SAP Basis FastTrak WAS 700 © Copyright IBM Corporation 2009

 Copied from Production (on request) to support regression testing with