Lesson 1

SAP Solution Ofering

The SAP Software Portfolio
Ofers for Companies of All Sizes
SAP offers a vast range of products for companies of all sizes. SAP has scalable
products, ensuring that they can be adjusted to any size and adaptable to the
continuously changing processes of a company.
SAP Business One
SAP Business One is a comprehensive, integrated EP application !ith an
interface similar to "indo!s, !hich has been developed specifically for small and
midsize companies. #t distinguishes itself by simple navigation and e$pansion
options, innovative %rag&elate functions as !ell as integration !ith 'icrosoft
"ord and E$cel. (he soft!are enables you to uniformly manage the most
important business areas such as sales, distribution and finances !ith one single,
integrated application. (his enables SAP Business One to provide an up)to)date
overvie! of your company.s most important data at any time. (his information
helps you meet customer re*uirements even *uic+er, an important prere*uisite
for profitable gro!th.
SAP Business One is the ideal solution for small companies !ith less than ,--
employees and .- users !ho are loo+ing for an affordable system that covers
their core processes /such as finance, sales, customer service and operations0,
thus ensuring successful and profitable operations. (he solution can be used as a
local soft!are or hosted by a partner !ith an average implementation time of less
than one month. SAP Business One is sold e$clusively through a global partner
net!or+ of currently ,,.-- certified and e$perienced partners. (hey offer 12 hour
support, !hich also covers the more than .3- enhancements from independent
soft!are providers. SAP Business One is currently being used by more than
,2,3-- customers in over 2- countries.
SAP Business ByDesign
SAP Business By%esign is based on an entirely ne!ly developed, designed
application platform. Business applications have been programmed ane! from
scratch based on a model. (he interaction bet!een applications and systems ta+es
place via specified services or interfaces4 Application)to)Application /A1A0,
Business)to)Business /B1B0 as !ell as ne! 5# interfaces. Standardized protocols,
!hich are also simply referred to as "eb Services, are used for this purpose. But
this is not the definition of an Enterprise Service Oriented Architecture /Enterprise
SOA0. #t is rather the modeling of the applications and the A1A, B1B and 5#
interfaces that distinguish an Enterprise SOA.
SAP Business By%esign is SAP.s latest solution for small and midsize companies
!ith bet!een ,-- and 3-- employees, !ho !ant to use an on demand solution to
improve their core processes and at the same time benefit from lo!er entry and
operating costs. #t is aimed, in particular, at midmar+et companies !ho are not
using integrated business soft!are so far.
(he solution combines the advantages of an integrated, end)to)end application
!ith the lo! ris+ potential and the lo! total operating costs of an on demand
solution. An on demand solution that distinguishes itself through integrated
service and support, adaptability and more user friendliness and also guarantees
transparency and the observation of legal re*uirements ) all this on the basis of
an Enterprise SOA by design. SAP Business By%esign the most complete, fully
integrated on demand solution. 'ore than a pure niche solution, it supports the
re*uirements of midsize companies in all areas such as effective management of
finances, human resources, projects, production as !ell as supplier and customer
relationship management as !ell as regional and local legal re*uirements and
compliance management as core design principles. #t !as not developed !ith
the traditional categories of business applications or customer relationship
management and others. #t !as rather developed for business processes in the
entire company !ith user interfaces that are customized to the user roles. SAP
Business By%esign offers end)to)end processes for the !or+ center of the future.
SAP Business All-in-One
All soft!are has to be adapted to the specific company. A midsize company !ith
fe! employees and comparatively stable processes can use preconfigured SAP
systems. SAP All)in)One is the brand name for vertical /industry)specific or
country)specific0 applications that are based on the technology of SAP 6et"eaver
and !ere developed in conjunction !ith SAP.s partners.
SAP Business All)in)One is the ideal solution for small and midsize companies
!ith very industry)specific re*uirements !ho have several divisions and a
mature #( infrastructure. (he solution can be used as a local soft!are or
hosted by a partner and is based on SAP EP. #t provides an industry)specific
function portfolio based on SAP Best Practices. #t is made available through 77-
midmar+et solutions by more than ,,--- partners. SAP Business All)in)One is
affordable and can be planned and than+s to preconfigured business scenarios and
implementation accelerators it can be implemented s!iftly /2 to ,7 !ee+s0. SAP
Business All)in)One is currently being used by more than ,-,--- customers in
over 3- countries.
SAP Business Suite in Detail
(he SAP Business Suite, !hich has evolved from older 8. releases or SAP
systems, is not Enterprise SOA by design but by evolution. Put differently4 the
ability to use Enterprise Services !ill be .enabled. subse*uently, but this !as
not a design principle from the start. Of course, SAP EP 7.- !ill also enable
Enterprise SOA integration scenarios, especially by means of the 9# Enterprise
Service epository.
(his remar+ is intended as bac+ground information for the instructor and should
only be passed on to participants on re*uest.
(he SAP Business Suite is an e$tended family of business applications that
enables companies to manage their entire value chains. (he included business
applications provide users !ith consistent results throughout the entire company
net!or+ and give your company the fle$ibility it needs in today.s dynamic mar+et
situations. (he application consists of a number of different products that support
cross)company processes.
SAP.s soft!are portfolio is constantly e$tended, optimized, and tailored to the
needs of the mar+et and of customers. SAP has therefore, for e$ample, developed
many industry)specific applications over the years. (he topic of integrating
different business systems /even from different vendors and across company
boundaries0 has become increasingly important recently. Products for small to
midsize businesses have also been added to SAP.s family of soft!are solutions.
(he SAP Business Suite, a complete business soft!are pac+age that is uni*ue
!orld!ide, plays a central role. 'any companies are already profiting from the
comprehensive and fle$ible business applications !ith highly evolved functions4
complete integration, industry)typical functions, unlimited scalability and smooth
collaboration via the internet.
(he SAP Business Suite provides4
. A complete spectrum of business solutions
. A technological infrastructure that combines openness and fle$ibility !ith
maturity and stability
. #nterfaces for integrating non)SAP products
. :omponents that can be adapted to meet multiple business re*uirements
. 6umerous industry)specific functions
Business Process Platform (BPP)
A Business Process Platform is the prere*uisite for the deployment of
a service)oriented architecture for business applications /Enterprise
Service)Oriented Architecture, Enterprise SOA0. (he SAP BPP is composed
of the follo!ing modules4
SAP et!ea"er
SAP 6et"eaver is an open integration and application platform
for all SAP applications and certain SAP partner applications.
SAP 6et"eaver is a !eb)based platform, !hich serves as the
basis for the Enterprise SOA and enables the cross)company and
technology)independent integration and coordination of employees,
information and business processes. (han+s to open standards,
information and applications from any source and based on any
technology can be integrated. SAP 6et"eaver is interoperable !ith the
most important technological standards such as the ;ava 1 Platform,
;ava Enterprise Edition /;ava EE0 and 'icrosoft .6E(. (he platform
provides a ma$imum of reliability, security and scalability ensuring that
business processes that are critical for success run !ithout problems.
SAP applications
(he SAP Business Suite includes e$tensive, integrated applications,
!hich customers can license completely or individually. 'ore recent
SAP applications use the Enterprise Service Repository, repository
for processes and Enterprise Services. Enterprise Services map
business processes using open standards.
Both SAP 6et"eaver and the SAP applications are continuously enhanced
through Enhancement Packages. Enhancement pac+ages are shipped
at regular intervals in order to ma+e it possible to respond to mar+et
re*uirements *uic+er and to provide additional benefits to customers and
partners !ithout the need to !ait for the ne$t major product release.
Composite Applications (xApps)
SAP $Apps are a portfolio of .Pac+aged :omposite Applications., !hich
you can use to promote improvements and innovation in your company more
easily. "ith their ability to combine e$isting, heterogeneous systems to
form cross)functional processes, SAP $Apps :omposite Applications bring
people, information, and business processes together to ma+e your company
more dynamic and competitive. (his fle$ibility enables you to implement
business)!ide strategies more easily and efficiently. SAP $Apps increase
the value of e$isting investments in the core business area and ma$imize the
return on strategic investments4 employees, +no!ledge, products, business
relationships, and information technology.
<ou can use the SAP :omposite Application =rame!or+ /:A=0 to develop
and run your o!n $Apps.
(his graphic is still brand ne! /in >. 1--?0 and differs significantly from earlier
graphics. One reason !as to bring the product vie! /."hat SAP products are
available@.0 and the license vie! /."hat can you buyAlicense from SAP@.0 closer
(ogether.
(he follo!ing list should help to e$plain !hat is behind the individual terms. #n
SAP(E: one cannot e$pect the instructor to be an e$pert in all applications )
but you should at least be able to provide a rough description of the individual
applications. #f they are still valid, the specified lin+s provide additional
#nformation.
Applications for Governance Risk an! Compliance (GRC)" Applications
for governance /SAP B: epository0, ris+ management /SAP B: is+
'anagement0 and compliance !ith legal re*uirements /SAP B: Access
:ontrol, SAP B: Process :ontrol, SAP B: Blobal (rade Services, SAP
Applications for environment, health, and safety compliance management,
B: composite applications by SAP and :isco0C for more information see
Applications for Performance #anagement" Applications
for performance management /SAP Strategy 'anagement, SAP
Business Planning and :onsolidation, SAP Business Profitability
'anagement by Acorn, SAP $App Analytics0.
SAP Enterprise Resource Planning (SAP ERP)" Applications for
supporting resource planning across an entire enterprise
. SAP EP Duman :apital 'anagement
. SAP EP =inancials
. SAP EP Operations
. EP :orporate Services
SAP Customer Relationship #anagement (SAP CR#)" Applications for
end)to)end, customer)oriented business processes.
SAP Supplier Relationship #anagement (SAP SR#)" SAP S'
integrates strategic purchasing processes such as vendor *ualification
and vendor management, electronic invitations for tender and auctions
or contract management !ith the other core processes in your company
and !ith the processes of your suppliers.
SAP Supply Chain #anagement (SAP SC#)" Applications
for managing the entire logistical chain to synchronize supply
and demand across company borders.
SAP Pro!uct $ifecycle #anagement (SAP P$#)" Applications
for including internal and e$ternal partners directly in the operational
product development and production processes.
. %n!ustry Applications" #ndustry)specific applications
. Ban+s
. Dealthcare
. 5niversities and research institutes
. #nternal & e$ternal security
. Public sector
. #nsurance
. Service industry
. "holesale
. etail
. Eogistics service providers
. 'edia industry
. (elecommunications
. 5tilities industry
. Automobile industry
. :onstruction industry, engineering, construction and operations
. Digh tech and electronics industry
. :onsumer products industry
. Areospace and space industry
. 'echanical engineering
. 'etal, !ood and paper industry
. 'ining
. :hemicals
. Eife sciences
. Oil and gas industry
SAP xApps Composite Applications" :omposite applications that cover
several company solutions across persons, information and processes
. SAP $App :ost and >uotation 'anagement /SAP $:>'0
. SAP $App #ntegrated E$ploration and Production /SAP $#EP0
. SAP $App Eean Planning and Operations /SAP $EPO0
. SAP $App 'anufacturing #ntegration and #ntelligence /SAP $'##0
. SAP $App Product %efinition /SAP $P%0
. SAP $App esource and Portfolio 'anagement /SAP $P'0
. SAP $App Sales and Operations Planning /SAP $SOP0
. SAP $App Spend Analytics /SAP $SA0
Applications for %nformation &orkers" Applications granting employees
access to company data and business processes anytime and any!here
. %uet for 'icrosoft Office and SAP
. SAP #nteractive =orms by Adobe
. SAP 6et"eaver Enterprise Search
SAP 'et&eaver" Open integration and application platform for all SAP
applications
. SAP 6et"eaver Application Server
. SAP 6et"eaver Business #ntelligence
. SAP 6et"eaver E$change #nfrastructure
. SAP 6et"eaver 'aster %ata 'anagement
. SAP 6et"eaver 'obile
. SAP 6et"eaver Portal
. SAP Auto)#% #nfrastructure
. SAP 6et"eaver #dentity 'anagement
Conte#t of Applications an$ Components
6umerous applications for business challenges are provided in the conte$t of
the SAP Business Suite. Do!ever, many applications have similar or identical
re*uirements for business functions in subareas. %ifferent applications therefore
contain similar /soft!are0 components in parts. A component is the smallest,
separately producible, deliverable, installable, and maintainable soft!are unit.
:omponents refer to, for e$ample, an SAP E:: system, an SAP S:' system or
also an SAP 6et"eaver portal system. (he graphic provides an overvie! of
this hierarchy /components as building bloc+s of solutions0 using the SAP S:'
application as the e$ample.
Possi%ilities with SAP Business Suite
(o give you a clearer impression of the possibilities of the SAP Business Suite,
you can see some of the business scenarios that are possible using SAP Business
suite from following graphics.
(he SAP Business Suite offers many options for integrating your company)internal
business processes and, li+e!ise, integrating business partners. systems. <ou
can implement the integration of cross)enterprise processes using different
technologies, such as !ith Application Link Enabling /AEE0, using Electronic
Data Interchange /E%#0, through 9'E data e$change, or also using Composite
Applications /$Apps0 and "eb Services.
SAP &elease Strategy
'istory of Selecte$ Software Components
(his section provides a bit of history of a fe! selected soft!are components.
Technical Basis (Application Ser"er(
Bac+ in the days !hen SAP basically offered t!o products /SAP 81 and SAP
8.0, the development of the /technical0 basis !as closely lin+ed to application
development. (he release names of the SAP Basis corresponded to the SAP 8.
version, for e$ample, SAP Basis 2.-B !as the technical basis for SAP 8. 2.-B
Around the turn of the millennium, the SAP portfolio gre! significantly, ne!
products !ere created that re*uired more fre*uent changes and enhancements of
the SAP Basis than SAP 8.. (his mar+s the transition from the classical SAP
Basis /last version4 SAP Basis 2.7%0 to SAP &e( Application Server /SAP "eb
AS0. 6e! internet technologies /#nternet :ommunication 'anager from SAP"eb
AS 7.,- on!ards0 and the supplementing of the classical ABAP environment !ith
;ava8;EE /from SAP "eb AS 7.1- on!ards0 !ere important milestones.
SAP "eb AS 7.2- forms the technical basis /.application platform.0 of SAP
6et"eaver -2. SAP 6et"eaver offers e$tensive capabilities /such as Business
#ntelligence0, !hich are all based on the application platform. =rom SAP
6et"eaver ?.- /previously4 SAP 6et"eaver 1--2s0 the names and releases
!ere adapted further, so no! SAP 6et"eaver ?.- is based on SAP 'et&eaver
Application Server )*++ /SAP 6et"eaver AS0.
Central )&P *unctions
(he follo!ing graphic sho!s the historical development for the current SAP EP
:entral :omponent /E:: 7.-04
Figure 6: Evolution from SAP R/3 via SAP R/3 Enterprise to SAP ECC
As already mentioned, in times of SAP R,-, the technical basis and application
development !ere interlin+ed, up to and including SAP 8. 2.7:.
"ith SAP R,- Enterprise /2.?0, !hich is based on SAP"eb AS 7.1-, the concept
of SAP 8. Enterprise E$tensions !as introduced.
A central application /previously4 solution0 of the SAP Business Suite is SAP
EP for Enterprise esource Planning. (he central soft!are component of SAP
EP is SAP ERP Central Component /SAP E::0. SAP E:: 3.- can thus be
considered the technical successor of SAP 8. Enterprise and is based on an SAP
"eb AS 7.2-. At the time of creating this documentation, the current version is
SAP EP 7.- /previously4 SAP EP 1--30, !hich also includes an SAP E::
7.- and other components, !hich operates on the basis of SAP 6et"eaver AS
?.--. =unctional enhancements for the different soft!are components are made
available through enhancement pac+ages.
SAP 6" AS ?.,- or SAP 6et"eaver ?., are currently not used as the technical
basis for an SAP E:: system. Other SAP 6et"eaver components, such as
SAP 6" Process #ntegration /P#0 and SAP 6" :omposition Environment /:E0
already re*uire this SAP 6et"eaver release level.
A"aila%ility an$ Deli"ery
SAP applications, SAP 6et"eaver, Enhancement Pac+ages and $Apps are offered
to customers in t!o phases.
Figure 7: Phases of Software Deliver ! SAP
&estricte$ Shipment Phase
6e! soft!are releases are only available to a restricted number of customers
!hose increase is controlled. (he Release to Customer date mar+s the start of
the Restricted Shipment Phase.
%uring the restricted shipment phase, the ne! soft!are release passes through a
standardized process, the Ramp-Up. :haracteristics of the ramp)up process are4
. amp)up is the name for the mar+et introduction process of ne! products
or ne! releases of SAP soft!are.
. (he soft!are can be used for a productive implementation.
. %uring the ramp)up, the soft!are is only available for a limited circle of
customers, customers .apply. to SAP to participate in a ramp)up.
. (he ramp)up serves to ta+e customer !ishes into consideration before the
respective SAP soft!are is generally available.
. Participants in the ramp)up are given direct contact to the SAP development
and are provided !ith !ide support in implementing the SAP soft!are.
. A ramp)up usually ta+es about 7 months.
'ote" =or more information about the ramp)up, see
http488service.sap.com8rampup.
+nrestricte$ Shipment Phase
(he second phase of the delivery is called unrestricted shipment phase. After
the Deault Release Date all customers can re*uest the ne! soft!are !ithout
restrictions.
(he respective latest, generally available version of SAP soft!are is called Deault
Release. "hen SAP customers order soft!are from SAP, they are usually given
the current default release.
,aintenance
<our maintenance contract includes Support Pac+ages, !hich are provided by SAP
via the SAP Service 'ar+etplace. Support Pac+ages solve /component)dependent0
problems that can result !hen using the SAP soft!are. SAP provides these
Support Pac+ages at certain intervals.
"#$#% &aintenan'e Strateg
Figure (: "#$#% &aintenan'e Strateg
Since 1--2, SAP has been offering a ne! maintenance strategy for all products
that are based on SAP 6et"eaver. (his 3),)1 maintenance strategy offers
maintenance for five years for the mainstream maintenance, follo!ed by one year
e$tended maintenance for a maintenance fee of t!o percent more and, optionally,
another t!o years for a maintenance fee !hich is four percent more than the
standard maintenance fee. Soft!are installed at customer locations can transit into
the phase of customer)specific maintenance.
"e distinguish the follo!ing three phases of maintenance4
,ainstream maintenance
'ainstream maintenance starts from the release to customer point in time
and usually ends 3 years after the default release date.
)#ten$e$ maintenance
:ustomers can e$tend the support period /in !hich corrections or legal
changes are ta+en into account0 for an increased maintenance fee /F1G
for , year, F2G for 1 years0.
Customer-speci-c maintenance
=rom a certain point in time during the lifecycle of a release, this release
is no longer adjusted to meet e$ternal re*uirements. Such re*uirements
are, for e$ample, the implementation of legal changes or the support of
ne! technologies. (he time in *uestion is mar+ed by the end of e$tended
maintenance or the end of mainstream maintenance, if no e$tended
maintenance is offered. :ustomer)specific maintenance starts at this point
in time.
'ote" See http488service.sap.com8maintenance for additional information
on the maintenance strategy. SAP note 313-3 deals specifically !ith the
particularities of customer)specific maintenance.
+pgra$e
<ou should thin+ about upgrading to the latest release !hen your SAP soft!are
is approaching the end of its mainstream maintenance, at the latest. %uring an
upgrade of your SAP soft!are, you can generally s+ip one or more of the soft!are
releases /of your application0 that have appeared in the meantime. =or e$ample, an
upgrade from SAP 8. 2.7: to SAP EP 7.- is technically possible, even though
you change product during this upgrade /from SAP 8. to SAP EP0.
SAP offers upgrade paths for SAP applications, SAP 6et"eaver, Enhancement
Pac+ages, $Apps and :ontent Shipments. (here might be cases in !hich an
upgrade re*uires several steps /especially due to technical restrictions0.
'ote" =or more information on upgrade, see http488service.sap.com8up)
grade.
Lesson 2
SAP et!ea"er O"er"iew
(he SAP 6et"eaver technology platform is designed for the fle$ible, step)by)step
and efficient introduction of important #( processes in companies. (han+s to the
high level of integration of the individual platform functions, its openness and the
use of industry standards, the integration and application platform contributes
significantly to!ards reducing the total cost of o!nership /(:O0 across the
entire system landscape. SAP 6et"eaver represents the technical basis of the
SAP Business Suite, SAP $Apps :omposite Applications and other, partly
industry)specific SAP applications.
SAP 6et"eaver is also the technical basis for the for!ard)loo+ing, service)oriented
architecture for business applications /enterprise SOA0. #n an enterprise SOA, the
application functions are made available in the form of enterprise services. (hese
are !eb services that can be combined fle$ibly and used for business purposes.
(hey are provided by different providers through data net!or+s and communicate
!ith other applications using open, standardized interfaces.
SAP 6et"eaver integrates and connects people, information and business
processes across technologies and companies. #t enables companies to adjust
to changes *uic+ly. SAP 6et"eaver ensures that a companyHs crucial business
processes are reliable, safe and scaleable. =urthermore, SAP 6et"eaver enables
companies to ma$imize the benefits from the current soft!are and systems.
6on)uniform integration technologies are consolidated and predefined business
content is provided thus reducing the amount of manual !or+ re*uired. SAP
6et"eaver is based on a technology using industry standards and can be enhanced
!ith popular development tools such as ;ava 1 Platform, Enterprise Edition
/;1EE0, 'icrosoft .6E( and #B' "ebSphere.
SAP et!ea"er .ayers
Figure $): SAP *et+eaver: Capa!ilities
People /ntegration
People integration ensures that your employees have access to the
information and functions that they need in order to perform their activities
*uic+ly and efficiently. (he functions of the SAP 'et&eaver Portal are
the most important in this conte$t. SAP 'et&eaver #o(ile serves as the
universal platform for company mobility and supports SAP solutions for
'obile Business.
/nformation /ntegration
(his integration layer provides access to all structured and non)structured
information in your company. (he +ey areas of information integration are
mostly formed by SAP 'et&eaver Business %ntelligence, .no/le!ge
#anagement, as a component of SAP 6et"eaver Portal and SAP
'et&eaver #aster 0ata #anagement. All aforementioned +ey areas
provide comprehensive options for uniform access to distributed information
in a company.
Process /ntegration
Process integration ensures that business processes !or+ across system
borders in a landscape of heterogeneous systems. (he SAP 'et&eaver
Exchange %nfrastructure /SAP 9#0 plays a crucial role here and connects
SAP systems and non)SAP systems. #t mainly uses open standards from
the 9'E and ;ava !orld to do so.
Application Platform
(he SAP 'et&eaver Application Server provides a proven infrastructure
for operating business applications that are based on +ey technologies such
as ;1EE or ABAP. Besides the runtime environment for ;1EE and ABAP
applications, the corresponding development tools are also shipped and help
you implement your applications. Open standards, bro!ser)based access to
applications and !eb services complete the application platform and serve as
an important instrument for the enterprise service architecture.
Beyond these four steps and in parallel to them, SAP 6et"eaver offers Eifecycle
'anagement and the :omposite Application =rame!or+4
.ifecycle ,anagement
Eifecycle 'anagement supports design, development, deployment and
change management of the entire solution and thus meets the re*uirements
in the security, design and modeling, testing and systems environment
management areas.
Composite Application *ramewor0
(he :omposite Application =rame!or+ /:A=0 is integrated into SAP
6et"eaver and enables SAP and its partner to use tools, frame!or+s, rules
and methods to create ne! applications that are based on business processes
across function areas.
SAP et!ea"er Application Ser"er (SAP et!ea"er
AS(
Almost every SAP system is based on SAP 6et"eaver AS and uses it as the
runtime environment. (ogether !ith the database, SAP 6et"eaver AS is the the
application platform of SAP 6et"eaver.
SAP 'et&eaver AS is the logical result of the further development of the
SAP Application Server (echnology /previously4 SAP Basis0, !hereby special
attention is paid to !eb)based applications.
SAP 6et"eaver AS offers4
. A reliable and e$tensively tested runtime environment, !hich has been
developed further continuously over more than ten years
. A frame!or+ for e$ecuting comple$ business processes that meet the highest
security standards
. A reliable and user)friendly development environment
. Support for open standards, including D((P, D((PS, S'(P, "eb%AI,
SOAP, SSE, SSO, 9.3-J, 5nicode, D('E, 9'E and "'E
. Digh scalability
. Support for different operating system and database platforms
Since the applications delivered by SAP do not al!ays re*uire both runtime
environments, that is, ABAP and ;ava, there are different installation options for
SAP 6et"eaver AS. (hese are4
. SAP 'et&eaver AS ABAP" :omplete infrastructure in !hich ABAP)based
applications can be developed and used.
. SAP 'et&eaver AS 1ava" :omplete infrastructure in !hich ;1EE)conform
applications can be developed and used.
. SAP 'et&eaver AS ABAP21ava" :omplete infrastructure in !hich
ABAP)based and ;1EE)based applications can be developed and used. (his
installation emphasizes the seamless ;ava)ABAP integration.
Lesson 3
a"igation
a"igation in 1eneral
Diferent +ser /nterfaces in the SAP )n"ironment
(here are numerous different types of SAP systems, such as .classical. EP
systems, but there are also other system types li+e Portal or Business #nformation
"arehouse systems, for e$ample. %epending on !hat they are used for, these
different system types do offer rather different user interfaces.
(he follo!ing list names some fre*uently used access technologies, !hich end
users of these system /so not .technicians.0 use fre*uently.
Please note that the above list does not cover all SAP products are and that not
all possible /K0 access technologies are listed in all cases. =or e$ample, an SAP
E:: system can also be accessed by bro!ser or using the SAP !UI for ;avaC SAP
6et"eaver B# is also accessible by SAP !UI for "indo!s and so on.
(he follo!ing display !ill be limited to the most popular access technology,
the SAP !UI.
(he presentation interface, SAP !UI /Braphical 5ser #nterface0 enables the user
to interact !ith the SAP system and enter or display data.
SAP !UI implements the graphical user interface using the functions provided by
the relevant presentation environment. SAP B5# is based on the "indo!s Style
Buide and is available for several platforms, providing the same functions for
each. #f you learned to use SAP !UI on one platform, you can use the system on
another platform e$actly the same as before, !ith the e$ception of a fe! small
platform)specific B5# attributes. (here are different variants of the SAP !UI,
!hich can all be operated in the same !ay, irrespective of the underlying platform.
(he follo!ing types of SAP !UI are available4
. SAP !UI for the "indo!s environment
. SAP !UI for the ;ava Environment
. SAP !UI for D('E
'ote" #n the above list, the official terms of the SAP !UI are usedC these
are only available in English. :ollo*uially, the follo!ing terms are used
synonymously /in the same order04 SAP !UI or "indo#s, $a%a !UI and
"eb !UI. Please note that these are not the .official SAP terms. but
are used fre*uently nonetheless.
Caution" (he above variants of the SAP B5# are suitable only for
!or+ing !ith ABAP)based SAP systems /including the SAP B5# for the
;ava Environment0.
;ava)based SAP applications are accessed using a bro!ser.
SAP !UI for the "indo!s environment /abbreviated to SAP G3% for &in!o/s0
is the SAP !UI implementation in a 'icrosoft "indo!s environment. SAP B5#
for "indo!s is !ritten in : or :FF, runs on "indo!s)based platforms, and
supports all transactions in an SAP system.
(he data flo! bet!een the presentation layer and the application layer does not
consist of prepared screens, but rather of logical, compact information about
control elements and user input /%#AB protocol0. (he volume of data transferred
for each screen change is generally a fe! LB. <ou can therefore also easily
connect presentation servers over "A6s.
SAP !UI for the ;ava Environment /abbreviated to4 SAP G3% for 1ava0 is !ritten
in ;ava and is the platform)independent implementation of SAP !UI. Ei+e SAP
!UI for the "indo!s environment, this B5# also uses the %#AB protocol, so the
volume of data transferred for each screen change is also generally only a fe! LB
and you can easily connect presentation servers over "A6s.
<ou can either install SAP !UI on the front end, or alternatively you can install it
on a terminal server and access it using terminal clients.
SAP G3% for 45#$ consists of the #nternet (ransaction Server /#(S0 in the
Application Server ABAP /short4 AS ABAP0 on the server side and a "eb
bro!ser on the client side. (he #(S is re*uired to convert the SAP !UI data flo!
already in the AS ABAP into D('E and bac+. #n this case, an D('E data stream
is e$changed bet!een the #nternet :ommunication 'anager of the AS ABAP and
the front)end. (he primary advantage of the SAP !UI or &'(L is the simpler
installation on the front)endC a bro!ser installation suffices.
(he follo!ing graphic sho!s the various alternatives and the flo! of
communication !ith the AS ABAP dispatcher.
'ote" <ou can find further information on the various SAP !UI
alternatives in the follo!ing SAP 6otes4
. SAP 6ote 77J?,4 front)end platforms supported
. SAP 6ote .,237M4 functions not available !ith SAP B5# for D('E
. SAP 6ote ,273-34 SAP B5# for the ;ava environment
. SAP 6ote ,.MM7J4 SAP B5# on the "indo!s (erminal Server
.ogging on to the System
'ost of the solutions shipped by SAP can be accessed using the SAP !UI )SAP
!raphical User Interace*. =or the sa+e of simplicity, further descriptions refer to
the SAP !UI for the "indo!s environment.
SAP provides another program for starting the front)end4 SAP Logon. "hen you
call up SAP Logon, it displays a list of SAP systems for !hich you can start the
logon process. (his list is ta+en from a file on the front end4 saplogon*ini. (his
file is usually centrally preconfigured and provided for end users.
%uring logon, the SAP Eogon program also enables logon loa! !istri(ution
using the resources available for the system selected.
"hen logging on to an SAP system, you !ill be prompted to enter the user and
pass!ord, among other things. #f you have implemented a Single Sign67n (SS7)
solution, you may not need to enter this information. "hen you log on, you
also select a certain client of the SAP systemC this field is usually already filled
appropriately.
4int" A client usually represents a company in an SAP system. (his
means that if an SAP system has several clients, then several companies
can be represented and simultaneously active in that system. (he client
has a corresponding +ey field in the tables of the database used by that
SAP system. "hen !or+ing in a client, you only have access to business
data from the same client. :lients therefore correspond to independent
business entities.
"hen logging on, you can select a logon language supported by that system. SAP
systems can support a large number of languages, the minimum being English
and one other selected language. (he number of installed languages determines
!hich languages your system supports.
On the logon screen, you also have the option of using the +e# pass#ord
pushbutton to change your pass!ord, at the most once per day.
<our system administrator can add additional te$t to your logon screen. (o do so,
follo! the SAP)6ote 1-32M? ) O!n te$t on SAPG3% logon screen*
'ote" SAP 6otes contain detailed information on certain functions or
corrections for +no!n errors in SAP products. <ou can access SAP
6otes through, for e$ample, the SAP Ser%ice (arketplace on the #nternet,
using a valid user /S)user0 and pass!ord4 http488service.sap.com8notes
http488service.sap.com8notes.
#n the course of one logon to a system, you can !or+ in several sessions
/processing !indo!s of an SAP system0 simultaneously. <our system
administrator can use a system parameter to define ho! many sessions are
permissible for each logon to the SAP system. =or more details please see the
SAP)6ote ,1277 ) Eogon restrictions in 8..
5ser data is stored in the system by client, that is, you can, for instance, log on
to client ,-- in your system, but you !ill not have a user for client 1--, even if
your system has a client 1--. (he data for a particular user !ithin a client is
called the user master recor!.
'ultiple logons to SAP systems are logged. (his is for reasons of both security
and licensing. #f the same user logs on more than once, then for each subse*uent
logon, the system displays a !arning message that offers the user the follo!ing
three options4
. :lose all e$isting session/s0 and log on again
. Leep e$isting session/s0 open, and open an additional session /this is
recorded in the log0.
. (erminate this logon
Changing the Passwor$
5se the initial pass!ord assigned to you !hen you log on to the system for the
first time. %uring the first login, you are prompted to save a changed pass!ord.
=or security reasons it ma+es sense to change the pass!ord occasionally.
Changing the Change$ Passwor$ Again Prere2uisites
4int" 5sers can change their pass!ord no more than once a day on the
initial screen. #n contrast, user administrators !ith authorization for
transaction S3+8 can change a userHs pass!ord as often as they !ant.
Actually, the administrator can only assign ne! initial pass!ords.
Pro'e,ure
,. On the logon screen of the SAP system, enter your data and your current
pass!ord.
1. On the top left, clic+ the +e# Pass#ord pushbutton.
.. :hange your pass!ord as described above and save your data.
Screen Structure
Once you have logged on successfully, the initial screen of the SAP system
appearsC this screen is also +no!n as the SAP Easy Access screen.
(he SAP Eas, Access screen is the default initial screen in SAP systems. (he left
side of the screen contains a tree hierarchy of the menus available to you in the
SAP systemC you can use the right side of the screen to display your company
logo. (his graphic is made available centrally by your system administrator and
cannot be customized by individual users.
<ou can find a detailed description of ho! to configure the graphic in SAP Eas,
Access under E-tras ./// Administration inormation /if you have the correct
authorization0. Please note that the graphic is stored in the system and transported
to the front end every time a user logs on. Although it is transported in compressed
form, the graphic should not e$ceed 1- LB. <ou can also prevent the graphic from
being displayed by either choosing the setting Lo# Speed Connection in the SAP
Logon program /see SAP)6ote ,7,-3. ) 5sing SAPB5# in "A60, or by using
E-tras ./// Settings in the SAP Easy Access screen.
A typical screen /!ith some common elements0 appears if you choose S,stem .
User Proile./// 0#n Data and then the Deaults tab page. <ou !ill then see this
screen !ith the data for your o!n user4
An SAP user interface can contain the follo!ing simple screen elements, for
e$ample4
. :ommand field
. 'enu bar, system function bar, title bar, application toolbar, status bar
. :hec+ bo$es
. adio buttons
. (ab
<ou can start applications directly by entering their transaction code in the
comman! fiel!, !hich is usually hidden. <ou can find the transaction code for an
application either in the overvie! menu on the SAP Eas, Access screen, in the
status bar /see belo!0, or in the application itself under S,stem ./// Status.
(he #enu (ar is the top line of any dialog !indo! in the SAP system. (he
menus sho!n here depend on !hich application you are in. (hese menus may
also contain cascading menus.
(he pushbuttons in the stan!ar! tool(ar are sho!n on every SAP screen. #f they
are not available in an application, pushbuttons that you cannot use on that screen
are deactivated. #f you place the cursor over a pushbutton for a short time, the
system displays a flag !ith the name or function of the pushbutton. #f appropriate,
the corresponding function +ey setting is also displayed.
(he title (ar is the function that you are currently in.
(he application tool(ar sho!s the pushbuttons available in the application that
you are currently in.
(he Status (ar displays information on the current system status, such as
!arnings and errors. <ou can also change the display variant to sho!, for e$ample,
the transaction code of the transaction you are currently in.
"ithin a field group check (oxes allo! to select several options at the same time.
"ith ra!io (uttons you can only select one option.
A ta( organizes several subscreens to improve clarity.
%nput fiel!s and push(uttons are additional screen elements.
.ogging of from the System
<ou should log off the system !hen you have finished your !or+ in the SAP
system. <ou have several options for doing this4
.og of "ia the ,enu Bar
,. #n the menu bar, select S,stem ./// Log o.
4int" Alternatively, clic+ the yello! arro! in the SAP Easy
Access menu or enter the 3nen$ command in the command field.
#f several sessions are open, the yello! arro! only closes the
active !indo!. (he dialog field for logging off only appears in the
last !indo!.
Caution" (he 3ne# command immediately terminates your logon
!ithout *uerying the dialog !indo!s first. All sessions of your
terminal session are closed and entries that have not been saved
are lostK
1. A Eog off %ialog Bo$ appears and tells you that you !ill lose data that has
not been saved !hen you log off.
Figure $-: .og off Dialog /o0
.. (o log off, choose 1es.
4int" =rom the perspective of the "indo#s operating system, an
SAP session is a normal application. Dence, you can also close SAP
sessions !ith the means of the operating system, such as by using
the +ey combination Alt234. "hen you close the last !indo! of
your session, the dialog bo$ is also displayed.
A$"ance$ a"igation in the SAP 1+/
+ser ,enu an$ SAP ,enu
(he SAP Access menu is automatically displayed after logging onC it represents
the standard access point to an SAP system for the SAP B5# for "indo!s.
(he navigation bar in the left part of the screen contains a clear tree structure,
consisting of menu entries and favoritesH entries. <ou can adjust the favoritesH area
in particular to your needs. (he entries of the SAP menus and the user menus can
only be changed by system administrators.
(he end user can s!itch from the role)based user menu to the SAP standard menu
/if the system settings allo! this0.
4int" System administrators can use table USERS/SS( to determine
!hether or not users are allo!ed to s!itch bet!een the SAP menu and
their user menus. #f both menus are disallo!ed, then the user menu is still
displayed. (he availa(ility of the user or SAP menu does not affect a
userHs authorizations. (his means that a user can al!ays call authorized
functions using a transaction code, independent of the menu structure.
(he role)based user menu is created on the basis of the role/s0 assigned to the user
and transferred to the front end. (his means that it ma+es sense to +eep roles as
small as possible because large roles could ta+e a long time to transfer to the
front end in certain circumstances. #f a user has several roles assigned, then some
functions can be repeated in different parts of the role)based user menu. #f you do
not !ant these to appear t!ice, see SAP)6ote .3?7J. ) edundancy avoidance in
Easy Access /and the other notes listed therein0 for information on identifying and
deleting duplicates, and related *uestions.
4int" As long as you have the appropriate authorization, you can also
display user menus other than the ones assigned to you in your user master
record. (o do this, choose 0ther menu. 5se Create role to start the role
maintenance transaction, P=:B.
(he user and SAP menus can be structured in a pretty comple$ !ay. #t is then
difficult to remember the e$act path for the transaction you are loo+ing for. As long
as the transaction has not been copied into the favorite area, you can find it more
easily !ith special search transactions. (he transactions SEARC49SAP9#E'3
and SEARC493SER9#E'3 search the corresponding menus for the predefined
te$t pattern. (he search result is prepared in a list vie! from !hich you can ta+e
the navigation path. (he transactions found cannot be started directly !ith a
double)clic+.
*a"orites ,anagement
#n addition to the area menu or SAP menu, the user is also provided !ith functions
in the favoritesH area. Ein+s to fre*uently used transactions, !eb lin+s or files can
be stored in the favoritesH area.
(he favorites list thus contains references to SAP system functions or lin+s to
internet content or to files on the end userHs front)end computer. (he favorites
list, !hich is initially empty, can be edited by each end user in accordance !ith
his or her preferencesC you can only vie! your o!n favorites list. Since data on
the favorites is stored !ithin the SAP system, each user might have different
collections of favorites in different systems.
4int" :omplete favorites menus, incl. the folder structures, can be easily
copied by uploading or do!nloading from one SAP system to another. (he
do!nloaded favorites menus are stored temporarily on the front)end P:.
(o improve the structuring, sort the favorites in o!n folders. <ou can edit favorites
in the SAP Eas, Access screen using the menu entry 3a%orites.
(he 3a%orites menu gives you the option of adding a function from the user /or
SAP0 menu to your personal favorites list by selecting the function and choosing
3a%orites.Add. Dere, the menu path is also !ritten !ith the te$t of the favorites
entry to a limited e$tent. #f you have highlighted a menu entry using the mouse,
you can copy the selected node in the favoritesH area by right)hand mouse clic+.
Alternatively, you can also drag the elements from the menu area using the mouse
and store them in the favoritesH area /%rag&%rop0. <ou can add 5Es or lin+s to
files to your list of favorites by choosing 3a%orites ./// Add other ob5ects. :lic+
on the triangle symbol to the left of the file symbol to e$pand or collapse the list
of favorites.
4int" (o change the name of a transaction in =avorites, highlight the
corresponding favorites entry and select the menu path 3a%orites .
Change. <ou can change and save the te$t in the dialog bo$ that opens.
<ou can delete favoritesH entries that you no longer need. #n doing so, the lin+ to
the corresponding function is deleted from your favoritesH list. #f you !ant to
delete the entire =avorites menu, highlight the entry 3a%orites and right)clic+ to
call up the available conte$t menu. :hoose Delete all a%orites.
Calling +p *unctions
<ou have several options for navigating in an SAP system4
. Entering transaction codes in the OL :ode field
. By choosing items from menus in the menu bar
. By choosing items from the favorites list or from the user or SAP menus
<ou can reach the menus in the menu bar by simply using the +ey combination
Alt4567 /N corresponds to the underlined letter of the selected menu item0 or
Alt and cursor navigation using the arro! +eys on the +eyboard.
<ou can use the +eyboard to get to the SAP Eas, Access screen or the OL :ode
field and call system functions from there.
4int" 5se the follo!ing +eys to navigate using the +eyboard4
. 5AB moves from one field element to the ne$t !ithin a field group.
. Ctrl 2 5AB goes from one field group to the first element of the
ne$t field group.
. Ctrl 2 , goes directly to the OL :ode field.
<ou can find further shortcuts using Customi6ing o local la,out
)Alt2378*./// SAP !UI &elp.
"hen the OL :ode field is active /also +no!n as command ield0, you can use the
=, +ey to display possible entries for this important field. (he follo!ing entries
are possible4
. 3n to cancel the current transaction
. 3n8888 to call transaction :::: directly from another transaction.
"ithout the prefi$ you can only call 9999 from the SAP Eas, Access
screen.
. 3o to display the overvie! of o!n sessions
. 3o8888 to call transaction 9999 in a ne! session directly from another
transaction
. 3nen$ to end the logon session !ith a confirmation dialog bo$
. 3ne# to end the logon session !ithout a confirmation dialog bo$
. 3i to delete the session you are currently using
'ote" (he OL :ode field is an e$ception in that choosing the =2 +ey does
not display the input help. (he =2 +ey in the OL :ode field lists the last
,3 different entries in the OL :ode field. (his list is stored in the registry
on the front end and is valid for all sessions on the front end /regardless
of the system used0.
'elp Options
(he SAP system provides you !ith various help options, !hich !ill be introduced
in the follo!ing section.
*9 'elp
<ou can use the =, +ey to display an e$planation of fields, menus, functions and
messages. (he =, help also displays technical information on the relevant field.
(here you !ill find the parameter #% that you can use !hen setting user)specific
default values for input fields that are also lin+ed to the parameter #%. <ou can
also display interesting information by, for e$ample, calling the =, help for the
OL :ode field.
<ou can also use other buttons in the Performance Assistant dialog bo$ to
display information on the selected field. One of the most important pieces of
information, besides the lin+ to the conte$t)sensitive Application &elp, is the lin+
to the 'echnical Inormation. :hoose this to display detailed information, such
as the parameter #% assigned to the field. <ou can use parameters to set defaults
for fre*uently used input fieldsC to do this, the parameters are stored !ith the
desired values in the user master record.
'ote" <ou may need to activate the Performance Assistant first using the
menu &elp ./// Settings ./// 37 &elp.
*: 'elp
<ou can choose =2 to display possible input values. <ou can also call up the =2
help for a field using the button immediately to the right of the selected field. #f
a field contains a chec+mar+ symbol, you can only proceed to the ne$t step in
that application after entering a permitted value /re*uired entry0. <ou can use
transaction or screen variants, or :ustomizing to mar+ fields as mandatory or
optional, hidden or filled !ith hidden standard values.
(he =2 help displays a list of possible entries for a field. #f there are a large
number of possible entries, a separate selection screen is displayed. #f there is a
long hit list, the =2 help only displays as many entries as the user has specified on
the 34 &elp tab page under &elp ./// Settings. (he default value for the ma$imum
number of displayed hits is 3--. (a+e the time to familiarize yourself !ith the
other settings you can ma+e here.
4int" 5sers can also create personal values lists. An S&% employee !ho
is only responsible for 'unich, for e$ample, only !ants to see the 'unich
clients and defines a corresponding personal value list. Do!ever, despite
this, the employee still has the option at all times of s!itching to the total
vie! of all customers or of updating or completely deleting the values list.
SAP .i%rary (Online Documentation(
(he SAP $i(rary is a useful aid to getting to +no! system functions. #t allo!s
you to access the online documentation. (he information stored here does not
simply describe ho! to use system functions, it also e$plains system architecture
concepts, gives e$amples of ho! you can configure various processes, and !arns
you about possible user errors and their conse*uences. (he online documentation
also contains several tips and tric+s to help you carry out common tas+s more
easily and *uic+ly.
4int" <ou can also access the SAP Eibrary on the #nternet. :all
the address http",,help*sap*com* <ou can access the full product
documentation for different releases hereC a user)friendly full)te$t search
by solution is also available.
The System an$ 'elp ,enus
(he S,stem and &elp menus are al!ays available !ith the same options on every
screen in an SAP system.
(he S,stem menu allo!s you to access various system functions. (his menu also
contains functions that you can only access using this menu /and not in any other
!ay0. <ou can log off using S,stem ./// Log o, and display useful information
on your system and the function you are currently using, such as the transaction
code, by choosing S,stem ./// Status.
<ou can use the &elp menu to access the system documentation. <ou can also
display the Release 'otes and configure the standard settings for your =2 Delp.
Do!ever, you !ill mostly use the Delp menu to navigate to the specific section
of the documentation relevant for your current !or+ in the current conte$t. (he
conte$t)sensitive help is also called Application 4elp. (he tool for accessing the
documentation as a !hole is the SAP $i(rary.
Lesson 4
Principal Architecture of the SAP et!ea"er
Application Ser"er
/ntro$uction
SAP systems are used for mapping business processes or business applications.
(hese applications should be implemented independent of the hard!are
environment used /operating system, database0 to the greatest e$tent possible. (o
do so, SAP +et"ea%er provides t!o different runtime environments4 an ABAP
runtime environment /usage type AS ABAP0 and a ;ava runtime environment
/usage type AS $a%a0.0.
ABAP /Advanced Business Application Programming0 is a programming
language developed by SAP. 'any business applications of an SAP system are
!ritten in ABAP. ABAP has been optimized for developing highly)scalable
business applications. :ustomers can use the ABAP "or+bench for developing
completely ne! applications as !ell as enhancing and modifying SAP standard
applications. #n doing so, the entire, mighty infrastructure of the AS ABAP can
be used, !hich also supports the creation of the most comple$ applications by
large groups of developers. (he Application Server ABAP provides the runtime
environment for programs !ritten in ABAP.
SAP not only provides a runtime environment for ABAP programs but also
a runtime environment for 1ava programs. AS $a%a is an application server
according to the ;ava 1 Enterprise Edition /;1EE0 standard.
(he 1ava programming language !as first introduced by Sun 'icrosystems
#nc.. in ,JJ3. ;ava is an object)oriented and platform)independent programming
language that has spread across many areas. (he ;ava concept enables the
development of a large range of different application types ) from classical
applications to applets used in !ebsites to client8server applications.
1ava ; Platform Enterprise E!ition (1;EE) is a vendor standard for a !hole
range of soft!are components that are primarily created in the ;ava programming
language. Sun uses the ;1EE compatibility test to ensure that the specifications of
;ava 1 Enterprise Edition are reached.
(he purpose of this specification is to provide a generally accepted frame!or+ for
using modular components to develop distributed, multi)level applications. "ith
the ;1EE specification, Sun !ants to ensure that conform "eb applications run on
all ;1EE compatible servers. According to the ;1EE specification the application
logic is pac+aged in Enterprise 1avaBeans /E;B0. (hey represent ;ava program
components. A container implicitly provides the components !ith the services
of the runtime environment.
Client an$ Ser"er; Terminology De-nition
Before !e discuss various client8server configurations in the conte$t of SAP
systems, !e first need to define the concepts client and server. (here are basically
t!o !ays of doing this.
#n the har!/are6oriente! vie!, the term server means the central server in a
net!or+ that provides data, memory, and resources for the !or+stations /clients0.
#n the soft/are6oriente! vie!, client and server are both defined at the process
level /service0. A service in this conte$t is a service provided by a soft!are
component. (his soft!are component can consist of a process or a group of
processes /such as a SAP "eb Application Server0 and is then called a server for
that service. Soft!are components that use a service are called clients. At the
same time, clients can also be servers for other specific services.
(he follo!ing graphic clarifies the t!o approaches to the definitions.
#n the conte$t of SAP systems, the terms client and server are generally used as
defined in the soft!are)oriented vie!.
Client3Ser"er Con-guration for SAP Systems
(he follo!ing processes are often used for operating business application soft!are4
. Presentation processes /for e$ample, for displaying screens0
. Application processes /for e$ample, for e$ecuting application programs0
. %atabase processes /for e$ample, for managing and organizing database data0
"hen you are installing and configuring an SAP system, you need to decide ho!
you are going to distribute the re*uired processes among the available hard!are.
(here are various !ays of doing this, some of !hich are described in more detail
belo!. :onfigurations are either single)tier or multi)tier, depending on the number
of hard!are layers used /see the follo!ing graphic0. (he SAP ECC system is an
e$ample of business application soft!are.
. #n single)tier configurations, all processing tas+s /database, application and
presentation processes0 are performed by one computer. (his is classic
mainframe processing.
. (!o)tier configurations are usually implemented using special presentation
servers that are responsible solely for formatting the graphical interface.
. #n a three)tier configuration, each layer runs on its o!n hosts. 'any different
application servers can simultaneously !or+ !ith the data of a database
server.
Single)tier configurations are generally used for tests and demonstrations /for
e$ample, an SAP system on a laptop0. #f many users !ant to !or+ on a system
configured in this !ay, then the e$tra hard!are costs for each additional user
become greater than the costs associated !ith implementing additional hard!are
levels /for e$ample, moving the presentation processes to other hosts0.
(he t!o)tier configuration !ith distributed presentation processes /as sho!n in
the previous graphic0 can maintain good performance for a significantly higher
number of users, !ithout substantially increasing the hard!are costs. (he load
resulting from the presentation processes is distributed to the various front)end
computers and so does not influence the performance of the database host.
Do!ever, if the number of users e$ceeds a certain upper limit, the central host, on
!hich both application and database processes run, ris+s becoming a bottlenec+.
(o prevent this, you can improve the performance of the SAP system by
distributing the application)layer processes to several hosts. Another advantage of
adding a hard!are layer specifically for application processes is that it facilitates
scalability. #f the number of SAP users in a system increases over time, negatively
affecting system performance, then this problem can, in most cases, be solved
simply by adding another host for application processes.
An alternative t!o)tier configuration is to install po!erful des+top systems and
to use these for presentation and applications /t!o)tier client8server0. (hese
configurations are especially suited to applications !ith high processor demands
/for e$ample, simulations or for soft!are developers0, but are not implemented
in the SAP environment, other than for test purposes, due to the additional
administration re*uired.
#n the SAP Business Suite environment, more comple$ client8server configurations
consisting of more than three tiers are both theoretically possible and used in
practice. An additional level could be a !eb server, for e$ample.
The /nstance
An instance is an administrative unit that combines SAP system components
providing one or more services. (he services provided by an instance are started
or stopped together. <ou use a common instance profile to set parameters of
all the components of an instance. Each instance has its o!n buffer areas. An
instance runs on one physical computer, but there can be multiple instances on
one computer. An instance is identified by the system #% /S#%0 and the instance
num(er.
4int" (he terms /SAP0 instance and Application Server are often used
synonymously.
"hen you install an SAP system, you already have the option of separating the
processes at application level from those at database level. (his means that the
database for an SAP system can be installed and operated on a separate physical
computer, separated from the instances of the SAP system. (here is e$actly one
database for each SAP system. (he database usually has the same system #%
/%B #%0 as the SAP system.
(he central instance of the SAP system is distinguished by the fact that it offers
services that no other instance of the system offers. =or the AS ABAP, these are the
'essage Server and the En*ueue !or+ process /see belo!0. =or the AS ;ava you
can recognize the central instance by the Soft!are %eployment 'anager /S%'0.
(he central services instance provides central services of the AS ;ava, the
'essage Service and the En*ueue Service /see belo!0. =or the AS ABAP,
these services can also be moved to the ABAP central services instance for
high availability reasons. (hese AS ABAP systems therefore no longer have a
central instance.
All other instances of the system are typically called !ialog instances.
#f the central instance and the database /and for the AS ;ava also the central
services instance0 are installed on the same computer, this is referred to as a
central system.
Processes of the SAP et!ea"er Application Ser"er
(he SAP runtime system consists of a large number of parallel processes that !or+
together. Dere, you can distinguish bet!een the runtime environment for ABAP
/AS ABAP0 and the runtime environment for ;ava /AS ;ava0 .
AS A/AP Pro'esses
#n the AS ABAP, these processes on every application server include the
!ispatcher as !ell as a number of /ork processes depending on the hard!are
resources4
. (he!ispatcher distributes the re*uests to the !or+ processes.
. 0ialog /ork processes fulfill all re*uests for the e$ecution of dialog steps
triggered by an active user. Every dispatcher re*uires at least t!o dialog
!or+ processes.
. Spool /ork processes pass se*uential data flo!s on to printers. At least
one spool !or+ process is re*uired for each SAP system. #t is possible to
configure more than one spool !or+ process for each dispatcher.
. 3p!ate /ork processes e$ecute update re*uests. Similarly to spool !or+
processes, you need at least one update !or+ process per SAP system, and
you can configure more than one per dispatcher.
. Backgroun! /ork processes e$ecute programs that run !ithout interacting
!ith the user. <ou need at least t!o bac+ground !or+ processes for each
SAP system. <ou can configure more than one bac+ground !or+ process
for each dispatcher.
. (heen<ueue /ork process administers the loc+ table in the shared memory.
(he loc+ table contains the logical database loc+s of the ABAP runtime
environment of the SAP system. Only one en*ueue !or+ process is needed
for each system.
(o summarize, the dispatcher of an ABAP instance manages different types of
!or+ processes4 dialog, update, bac+ground, en*ueue and spool !or+ processes.
(hese !or+ processes !or+ on different tas+s !hen e$ecuting the business
procedures in the SAP system.
(he administrator of an SAP system can use profile parameters to configure the
number of different !or+ processes.
#n addition to the !or+ processes, the ABAP runtime system provides additional
services /these are not !or+ processes0 for internal and e$ternal communication4
. (he#essage Server /'S0 handles communication bet!een the distributed
dispatchers !ithin the AS ABAP, thereby enabling scalability of several
parallel application servers. (he message server is configured only once
per SAP system.
. (hegate/ay reader /B"0 enables communication bet!een SAP systems,
or bet!een SAP systems and e$ternal application systems. (here is one
per dispatcher.
. (he%nternet Communication #anager /#:'0 enables the communication
!ith the SAP system using !eb protocols such as D((P. (he #:' receives
re*uests from the client and for!ards them to the SAP system for processing.
#n an ABAPF;ava system /see belo!0, it recognizes !hether the re*uest is a
call for the AS ABAP or the AS ;ava and for!ards the re*uest accordingly.
#t can also direct D((P re*uests from an SAP system to a "eb server and
send the response bac+ to the SAP system. <ou can configure a ma$imum of
one #:' process per application server /soft!are)based vie!0.
AS <a"a Processes
(he follo!ing processes e$ist in AS 1ava4
. (he!ispatcher distributes incoming re*uests to the server processes.
. (heserver process e$ecutes the ;ava applications. Every server process is
multi)threaded and can thus process a large number of re*uests in parallel /in
contrast to the ABAP !or+ processes0. =or each dispatcher there is at least
one server processes and there can be up to ,7 server processes.
. (he ;ava message service manages a list of ;ava dispatchers and server
processes. #t is responsible for the communication !ithin the ;ava runtime
environment.
. (he ;ava en<ueue service manages logical loc+s that are set by the e$ecuted
;ava application program in a server process.
. (heSoft/are 0eployment #anager /S%'0 is the standard tool used to
install ;ava soft!are components on the SAP "eb AS ;ava.
Types of SAP et!ea"er AS
%epending on the application or product used, different types of application server
are installed.
. AS ABAP system" :omplete infrastructure in !hich ABAP)based
applications can be developed and used.
. AS 1ava system" :omplete infrastructure for developing and using
;1EE)based applications.
. AS ABAP21ava system" :omplete infrastructure in !hich ABAP)based
and ;1EE)based applications can be developed and used. Such a system
should only be installed if e$plicitly re*uired by the application. =or
e$ample, SAP 6et"eaver P# ?.- or SAP Solution 'anager 2.-
One of the main characteristics of the SAP 6et"eaver AS is that ABAP tables,
programs and application data is stored in the ABAP schema of the database !hile
;ava data is stored in the ;ava schema. Dere, the ABAP runtime environment
can access the ABAP schema of the database, and the ;ava runtime environment
can access the ;ava schema. #n the ABAPF;ava system, the different runtime
environments communicate directly via the SAP ;ava :onnector /;:o0.
AS ABAP Architecture
#n AS ABAP, the central instance is distinguished by the fact that the message
server and the en*ueue !or+ process run there. All other instances of the system
are usually called dialog instances. Alternatively, the instances are also named
after the services provided.
(he services that an application server can provide are determined by the type of
!or+ processes it has. An application server can then ta+e on several roles, for
e$ample, as a dialog server and simultaneously as an update server, if it provides
several dialog !or+ processes and at least one update !or+ process.
'ote" An overvie! of the AS ABAP instances is available in S'3, /in
SAP Easy Access under 'ools ./// Administration ./// (onitor ./// S,stem
(onitoring./// Ser%ers.
<ou can use the transaction S'3- to display an overvie! of the !or+
processes on the instance that you are logged on toC you can also display
this overvie! by choosing 'ools ./// Administration ./// (onitor ./// S,stem
(onitoring ./// Process 0%er%ie# on the SAP Easy Access screen.
(he ABAP message server provides the AS ABAP !ith a central message
service for internal communication /for e$ample, for starting updates, re*uesting
and removing loc+s, triggering bac+ground re*uests0. (he message server also
provides information on !hich instances of the system are currently available.
(he ABAP dispatchers of the individual application servers communicate via the
ABAP message server, !hich is installed e$actly once per SAP system.
"hen you log on to the AS ABAP using the SAP B5# for "indo!s or the SAP
B5# for ;ava using logon groups, the message server performs a load distribution
of users to the available instances. (his load distribution, !hich ta+es place
during the logon procedure, is also +no!n as logon load balancing. After the load
distribution by the message server, the SAP B5# communicates directly !ith the
dispatcher. (he user remains logged on to this instance until he logs off again.
'ote" An overvie! of users !ho are logged on the the instance to !hich
you are also logged on, is available using transaction S'-2 /'ools.
Administration ./// (onitor./// S,stem (onitoring./// User 0%er%ie#0.
<ou can see to !hich instance you are logged on under S,stem ./// Status.
#f you are accessing the AB ABAP via !eb protocols such as D((P using the
bro!ser, the #nternet :ommunication 'anager /#:'0 receives the re*uest. (his
for!ards the re*uest to the dispatcher of its instance.
:ommunication from other SAP systems via emote =unction :all /=:0 is
accepted by the Bate!ay eader /B"0.
AS <a"a Architecture
#n AS ;ava, the central instance is distinguished by the fact that the Soft!are
%eployment 'anager /S%'0 runs there. (he central services 'essage Service
/'S0 and En*ueue Service /ES0 run in the central services instance /:S instance0.
All other instances of the system are usually called dialog instances.
'ote" (he entirety of the ;ava environment /all processes and the database
scheme0 is also referred to a 1ava cluster, and the individual processes
/dispatcher and server0 as no!es of the ;ava cluster.
<ou can get an overvie! of started ;ava processes /;ava dispatcher and
;ava server processes as !ell as S%'0 via the s,stem inormation of
the ;ava runtime environment //http488ODostnameP4O;ava)%ispatcher)
D((P)Port of the #nstanceP8sap8monitoring8System#nfo, for e$ample
http488t!df,1.2.!df.sap.corp43---- ./// S,stem Inormation0
Analogous to the AS ABAP, the message service of the AS ;ava provides a central
message service for internal communication. (he ;ava message service also
provides the information !hich instances and nodes of the AS ;ava are available.
Each node of the ;ava cluster can communicate directly !ith the message service.
#n the AS ;ava, the en*ueue service holds logical loc+s. Each node of the ;ava
cluster can communicate directly !ith the en*ueue service.
"hen the AS ;ava is accessed using a bro!ser, the ;ava dispatcher receives
re*uests, !hich are then processed by the server processes.
AS ABAP4<a"a Architecture
=or the AS ABAPF;ava /meaning ABAP and ;ava processes in the same SAP
system, under the same system #%0, the same architectural principles apply as for
separate AS ABAP and AS ;ava systems. Do!ever, there are some particularities
because both runtime environments are integrated !ith each other in this case.
'ote" (he AS ABAPF;ava is often called .add)in installation. because
it is possible to install an AS ABAP first and then supplement it !ith
the AS ;ava at a later point in time.
(he central instance of an AS ABAPF;ava system can be recognized by the
follo!ing processes4 ABAP)'S, en*ueue !or+ process and S%'. (he central
services of the ;ava runtime environment /;ava)'S, ;ava)ES0 are also provided
in the ;ava central services instance here. All other instances are usually called
dialog instances.
Since both runtime environments are capable of ans!ering re*uests via !eb
protocols, the #nternet :ommunication 'anager must no! decide !hether the
re*uest is addressed to the ABAP or the ;ava runtime environment. #t decides this
by means of the 5E of the re*uest. #n case of a re*uest to the ABAP runtime
environment, for e$ample, the call of an ABAP !eb dynpro, the #:' for!ards the
re*uest to the ABAP dispatcher and the !or+ processes respond to the re*uest. #f
the re*uest is a re*uest for the ;ava runtime environment, for e$ample, the call of a
;ava Server Page /;SP0, the #:' for!ards the re*uest to the ;ava dispatcher and
one of the server processes responds to the re*uest.
#n an AS ABAPF;ava system, data is also +ept in separate database schemas /but
in the same database installation0. (hat is, !or+ processes can only access ABAP
data and server processes can only access ;ava data. #n the data e$change, both
runtime environments then communicate using the SAP 1ava Connector /;:o0.
(his communication is necessary, for e$ample, if billing data that is stored in the
ABAP data schema is supposed to be displayed in a ;ava user interface.
(he SAP ;:o is integrated into the AS ;ava and is also used !hen an AS ;ava
system has to communicate !ith a remote AS ABAP system.
AS ABAP Processes
Processing of &e2uests in AS ABAP
(he users can log on to the SAP system using either the SAP B5# or a "eb client
/bro!ser0. "hen logging on via the SAP B5#, user re*uests are processed by the
ABAP runtime environment, !hen logging on via a bro!ser, processing can be
done by the ABAP or the ;AIA runtime environment, depending on the re*uest.
Processing &e2uests %y the SAP 1+/
5sers logon via the /ABAP0 message server /load balancing0 or they logon
directly on the ABAP dispatcher, the !or+ processes e$ecute the user re*uests.
(he processing of a user re*uest in AS ABAP, as outlined in the graphic, involves
different processes on all three layers /presentation, application and database
layer04
(he screen entries of a user are accepted by the SAP presentation program
SAP G3% /SAP Braphical 5ser #nterface0, converted to an internal format and
for!arded to AS ABAP.
(he /ABAP0 !ispatcher is the central process of AS ABAP. #t manages the
resources for the applications !ritten in ABAP in coordination !ith the respective
operating system. (he main tas+s of the ABAP dispatcher include the !istri(ution
of the re<uests to *its* /ork processes, the integration of the presentation layer
and the organization of communication transactions.
(he dispatcher first saves the processing re*uests in re*uest *ueues and then
processes them according to the .first in, first out. principle.
(he ABAP dispatcher distributes the re*uests one after the other to the available
!or+ processes. %ata is actually processed in the /ork process, !hereby the user
!ho created the re*uest using the SAP B5# is not al!ays assigned the same !or+
process. (here is no fixe! assignment of !or+ processes to users. (o process
user re*uests it is often necessary to read data from the ABAP schema of the
!ata(ase or to !rite to it. =or this, every !or+ process is connected !irectly to
the ABAP schema of the !ata(ase.
Once the process is complete, the result from the !or+ process is sent via
dispatcher bac+ to the SAP B5#. (he SAP B5# interprets this data and generates
the output screen for the user.
(he (uffers help to speed up processing of user re*uests. %ata that is often read
but seldom changed /for e$ample, programs or :ustomizing data such as clients,
currencies or company codes0 can be +ept as a copy of the database content in the
shared memory of the application server. (his means that the data does not have to
be read from the database every time it is needed, but can be called very *uic+ly
from the buffer. Each instance has its o!n buffers.
"or+ processes e$ecute the process logic of application programs. #n addition to
internal memory, a !or+ process has a task han!ler that coordinates the actions
!ithin a !or+ process, soft!are processors and a !ata(ase interface. (he
!ynpro processor e$ecutes the screen flo! logic of the application program, calls
processing logic modules, and transfers field content to the processing logic. (he
actual processing logic of ABAP application programs is e$ecuted by the ABAP
interpreter. (he screen processor tells the ABAP processor !hich subprogram
needs to be e$ecuted, depending on the processing status of the screen flo! logic.
(he dialog !or+ process selected by the dispatcher, performs a roll)in of the user
conte$t first. (hat is, the data that contains the current processing status of a
running program as !ell as data that characterizes the user is made +no!n to
the !or+ process. (he !or+ process then processes the user re*uest, !hich may
involve, for e$ample, re*uesting data from the database or from the buffers in the
shared memory. Once the dialog !or+ process has processed the dialog step,
the !or+ process returns the result, rolls the user conte$t bac+ out to the shared
memory, and is no! available again for a ne! user re*uest from the re*uest *ueue.
(he result is transferred to the SAP B5# and the user sees the ne! screen.
elational %atabase 'anagement Systems /%B'S0 are generally used to
manage large sets of data. An %B'S saves data and relationships bet!een
data in the form of t!o)dimensional tables. (hese are +no!n for their logical
simplicity. %ata, tables, and table relationships are defined at database level in the
database catalog /the data dictionary0 of the %B'S.
"ithin the SAP programming language ABAP, you can use ABAP Open S>E
/S>E A Structured >uery Eanguage, database *uery language0 to access the
application data in the database, regardless of the %B'S used. (he database
Data%ase /nterface of AS ABAP
interface, !hich is part of every !or+ process of AS ABAP, translates Open
S>E statements from ABAP into the corresponding S>E statements for the
specific database used /6ative S>E0. (his allo!s ABAP programs to be
!ata(ase6in!epen!ent.
'ote" ABAP Open S>E is a database *uery language based on the /#SO0
S>E standard that also contains enhancements that are not included in
the standard.
"hen interpreting Open S>E statements, the SAP database interface chec+s the
synta$ of these statements and ensures the optimal utilization of the local SAP
buffers in the shared memory of the application server. %ata that is fre*uently
re*uired by the applications is stored in these buffers so that the system does not
have to access the database server to read this data. #n particular, all technical data,
such as ABAP programs, screens, and ABAP %ictionary information, as !ell as a
number of business administration parameters, usually remain unchanged in an
operational system and are therefore ideally suited to buffering.
=urthermore, native S>E commands can be used directly in ABAP, that is,
!ithout using the local buffers and !ithout the database interface interpreting the
commands. <ou can do this by including the commands in an E9EC S:L; ) E+D
E9EC; brac+et in the ABAP program. (he ABAP #nterpreter does not chec+ the
synta$ of any commands !ithin this brac+et. #f you use native S>E, you can no
longer maintain the platform independence of the affected programs.
Processing Dialog &e2uests
(he e$ecution of dialog re*uests is characterized by the follo!ing 4
. A program dialog step is assigned to one specific dialog !or+ process during
e$ecution.
. (he individual dialog steps for a program consisting of several screens can
be e$ecuted by different dialog !or+ processes during program runtime.
(his is called /ork process multiplexing.
. A dialog !or+ process se*uentially processes dialog steps for various users
and programs.
(his is illustrated by the follo!ing figure.
SAP application programs differentiate bet!een user interaction and processing
logic. (he user actions are technically realized using screens, also called !ynpros
/from dynamic programs0, !hich consist of a screen image and the underlying
flo! logic. (he dynpro processor of the !or+ process e$ecutes the screen flo!
logic of the application program, calls processing logic modules, and transfers
field content to the processing logic. (he screen flo! logic itself is further divided
into PB7 /Process Before Output0, !hich is processed before the screen image is
sent, and PA% /Process After #nput0, !hich is processed after a user interaction on
the screen. (he PA# part of a dialog step logically belongs to the preceding screen
image, !hile the PBO part logically belongs to the subse*uent screen image. (he
actual processing logic of ABAP programs is e$ecuted by the ABAP interpreter.
(he screen processor tells the ABAP processor !hich subprogram needs to be
e$ecuted, depending on the processing status of the screen flo! logic.
#f, during a dialog step, data needs to be e$changed !ith the database or the
buffers, then this e$change ta+es place through the database interface, !hich
enables access to database tables, ABAP programs or the ABAP %ictionary
among other things.
Transactional Processing in AS ABAP
The Term Transaction
(ransactions are processing units, that functionally belong together. (hey have
four principal characteristics. (he initial letters of these characteristics together
form the acronym AC%0 .
. Atomic
. :onsistent
. #solated
. %urable
Atomic means that a transaction is either fully successful or does not have any
effects at all. #f a transaction)oriented system goes do!n, you need to ensure that
inconsistent, partial results are not stored.
Consistent means that the system status changes from one that is accurate and
consistent in business terms to another that is also accurate and consistent in
business terms.
%solate! means that the changes made !ithin a transaction can only be seen by
other transactions, even those that run simultaneously, after the final confirmation
/.:ommit.0.
(he results of a transaction are !ura(le because after the final confirmation they
are stored permanently in the database.
Data%ase Transactions an$ ABAP Transactions
Every !or+ process is connected to a specific communication partner at database
level for the duration of an SAP instanceHs runtime. "or+ processes cannot
e$change communication partners at runtime. (his is !hy a !or+ process can only
ma+e changes to the database !ithin one database transaction.
A database transaction is, in accordance !ith the A:#% principle, a non)divisible
se*uence of database operations, at the beginning and end of !hich the dataset on
the database must be consistent. (he beginning and end of a database transaction
are defined by a commit command /.database commit.0 to the database system.
%uring a database transaction /bet!een t!o commit commands0, the database
system itself ensures that the dataset is consistent. (he database system itself ta+es
on the tas+ of restoring the dataset to its previous state after a transaction has
terminated !ith an error /.rollbac+.0.
Business transactions are processing units grouped to provide a specific functionC
these processing units e$ecute changes to the database that are consistent and
ma+e sense in business terms. (ypical e$amples are credit and debit updates,
!hich only ma+e sense together, or creating an order and reserving the relevant
materials. :orrespondingly, an AS ABAP transaction is defined as a non)divisible
business process that must either be e$ecuted completely or not at all. AS ABAP
transactions are implemented as se*uences of logically related dialog steps that
are consistent in business terms. Every user dialog step is represented by one
screen image.
SAP transactions are not necessarily e$ecuted !ithin one single dialog !or+
process. "ithin a transaction that changes data on the database, the user
re*uests database changes using the displayed individual screens. Once the
transaction is complete, the changes must result in a consistent database status.
(he individual dialog steps can be processed by different !or+ processes /!or+
process multiple$ing0, and each !or+ process se*uentially handles dialog steps for
unrelated applications. Applications !hose dialog steps are e$ecuted by the same
!or+ process one after the other cannot run !ithin the same database transaction
if they are not related to each other. (herefore, a !or+ process must start a ne/
database transaction for each dialog step.
(he relationship bet!een database transactions and SAP transactions is illustrated
in the graphic .elationship bet!een database transactions and SAP transactions..
.oc0 ,anagement
(o ensure data consistency !ithin an SAP system, you must ensure that data
records cannot be accessed and changed by more than one user at any one time.
(o do this, the SAP system has its o!n loc+ management concept.
=rom a database perspective, every dialog step forms a physical and logical unit4
the !ata(ase transaction.. (he database loc+ administration can only coordinate
this type of database transaction. =rom an SAP point of vie!, ho!ever, this is
not sufficient, because SAP transactions, !hich are formed from a se*uence of
logically related !or+ steps that are consistent in business terms, are generally
made up of several dialog steps. SAP systems need to have their o!n lock
management. (his is implemented using the en*ueue !or+ process. (his also
ensures that the platform)independence of the loc+ management is maintained.
(he SAP loc+ concept !or+s on the principle that SAP programs ma+e loc+
entries for data records to be processed in a lock ta(le. Eoc+ entries can only be
made if none already e$ist for the table entries to be loc+ed.
(he en<ueue /ork process manages the logical loc+ of the SAP transactions in
the lock ta(le. (he loc+ table is located in the main memory of the instance
!ith the en*ueue !or+ process.
'ote" (he instance !hose main memory contains the loc+ table is also
+no!n as the en*ueue server.
#f a user !ants change access to data, the e$ecuting dialog !or+ process re*uests a
loc+ /to do so, the application developer must program this re*uest e$plicitly0.
#f a dialog re*uest is processed on the en*ueue server, the dialog !or+ process can
access the loc+ table directly. #t no! chec+s !hether a ne! loc+ can be generatedC
that is, !hether there is a collision !ith loc+s that have already been set. #f a loc+
can be set, the dialog !or+ process creates it and the user /loc+ o!ner0 is given the
loc+ +ey. (he loc+ +ey is +ept in the user conte$t in the shared memory.
#f the dialog !or+ process that processes the user re*uest and the en*ueue
!or+ process are not running on the same instance, these t!o !or+ processes
communicate through the message server. #n this case, the loc+ re*uest is
for!arded from the dialog !or+ process to the en*ueue !or+ process via the
dispatchers and the message server. (he en*ueue !or+ process no! chec+s
!hether a loc+ can be set. #f this is possible, the loc+ is set by the en*ueue !or+
process and the loc+ +ey transferred to the re*uesting dialog !or+ process via
dispatcher and message server.
"hen the loc+ is re*uested, the system chec+s !hether the re*uested loc+
conflicts !ith e$isting entries in the loc+ table. #f the loc+ table already contains
corresponding entries, the loc+ re*uest is refused. (he application program can
then inform the user that the re*uested operation cannot currently be e$ecuted.
(he application developer can choose bet!een different loc+ modes4
. "rite loc+s /loc+ mode E$clusive0C the loc+ data can be edited only by
one user. (he re*uests for another !rite loc+ and another read loc+ are
rejected. A !rite loc+ protects the loc+ed objects against all types of other
transactions. Only the same loc+ o!ner can set the loc+ again /cumulate0.
. ead loc+s /loc+ mode Shared0C several users can have read access to the
loc+ed data at the same time. (he re*uests for additional read loc+s are
accepted, even if they are from other users. A !rite loc+ is rejected.
. Enhanced !rite loc+s /loc+ mode e:clusive noncumulative0C !hile !rite
loc+s can be successively re*uested and released by the same transaction,
an enhanced !rite loc+ can only be re*uested once, even by the same
transaction. All other re*uests for loc+s are rejected.
. Optimistic loc+s /loc+ mode 7ptimistic0C optimistic loc+s respond li+e read
loc+ at first and can be changed to !rite loc+s. An optimistic loc+ is set if the
user displays the data in change mode. Optimistic loc+s on the same object
do not collide. #f the user !ants to save the /changed0 data, the optimistic
loc+ must be changed to a !rite loc+ /mode E0. /(his fails if someone set
a non)optimistic loc+ on the object before.0 Other optimistic loc+s on the
object are deleted in the process.
Eoc+s set by an application program are either released by the application program
itself or by the update program once the database has been changed. Eoc+s that
have been passed on to an update !or+ process in this !ay are also !ritten to a
file at operating system level and can therefore be restored if the en*ueue server
goes do!n.
(ransaction S',1 /'ools ./// Administration ./// (onitor./// Lock Entries0 displays
the loc+s that are currently set. #f a loc+ has already been inherited to the update
process, the backup lag has also been set. Such a loc+ !ill also be included in the
loc+ table again after restarting the en*ueue server.
(here are basically t!o !ays of deleting loc+s held by users4
. Ending the user session in the user overvie! /transaction S'-2 or 'ools .
Administration ./// (onitor ./// S,stem (onitoring ./// User 0%er%ie#0
. 'anually deleting the loc+ entries in S',1
(he first method /ending the user session0 also results in the original loc+ o!ner
leaving the transaction and thereby releasing all loc+s heldC the second method
/manually deleting using S',10 merely deletes the loc+ entry from the loc+
table. (his theoretically enables several users to change the same data records
simultaneously.
Caution" Before deleting loc+s, the system administrator must first
chec+ ) susing transaction S'-2 ) !hether the user !ho o!ns the loc+
is still logged on to the system. <ou should only delete loc+ entries !ith
transaction S',1 if the loc+ o!ner is no longer logged on to the system
but still o!ns the loc+ /for e$ample, if the connection bet!een SAP B5#
and the SAP system has been bro+en because the user has s!itched off his
or her front)end computer !ithout logging off from the system0.
Stan$alone )n2ueue Ser"er 3 ABAP Central Ser"ices
=or reasons of high availability, the en*ueue !or+ process together !ith the
ABAP message server can also be detached from the central instance and installed
as an ABAP central services instance /AS:S0. =or more details, please refer to
the SAP 6et"eaver Eibrary4 SAP +et"ea%er b, <e, Capabilit,./// Application
Platorm b, <e, Capabilit, ./// ABAP 'echnolog,./// Client=Ser%er 'echnolog, .
'he SAP Lock Concept )BC-CS'-E:* ./// Standalone En>ueue Ser%er
+p$ate
#n the SAP system, a business process is mapped using an SAP transaction that
can contain several screen changes /for e$ample, the creation of an order0. %ata
changes effected by this process are supposed to be e$ecuted completely or not at
all in the database. #f the operation is terminated during the transaction or an error
occurs, the transaction is not supposed to ma+e any database changes at all. (he
SAP update system, !hich is described belo!, ta+es care of this.
(he update system also offers increased security, performance and restorability
in the e$ecution of database changes.
(he updating system is a technology !hich allo!s SAP transactions to off)load
time)intensive database changes. (hese are then carried out asynchronously
in special up!ate /ork processes. #t also circumvents the roll)bac+ problems
caused by the difference in the conception of the logical unit of !or+ /E5"0 in an
SAP transaction and in the database.
#f, during a dialog !or+ process, data temporarily stored for processing is passed
to an update !or+ process for further processing, the dialog !or+ process does
not !ait for the update re*uest to be completed4 the update is asynchronous /not
simultaneous0. (he asynchronous update process is illustrated in the graphic .(he
Principle of Asynchronous 5pdates..
(he dialog part is completed !ith the ABAP command C0((I' "0R<C the
update part of the transaction starts4 the update server transfers the update re*uest
to an update !or+ process. Dere, each dialog step corresponds to a database
transaction /!hich is e$ecuted either completely or not at all in the database
and there completed !ith a C0((I' command0. (he update part of the SAP
transaction is e$ecuted in a database transaction. #t is only then that the data is
copied to the application tables.
#f users !ant to change a data record in an SAP transaction, they call the
corresponding transaction in the dialog, ma+e the appropriate entries on the
screens and then initiate the update process by saving the data. (his process
triggers the follo!ing steps4
,. (he program loc+s the data record for other users. (he program does
this by addressing the en*ueue !or+ process /using the message server if
appropriate0. (he en*ueue !or+ process ma+es the relevant entry in the loc+
table or /if another user has already loc+ed the data0 informs the user that the
data record cannot currently be changed.
1. #f the en*ueue !or+ process succeeded in !riting the loc+ entry to the loc+
table, it passes the loc+ +ey it created to the user, the program reads the
record to be changed from the database and the user can change the record
on the screen image of the SAP transaction.
.. #n the active dialog !or+ process, the program calls a function module using
CALL 3U+C'I0+ ;;; I+ UPDA'E 'AS< and !rites the change re*uest
to database update tables. (hese are also called IBQ tables, because their
names begin !ith .IB.. (hey act as temporary memory and store the data
to be changed until it can be collected and !ritten to the application tables
in the database /in a single database transaction0.
2. At the end of the dialog part of the transaction /for e$ample, !hen the user
saves the data . possibly after completing other dialog steps0, the program
initiates the close of the transaction !ith the C0((I' "0R< statement.
(he !or+ process that is handling the active dialog step completes the update
header and triggers an update !or+ process.
3. Based on the information /+ey of the update order, loc+ +ey0 transferred from
the dialog !or+ process, the update !or+ process reads the log records that
belong to this SAP transaction from the IBQ tables.
7. (he update !or+ process transfers the changes mar+ed and collected in the
IBQ tables to the database as a change re*uest and evaluates the database
response. #f the changes !ere successfully !ritten to the target tables, the
update !or+ process triggers a database commit after the last change to the
database and deletes the entries from the IBQ tables. #f an error occurs, the
update !or+ process triggers a database rollbac+, leaves the log records in
the IBQ tables and mar+s them as defective.
?. (he loc+ entries in the loc+ table are reset.
'ote" (he application developer decides !hether and ho! to use
asynchronous updates !hile programming the transaction. Besides
the asynchronous update, there are some other update techni*ues /for
e$ample, synchronous or local0.
(o increase performance further, application developers can configure
different types of updates4
. time)critical, primary =8 up!ates. (hey are relevant to objects that
have a controlling function in the SAP system, such as a change to
the material stoc+ or an order creation.
. non)time)critical, secondary =; up!ates that depend on the I,
updates. (hese are, for e$ample, purely statistical updates such as
the calculation of results.
. non)time)critical updates that are collected and processed at a later
point in time /collective run0.
(he I, modules for an SAP transaction are processed se*uentially in a
single update !or+ process. #f your SAP system has a !or+ process for
I1 updates /type 5P10, then I1 modules !ill only be updated there.
Once it has successfully completed processing, the I, update !or+
process releases the relevant loc+s again. (his means that the .normal.
update !or+ processes are available again more *uic+ly for time)critical
I, updates, and that the relevant loc+ entries are deleted sooner. #f you
have not configured any I1 update !or+ processes, then the I, !or+
process handles all updates.
#n the collective run, the modules are not updated automatically but only
!hen a special report /report RS(7?@@A0 triggers the update. All calls of
the function modules are then collected, aggregated and updated at once.
#n doing so they are handled li+e I1 update modules.
#f an error occurs during an update, then processing of the active update
component terminates. 5sers can be notified automatically by e$press mail !hen
an update terminates.
#f a dialog !or+ process terminates !hilst !riting data to the IBQ tables, the tables
!ill contain data that !ill not be updated. (hese entries can be automatically
deleted the ne$t time you start the system or they can be deleted manually. (he
application tables remain unchanged.
An asynchronous update may terminate for a variety of reasons. #f, for e$ample,
several attempts are made to enter the same data record /using insert0 in a table,
this triggers the e$ception condition .%uplicate Ley. in the coding because an
entry already e$ists in the table under this +ey. (herefore, the corresponding data
record cannot be !ritten to the database table more than once.
"hen an update terminates, the system sends an e$press mail to the user !ho
triggered the update. Any additional steps must be carried out by the system
administrator. (ransaction S',. /update re*uests0 provides system administrators
!ith analysis tools to handle terminated updates. Once the error that caused the
termination has been corrected /for e$ample, hard!are damage repaired0, the
end user should restart the processing.
Printing
SAP systems provide a !ide variety of options for representing business and other
data. (his data, created and formatted in a dialog step, can then be sent to printers
and other output interfaces /fa$, e)mail, and so on0. A printer must first be set up
in the system before it can be addressed.
<ou can select a printer that has already been set up by choosing the print icon
)Ctrl 2 P*, then using the =2 help. A standard printer is usually set as default in
your user profile.
Once a printer has been set up, the SAP system has all the information it needs to
be able to create a spool re*uest.
A spool re<uest contains information on the data to be output, its formatting,
and the printer model used. (he spool re*uest generated is stored in the 5emSe
/temporary se*uential file0.
4int" Spool re*uests can be created by dialog !or+ processes or by
bac+ground !or+ processes. Spool !or+ processes do not create spool
re*uests.
As you can see from the graphic Spool processing in an SAP system, a spool
!or+ process formats the data specified in the spool re*uest and creates an output
re<uest. (he output re*uest contains all data in an appropriate format for the
printer. (his data can either be passed on to an appropriate operating system spool
process locally /on the same computer0 or remotely /over a net!or+ connection0.
'ote" #n an SAP system, the connection bet!een a spool !or+ process
and the operating system spool process is +no!n as the access metho!.
(here are more access methods than displayed above. (hese are the t!o
most commonly used access methods for connecting printers to SAP
systems. #n this conte$t, remote or local do not refer to the physical
location of the output but to the place !here the spool !or+ process is
.connected. to the operation system spool process.
=or print processing, the best performance is achieved by sending the data to be
printed to the operating system as soon as possible. <ou do this using the local
access method. (he operating system then performs all remaining tas+s, such as
*ueuing and data transfer to the selected printer.
4int" One minor but indispensable re*uirement for printing from SAP
systems is that each selectable printer allo!s printing at operating system
level.
<ou can display your o!n spool and output re*uests via S,stem ./// 0#n Spool
Re>uests /transaction SP-10.
Iia S,stem ./// User Proile./// 0#n Data /transaction code S5.0 you can specify
personal settings for printing on the Deaults tab page in the Spool Control section.
Bac0groun$ Processing
SAP bac+ground processing is a method for automating routine tas+s and
for optimizing the use of your organization.s SAP computing resources. #n
bac+ground processing, you instruct the 8. System to run programs for you. <ou
can use bac+ground processing to e$ecute long)running or resource intensive
programs at off pea+ times. <ou can use it to assign the system the tas+ to e$ecute
reports and programs. (here is no strain on your dialog resources and reports
running in the bac+ground are not subject to the runtime restrictions of dialog
processing /termination of the program after a runtime of ten minutes0.
(he segregation of bac+ground processing to special !or+ processes gives you
an additional dimension for separating bac+ground processing and interactive
!or+. 6ormally, bac+ground processing and interactive !or+ in the system ta+e
place at different times. =or e$ample, the system is used interactively during the
day and bac+ground processing ta+es place at night. <ou can use (ackgroun!
/ork processes to separate bac+ground processing and interactive !or+ also
by servers because bac+ground jobs are only e$ecuted on servers that offer
bac+ground processing.
Figure 1": S'he,uling /a'2groun, 3as2s 45o!s6
(he end user can usually schedule the program to be started in the bac+ground
as a >o( from the application transaction. (he job then .!aits. for the planned
e$ecution time in the job scheduling table. #f the time has come and free
bac+ground !or+ processes are available, the job is distributed to a bac+ground
!or+ process by the bac+ground scheduler and then e$ecuted. 5sers can display
the result in the application transaction or, in case of list generating programs, loo+
at the spool re*uest belonging to the job /see Printing section0. (o display your
o!n jobs, choose S,stem ./// 0#n $obs /transaction code S'90.
(he system administration and the !or+ preparation have access to a tool for
scheduling different types of bac+ground ta+es !ith transaction S'.7 /'ools .
CC(S ./// Background Processing./// Deine $obs0. (he system)!ide monitoring
of jobs ta+es place !ith transaction S(?B /'ools ./// CC(S ./// Background
Processing./// $obs - 0%er%ie# and Administration0.
=or cross)system scheduling and monitoring of bac+ground tas+s, you can use
SAP :entral Process Scheduling /SAP :PS0 and other licensed partner products.
Communication "ia the 1ateway
Each instance of an AB ABAP system contains a gate!ay. (his is used for the
communication bet!een !or+ processes of different instances or SAP systems as
!ell as !or+ processes and e$ternal programs. (he gate/ay rea!er /usually just
called gate!ay0 is the main process of the gate!ay system. (he dispatcher starts
it and chec+s it periodically.
Figure 16: 7atewa Communi'ation
#n the communication bet!een instances of a system or systems using remote
function call /=:0 or :P#:, the gate!ay is al!ays involved. #f a dialog !or+
process has to establish an =: connection to a remote system in the conte$t of
a re*uest, for e$ample, to fetch customer data, it uses the gate!ay, !hich then
ta+es care of the communication !ith the remote system. (he gate!ay for!ards
the re*uest to the gate!ay of the remote system. (he remote gate!ay transfers
the re*uest to the dispatcher. (his in turn for!ards the re*uest to one of its !or+
processes, !hich then communicates directly !ith .its. gate!ay.
#nbound =: connection are therefore al!ays received by the gate!ay. Outbound
connections are initiated by the !or+ process.
Processing !e% &e2uests
"eb re*uests are received by the %nternet Communication #anager /#:'0.
(hese D((P/S0 re*uests can be processed either in the ABAP !or+ process /for
e$ample, ABAP !eb dynpro applications0 or for!arded to AS ;ava in an AS
ABAPF;ava system /for e$ample, ;ava !eb dynpro applications0. (he #:' can
use the 5E to decide to !here it for!ards the re*uest /if it cannot reply to the
re*uest from its cache0.
Figure 17: Pro'essing a +e! Re8uest
#f the re*uest is to the ;ava runtime environment, it is sent to the ;ava dispatcher
/1b0, !hich then for!ards it to a ;ava server process /.b0. (he ;ava server
process then refers to the databaseHs ;ava schema, if applicable, and uses the ;ava
dispatcher process to send the response bac+ to the #:'. =inally, the #:' sends
the response from the SAP system to the user !ho sent the re*uest /30.
#f the re*uest is to the ABAP runtime environment, the #:' for!ards it to the
ABAP dispatcher /1a0, !hich then handles it li+e a typical SAP B5# re*uest /see
previous section0. (he !or+ process that processes the en*uiry no! communicates
directly !ith the #:' /2a0. (he #:' returns the response to the user !ho sent
the re*uest /30.
AS <a"a Processes
Processing of &e2uests in AS <a"a
(he processing of a user re*uest in AS ;ava, as outlined in the graphic, involves
different processes on all three layers /presentation, application and database
layer04
A !eb bro!ser is the standard user interface for AS ;ava. A user re*uest for
AS ;ava is usually an D((P re*uest that is received by the 1ava !ispatcher.
(he dispatcher for!ards the processing re*uests to one of the server processes
of .its. instance.
(he actual processing ta+es place in the server process, !hereby the user !ho sent
the re*uest is usually assigned the same server process again for the ne$t re*uest.
(he dispatcher and server processes of AS ;ava are also called no!es. All
processes of AS ;ava together !ith the database schema form the 1ava cluster.
#n contrast to the processes of AS ABAP /e$cluding the #:'0, the cluster nodes
of AS ;ava are multithrea!e!. (his means that an AS ;ava process consists of
many threads and one re*uest can be processed in each thread. Dence, one server
process al!ays processes many user re<uests in parallel.
(o process user re*uests it is often necessary to read data from the ;ava schema of
the database or to !rite to it. (o do so, each server process is connected multiple
times to the 1ava schema of the !ata(ase via a connection pool /%B pool0.
Once processing is complete, the processing result from the server processes is
returned to the !eb bro!ser via the dispatcher.
(he (uffers help to speed up processing of user re*uests. (his means that the data
does not have to be read from the database every time it is needed, but can be
called very *uic+ly from the buffer. Each server process has its o!n buffer.
(he nodes of AS ;ava are split into different functional modules called managers
and services. (he managers form the 1ava Enterprise Runtime. (he ;ava
Enterprise untime provides basic core functions of AS ;ava. #t is also referred
to as +ernel.
(ogether !ith the interfaces and libraries, the services are called 1;EE Engine
Components. (he ;1EE Engine :omponents provide programming interfaces
/AP#s0 to the applicationsC the applications can then use these AP#s to access
the AS ;ava functions.
#n case of an D((P re*uests to the ;ava dispatcher the Connections #anipulator
#anager holds a connection object !ith information about the client sending the
re*uest. (he re*uest is then for!arded to one of the processes of this instance by
the 455P provi!er service using a cluster manager.
(he cluster manager of the server process receives the re*uest and for!ards it to
the D((P provider service. #m &e( Container Service, the presentation logic
of the application is then processed. (he !eb container service provides the
processing of servlets and ;avaServer Pages /;SP0. (he business structure logic
of the application is processed in the form of E;B beans in the E1B Container
Service. #f, in the processing of the re*uest, data from the database is re*uired,
the 10BC Connector Service is used to establish a connection to the database
and the data is re*uested there. #f the same tables contents have already been
*ueried by this server process, the content can be retrieved in the table buffer at
application level /if buffering is allo!ed for the table0.
(he response to the !eb bro!ser using D((P is then returned in the same !ay.
Transactional Processing in AS <a"a
(he AC%0 concept has no! been implemented in AS ;ava in the same !ay as
in AS ABAP. #n AS ;ava, the 5ransaction Service is responsible for managing
transactions. (he t!o ;1EE standards 1ava 5ransaction AP% /;(A0 and 1ava
5ransaction Service /;(S0 are implemented using the (ransaction Service.
Applications /application developers0 can use the ;ava (ransaction Service by
means of the ;(A interface.
#n the ;1EE standard, much of the implementation of the transaction logic is
left to the respective database used. Dence, a transaction at application level
often corresponds e$actly to one database transaction in the ;1EE standard. (he
follo!ing figure illustrates the correlation using a ;SP application as the e$ample.
Figure "7: 3ransa'tions in AS 5ava
#n AS ;ava, changes and entries in the user interface /in the !eb bro!ser0 are not
made persistent immediately in the database. "hen the user saves his entries, the
;ava transaction is completed immediately and the data is made persistent in a
database transaction. A ;ava transaction thus consists of a database transaction.
Persistence
SAP has created 7pen S?$ for 1ava frame!or+ for AS ;ava. Dence, ;ava
application developers have access to various database)independent programming
techni*ues as !ell as important functions for improved performance and trouble
shooting.
Figure "(: 9pen S:. for 5ava
#f the ;ava program is supposed to be porta(le, that is, run !ith a database other
than the one used originally, developers can choose bet!een Open S>E8;%B:,
Open S>E8S>E;, E;B /Enterprise ;avaBeans0 and ;%O /;ava %ata Objects0. #f
developers use 6ative S>E in the program, they loose the portability and cannot
use the table buffer of Open S>E for ;ava =rame!or+s.
.oc0 ,anagement
(he loc+ concept of the database is used in the ;1EE standard. So if application
developers ma+e sure that they implement database)independent database
accesses, the application !ill be portable but !ill respond semantically different
on different database platforms. =or this reason and to improve response times,
SAP introduced the concept of the en*ueue service analogous to AS ABAP.
#f a user !ants change access to data, the e$ecuting server process re*uests a loc+
/to do so, the application developer must program this re*uest e$plicitly0.
(he application developer uses the interface of the Application $ocking Service
to re*uest a logical lock.
(he re*uest is for!arded to the En<ueue Server via the $ocking A!apter
Service and the $ocking #anager. (he en*ueue server no! chec+s !hether a
ne! loc+ can be generatedC that is, !hether there is a collision !ith loc+s that have
already been set. #f a loc+ can be set, the dialog !or+ process creates it and the
user /loc+ o!ner0 is given the loc+ +ey.
"hen the loc+ is re*uested, the system chec+s !hether the re*uested loc+
conflicts !ith e$isting entries in the loc+ table. #f the loc+ table already contains
corresponding entries, the loc+ re*uest is refused. (he application program can
then inform the user that the re*uested operation cannot currently be e$ecuted.
<a"a Cluster Architecture
The <a"a /nstance Concept
SAP 6et"eaver Application Server ;ava ta+es the instance concept of SAP Basis,
!hich combines multiple components that are monitored, started, and stopped
together into an administrative unit.
(he follo!ing components are part of a ;ava instance4
. (heserver processes provide the infrastructure in !hich the ;1EE
applications run.
. (he1ava !ispatcher distributes the client re*uests to the free server
processes of the instance.
An instance al!ays runs on one physical server, but there can be multiple instances
on one server. "ithin an SAP system, an instance is defined using the system #%
/S#%0 of the SAP system and the instance number. An SAP system consists of a
database and one or more instances. (hese instances can either be purely ABAP
or ;ava instances, or instances !ith ABAP and ;ava infrastructure.
(he :entral Services form a special ;ava instance. (hey provide the basis of
communication and synchronization !ithin a ;ava cluster. (he central instance is
another special instance. (his runs on a physical server !ith the :entral Services.
%uring its installation, the Soft!are %eployment 'anager is also installed.
(o ensure high)performance !hen processing ;ava re*uests, the SAP system
can be scaled using the number of server processes for each instances or using
the number of instances.
<a"a Cluster Architecture
All ;ava components of an SAP system are +no!n as a ;ava cluster. A ;ava
cluster consists of4
. A /central0 1ava instance !ith a dispatcher and at least one server process.
. (heCentral Services, !hich contain a message server and an en*ueue
server.
. A!ata(ase for the central storage of data.
. Optionally, additional ;ava instances
A minimal cluster installation and an installation !ith multiple SAP 6et"eaver
AS ;ava instances are sho!n as e$amples in the follo!ing figures.
Figure 6): &inimal Cluster ;nstallation
The <a"a Dispatcher an$ Ser"er Processes
:lient re*uests to SAP 6et"eaver AS ;ava are received by the ;ava dispatcher.
#t selects a free server process to process the re*uest and creates the connection
bet!een the client and the server process. (he dispatcher distributes ne! incoming
re*uests to the available server processes using a .round robin. algorithm. #f
there is already a connection to the client, the re*uest is for!arded to the server
process that is already processing re*uests for this client. (he individual steps in
the processing of a re*uest are outlined in the follo!ing figure.
"ithin the ;ava dispatcher, the connection re*uest handler receives the very first
re*uest from a client. #t initializes a connection object, !hich is then assigned
to this connection. (he connection re*uest handler then uses load balancing to
determine !hich server process processes the re*uest.
After the initialization of a connection object, the client is then connected to this
connection manager for all follo!ing re*uests. (he connection manager selects
the re*uired session service /such as D((P0 on the basis of the re*uest type. (he
re*uest is then for!arded to the server process by the communication handler.
(he server process of the SAP 6et"eaver Application Server ;ava runs the
;ava applications. (he structure of server processes essentially corresponds to
the structure of the ;ava dispatcher. (he server processes are implemented as
multi)threaded servers and can therefore process multiple re*uests in parallel. (he
system or application threads ta+e over the processing of the re*uests.
Central Ser"ices
(he :entral Services run on one host and form a separate ;ava instance. (hey
consist of the message service and the en*ueue service.
(he :entral Services provide the basis for communication and synchronization for
the ;ava cluster4
. (hemessage service administers a list of the dispatchers and the server
processes of the ;ava cluster. #t represents the infrastructure of data e$change
/for small *uantities of data0 bet!een the nodes involved. #n the case of load
balancing bet!een a large number of ;ava instances, it also provides the load
balancing information for the SAP "eb %ispatcher.
. (heen<ueue service administers logical loc+s that are set in a server
process by the e$ecuted application program. #t is also used for cluster)!ide
synchronization.
(he :entral Services are essentially re*uired !hen a ;ava cluster is installed.
(hey are started on a host !ith a separate system number and the system #% /S#%0
of the entire system. #f the :entral Services are running, other ;ava instances
are started !ith the program ;:ontrol /see the unit Starting and Stopping a SAP
6et"eaver AS ;ava0.
,essage Ser"ice
(he message service is a separate program that allo!s communication bet!een the
elements of a ;ava cluster. (he message service +no!s all active ;ava instances.
(he terms message server and message service are used !ith the same meaning in
the training material. (o be precise, the message server is a program8process that
provides the message service.
(he message service performs the follo!ing tas+s in the ;ava cluster4
. 6otification of events that arise in the cluster, for e$ample, if a node of
the cluster disappears /due to failure or the instance being shut do!n0, or
!hen a service is started or stopped.
. :ommunication bet!een different services
. =or!arding of messages and re*uests to all participants /broadcast0
. Prepare logon information for the SAP "eb %ispatcher
. Support for message server failover
. Buaranteed message transmission
. E$change of cache information in the cluster
By using the message service, you can avoid performance problems that occur if
all the cluster elements are connected !ith each other and e$change data !ith each
other. (his previously lead to significant performance problems, particularly !ith
large clusters. (he same technology is used as !ith the SAP 'essage Server for
the earlier SAP 6et"eaver AS versions !ithout ;ava.
)n2ueue Ser"ice
(he en*ueue service runs on the :entral Services instance of the ;ava cluster. #t
manages the loc+ table in the main memory and receives re*uests for setting or
releasing loc+s. #t uses the tried and tested SAP loc+ concept.
(he terms en*ueue server and en*ueue service are used !ith the same meaning in
the training material. (o be precise, the en*ueue server is the program or process
that provides the en*ueue service.
(he en*ueue service has the follo!ing tas+s4
. #nternally, it is used for synchronization !ithin the ;ava cluster
. (he applications can loc+ objects are release loc+s again. (he en*ueue
service processes these re*uests and manages the loc+ table !ith the e$isting
loc+s.
.esson "
Starting an$ Stopping SAP Systems
System Start; Process
Start Process of the SAP System
(he starting of an SAP system is the basic prere*uisite for being able to !or+ !
the system. estarts of SAP systems are also re*uired after maintenance !or+ o
the hard!are in use and changes to the SAP systemHs profile. Starting an SAP
system is an initial process !ith !hich every administrator should be familiar.
Starting an SAP System is performed in a number of steps and is the tas+ of the
operating system user @si!Aa!m.
Start the database4
. (he underlying element of the entire SAP system is the database. Before the
SAP instances are started, this must have operational status. (he database is
therefore al!ays started as the first step.
Start the :entral Services instance /AS ;ava and AS ABAPF;ava0
. Start the :entral Services instance that contains both the en*ueue and the
message service for the ;ava part of the SAP system. (he :entral Services
are installed as an independent instance.
Starting the :entral #nstance4
. 6e$t, the operating system collector SAP7SC7$ is started, if it is not
already active. (his standalone program runs in the operating system
bac+ground, independently of SAP instances. (his program collects data
about operating system resources and ma+es this data available through the
shared memory of all SAP instances.
'ote" #f you later discover that SAPOS:OE has not been started,
you can start it at any time by calling transaction S(-7 and choosing
the path Detail Anal,sis (enu ./// 0S Collector ./// Start.
. (he central instance !ith the message server and the dispatcher and its !or+
processes is then started. #f the start up parameters are set accordingly, the
dispatcher also starts the #nternet :ommunication 'anager /#:'0 and the
processes of AS ;ava /if it is installed0. <ou should only start other /optional0
instances once the message and en*ueue servers are active.
Starting the dialog instances
. #f the dialog instance is not running on the same host as the central instance,
the SAPOS:OE operating system collector is first started on this host /if
it is not yet running0.
. (he dispatcher is then started !ith its !or+ processes.
The sapstartsr" Process
Figure 66: Pro'ess of Starting an SAP ;nstan'e with the SAP &anagement
Console 4SAP &C6
As of release SAP 6et"eaver ?.-, the start service sapstartsr% that has been used
for many years in the "indo!s installation is installed on all platforms. (he
service is a "indo!s service or a 5ni$ daemon for the administration of an SAP
instance.
A sapstartsr% process is started for each SAP instance and does not terminate
even if the instance is stopped. "hen it starts, sapstartsr% reads the start
profile of its instance and opens its "eb service interface by default on
the ports ACC7? /D((P,, RR represents the instance number0 and, providing
SSE is configured, on ACC74 /D((PS0. (he start service then !aits for
incoming re*uests from "eb service clients and processes these. (he "eb
service interface contains a number of functions for administrating and
monitoring an SAP instance, in particular the SAP 'anagement :onsole
/SAP ':0. sapstartsr% also has a limited "eb server function that allo!s
you to do!nload all files under DIR/E9ECU'BALE=ser%icehttp by !ay of
D((P/S0. (his can be used to start the SAP 'anagement :onsole from a
"eb bro!ser on any host, for e$ample. #f no other 5E is specified /for
e$ample, http488OhostnameP43RR,.0, the system automatically redirects you to
http488OhostnameP43RR,.08servicehttp8sapmc8sapmc.html, for e$ample, to start
the SAP':.
sapstartsr% manages an internal list of protected operations. (hese can be changed,
if necessary, !ith the start profile parameter ser%ice=protected#ebmethods. "ith
the start profile parameter ser%ice=hostname you can also determine the #P address
8 host name to !hich the "eb service port should be connected /default4 all 8
-.-.-.-0, to limit accessibility in the net!or+. <ou then have to restart sapstartsr%.
(o do this, refer to SAP 6ote J1?7.? ) "eb ser%ice authentication in sapstartsr%
as o release B;@@.
System Start; .ogs
.ogging the Start Process
(he start process is an especially important phase, !hich is logged by the
operating system, the SAP system, and the database. #f the SAP system does not
start up, you can find the relevant error message in the log files. #t may be that
there !ere problems starting the database, meaning that the SAP system could not
subse*uently be started.
Figure 67: .ogging the Start Pro'ess in the SAP Sstem
Eogs about the start process of the SAP system are stored in the file system. #f
there are problems during the start, these logs can provide useful information such
as error messages or problem descriptions. (hese files are in the home directory
/DIR/&0(E0 of the respective instance.
%uring the start process, the S'DERRDnE log files are created by the SAP service.
(he starting processes !rite to the individual files, depending on the se*uence in
!hich they are listed in the start profile. (he contents of these log files therefore
depends on the individual system setup, and could, for e$ample, be as follo!s4
. S'DERR74 #nformation about the start process of the database system.
. S'DERR84 #nformation about the start process of the message server.
. S'DERR?4 #nformation about the start process of the dispatcher.
<ou can set the level of detail of the logged information to four levels using the
rdisp='RACE profile parameter. (he possible values for this parameter are4
. -4 Errors only
. ,4 Error messages and !arnings /default0
. 14 Error messages and a short trace
. .4 Error messages and a complete trace
(he higher the trace level, the larger the amount of logged information, and
therefore the larger the size of the files. <ou should therefore only increase the
default value for short periods for problem analysis.
(he trace level can be set separately for individual !or+ processes in the process
overvie! /transaction S'3-0.
Pro%lem Analysis
#f the SAP system does not start correctly, this can be due to a variety of reasons.
(o analyze the problem, proceed as follo!s4
. :hec+ the error messages and !arnings of the respective operating system
!ith the corresponding operating system tools.
. :hec+ the status of the respective database system using the error log files.
<ou !ill find information about this in the lesson4 .Appendi$ ) %atabase
Eogs..
. :hec+ the start log in the SAP ':. Select the instance that is affected, and
from the conte$t menu, choose List De%eloper 'races.
. :hec+ the error files stderrDnE that !ere created by the SAP Service.
. :hec+ the trace files of the individual SAP !or+ processes4
. de%/ms4 %eveloper trace for the message server
. de%/rd4 %eveloper trace for the gate!ay
. de%/disp4 %eveloper trace for the dispatcher
. de%/#DmE /m is the !or+ process number04 %eveloper trace for the
!or+ processes
#f you can still log on to the SAP system, chec+ the system log of the SAP system
using transaction S'1,.
Sstem Shut,own: <ow an, +h=
Stopping the SAP Sstem
#t may be necessary to stop an SAP system for a variety of reasons, for e$ample,
restarting after permanently changing profile parameters, before installing +ernel
patches, or allo!ing hard!are upgrades to be carried out.
Figure 6-: /efore Stopping the SAP Sstem
Before you stop the system, you should chec+ the status of the system. (his
involves, among other things4
. Active 5sers4
:hec+ !hich users are logged on using the 5ser Eist /S'-20.
. Bac+ground Processing 4
:hec+ !hich jobs are active using the ;ob Overvie! /S'.?0. #f jobs are
terminated by the system stop, these jobs must be rescheduled. ;obs that are
scheduled for the time !hen the system is stopped run automatically once
the system restarts.
. Batch #nput4
(he transaction Batch #nput4 Session Overvie! /S'.30 displays running
batch input jobs.
. 5pdate4
5se the 5pdate Overvie! /S',.0 to chec+ !hether update processes are
terminated by the system stop. (hese update records are rolled bac+ during
the stop, and are set to the status .init.. (hese records are then updated
again during the restart.
Before you stop your system, you should inform users using a system message
/S'-10.
Figure 7): Stopping the SAP Sstem
(he stopping of the SAP system is performed in the opposite order of starting.
Stop the instances4
. #n the SAP system itself !ithin the ::'S /transaction S-.0 by choosing
Control ./// Stop SAP Instance.
. #n the 'icrosoft 'anagement :onsole, right)clic+ to sho! the conte$t menu
and choose the Stop function. %epending on !hether you have selected an
individual instance or the SAP system, the follo!ing are stopped4
. A single instance
. :entral instance and all dialog instances
(he SAP service !aits for a stop message from the SAP ': or from the ::'S
and then stops the SAP system. (he service itself does not stop.
(he services themselves can be stopped and restarted !ith the corresponding
operating system tools, such as the "indo!s Service :ontrol 'anager.
(he database is stopped using the relevant database system tools.
Eog on in 56#9 as a user !ith SAP administrator authorization /OsidPadm0.
(o start the central instance, call the shell script
startsap_<host>_<instance no> in the home directory
of the OsidPadm user. #f there is only one instance for each application server, the
alias startsap references the script startsap_<host>_<instance no>.
(he script startsap first starts the saposcol process !hich collects statistical
data for the operating system that it provides to the SAP system.
(he ne$t step is a chec+ to see if the database is running. #f not, the script
startdb is called to start the database.
(he final step starts all of the processes for the instance /message server,
dispatcher, !or+ processes, and so on0.
After the central instance is started, you can optionally start other instances.
(he startsap script can be called !ith the follo!ing options4
DB4 starts the database system
R34 starts the instances and associated processes for the instance
ALL4 starts the database system and the instance /default setting, can be omitted0
(o start the SAP system, the startsap script calls the sapstart process !ith
the start profile specified in the script in the variable S'AR'/3ILES.
"hen you stop the SAP system, you should first stop all dialog instances and then
stop the central instance. <ou have t!o options for doing this4
=rom the SAP system using the ::'S :ontrol Panel.
Eog on under 56#9 as the SAP administrator /OsidPadm0 at operating system
level and enter the command stopsap from your home directory.
(he stopsap script can be called !ith the follo!ing options4
. DB4 stops the database system !ith the help of the stopdb script
. R34 stops the instances of the SAP system
. ALL4 stops the database system and the instance /default setting, can be
omitted0
(he database can be stopped separately !ith database tools.
Data%ase .ogs
(he Oracle database logs all significant events such as start)
ing and stopping the database and error messages in the file
<Laufwerk>:\oracle\<SID>\saptrace\background\ALRT.LOG.
%etailed information about errors is logged in the Oracle (race =ile4
<Laufwerk>:\oracle\<SID>\saptrace\usertrace\Ora<no>.trc.
#f the system administrator administers the database !ith sapdba, this !rites its
o!n log files in the follo!ing directories4
<Laufwerk>:\oracle\<SID>\sapreorg
<Laufwerk>:\oracle\<SID>\sapcheck
<Laufwerk>:\oracle\<SID>\sapbackup
O"er"iew of the Process for Starting an$
Stopping a SAP et!ea"er AS <a"a
System Start; Process
(he starting of an SAP system is the basic prere*uisite for being able to !or+ !ith
the system. (he start process presented in this lesson describes the process flo!
!hen starting an SAP system !ith ABAP and ;ava stac+ as !ell as !hen starting
an SAP system !ith a ;ava stac+ but !ithout an ABAP stac+. Every SAP system
has a database and at least one instance. One of these instances provides central
functions and is therefore +no!n as the central instance. (his central instance and
all other so)called dialog instances can consist either only of a ;ava stac+ /SAP
6et"eaver AS ;ava0 or of ABAP and ;ava stac+s /SAP 6et"eaver AS ABAP
F ;ava0. #n the case of an SAP system that has at least one instance !ith a ;ava
stac+, there are also :entral Services !hich must also be ta+en into account during
the start process.
#n principle, the starting of the system is performed in multiple steps, and is the
tas+ of the operating system user @si!Aa!m4
,. Starting the database
(he database is the fundamental element of the entire SAP system. (his
must be in an operational state before SAP instances are started.
1. Starting the :entral Services #nstance
(he :entral Services consist of the ;ava message server and the ;ava en*ueue
server. (he cluster elements e.g. ;ava)dispatcher and ;ava)server connect to
the ;ava message server during their o!n start process.
.. Starting the :entral #nstance
After the :entral Services have been started, the central instance is started
!ith the ;ava dispatcher and servers. (he ;ava stac+ is started and stopped
by the ;ava Startup and Control 3rame#ork.
(he Soft!are %eployment 'anager /S%'0 is also started !ith the central
instance.
2. Start additional dialog instances
Other so)called dialog instances are started. "hen an instance is started, its
;ava dispatcher and servers are started.
=or the start process, you differentiate bet!een the starting of SAP systems !ith
purely ;ava instances /!ithout ABAP0 and mi$ed instances /;ava and ABAP
stac+0. Additional details are provided in the follo!ing sections.
Stop Process; Process
(he stopping of an SAP system is performed in reverse se*uence. (he dialog
instances are al!ays stopped first, and then the central instance.
=or SAP system installations on the 'icrosoft "indo!s operating system, the
database is not stopped at the same time. (his can be done !ith the tools of the
relevant database. #n the case of SAP system that are installed on 56#9 operating
systems, the database is generally stopped at the same time.
Starting an$ Stopping an SAP et!ea"er AS ABAP
4 <a"a
%uring the installation of an SAP system, you can add a ;ava stac+ to each ABAP
instance. (he instances are started and stopped using appropriate tools at operating
system level ) such as the SAP 'anagement :onsole /SAP ':0. "ithin an
instance, the ;ava stac+ is controlled by the ABAP dispatcher. #n concrete terms,
this means that the start and stop processes are triggered by the ABAP dispatcher.
(o do this, the ABAP dispatcher sends a start command to the so)called Startup
and Control 3rame#ork. (he corresponding ;ava cluster elements are started
using the Startup and Control 3rame#ork.
'ote" (he Startup and Control 3rame#ork is the infrastructure that SAP
provides for starting and stopping of ;ava cluster instances.
(he stop process is performed by the ABAP dispatcher in the same !ay as the start
process. (he ABAP dispatcher also informs the Startup and Control 3rame#ork
and transfers the stop command in this case.
Starting an SAP et!ea"er AS <a"a
=or some components, such as SAP Enterprise Portal or SAP 6et"eaver
%eveloper Studio, you only re*uire a SAP 6et"eaver Application Server as
a technical foundation. (his means that only pure ;ava instances !ithout an
associated ABAP stac+ are installed.
Pure ;ava instances can therefore not be managed by the ABAP dispatcher. (he
start and stop processes can be initiated using appropriate operating system
commands ) such as the SAP 'anagement :onsole /SAP ':0 or the 'icrosoft
'anagement :onsole /SAP '':0 under "indo!s as !ell as the scripts
startsap and stopsap under 56#9.
Tools for Starting an$ Stopping
Starting an$ Stopping an SAP et!ea"er AS ABAP
4 <a"a
"hen SAP 6et"eaver AS ABAP F ;ava is started, the entire instance is al!ays
started. #f the instance is started then the ;ava stac+ can be stopped and started
again individually by the ABAP dispatcher.
Starting an, Stopping instan'es of SAP *et+eaver AS A/AP > 5ava
Figure -): Starting an, Stopping instan'es of SAP *et+eaver AS A/AP >
5ava
#nstances of SAP 6et"eaver AS ABAP F ;ava can be started and stopped
independently of the operating system using the SAP 'anagement :onsole /SAP
':0.
As of SAP 6et"eaver release 1--2, a ne! operating system)independent
application is supplied !ith the SAP 'anagement :onsole /SAP ':0 /see SAP
6ote ,-,22M-0. (his allo!s you to display monitoring information and perform
administration tas+s such as start and stop operations. (he tool is a standalone
;ava application !hich can be started either as an applet or locally. (he SAP
': is supplied as standard !ith the start program sapstartsr% and is ready for
use !ithout any additional installation.
SAP ': is a ;ava application !hich is supplied as a ;ava applet as standard.
<ou simply use a "eb bro!ser to do this.. (o use the applet correctly, you
re*uire a ;E /;ava untime Environment0 of version ,.2 or higher. #n addition,
the corresponding ;ava plug)in for the bro!ser must be activated correctly. (o
start SAP ': after installing the corresponding SAP 6et"eaver AS, enter the
follo!ing 5E in your bro!ser4
http488OhostnameP43OinstancenumberP,.
Or, if you have configured https in sapstartsrv /see SAP 6ote ,-.7,-?04
https488OhostnameP43OinstancenumberP,2
(he SAP ': allo!s you to start and stop all the SAP 6et"eaver AS ABAP F
;ava instances as !ell as the :entral Services. <ou can also display information
about the instances of the SAP system and the corresponding database /name,
manufacturer and name of the host on !hich the database is located0. Starting and
Stopping !ith the SAP 'anagement :onsole0.
=or each instance, SAP ': displays information about the ABAP and ;ava stac+
processes /see figure4 SAP 'anagement :onsole4 Process #nformation0.
Figure -%: SAP &anagement Console: Pro'ess ;nformation
(he SAP 'anagement :onsole also allo!s you to display the trace files for the
individual processes.. <ou can use these trace files to analyze problems. Do!ever,
these files also enable you to identify the employed ports /such as, for e$ample,
the message server port, http port, P2 port and telnet port0 /see figure4 SAP
'anagement :onsole4 (race =iles0.
#n the case of SAP 6et"eaver AS ABAP F ;ava, it is possible to allo! the ABAP
stac+ to continue running, and only stop and then restart the ;ava stac+. <ou do
this using transaction S'#:'. <ou can either start8stop the /local0 instance onto
!hich you are logged in the transaction S'#:' or start8stop all the instances in
the /global0 ;ava cluster /see figure4 Starting and Stopping the ;ava Stac+ of an
SAP 6et"eaver AS ABAP F ;ava from the (ransaction S'#:'0.
Figure -": Starting an, Stopping the 5ava Sta'2 of an SAP *et+eaver AS
A/AP > 5ava from the 3ransa'tion S&;C&
#t is not possible, and also not useful, to stop only the ABAP stac+ and leave the
;ava stac+ started in the case of AS ABAP F ;ava.
SAP 6et"eaver AS ;ava is started and stopped in the same !ay as SAP 6et"eaver
AS ABAP F ;ava by means of the SAP 'anagement :onsole /see figure4 Starting
and Stopping SAP 6et"eaver AS ;ava !ith the SAP 'anagement :onsole0.
#n the case of SAP 6et"eaver AS ;ava, the instance names are
;:Oinstance)numberP for the central instance and ;Oinstance)numberP for the
so)called dialog instances.
Special Characteristics of Starting an$ Stopping +n$er
,icrosoft !in$ows
"ith the 'icrosoft "indo!s operating system, you can use both the SAP
'anagement :onsole and the 'icrosoft 'anagement :onsole !ith an SAP
plug)in /SAP '':0 to start and stop an SAP system.
(he SAP '': allo!s you to start and stop all the instances of the SAP system
as !ell as the :entral Services. =or some databases, you can also display
administration information and the status of the database. Some database types
can also be administered using the SAP '':.
(he information displayed in the SAP '': and the start and stop procedures
are similar to the bro!ser)based SAP 'anagement :onsole /SAP ':0. (his
is illustrated by the ne$t t!o figures.
#n the same !ay as the SAP ':, SAP '': also ma+es it possible to display the
employed ports via the trace files for the individual processes..
4int" #n the environment of SAP 6et"eaver AS ;ava, there is a special
;ava development environment, !hich is installed locally on every P:.
#t usually consists of an SAP 6et"eaver %eveloper Studio and an SAP
"eb AS ;ava as a test environment for ;ava developments. (he SAP
6et"eaver Application Server ;ava can be .restarted. from the SAP
6et"eaver %eveloper Studio.
5nder"indo!s, the SAP system can also be started and stopped !ithout a B5# by
calling a command by means of the e$ecutable files startsap.e$e and stopsap.e$e.
(his can be done using a simple telnet access.
(o start an instance of the SAP system, open a telnet connection and enter the
follo!ing command4 startsap name=<SID> nr=<instance nr.>
SAPDIAHOST=<hostname>
(o stop an instance of the SAP system, open a telnet connection and enter the
follo!ing command4 stopsap name=<SID> nr=<instance nr.>
SAPDIAHOST=<hostname>
=or the SAP%#ADOS( parameter, enter the name of the host on !hich the
instance is to be started.
Special Characteristics of Starting an$ Stopping +n$er
+/8
=or SAP systems that are installed under 56#9, you run the scripts startsap and
stopsap to initiate the start and stop processes. #f multiple SAP instances are
installed on one physical server, you add the instance name to the names of the
scripts startsap and stopsap.
(he startsap script can be called !ith the follo!ing options4
. DB4 starts the database system
. R34 starts the instances and associated processes for the instance
. J2EE4 starts the instances and associated processes for the instance
. ALL4 starts the database system and the instance /default setting, can be
omitted0
(he stopsap script can be called !ith the follo!ing options4
. DB4 stops the database system !ith the help of the stopdb script
.
. J2EE4 stops the instances of the SAP system
. ALL4 stops the database system and the instance /default setting, can be
omitted0
(o start the SAP system, the startsap script calls the sapstart process !ith
the start profile specified in the script in the variable S'AR'/3ILES.
%atabase and SAP instances can each be individually started and stopped !ith the
options DB or R?, e.g. startsap R3 DVEBMGS00.
Caution" (he option $8EE can be used in the same !ay as the option R?.
#n the case of SAP 6et"eaver AS ABAP F ;ava, both the ABAP stac+
and the ;ava stac+ are started and stopped.
<a"a Startup an$ Control *ramewor0
Startup an$ Control *ramewor0
SAP provides a separate Startup and Control 3rame#ork for SAP "eb
Application Server ;ava. (his =rame!or+ is used to start, stop, and monitor the
;ava stac+ processes !ithin the SAP system instances ) but not, ho!ever, the
:entral Services. #t consists of the follo!ing processes4
;:ontrol4
. ;:ontrol starts, stops, and monitors the processes of a ;ava instance .
primarily the server and dispatcher processes. SAP Signal Dandling is
implemented !ith ;:ontrol, to for!ard the start and stop commands to the
processes of the ;ava stac+.
. ;:ontrol restarts terminated processes, ends hanging processes, and sends a
shutdo!n signal to the processes of the ;ava stac+.
. ;:ontrol reads the description of the instance from profile files.
. ;:ontrol starts the ;Eaunch processes, !hich in turn start ;ava nodes such as
dispatchers or servers.
. ;:ontrol creates a shared memory segment for the internal administration
data of all ;Eaunch processes.
;Eaunch4
. ;Eaunch starts a ;ava program, loads a ;ava I' /;I'0 in its o!n address
space and assumes the function of the corresponding cluster element. (he
parameterizing of the ;I' is read before the loading.
. ;Eaunch receives commands from the ;:ontrol process /through named
pipes0 to stop cluster elements such as dispatchers or servers.
. (he ;Eaunch process ends itself if its parent process ;:ontrol is no longer
running.
Start Process of a <a"a /nstance
(he start procedure in the Startup and Control 3rame#ork4
/See also figure4 Starting !ith the Startup and :ontrol =rame!or+0
,. ;:ontrol is started.
1. ;:ontrol starts a ;ava instance bootstrap process !ith
parameters that are defined in the file bootstrap;properties
/=usr=sap=DSIDE=DinstanceE=58ee=cluster=bootstrap0. (he bootstrap process
synchronizes all re*uired binaries for the ;ava nodes from the database !ith
the file system. (his is necessary, since the Class Loading is performed using
the file system in the ;ava environment. (he database al!ays contains the
current /deployed0 binaries and properties and distributes these to every ;ava
node !hen starting.
.. (he ;ava instance bootstrap process reads the instance description from the
;ava schema of the database.
2. (he ;ava instance bootstrap process stores a file instance;properties,
containing the instance description, at operating system level.
3. ;:ontrol reads the instance description from the file system.
7. ;:ontrol starts the bootstrap processes !hich are specific to ;ava nodes
and !hich read the descriptions for the nodes from the database and store
them in the file system.
?. ;:ontrol creates a connection to the :entral Services message server. #f this
connection is established successfully, the operation continues !ith the ne$t
step. #f no connection is established to the message server, ;:ontrol initiates
an Emergency Shutdo!n.
M. #n the final step, ;:ontrol starts all the ;ava nodes such as dispatchers and
servers as ;Eaunch processes and, !hen doing so, loads a ;I' in the
;Eaunch process.
;:ontrol monitors the ;ava instance processes during their runtime, restarts
terminated processes, ends hanging processes, and sends the shutdo!n signal to
the ;Eaunch processes.
So)called profile files are first read !hen a ;ava instance is started. (he ;:ontrol
process then reads the files instance;properties and bootstrap;properties.
(he profile files are located on the operating system in the directory
%#TPO=#EE /'icrosoft "indo!s4 Ddri%eEFGusrGsapGDSIDEGS1SGproile
or 56#94 =usr=sap=DSIDE=S1S=proile0 and are generated at installation
time. (here are three different profile files4 the default profile /Deault;pl0,
the start profile /S'AR'/DinstanceE/DhostE0, and the instance profile
/DSIDE/DinstanceE/DhostE0.
'ote" (he :entral Services profiles are read !hen the :entral Services
are started.
,. (he Signal Dandler of ;:ontrol receives a stop signal from the stopsap script
/56#90 or from the "indo!s Service.
1. ;:ontrol for!ards the signal through named pipes to all running ;Eaunch
processes /;ava servers and dispatchers0.
.. (he ;Eaunch process of a ;ava cluster element should react to this notification
/soft shutdo!n0 !ithin a certain period of time. After this time has e$pired,
the ;Eaunch process is terminated by ;:ontrol. "hen this is done, the ;I'
!ithin the ;Eaunch process is ended, as is the ;I' of the ;Eaunch process.
5Cmon
(he ;:mon tool can be used to monitor the ;:ontrol process. ;:mon
is part of the Startup and Control 3rame#ork, and is located in the
;:ontrol8;Eaunch home directory, that is, in the e$ecutable directory
=usr=sap=DSIDE=DinstanceE=S1S=e-e=;;;.
;:mon can be started !ith the command $Cmon pHDSAP instance proileE.
;:mon provides an administration interface for elements in the ;ava cluster that
can be called from the operating system.
.ogs of the Start an$ Stop Processes of SAP
et!ea"er AS <a"a
.og an$ Trace *iles
#n the case of an error or une$pected behavior of the Startup and Control
3rame#ork, it is important to chec+ the follo!ing trace and log files4
. devTjcontrol
. devTOnode nameP, such as devTdispatcher
. jvmTOnode nameP.out, such as jvmTdispatcher.out
. stdTserverO9P.out, e.g. stdTserver-.out
. stdTdipatcher.out
(he trace and log files are stored in the #ork director, of an instance. (his
directory is called =usr=sap=DSIDE=Dinstance nameE=#ork /56#90 and
analogously in the 'icrosoft "indo!s environment.
!ev9>control is the trace file for the ;:ontrol process. devTjcontrol is the most
important trace file for problem messages !hen starting 6et"eaver AS ;ava.
:urrent messages are !ritten at the end of the file.
!ev9@no!e nameA is the trace file for ;Eaunch processes. (he trace file
devTOnode nameP is !ritten for each started ;Eaunch process, and therefore for
every dispatcher and server process.
>vm9@no!e nameA*out is the output file for the ;ava Iirtual 'achine /;I'0.
(his ;Eaunch process represents a ;ava node such as a dispatcher or a server
and therefore a ;I'. (he output of a ;I' is for!arded to the file jvmTOnode
nameP.out in the !or+ directory of a ;ava instance.
st!9server@:A*out and st!9!ispatcher*out are the default output files for the
started managers and services of the the corresponding nodes.
=or all of the log files listed above, you !ill also find log files in the #ork director,
!ith the ending ;old, /hich can also often be used for troubleshooting.
.esson 6
/ntro$uction to System Con-guration
'ow the System )"aluates /ts Parameters
Con-guring the System Parameters
(he configuration of the individual instances and therefore of the SAP system is
performed using system parameters. (he default values for these parameters are
defined in the program code of the +ernel.
Figure $)": Assigning Sstem Parameters
<ou can change these default values using the profile files, !hich are read !hen
an instance is started. (hese profile files are created during the installation of
the system and can also be edited later.
As the profile files are only read !hen the system is started, you must restart the
instance or the entire system after changing individual parameters.
%ynamic s!itching, that is, !hile the system is running, is only possible for a
small number of system parameters.
(he profile files are automatically created during installation. After installation
is complete, the profile files are stored at operating system level in the directory4
GusrGsapGDSIDEGS1SGproile. (his directory can be read by all instances of an SAP
system using the share or mount techni*ue.
(he SAP system has three system profiles. (hese are4
. Start profile
. %efault profile
. #nstance profile
#n principle, you can change these files !ith operating system tools /editors0.
#n the process, users must themselves ensure that the changes are performed
correctly. Parameters that are set incorrectly can lead to the system not starting.
#t is far more convenient and safer to change the profile parameters using the
tools in the SAP system.
(he instance)specific start profile /S'AR'DinstanceEDinstance numberE/Dhost
nameE0, specifies !hich processes are to be started for each instance. (hese are,
for e$ample, the message server and the dispatcher.
(here is only one default profile /DE3AUL';P3L0 for each SAP system, and
it is read by all instances. #t contains system)!ide settings, such as the system
name, the name of the database server, the name of the en*ueue server, or also
the default logon client.
(he instance profile /DSIDE/DinstanceEDinstance numberE/Dhost nameE0
defines parameters that apply for one instance, such as the number and type of
!or+ processes, or the definition of the size and allocation of the main memory
area used by the SAP system. (he instance profile is therefore instance)specific.
(he current values of the system parameters can be displayed in the system.
(here are t!o !ays to do this4 eport SP=PA and transaction S,,. Both
functions display the system parameters for the instance to !hich the user is
currently logged on. eport SP=PA displays a list of all instance)specific
system parameters, along !ith the parameters that apply system)!ide. <ou can
restrict this list to specific parameters. A table displays the system default value
for the individual parameters as it is defined in the program code of the +ernel and,
if the default value has been overridden by a profile parameter, the user)defined
value. A short description and, if re*uired, documentation for the parameters can
also be displayed. (ransaction S,, displays information and documentation for
individual profile parameters. #t also sho!s !hether the parameter can be changed
!hile the system is running !ith the D,namicall,S#itchable indicator.
'ote" #n the 'P31PR0P'1 table, all dynamically s!itchable profile
parameters are identified !ith the D,namic indicator. <ou can use
transaction SE,7, for e$ample, to display this table.
Outside the SAP system, you can display the values of the profile parameters at
operating system level using the user OsidPadm !ith the program sappfpar.
<ou can display the current value of a parameter !ith sappfpar 5parameter
name7. (he command sappfpar all returns a list of all parameters. <ou
can chec+ the parameters that are set using sappfpar chec0. (he command
sappfpar help returns a short overvie! of possible options.
<ou can also specify an instance profile, an instance number, or the SAP system
name !ith this command using the options pf=5instance pro-le7,
nr=5instance num%er7, or name=5S/D7.
4int" 6ote that, for the evaluation of profile parameters using the tools
described above, some profile parameters are the same system)!ide,
!hile others can be set differently for each instance. (he report SP=PA
displays the configuration of the instance on !hich you run the report.
'ow to Set System Parameters
A$ministering an$ ,aintaining Pro-les
#f you !ant to change profile parameters, you can ma+e these changes using
operating system)specific editors. Do!ever, this procedure has certain dangers,
as the user must ensure that the changes are performed, and also documented,
correctly. #ncorrectly set parameters can prevent an instance starting. (he
SAP system therefore provides integrated profile administration and parameter
maintenance.
Profile administration in the SAP system offers a number of advantages to the user.
A!vantages of Profile A!ministration in the SAP System
. :entral administration and maintenance of the instances
. :hanges in profiles chec+ed for consistency
. Administration of multiple versions of a profile
. :omparison of the actively used profile and the profile stored in the database
. #mmediate activation of selected parameters
Caution" Before you ma+e changes to the profile files, create bac+ups. #f
an error should occur, you can then start the SAP system !ith the restored
files and perform troubleshooting.
After installation, the profile parameters are, at first, only present at operating
system level. (o use the profile administration of the SAP system, the profiles
must be imported into the database. %uring this import, the system performs
a consistency chec+ and a chec+ of the !ay in !hich the parameters interact.
:hanges to profile parameters can then be performed in the SAP system, !ith the
previously mentioned advantages. (hese changes are then stored in the database,
and !ritten bac+ to file level. (he changes only ta+e effect !hen they are read by
the systemC that is, at a restart of the system.
<ou perform the administration and maintenance of profiles in transaction S,-.
#n the first step, you import the profiles into the database by choosing Utilities
./// Import Proiles ./// 0 acti%e ser%ers. After selecting the profile to edit, you
can change individual profile parameters. (here are three different levels for
maintaining the profiles. (he a!ministration !ata contains the type of profile
/start, default, or instance profile0, a short description, the path of the file, the
name of the instance, and the time of the last activation.
<ou can perform the maintenance of the parameters of the individual profiles
through either (asic maintenance or exten!e! maintenance. Basic maintenance
allo!s you to adjust the most important parameters and supports the user through
the use of logical descriptions. E$tended maintenance displays the unformatted
content of the profileC that is, the technical names of the profile parameters.
#n e$tended maintenance, you can not only change the values of individual
parameters, but also add ne! parameters and delete e$isting parameters.
(he changes are stored in t!o steps. #n the first step, the changes are temporarily
copied !hen you choose Cop,. (he values are permanently saved to the database
in a second step !hen you choose Sa%e. (he changes are therefore successfully
saved to the database and must no! be !ritten at operating system level. (his
is done either automatically during saving by confirming the relevant *uery, or
manually from the menu by choosing Proile ./// Acti%ate.
:hanges to instance)specific profiles ta+e effect after a restart of the corresponding
instance. :hanges to the default profile ta+e effect only after a restart of all
instances in the entire system.
:hanges to these files are, ho!ever, the e$ception rather than the rule.
Consistency Chec0
Additional functions available in transaction S,- are the consistency chec+
and the comparison of profiles.
%uring a consistency chec+, the system chec+s the synta$ and the semantics for
individual or for all profiles.
(he Utilities ./// Check all proiles option also contains a consistency chec+
bet!een the profiles of a type. (his means that, for e$ample, the system chec+s for
the start profile !hether only one message server is being started for each system.
%uring the comparison of profiles, the system compares the profile that is in active
use !ith the profile stored in the database. (his comparison is automatically
performed !hen an instance is started. #f the system identifies a difference
bet!een the active profile and the profile stored in the database, the system
displays a message in the Alert 'onitor.
A$ministration an$ Con-guration Tools of SAP
et!ea"er AS <a"a
+sage Areas of the Tools
(his section provides you !ith an overvie! of the various tools and their usage
areas. Some tools are particularly suitable for a usage area, or are the only tool that
can be used for a usage area. Several tools are suitable for other usage areas, on
the other hand. (his is e$plained in more detail in this section. (he follo!ing tools
are available for the administration and configuration of SAP 6et"eaver AS ;ava4
Con-g Tool
<ou use the :onfig (ool to maintain the settings for SAP 6et"eaver AS ;ava in
the database. #t is therefore necessary that the database is started, so that you can
change the settings !ith the :onfig (ool.
(he ;ava =# Settings /the settings of the ;ava Iirtual 'achine0 of SAP
6et"eaver AS ;ava can only (e maintaine! /ith the Config 5ool. <ou can
use the :onfig (ool to configure the managers and services of SAP 6et"eaver
AS ;ava. =or information about this, see the figure .:onfig (ool ,.. (he figure
.:onfig (ool 1. sho!s the special features of the tool.
(he settings that you ma+e !ith the :onfig (ool only ta+e effect !hen the SAP
6et"eaver AS ;ava is startedC that is, you must restart the SAP 6et"eaver AS
;ava after maintaining settings.
(he :onfig (ool is called on the host on !hich the central instance of the SAP
6et"eaver AS ;ava is running. Authentication is performed using the logon to the
operating system of the host.
SAP et!ea"er A$ministrator
(he SAP 6et"eaver Administrator /6"A0 combines the most important
administration and monitoring tools for ;ava and ABAP systems in a ne!,
bro!ser)bases user interface. (he most important benefits offered by 6"A are4
. <ou no longer need to s!itch bet!een different tools for the administration,
troubleshooting and problem analysis of your entire SAP 6et"eaver system
landscape.
. #nstead, you have for ;ava, and increasingly for ABAP systems, a central,
cross)landscape administration tool !hich enables you to start and stop
instances, chec+ configuration settings and logs and monitor the correct
functioning of the components.
. 6"A displays all the monitoring infrastructure data, i.e. alerts together
!ith the current and historical values.
. (he B5# adheres to the current guidelines concerning interface design, is
easy to use, tas+)oriented and complete. #f you use "eb %ynpro, it runs
in the bro!ser.
"ith the SAP 6et"eaver Administrator, you log on to the http port of a SAP
6et"eaver AS ;ava instance. #t is therefore necessary that the SAP 6et"eaver AS
;ava instance is started. (he SAP 6et"eaver Administrator can be called using
the follo!ing 5E4 http488OechnernameP4Ohttp)PortP8n!a. #n this !ay, it can
be used for remote administration !ithout it being necessary to install additional
tools locally. Please note figure .SAP 6et"eaver Administrator ,.. (he figure
.SAP 6et"eaver Administrator 1. sho!s the special features of the tool.
6"A !as first shipped for SAP 6et"eaver -2 SP Stac+ ,1. An enhanced
version !as supplied for SAP 6et"eaver ?.- . 6"A !ill also be continuously
further developed in subse*uent releases and ne! administration and monitoring
functions !ill be added.
"ith the Iisual Administrator, you log on to the P2 port of an SAP 6et"eaver
AS ;ava instance. #t is therefore necessary that the SAP 6et"eaver AS ;ava
instance is started. (he Iisual Administrator can also be installed on a host on
!hich no SAP 6et"eaver AS ;ava instance is installed. #n this !ay, it can be used
for remote administration. <ou can use the Iisual Administrator to configure the
services and managers of all SAP 6et"eaver AS ;ava instances in the :luster.
(he changes to the selected parameters ta+e effect during runtime. <ou can use
the Iisual Administrator to start or stop services. <ou cannot change the Iirtual
'achine parameters !ith the Iisual Administrator. =or information about this,
see the figure .Iisual Administrator ,.. (he figure .Iisual Administrator 1.
sho!s the special features of the tool.
#f necessary, you can use the Iisual Administrator to shut do!n an SAP
6et"eaver AS ;ava instance by stopping the ;ava dispatcher and the server
processes. =or an add)in installation you can use the dynamic profile parameter
rdisp=58ee/start of the SAP 6et"eaver AS ABAP instance to deactivate the
starting of the SAP 6et"eaver AS ;ava instance.
Shell Console A$ministrator
"ith the Shell :onsole Administrator, you log on to an SAP 6et"eaver AS ;ava
instance. #t is therefore necessary that the SAP 6et"eaver AS ;ava instance is
started. (o use Shell :onsole Administrator, you must log on via (elnet at the SAP
6et"eaver AS ;ava (elnet port. (elnet is available on many operating systems
and can therefore be used for remote administration !ithout additional installation.
<ou can use Shell :onsole Administrator to display basic information for an SAP
6et"eaver AS ;ava system in a simple !ay. Shell :onsole Administrator is also
suitable for starting and stopping services. <ou cannot change I' parameters
using Shell :onsole Administrator. =or information about this, see the figure
.Shell :onsole Administrator ,.. (he figure .Shell :onsole Administrator 1.
sho!s the special features of the tool.
#f necessary, you can use the Shell :onsole Administrator to shut do!n the SAP
6et"eaver AS ;ava instance by stopping the ;ava dispatcher and the server
processes.
<ou can use the Shell :onsole Administrator to configure the services and
managers of all ;ava instances in the :luster. #t is significantly easier to ma+e the
changes to managers and services !ith the Iisual Administrator. (herefore, only
specialists should ma+e changes to managers and services using Shell :onsole
Administrator.
Calling the A$ministration an$ Con-guration Tools
(his section describes the features of calling the different tools.
#f you are using an SAP system on the iSeries platform, please refer to SAP 6ote
,-77-.M ) iSeries4 Special =eatures of (ool 5se in the ;1EE environment.
Con-g Tool
(he :onfig (ool is a tool for administering and configuring SAP 6et"eaver AS
;ava. (he :onfig (ool is started !ith the call conigtool;bat at operating system
level of the host on !hich the central instance of SAP 6et"eaver AS ;ava is
running. (he file conigtool;bat is stored under the follo!ing path at operating
system level4 GusrGsapGDSIDEGDcentral instanceEG58eeGconigtool. 6o user or
pass!ord are re*uired to call the :onfig (ool. <ou must still confirm !hether
you !ant to use the default database settings or !hether you !ant to change
them. (he :onfig (ool is available to you to edit the parameters /see the figure
.:onfig (ool ..0.
%uring the start process of the SAP 6et"eaver AS ;ava instance, the parameters
for the start and running operation are read from the database and copied to the file
system. "ith the :onfig (ool, these parameters are maintained in the database. #t
is therefore necessary that the database is running so that the :onfig (ool can read
the current parameters from the database. "hen the :onfig (ool is opened, you
can see and change the default database settings by choosing the +o button. (he
!indo! contains the connection data for the database. (his is maintained during
the installation process. <ou can read in the parameters currently saved in the
database at any time !ith the connect to DB button.
SAP et!ea"er A$ministrator
"ith the SAP 6et"eaver Administrator, you log on to the http port of an SAP
6et"eaver AS ;ava instance. #t is therefore necessary that the SAP 6et"eaver
AS ;ava instance is started. (he SAP 6et"eaver Administrator can be called
using the follo!ing 5E4 http488OechnernameP4Ohttp)PortP8n!a. (he SAP
6et"eaver Administrator start page displays the three areas Administration,
:onfiguration and 'onitoring.
>isual A$ministrator
(he Iisual Administrator is a tool for administering and configuring SAP
6et"eaver AS ;ava. "ith the Iisual Administrator, you log on to an SAP
6et"eaver AS ;ava instance. (his must therefore already be running ) other!ise
the logon process is unsuccessful. (he Iisual Administrator is started !ith the
call go;bat at operating system level. (he file go;bat is stored under the follo!ing
path at operating system level4 GusrGsapGDSIDEGDcentral instanceEG58eeGadmin.
Once the Iisual Administrator has been started, a selection !indo! appears, in
!hich you select the system to !hich you !ant to log on. #f you are starting
the Iisual Administrator for the first time, you must first create a system entry
in the selection !indo!. :hoose the button +e#. A ne! !indo!, in !hich you
define a connection to your system, appears /see the figure .Iisual Administrator4
Eogon.0. <ou enter, for e$ample, the name of your system here and choose, for
e$ample Direct Connection 'o a Dispatcher +ode.
A !indo! no! appears in !hich you specify the logon parameters such as the
user name of the administrator, the host name, and the P2 port for the Iisual
Administrator /see also .Iisual Administrator4 Eogon ne! :onnection.0. <ou
have no! created a system entry in the logon !indo!.
<ou can no! logon to the system by choosing the Connect button, entering the
pass!ord on the logon !indo!, and choosing Connect. <our logon is successful
as soon as a green diamond appears in the status bar and the value ,--G is reached
in the status bar. See also the figure .Iisual Administrator4 Eogged On..
Shell Console A$ministrator
<ou can perform some administration tas+s for SAP 6et"eaver AS ;ava !ith
Shell :onsole Administrator. (o do this, you must specify the host name and the
(elnet port of the SAP 6et"eaver AS ;ava instance !hen you call Shell :onsole
Administrator. <ou are then prompted to log on to the SAP 6et"eaver AS ;ava,
as sho!n in the figure .Shell :onsole Administrator.. <ou use the same user and
pass!ord to do this as for the Iisual Administrator. Since you are logging on to
the SAP 6et"eaver AS ;ava instance, this must already be running.
Lesson 7
Access to 'elp
Con-guring the Online Documentation
Access to the Documentation with the SAP .i%rary
(he SAP Eibrary, !hich is also +no!n as the online documentation, is an
important source of information, and contains information about all relevant
topics in the SAP environment. #nstalling the online documentation locally or
company)!ide helps users to !or+ more effectively !ith the SAP system.
By choosing SAP Eibrary in the &elp menu, you can display the online
documentation. (he terms SAP Eibrary and online documentation are often used
synonymously. (he SAP Eibrary of an SAP system al!ays contains the complete
online documentation for the system. =or SAP 6et"eaver, for e$ample, the SAP
Eibrary currently offers access to more than ,-,--- documents.
5sing the SAP Eibrary, you can easily search the online documentation, access a
glossary, and call an introduction to using SAP systems /.Betting Started.0.
(he online documentation is provided in various languages and, if the calling of
help has been correctly configured /as e$plained in the follo!ing pages0, is called
up in the userHs logon language.
'tml'elp*ile
"ith this help type, the documents are stored in :ompiled D('E format
/Q.:D'0. (he files are made available using a file server and are displayed
!ith the D('E Delp Iie!er. :ompiled D('E is a format developed
by 'icrosoft for storing D('E files in compressed format. (he storage
space re*uirement for :D' files is around a tenth of the re*uirement
for uncompressed D('E files and is comparable to the re*uirement for
"inDelp files. 'icrosoft introduced the D('E Delp Iie!er as a successor
to "inDelp. #t is based on 'icrosoft #nternet E$plorer. (his type of help can
only be used on 'icrosoft "indo!s .1 bit front end platforms. (his type
of help provides a full te$t search for all documents /global search0 or in
the documents of the current help file /local search0. #t is possible to print
multiple documents concurrently.
Plain'tml'ttp
"ith this help type, the documents are stored in the standard D('E format.
(he documents are made available using a "eb server and are displayed
!ith a standard "eb Bro!ser. (his help type can be used on all front end
platforms and the documentation is displayed using a standard "eb bro!ser
/'icrosoft #nternet E$plorer or 6etscape0. (his help provides a full te$t
search in all documents /global search0 and allo!s you to print individual
help documents.
Plain'tml*ile
(his /most simple0 help type also stores the documents in standard D('E
format. (he documents are made available using a file server and are
displayed !ith a standard "eb bro!ser. (his help variant can be used on all
front end platforms and allo!s you to print individual help documents.
Dynamic'elp
%ynamicDelp can be used on all front end platforms. #t uses the standard
D('E format for its filesC the file access ta+es place using the Lno!ledge
"arehouse server. (he documents are displayed in a standard "eb bro!ser.
=or more information, see the online documentation for the Lno!ledge
"arehouse.
Criteria for Selecting the 'elp Type
(he decision on !hich help type to install in a particular SAP system depends
mainly on the operating system of the front end client.
. #f you only use front ends !ith 'icrosoft "indo!s, !e recommend you
install the help type DtmlDelp=ile. (his help type offers a broader range
of search and print functions than the other t!o help types. <ou can of
course install each of the other help types. #f you deploy various front end
platforms at the same time and therefore have to choose a different help
type to DtmlDelp=ile, you can still use the DtmlDelp=ile help type !ith the
clients under 'icrosoft "indo!s /see section4 Eocal Override of the Delp
Settings on the =ront End0.
. #f you use different front end platforms to 'icrosoft "indo!s, you should
install PlainDtmlDttp since this help type offers a full te$t search through
the SAP Delp Portal.
. #f you have no "eb server and deploy different front end platforms to
'icrosoft "indo!s .1)Bit, you have to use the help type PlainDtml=ile.
. #f you !ant to call the SAP documentation from the SAP B5# for "indo!s
/"in B5#0, the SAP B5# for D('E /"eb B5#0, or a bro!ser)based SAP
application, you cannot use the help type DtmlDelp=ile to do so.
4int" <ou can display the D('E)based help !ith a "eb bro!ser on all
front end platforms supported by SAP. (here are certain prere*uisites or
restrictions, depending on the respective platform, ho!ever. <ou !ill
find further information in the installation guide for the help and in the
SAP 6otes 3M3.?M . Application help !ith ;ava B5# on 5ni$ /'=0 and
3?7.J2 . :alling SAP documentation on a 'A: OS 9.
"ith the #'B activity SAP Customi6ing Implementation !uide.SAP +et"ea%er
. !eneral Settings . Setting Iariants or &elp )SAP Librar,*, you define !hich
variant(s) of the online help are available to the users of the SAP system.
Caution" "ithout a corresponding configuration in transaction S,.,
it is not possible to call help successfully. (his is true even if there is
a correctly maintained local sapdoccd;ini file. #n this case, the system
displays the message 'o !ocumentation availa(le.
As of SAP 8. 2.7:, you no longer need to maintain profile parameters for the
online help. %uring an upgrade from SAP Basis 2.$ to SAP "eb Application
Server 7.1- or higher, the values stored in the eu8i!b8... profile parameters for help
type, storage location, and language version of the help files are read and copied as
a settings variant by an 9PA program. Since these automatically created settings
variants /BE6EA(E%TB<T9PA ...0 cannot be changed, you must create ne!
settings variants that copy the specifications for the storage location of the help
files from the automatically created entries, as long as they are still valid, and
then delete the automatically generated settings variants. 5se descriptive names
!hen creating ne! settings variants.
S&9?@ an e#ample for the help type 'tml'elp*ile;
. Iariant4
Documentation or a different descriptive te$t
. Platorm4
!?AC (his setting is also appropriate for 'icrosoft"indo!s 6( front ends,
for e$ample /See SAP 6ote ...3M20
. Area
Documentation /is automatically replaced by i#bhelp0
. Path
=or e$ample4 BBtw$fCCCCBDo0uBDEEBhelp$ata /!ithout language
selection0
. Language
) English, selected using the =2 help /this is automatically replaced !ith E+0.
. Deault
Setting this indicator in this e$ample means that the help type DtmlDelp=ile
is the default help in the area %ocumentation for "6.1 front ends.
(he above e$ample specifies that on 'icrosoft "indo!s)based front ends, the
.documentation. help variant !ith its settings determines the help that is usually
called. #n this case, this means that the online documentation is called from a
net!or+ drive BBt/!fCCCCB0okuB)++Bhelp!ataBE'. 6ote that the language #%
!as automatically added to the path.
=or front ends of other types /for e$ample, non)"indo!s based0, another help
type can be called by default. =or these other front ends, you must also set a
separate settings variant as the default.
By maintaining and providing multiple settings variants, you can ma+e the online
help available in various !ays. A settings variant specifies a configuration of help
type, storage location of the help files /server and8or path0 and the language
version of the help files for a particular front end platform. #f you provide
multiple setting variants for a front end platform, the users can choose bet!een
these variants from the menu &elp . Settings /E-tended &elp tab page0.
#n every settings variant, you must specify the Area !here it applies, in addition
to the front end platform. (he area indicates the application area of the SAP
Lno!ledge "arehouse from !hich the contents to be displayed are ta+en. (he
area %&B4E$P /documentation0 contains the online documentation delivered to
all customers. :ustomers that use the SAP Lno!ledge "arehouse can also define
settings variants for the area #"B(A#6 /training0.
A default setting for the selection of online documentation must be made in the
system for every utilized front end platform. #f multiple help types are installed,
the end user can choose bet!een these variants from the menu &elp . Settings
/E-tended &elp tab page0.
SAP 'elp Portal
(he SAP Delp Portal provides #nternet)based access to the available online
documentation for SAP soft!are solutions. (he Delp Portal can be accessed from
every "eb)capable front end !ithout logon. (he documentation provided can be
accessed very efficiently using a full te$t search.
SAP Ser"ice ,ar0etplace
(he SAP homepage http488!!!.sap.com provides information about all SAP
Solutions and about SAP as a company. (his information is public and can be
accessed by anyone.
#n addition to this, SAP provides various services, detailed information, and
other offers for customers and partners on the SAP Service 'ar+etplace at
http488service.sap.com. Access to the SAP Service 'ar+etplace /S'P0 is free of
chargeC ho!ever, it is protected by a user name and pass!ord logon. (here is at
least one person !ith access to the S'P at every customer. (his person can create
additional users and assign certain authorizations to those users.
(here are t!o simple options available to simplify navigation4
. Personalization of the initial screen
. 6avigation using >uic+ Ein+s, such as http488service.sap.com8smp. >uic+
Ein+s are simply added to the basic address after a .8.. #n this case4 .smp..
#mportant >uic+ Ein+s4
. ,user6a!min4 user administration on the S'P /for .your. users0
. ,sscr4 <ou can obtain SAP Soft!are :hange egistration +eys here
. ,notes4 (he online access to SAP 6otes is available using this >uic+ Ein+
. ,s/!c4 <ou can obtain patches, updates, and other soft!are for your SAP
systems here
. ,message4 (his >uic+ Ein+ allo!s you to create a message to SAP
. ,servicecat4 (he service catalog displays a list of the services offered by SAP
. ,instgui!es4 <ou can find installation guides for the various SAP solutions
here
. ,net/eaver4 (his >uic+ Ein+ leads to the ne!est information about SAP
6et"eaver.
. ,e!ucation4 <ou can find information about the SAP training courses
available !orld!ide in an online catalog here
Lesson 8
Printer Connection in AS ABAP
Con-guring Printers in SAP Systems
Printing from SAP Systems
(here are various document classes in the SAP system /such as report lists,
SAPscript or SAP Smart =orms documents0. Although the !ay in !hich
documents are created may be completely different, the output on paper is al!ays
performed using the same mechanism in t!o steps4 =irst a spool re<uest is
created. (he spool re*uest contains device)independent print data and includes
administrative information /such as author, date, number of copies0 and the actual
print data. Only !hen the spool re*uest is to be output on a particular device is an
output re<uest created. (he device)independent print data from the spool re*uest
is converted to the printer language that the selected output device understands.
(his procedure allo!s the user to display a spool re*uest before output. (here can
also be several output re*uests for one spool re*uest. (his can avoid the user
having to recreate /possibly !ith a great deal of effort0 a spool re*uest, if, for
e$ample, the toner in a printer is e$hausted, or the !rong paper !as in the tray.
(he user can of course create a spool re*uest and an output re*uest at the same
time /immediate print0 by choosing the Print out immediatel, option.
(he actual document content of a spool re*uest is stored in 5emSe /for temporary
se*uential objects0, for !hich you define the storage location !ith the profile
parameter rspo=store/location.
. Ialuedb /the default value04 Spool re*uests are stored in database table
'S'@? /Advantage4 bac+up as part of the database0.
. Ialue!4 Stored at operating system level in the global directory /advantage4
performance0.
'ote" <ou can also specify the storage location individually for the output
device in transaction SPA% /menu path Edit . Data Storage0.
SAP 6ote 1-,?7 contains additional possible values for rspo=store/location.
(he creation of an output re*uest prompts the SAP spool system to send a /usually0
printer)dependent, completely formatted data stream to a printer using an operating
system spooler /OS spool0. (his means that the addressed printer model must be
+no!n to the SAP system. %efinitions of this type are described as !evice types.
#f a printer cannot be controlled at operating system level, it cannot be used from
the SAP system, either.
(here are many !ays in !hich a spool !or+ process can reach an operating system
spooler. (he most important of these connections, described as access metho!s,
are introduced in the follo!ing sections.
A characteristic of local printing is that the spool /ork process an! operating
system spool are running on the same host. #t is irrelevant !hether the printer
is directly connected to this host, or is reached over a net!or+ /and possibly
another print server0. (he spool !or+ process passes on its data locally, that is
on the same host.
. On3'%: systems, the print data !ith access metho! $ is output using
operating system methods /for e$ample, !ith the commands lp or lpr0. (he
specific synta$ is stored in profile parameters.
. 5nder#icrosoft &in!o/s, the data !ith access metho! C is passed
directly to the operating system print AP#.
Eocal printing is the fastest and most reliable connection from the SAP system
to the operating system. As soon as the spool !or+ process has transferred its
data, it can deal !ith ne! output re*uests ) even if the operating system spooler
may still be occupied.
<ou can configure multiple spool !or+ processes for an SAP instance. (his has
) irrespective of the access method ) conse*uences for the output se<uence.
%ifferent spool re*uests for the same printer may be printed in a different order
to that in !hich they !ere created. #f you re*uire output in se*uence, you can
specify this for individual printers. Do!ever, a setting of this type reduces the
ability to process printouts in parallel. =or more information about this topic,
see SAP 6ote ,-M?JJ.
&emote Printing
"ith remote printing, the spool !or+ process and operating system spooler are
running on different hosts. #n e$actly the same !ay as !ith local printing, it is
irrelevant from the SAP systemHs point of vie! !hether the printer is directly
connected to the remote host, or is reached using another net!or+ connection.
(ypical scenarios for remote printing are4
. 6et!or+ printers provide their o!n operating system spoolers and are
directly connected to a computer net!or+. Printers of this type are directly
addressed from the SAP system using their names /access metho! 30.
. Access method 5 is also used if the remote host is a 56#9 system. SAP
6ote .J2-3 describes ho! access method 5 can be used for the various
56#9 versions.
. SAP provides the program SAPSprint for all hosts !ith 'icrosoft
"indo!s operating systems. SAPSprint is a "indo!s service capable of
multi)threading. Each output re*uest is processed in a separate, isolated
thread. (he output re*uests that SAPSprint receives from the SAP system
can thus be transferred to a particular printer individually. #f the printer is
not !or+ing, this does not disturb the printing of other output re*uests on
the other printers.
Access metho! S is usually used here /SAP protocol0, but access metho!
3 /56#9 Ber+eley protocol0 is also supported.
=or performance reasons, you should only use remote printing in a EA6
environment /not "A60 and should ensure that the operating system spoolers
are available.
*ront-en$ Printing
SAP users can output documents on their local printers using front6en! printing.
(hese local printers do not need to be individually defined in the SAP system.
ather the system administrator only needs to create a representative output device
for each operating system platform.
As of SAP "eb AS 7.1- you can use a ne! procedure for front)end printing )
front)end printing using control technology !ith access metho! G. (his no longer
re*uires an SAPlpd. =urthermore, the printer selection is not displayed in the SAP
system. A "indo!s printer selection !indo! is called directly from the control
instead. (echnically spea+ing, the ne! front)end printing is based on the control
that has been used in the SAP B5# for a long time.
:ontrols are %EEs that run in the process conte$t of the SAP B5#. (he ne!
print control receives the print data and transfers it to the printing system for
the operating system. #n contrast to conventional front)end printing !ith access
method =, front)end printing !ith control technology and access method B that
is available as of SAP "eb AS 7.1- offers the advantage that front)end printing
using SAP B5# for ;ava can also be set up independent of the platform.
=ront)end printing !ith control technology /access method B0 also enables
front)end printing from the SAP B5# for ;ava on non)"indo!s)based platforms,
such as 56#9. Printing using the "indo!s (erminal Server is also made easier
!ith front)end printing using control technology.
5seful information about front)end printing !ith control technology is available
in SAP 6ote M1,3,J.
(he processing of front)end printing is also performed, as !ith the other output
methods, using a spool !or+ process. (here can, therefore, be conflicts bet!een
regular and front)end print re*uests. <ou specify the ma$imum number of spool
!or+ processes that can be used for front)end printing for each SAP instance using
the profile parameter rdisp=#p/no/3ro/ma- /the default value is ,0.
=ront)end printing is suitable for output on local printersC ho!ever, it is not for
production or mass printing.
Of course, front)end printing re*uires a connection to the front)end P:. Do!ever,
this method cannot be used for bac+ground processing.
"hen using access method = /for releases up to and including 2.7:0, the print data
stream is transferred to the host on !hich the SAP B5# of the user is running. (his
method can be used for front)end P:s !ith different operating systems4
. #n the case of 'icrosoft "indo!s operating systems, the saplpd transfer
program receives the data stream and for!ards it to the default printer of
the 'icrosoft "indo!s output control /or a different printer, if this is
configured0. #f necessary, saplpd is started automatically.
. "ith other operating systems /56#9, Apple 'acintosh, and so on0, the data
is transferred directly to the operating system spooler. #n this case, the printer
name /identical for all users0 must be specified in the device definition.
=or more information, see SAP :omposite 6ote ,1M,-3. SAP 6otes .3,1.-
/before SAP "eb AS 7.2-0 and ??,7M. /as of SAP "eb AS 7.2-0 describe
front)end printing !ith the /standalone0 SAP #(S, or !ith the integrated #(S !hen
using the SAP B5# for D('E. SAP 6ote ,3-3.. contains information about
front)end printing !hen using "indo!s (erminal Server.
#f you use SAP B5# for D('E and print on your front end, you need access
method =. 5sing this print method, the print data should be sent to the bro!ser and
displayed. <ou can then print the document on your front end.
Creating Output De"ices
(he configuration of the spool system is a system administration tas+. (he central
tool for this is transaction SPA% /menu path 'ools . CC(S . Print . Spool
Administration0.
"ith front)end printing !ith control technology /access method B0, the printer is
given a generic name in the SAP system, and is assigned to the physical device
//DE3AUL'. Since the models used as front)end printers can vary considerably,
the device type S"I+ is assigned for "indo!s front ends. "hen printing !ith
SAP B5# for ;ava on other operating systems, you have to use a corresponding
device type, such as PostScript.
#f front)end printing ta+es place using SAP B5# for D('E !ith access method =,
the device type PD37 is selected. (he print data is then transferred to the front)end
bro!ser as a PostScript document and can be printed locally.
(o create an output device, call transaction SAP% and choose 0utput De%ices on
the De%ices = Ser%ers tab page. #f there are a large number of devices in your
system already, you can restrict the output list in the field ne$t to the button /for
e$ample .PQ.0. #mportant information for an output device4
7utput !evice
6ame, ma$imum of .- characters long /case)sensitive0.
Short name
=or internal system purposes /can be automatically generated0.
0evice type
Printer model8family /more information about this belo!0. (he device type
S"#6 transfers the SAP system format to the 'icrosoft "indo!s printer
driver. (his is useful, for e$ample, if various printers are used for front)end
printing in a 'icrosoft "indo!s environment.
Spool server
SAP application server !ith spool !or+ processes or logical server.
$ocation
=or e$ample, building and room number /so that users can find their output0.
#essage
5sed to temporarily override the location /such as .#s currently in
maintenance.0.
$ock printer in SAP system
Output re*uests for printers for !hich this indicator is selected are created
but not transferred to the printer. (he user receives the message ;;;no
immediate printing.
4ost spool access metho!
Do! does a spool !or+ process contact the operating system spooler@
4ost printer
6ame of the printer at operating system level. 6ote that this name is
case)sensitive. 5nder 'icrosoft "indo!s, there must not be a space in the
printer name, and net!or+ printers are addressed using their 56: names
/in the format GGR78?4AGP480. (he specification FFD)*A+.T calls the
default 'icrosoft "indo!s printer /for e$ample, for front)end printing in a
'icrosoft "indo!s environment0.
4ost name
Only for local printing, is calculated automatically from the spool server.
0estination host
Only for remote printing. 6ame of the host on !hich the operating system
spooler is running.
Devi'e 3pes
(he SAP system uses a device type to format the output device)specific print
output.
4int" "hen reference is made to an output device in the SAP
environment, it does not necessarily mean a printer. An output device can
also be, for e$ample, an Output 'anagement System or an archiving
system.
"hen the spool !or+ process generates an output re*uest, it uses the specifications
of the device type. (hat is, the device type describes ho! print data should be
formatted for a particular output device.
(he follo!ing figure illustrates ho! a device type is created.
(he follo!ing list e$plains the terms from the above figure.
Page format
A page format describes the format of a printable page in the SAP system.
A large number of standard page formats are predefined in the system. #f a
device is to support additional format that are not delivered, you can define
ne! formats. :onsider !hen doing so that your output device must, of
course, be able to use the ne! format.
Dormat type
A format type describes ho! output should appear on paper. #t primarily
contains the formatting of the page format.
Dormat
A format is a device)specific implementation of a format type. (hat is, the
SAP system can use the description in a format to control a device correctly
to, for e$ample, perform an output on a page !ith the Eetter format. A
format type is therefore not device)specificC the format, on the other hand, is
a device)specific implementation of a format type.
Character set
A character set contains the characters that can be output by a particular
output device. (hat is, to be able to use a particular character set for a
selected printer model in the SAP environment, the device type assigned to
this printer model must contain this character set.
Print control
Print controls allo! the control of particular display options of output
devices, such as boldface, changing the font size, changing the font, and so
on. Print controls use device)specific control character se*uences. (hat is,
to create a ne! device type, the display options offered in the SAP system
must be stored !ith the control character se*uences that the selected printer
model supports. (he control character se*uences to be used can be found in
the device vendorHs documentation.
<ou can see that using devices for !hich no suitable device type e$ists in the SAP
system may mean a significant effort.
Do! do you assign the correct !evice type to your printer@
. #n the ideal situation, there is already a device type in your SAP system.
6ote that a separate device type is not re*uired for every printer model of a
vendor, but just for each model family.
. SAP 6ote MJ1M contains a list of all printers supported by SAP. (here is an
attachment for this SAP 6ote containing corresponding device types.
. =or many printers, you can use a generic format /such as PostScript0 for
!hich device types e$ist. #t is also possible that your printer can be addressed
in the same !ay as another model that is supported by SAP /compatibility
mode0.
. (here are drivers for the 'icrosoft "indo!s operating systems for
practically all printers on the mar+et. <ou can use these printers as output
devices !ith device type S"#6. (he conversion to a print data stream is
performed by the 'icrosoft "indo!s driver in this case.
. (he SAP system contains all of the tools re*uired to create your o!n device
types or to adjust copies of e$isting device types. %etailed +no!ledge of the
SAP spool system and the printer control are re*uired to do this. <ou should
!eigh up the e$pense against the purchase of supported printers.
,anaging Spool &e2uests
,anaging Spool an$ Output &e2uests
(o maintain spool an! output re<uests, call the Output :ontroller /transaction
SP-, or choose S,stem . Ser%ices . 0utput Controller0. #f you only !ant
to chec+ the status of your o!n spool re*uests, choose S,stem . 0#n Spool
Re>uests /transaction SP-10.
(ransaction SP-, provides many selection criteria for selecting particular spool
or output re*uests. Every user can individually and easily define the selection
criteria that he or she re*uires using the 3urther Selection Criteria;;; function.
#t is even possible to monitor spool and output re*uests on other SAP systems.
(o do this, enter a valid =: connection in the S,stem +ame field. #f this field
remains empty, all systems that !ere selected for remote monitoring using
transaction S1- /table AE:O6SEB0 are addressed.
(he displayed list sho!s all spool or output re*uests that match your selection
criteria. (he list is created using the SAP Eist Iie!er /AEI0. (his allo!s you to
change the appearance of the list as you desire. (his means that you can sho! and
hide columns, sort columns, or create variants.
(he follo!ing indicators specify the status of a spool re*uest4
6
6ot yet sent to the operating system /no output re*uest e$ists0.
2
Spool re*uest is still being created /stored in spool system0.
&aiting
(he output re*uest has not yet been processed by the spool system.
Proc*
A spool !or+ process is formatting the output re*uest for printing.
Print*
(he output re*uest is being printed by the operating system spooler. #f the
*uery at the host spooler is not activated, this status is sho!n for around a
minute.
Compl*
(he output re*uest has been printed. #f the *uery at the host spooler is not
activated, the status changes to Compl; as soon as the output re*uest is
transferred to the host spooler.
@DEA
(here are output re*uests !ith various statuses.
Pro(lem
#ndicates an error not of a serious nature /such as incomplete character set0.
(his re*uest !as still printed.
Error
#ndicates a serious error /such as a net!or+ error0.
5ime
A particular time !as specified for the output of the re*uest by the re*uest
creator.
#f you select the status of a spool re*uest, the system displays the associated
output re*uests. =or the output re*uests of multiple spool re*uests, select these
and choose 0utput Re>uests /or choose 3A0.
=or every unsuccessful output re*uest, a log is !ritten that you can use for error
analysis.
egular deletion of old spool re*uests and monitoring the consistency of the spool
database are system administration tas+s.
(o !elete ol! spool re<uests, schedule the ABAP program RSP07@47 !ith
an appropriate variant as a perio!ically running bac+ground job. =or more
information about RSP07@47, see SAP 6ote ,.-J?M.
(o check the consistency of the spool !ata(ase, schedule the ABAP program
RSP07@4? !ith an appropriate variant as a !aily running bac+ground job. =or
more information about RSP07@4?, see SAP 6ote JM-73.
=or information about the reorganization of (emSe and spool, see also SAP
6ote 2M2--.
Lesson 9
+ser A$ministration Concept
Basics of +ser A$ministration
(he concept of the user master record and the authorization concept are e$plained
in more detail belo!. Both of these are important to obtain a better understanding
of SAP systems.
(he term user usually means user #% here. People log on to an operating system,
a database, or an SAP system using a user8pass!ord combination. Operating
systems, databases, and SAP systems usually have different authorization
concepts. #f a user8pass!ord combination is created in an SAP system for a person,
this does not mean that it is possible to log on to the operating system of a host
!ith the same user8pass!ord combination. Do!ever, it is possible that identical
user8pass!ord combinations are created for SAP systems and operating systems.
'ote" 5ser re*uests are processed by SAP !or+ processes. (hese !or+
processes all use a common user to access the database.
(his unit deals e$clusively !ith SAP users, !hich people use to log on to a client
of an SAP system. 5sers and authorization data are client)dependent.
Access to the operating system level of the SAP "eb Application Server and
the database server must be protected, or the operation or the data of the SAP
systems could be threatened.
A person can log on to a client of an SAP system if they +no! the user8pass!ord
combination for a user master record.
#n the SAP system, there is an authorization chec+ every time a transaction is
called. #f a user attempts to start a transaction for !hich he or she is not authorized,
the system rejects the user !ith an appropriate error message.
#f the user starts a transaction for !hich he or she has authorization, the system
displays the initial screen of this transaction. %epending on the transaction called,
the user enters data and performs actions on this screen. Additional authorization
chec+s are made for data and actions that are to be protected.
5sers are assigned authorizations using roles. (he authorizations are combined
in roles and the roles are entered in the user master record. (his is e$plained in
more detail later in this unit.
(he user type is an important property of a user. %ifferent user types are available
for different purposes4
0ialog
A normal dialog user is used for all logon types by just one person. %uring a
dialog logon, the system chec+s for e$pired8initial pass!ords, and the user
has the opportunity to change his or her o!n pass!ord. 'ultiple dialog
logons are chec+ed and, if appropriate, logged.
System
5se the S,stem user type for dialog)free communication !ithin a system or
for bac+ground processing !ithin a system, or also for =: users for various
applications, such as AEE, "or+flo!, (ransport 'anagement System,
:entral 5ser Administration. #t is not possible to use this type of user for
a dialog logon. 5sers of this type are e$cepted from the usual settings for
the validity period of a pass!ord. Only user administrators can change the
pass!ord.
'ote" See also SAP 6ote 711272.
Communication
5se the communication user type for dialog)free communication bet!een
systems. #t is not possible to use this type of user for a dialog logon. (he
usual settings for the validity period of a pass!ord apply to users of this type.
Service
A user of the type Ser%ice is a dialog user that is available to a larger,
anonymous group of users. #n general, you should only assign highly
restricted authorizations to users of this type. Service users are used, for
e$ample, for anonymous system accesses using an #(S or #:= service. (he
system does not chec+ for e$pired8initial pass!ords during logon. Only the
user administrator can change the pass!ord. 'ultiple logons are permitted.
Reference
Ei+e the service user, a reerence user is a general non)person)related user.
<ou cannot use a reference user to log on. A reference user is used only
to assign additional authorizations. <ou can specify a reference user for a
dialog user for additional authorization on the Roles tab page.
(o start user maintenance /transaction S5-,0, choose 'ools . Administration .
User (aintenance . Users.
<ou can create a ne! user master record by copying an e$isting user master record
or creating a completely ne! one. (he user master record contains all data and
settings that are re*uired to log on to a client of the SAP system. (his data is
divided into the follo!ing tab pages4
. Address4 Address data
. Logon data4 Pass!ord and validity period of the user, and user type. =or
further information about the pass!ord rules for special users, refer to SAP
6ote 711272,
. Deaults4 %efault values for a default printer, the logon language, and so on,
. Parameters4 5ser)specific values for standard fields in SAP systems,
. Roles and Proiles4 oles and profiles that are assigned to the user,
. !roups4 =or the grouping of users for mass maintenance.
<ou must maintain at least the follo!ing input fields !hen creating a user4 $ast
name on the Address tab page, initial pass/or! and identical repetition of
pass/or! on the Logon Data tab page.
Authorization Concept
Authorization O%Gects an$ Authorization Chec0s
5nderstanding the SAP authorization concept re*uires +no!ledge of the role and
the authorization profile in the user master record. (his lesson provides you !ith
the necessary +no!ledge to be able to create your o!n roles and authorizations.
Actions and the access to data are protected by authorization objects in the SAP
system. (he authorization objects are delivered by SAP and are in SAP systems.
(o provide a better overvie!, authorization objects are divided into various object
classes.
Authorization objects allo! comple$ chec+s that involve multiple conditions
that allo! a user to perform an action. (he conditions are specified in
authorization fields for the authorization objects and are A6% lin+ed for the
chec+. Authorization objects and their fields have descriptive and technical names.
#n the e$ample in the figure, the authorization object .5ser master maintenance4
5ser Broups. /technical name4 S/USER/!RP0 contains the t!o fields .Activity.
/technical name AC'I'0 and .5ser Broup in 5ser 'aster. /technical name4
CLASS0. (he authorization object S/USER/!RP protects the user master record.
An authorization object can include up to ten authorization fields.
An authorization is al!ays associated !ith e$actly one authorization object and
contains the value for the fields for the authorization object. An authorization
is a permission to perform a certain action in the SAP system. (he action is
defined on the basis of the values for the individual fields of an authorization
object. E$ample4 Authorization B in the graphic for the authorization object
S/USER/!RP allo!s the display of all user master records that are not assigned
to the user group SUPER. Authorization A, ho!ever, allo!s records for this user
group to be displayed.
(here can be multiple authorizations for one authorization object. Some
authorizations are delivered by SAP, but the majority are created specifically for
the customerHs re*uirements.
"hen a user logs on to a client of an SAP system, his or her authorizations are
loaded in the user conte$t. (he user conte$t is in the user buffer /in the main
memory, *uery using transaction code S5370 of the application server.
"hen the user calls a transaction, the system chec+s !hether the user has an
authorization in the user conte$t that allo!s him or her to call the selected
transaction. Authorization chec+s use the authorizations in the user conte$t. #f
you assign ne! authorizations to the user, it may be necessary for this user to
log on to the SAP system again to be able to use these ne! authorizations /for
more information, see SAP 6ote 231J-2 and the documentation for the parameter
auth=ne#/buering0.
#f the authorization chec+ for calling a transaction !as successful, the system
displays the initial screen of the transaction. %epending on the transaction, the
user can create data or select actions. "hen the user completes his or her dialog
step, the data is sent to the dispatcher, !hich passes it to a dialog !or+ process
for processing. Authority chec+s /AU'&0RI'1-C&EC<0 that are chec+ed during
runtime in the !or+ process are built into the coding by the ABAP developers for
data and actions that are to be protected. #f the user conte$t contains all re*uired
authorizations for the chec+s /return code A -0, the data and actions are processed
and the user receives the ne$t screen. #f one authorization is missing, the data
and actions are not processed and the user receives a message that his or her
authorizations are insufficient. (his is controlled by the evaluation of the return
code. #n this case, it is not e*ual to -.
All authorizations are permissions. (here are no authorizations for prohibiting.
Everything that is not explicitly allo/e! is for(i!!en* <ou could describe this
as a .positive authorization concept..
ole 'aintenance /transaction P=:B, previously also called Profile Benerator or
activity groups0 simplifies the creation of authorizations and their assignment to
users. #n role maintenance, transactions that belong together from the companyHs
point of vie! are selected. ole maintenance creates authorizations !ith the
re*uired field values for the authorization objects that are chec+ed in the selected
transactions.
A role can be assigned to various users. :hanges to a role therefore have an effect
on multiple users. 5sers can be assigned various roles.
(he user menu comprises the role menu/s0 and contains the entries /transactions,
5Es, reports, and so on0 that are assigned to the user through the roles.
<ou can access role maintenance !ith transaction P=:B or by choosing 'ools .
Administration . User (aintenance . Role Administration . Roles. Enter the
name of the role and choose the icon for Create or Change. :hoose the (enu
tab page.
Select and change functions4 (he menu tree can be adjusted for the individual
roles as re*uired.
<ou can insert transactions into the tree structure or delete them from it.
By choosing the Report button, you can integrate Reports. #n this case role
maintenance creates transaction codes /if they do not already e$ist0 !ith !hich the
reports can be called.
By choosing the 0ther button, you can add %nternet a!!resses or links to files
/such as tables or te$t files0. "hen integrating files, you must use the storage paths
instead of 5Es. <ou can also specify B" "eb reports, and lin+s to e$ternal mail
systems and Lno!ledge "arehouse.
:hange menus4 <ou can create, move, delete, and rename directories and
subdirectories as re*uired. <ou can use the %rag&%rop function in role
maintenance.
ole maintenance automatically creates the authoriFations that are associated
!ith the transactions specified in the menu tree. Do!ever, all authorization values
must be manually checke! an! a!>uste! if re<uire! in accordance !ith the
actual re*uirements and authorities. (he system administrator is responsible
for this tas+, together !ith the appropriate user department. "hen using
organizational levels, you do not carry out maintenance directly in the field, but by
means of the .0rg; Le%els;;. button /:trlF=M0.
:hoose the Authori6ations tab page and then Displa, Authori6ation Data or
Change Authori6ation Data, depending on the maintenance mode. :hec+ the
scope and contents of the authorizations.
#f these are proposed by the system, a green traffic light in the authorization
overvie! indicates that role maintenance has supplied at least one proposal for
each authorization field. A yello/ traffic light indicates that the authorization
must be maintained manually after it has been created. ole maintenance does
not provide a default value for the authorization. (he above e$ample deals !ith
access to files. ole maintenance cannot .guess. !hether data access should only
be read access, or should be read and !rite access.
Some fields appear in many authorizations. A number of important fields !ere
therefore combined into organizational levels, such as the company code. #f you
maintain an entry for the organizational level using the .0rg; Le%els;;. button,
you thus maintain all the fields that appear there in one go. A re! traffic light
therefore indicates an unmaintained organizational level.
Once all authorizations are maintained as re*uired, the authorization profile can be
generated by choosing !enerate. #mportant4 (he second character of the profile
name must not be an underscore /.T.0 /see SAP 6ote ,72770. After creation,
this name cannot be changed. (he authorizations are combined in profiles. (he
profiles must be entered in the user master record /by the role maintenance0 for the
authorizations to ta+e effect for the user. (his is called user master comparison.
+sers an$ &oles
(he assignment of users to roles is performed in the role maintenance transaction
/transaction P=:B0 or in the user maintenance transaction /transaction S5-,0.
Select the tab page User and the user #%s to be maintained there. "hen selecting
user #%s, the system uses the current date as the start of the validity period of the
assignmentC it sets .,.,1.JJJJ as the end date. <ou can change both values.
5sers can be lin+ed !ith more than one role. (his can be useful if some activities
/such as printing0 are to be permissible across roles.
(he assignment of roles to users does not automatically grant the corresponding
authorizations to the users. (o assign the authorizations, you must first perform
a user master comparison, during !hich the roleHs profiles are entered in the
user master record.
A user master comparison determines !hether authorization profiles should
be added to or removed from the current user on the basis of his or her role
assignment. %uring a comparison, profiles are added to a user master due to roles
that have been added. #f role assignments are manually or time)dependently
removed, the corresponding authorization profiles are deleted from the user
master record.
(he comparison can be performed for every role in!ivi!ually. Select the role in
role maintenance. :hoose the 5sers tab page and choose 5ser econciliation. #n
the dialog bo$ that the system displays, choose :omplete econciliation.
#f multiple role assignments are to be updated, you can perform a corresponding
comparison in role maintenance by choosing Utilities . (ass comparison
/transaction P=5%0. <ou can individually specify the desired roles, or update all
assignments by entering the asteris+ /Q0 character.
<ou can also activate the periodic user master comparison in role maintenance
by choosing Utilities . (ass comparison. :hoose the option Schedule or check
5ob or ull reconciliation. (he system then displays a search !indo! for the
bac+ground job P3C!/'I(E/DEPE+DE+C1. #f it does not find a corresponding
job, you can create a ne! one. (he default value is that all user masters are
compared once every day.
Lesson 10
System ,onitoring an$ Trou%leshooting AS ABAP
,onitoring Architecture
Fundamentals
Initial questions about monitoring:
. "hy@
. (o ensure the efficient processing of business processes
. (o ensure system security and stability
. Do!@
. :entral and cross)system
. "ith an alert if an error occurs
. "ith help that provides cross)system detailed information if an error
occurs
. "ith !hich tool@
. "ith the help of the ::'S Alert 'onitoring #nfrastructure and the
special transactions connected to it
6o!adays, many components are usually involved in a business process. (hese
components /!hether produced by SAP or not0 must be monitored, as both a
gradual reduction in performance or a sudden brea+do!n of a component could
affect overall productivity. #t is a tas+ of the administrator to monitor the system
landscape regularly, and not only in the case of errors, but to ta+e preventative
action.
Dor example"
A file system !here files of the SAP database are stored is ,--G full. (he
database can no longer e$tend the tables in the files. A user performs
a business transaction in the conte$t of !hich a data record should be
asynchronously added to one of these tables. (he insert fails due to the
space problem in the file system. (he database error is seen as so serious
that the entire asynchronous update process is automatically deactivated.
All user sessions hang !ith the display of the hour glass. (he SAP system
hangs. #f the fill level of the file system had been monitored regularly, the
administrator could have ta+en action at the right time and system do!ntime
could have been avoided.
'onitoring should be organized as efficiently as possible. (here is not enough
time for an administrator to log on to each host component to chec+ its status.
An efficient monitoring structure should be able to display the entire system
landscape centrally at a glance. #f an error occurs, the person responsible is
automatically notified. (ools should be provided for the analysis of errors that
provide cross)system detailed information about the problem.
(he ::'S Alert 'onitoring #nfrastructure gives you the option of central and
efficient monitoring for SAP systems.
(he infrastructure must be installed on every component that is to be centrally
monitored. (his is automatically the case for SAP systems !ith soft!are
component SAPTBAS#S 2.- or above. SAP 8. ..$ systems and components on
!hich no SAP system is active are connected using ::'S agents.
Each component collects its o!n monitoring data using the infrastructure and
stores it locally in the main memory. (his part of the main memory is called the
monitoring segment. #ts size can be configured.
One SAP system is selected as the central monitoring system #t should have as
high a release level as possible and also be highly available. #n large system
landscapes, !e recommend that you include a separate system that is used only for
special tas+s such as central monitoring, :entral 5ser Administration, transport
domains controller, or the SAP Solution 'anager. =rom a performance point of
vie!, the !or+load of the central monitoring system increases only insignificantly,
as the collection of monitoring data is usually decentralized.
(he central monitoring system collects the monitoring data for the components
and displays it in various vie!s. #n this !ay, the administrator has a central vie!
of the entire system landscape. #f errors occur, the administrator can jump directly
from the central monitoring system /by =:0 to the relevant component to correct
a problem in a detailed analysis.
Details
(he ::'S Alert 'onitoring #nfrastructure consists of three parts4 %ata collection,
data storage, and administration.
At the !ata collection level, small subareas of an SAP system are monitored by
special programs called data collectors. %ata collectors can be ABAP, :, or ;ava
programs. (here are several hundred data collectors in ABAP alone. Each data
collector chec+s its subcomponent at regular intervals and stores the collected
monitoring data in the main memory of its host.
At the !ata storage level, the area of the main memory that contains the
monitoring data from the data collector is called the monitoring segment. As the
main memory data is al!ays over!ritten, it can be permanently copied to database
tables. <ou can then analyze the data later. (he data collection and storage
elements must be present on every component that is to be centrally monitored.
Caution" 6ote that every instances of an SAP system has its o!n
monitoring segment in shared memory. (his means that for an SAP
system !ith eight instances, there are eight different monitoring segments.
(he number of monitoring segments is determined by the number of
instances. "hether or not several instances run on the same hard!are, for
instance, is of no significance here.
(he a!ministration level allo!s the data from the monitoring segment to be
displayed and evaluated. SAP provides an e$pert tool, the ::'S Alert 'onitor
/transaction S1-0 as a display transaction. (he SAP Solution 'anager can sho!
the data in a business process)oriented conte$t. #f the system identifies a problem,
it can e$ecute a prepared automatic reaction, such as informing the responsible
person. (he analysis method then helps you to investigate the problem.
(he ::'S Alert 'onitoring #nfrastructure can be e$tended. <ou can integrate
your o!n components using data collectors that you have !ritten yourself.
(hird)party vendors and partners can e$port the monitoring data from the
monitoring segment using various interfaces.
(he ::'S Alert 'onitor /transaction S1-0 displays the monitoring data from
the monitoring segment in a tree structure. (he tree structure allo!s a clear display
!hen you are displaying a large number of measured values.
Any node in the tree is called a 'onitoring (ree Element /'(E0.
(he measured values that are collected by the data collectors are displayed at
the lo!est level in the leaves of the tree. (he leaves are +no!n as monitoring
attributes.
(hreshold values can be stored for a monitoring attribute. SAP delivers default
threshold values. Do!ever, in order to customize the monitor as !ell as possible
for your system environment, you should chec+ these threshold values, and adjust
them if re*uired.
'onitoring attributes are grouped at the second lo!est level using monitoring
objects. =or e$ample, the monitoring object program buer contains, among
others, the attributes hit rate and s#ap.
All other nodes in the tree serve to structure the monitoring objects in a logical and
clear !ay, so that you can easily find the monitoring attribute that you re*uire.
A ::'S monitor displays different subareas of the monitoring data. A monitor
can contain data from multiple SAP systems.
<ou can access the monitor sets in the system by calling the transaction S1-.
Alternatively, in the SAP Easy Access menu, choose 'ools . CC(S .
Control=(onitoring . CC(S (onitor Sets.
SAP delivers preconfigured monitor sets that you can use immediately. Every
monitor set bundles monitors that display various parts of the entire monitoring
architecture, by topic area. #t is therefore easier, for e$ample, to find the database
area.
(he delivered monitor sets can be different for each system. =or e$ample, an SAP
:' system contains a special set for monitoring :' scenarios. (here are, of
course, special data collectors connected !ith this. (hese are preconfigured and
delivered !ith an SAP :' system.
(he monitoring data that monitors display can overlap. (his means that the
monitoring attribute hit rate of the program buffer can appear in several monitors.
#f you change, for e$ample, the threshold value for this attribute in one of these
monitors, it is changed in all monitors.
Some monitors, such as the monitor A%ailabilit, and Perormance 0%er%ie# in
the monitor set SAP CC(S (onitor 'emplates, do not display any data at first.
(his can be due to the fact that special settings are re*uired to start the underlying
data collectors.
(o begin !ith, you !ill use the preconfigured monitors. Eater, you can also create
your o!n monitors that display e$actly the data that you re*uire for your daily
monitoring !or+.
<ou can open a monitor by selecting its name.
After you have opened a monitor, the corresponding monitoring data displays in
the form of a tree. By clic+ing the .F. sign beside an '(E, you can e$pand the
tree do!n to its leavesC the monitoring attributes.
Alert threshold values for triggering yello! and red alerts are assigned to
monitoring attributes. #f the threshold value condition is fulfilled, first a yello!,
and then, if there is further deterioration, a red alert is triggered. (he color of the
monitoring attribute is propagated to its higher)level node in the tree, !here the
most severe alert is for!arded /red is more severe than yello!0. (his means that
you can determine !hether there is an alert in the tree from the root of the tree.
>iews
(he monitor should support you in your daily !or+. After you have opened the
monitor, the follo!ing t!o vie!s are available to you, amongst others4
. (heCurrent Status vie! displays the monitor !ith the ne!est reported data.
. (he0pen Alerts vie! displays the monitor !ith its history information.
=or e$ample, during the previous night there may have been problems that are no
longer occurring. #n the Current Status vie!, the monitoring attribute is green,
!hile it is displayed as red in the 0pen Alerts vie!. After you have ensured that
there are currently no problems, you can then investigate problems that have
previously occurred. <ou can see the selected vie! in the upper part of the monitor.
<ou can s!itch vie!s by choosing the Current Status or 0pen Alerts buttons.
<ou can easily process the alerts that occurred in the past in the 0pen Alerts
vie!. By double)clic+ing an '(E in the tree, you open the Alert Bro!ser, !hich
displays a list of all alerts for the selected '(Es and all alerts belo! it in the tree.
(his means that if you double)clic+ the root of the tree, the system displays a list
of all alerts in the tree, sorted by red and yello! alerts.
Select an alert that you !ant to process. (hen choose the Start Anal,sis (ethod
button. (his starts the analysis method that is assigned to the '(E. (he analysis
method is a special tool that supports you !hen investigating problems. #t can be
transactions, or specially programmed function modules, or 5E calls. <ou,
therefore, do not need to remember all of the special tools, but simply use the
::'S Alert 'onitor as a central point of entry.
After you have clarified the problem situation, choose 3? to return to the Alert
Bro!ser. (hen choose Complete Alerts. (he processed alert is removed from the
list and is stored in a database table.
Proceed in the same !ay !ith the remaining alerts, until the list is empty. "hen
you ne$t use your monitor, only the ne!ly)occurred alerts display.
#f you !ant to display completed alerts again, choose Sho# Alert &istor, in the
Alert Bro!ser. :ompleted alerts display !ith the status Done.
/nclu$ing &emote Systems
(he monitors delivered by SAP display more detailed monitoring data for the local
SAP system. :entral system monitoring, on the other hand, has the advantage that
you can monitor the entire system landscape at one glance, and not just your
local system.
<ou can centrally monitor all components that have a ::'S monitoring
infrastructure. SAP has delivered this infrastructure since SAP Basis 2.-. (o
include components that do not have an infrastructure, you can use the ::'S
agent programs SAPC(?9 for SAP 8. ..$ and SAPCC(SR for non)SAP
components.
(o include an SAP system in a central monitoring architecture, you must define
an =: connection over !hich the monitoring data for the SAP system can be
transferred to the central monitoring system. (he data collection is performed
independently by the ::'S monitoring infrastructure on the remote system.
=rom a security point of vie!, it is strongly recommended that you define a second
=: connection bet!een the system !ith !hich the analysis tools can be started
in the remote system from the central monitoring system. #f a problem occurs,
you can therefore branch directly from the central system to the remote system
to analyze the situation in more detail.
SAP systems are included in the central monitoring system in transaction S1,.
<ou can start the transaction from the SAP Easy Access menu by choosing 'ools
. CC(S . Coniguration . Attributes and (ethods.
#n S1,, choose 'echnical Inrastructure . Conigure Central S,stem . Create
Remote (onitoring Entr,.
#n the 'arget S,stem ID field, enter the S#% of the SAP system to be monitored.
6o! create the t!o =: connections from the central monitoring system to the
monitored SAP system. :hoose !oto . R3C Connections. (he system displays
transaction S'3J. :reate t!o =: connections here. 'a+e sure that connection
is of type .?..
#n the =: connection for the transfer of the monitoring data, you can enter a user
of the type Communication !ith a pass!ord that is valid in the monitored SAP
system. (his means that !hen the central monitoring system re*uests monitoring
data from the monitored SAP system, it is provided !ithout the need for user
interaction. (he user :S'EB is intended for this purpose.
4int" <ou should create this user in the remote system in client +++
using a function in transaction S1,. (o do this, use the path 'echnical
Inrastructure . Conigure Central S,stem . Create CS(RE! User.
#n the =: connection that is used for the start of the analysis method, do not enter
a user, but rather chec+ the field Current User. #f an analysis method is started in
the monitored system from the central monitoring system !hen problems occur,
callers must authenticate themselves in the monitored system.
(hen choose 3? to return to the transaction S1,. Enter the =: connections that
you created under R3C Destinations o 'ar; S,s;. :hoose Sa%e. (he SAP system
can no! be centrally monitored.
4int" #t ma+es sense to use the same naming convention for all the =:
connections you create for system monitoring. (he follo!ing naming
convention has proven effective for various reasons4
DATAFEEEF5S/D7 for the name of the =: connection used to read
data from the remote system
AA.HS/SF9EEF5S/D7 for the name of the .analysis =: connection..
<ou should al!ays use the =: connection for reading data in the remote
system !ith client ---. <ou can use any client for the analysis =:
connection. 5S/D7 stands for the S#% of the remote SAP system.
Properties >ariants an$ Threshol$ >alues
Threshol$ >alues an$ Properties >ariants
%ntro!uctory <uestions a(out properties variants an! threshol! values"
. "hy@
. So that alerts are not constantly or never triggered by the system
. So that system monitoring is adapted in the best possible !ay to meet
your re*uirements
. Do!@
. #n the central monitoring system in transaction S1-
. (ransport from there to the monitored SAP systems
. (ips4
. =irst create container for threshold values /properties variants0 and
activate
. (hen maintain threshold values for the '(Es in your o!n monitors
(hreshold values can be stored for a monitoring attribute. (hreshold values
determine !hen the monitoring attribute should trigger a yello! or a red alert, and
!hen it should become green or yello! again. (he ::'S monitor infrastructure is
delivered preconfigured !ith threshold values recommended by SAP. <ou should,
ho!ever, chec+ the threshold values, at least for the monitoring attributes that you
consider to be important and that you have included in your o!n monitors. #n this
!ay, you adapt the system monitoring to your system environment in the best
possible !ay. Other!ise, alerts can be constantly or never triggered, depending on
!hether the threshold value is too lo! or too high for your system environment.
Caution" (hreshold values must be stored locally in every system.
Do!ever, instead of maintaining the same threshold values in every
system, !e recommend that you maintain the values in the central
monitoring system and then distribute them to the monitored SAP systems
using the transport system.
(he prere*uisite for transporting the threshold values to other SAP
systems is that you have stored them in properties variants.
. "hat are properties variants@
. :ontainers in !hich system monitoring settings can be saved. =or
e$ample4 (hreshold values for an '(E
. "hat are properties variants used for@
. 'onitoring behavior can be s!itched dynamically
. 'onitoring behavior can be coupled to operation modes
. :opying settings to other systems
<ou can create as many properties variants as you li+e and save settings in them.
;ust one properties variant !ith your settings is active at any time.
Properties variants have three advantages4
. <ou can manually s!itch from one properties variant to another for test
purposes or to adjust the monitor to a special situation. (his means that all
monitor settings are automatically changed in accordance !ith the current
properties variant.
. <ou can connect a properties variant to an operation mode. #n this !ay, the
threshold value /for a yello! alarm0 for the dialog response time is set to
,2--ms during the day, !hile the threshold value is automatically increased
to .3--ms after the s!itch to night operation, since there is usually no dialog
processing in your monitored system during the night.
. <ou can transport the contents of properties variants to other SAP systems
using the transport system. =or e$ample, if you create a variant for
production systems in the central monitoring system, and define the threshold
values that are to apply for production systems there, you can then transport
the variant to all production systems and activate the threshold values there.
Properties variants are created in transaction S1,. <ou can find the important
functions for properties variants by choosing Properties . Iariants.
=irst, create your o!n properties variant.
:hoose Properties . Iariants . Create.
Enter a name and a description for the properties variant, and save it.
<ou can organize properties variants hierarchically.
<ou can specify a parent %ariant !hen you create variants. #f you do not
specify another variant, the variant .Q. is implicitly assumed to be the parent
variant, !hose parent variant, is, in turn, SAP-DE3AUL'. (he threshold values
recommended by SAP are stored in SAP-DE3AUL'.
(hen choose Properties . Iariants . Acti%ate.
Select your variant and choose Enter.
<our properties variant that is no! active, displays on the initial screen of
transaction S1,.
#f no threshold value is maintained for a monitoring attribute in your variant, the
system chec+s the parent variant. #f this also has no threshold value, its parent
variant is chec+ed, and so on. <our properties variant is empty after it has been
created. (herefore, after activation, the threshold values that are stored in the
variant .Q. or SAP-DE3AUL' apply.
(he connection of properties variants to operation modes is performed in
transaction S-2. Select the operation mode and choose 0peration (ode .
Change. <ou can enter the desired properties variant in (onitoring Properties
Iariant. (hen save your entries.
After you have activated your properties variant, you can chec+ the threshold
values for the monitoring attributes you consider important and have included
in your o!n monitors.
(o do this, open your monitor/s0. Select a monitoring attribute and choose
Properties. (he current tab page displays the valid threshold value definition.
(he thresholds for Change rom !REE+ to 1ELL0" and Change rom 1ELL0"
to !REE+ are defined to change sooner than the thresholds for Change rom
RED to 1ELL0" and Change rom 1ELL0" to !REE+. #n this !ay, you can
avoid your monitor .flic+ering., if the measured value is !avering around the
threshold value. #t is useful to give an all clear only once the situation has
mar+edly improved.
:hoose Displa, . Change. <ou can no! adjust the threshold values to your
re*uirements. Save your settings.
<ou can no! choose, in a dialog bo$, in !hich properties variant your changed
threshold values are to be stored. 6ote that the currently active variant is
preselected. <ou can change the selection as desired.
<ou can copy these settings to a transport re*uest and transport them to other SAP
systems. (o transport the threshold values, choose Properties . Iariants .
Iariant 0%er%ie# in transaction S1,. #n the variant overvie!, choose Iariant .
'ransport. By doing this, you create a transport re*uest that can be transported to
other SAP systems using the transport management system /('S0.
Caution" 6ote that from a technical point of vie!, these transports can be
made across releases and products. Do!ever, certain transport options
have limited applicability. =or e$ample, you cannot import threshold
values for attributes into an SAP system that for various reasons does not
.recognize. these attributes /release, product0. (he import does not create
inconsistencies in the target system, though.
<ou may need to process attributes in the various monitored systems
locally /for e$ample, threshold values for attributes that are only +no!n in
remote systems0. #t !ould be very helpful if you had already created the
corresponding properties variants by transport for logging your changes.
Trace Options
/ntro$uction
<ou can follo! the process of various operations in your SAP system !ith trace
functions. (his allo!s you to monitor the system and isolate problems that occur.
(here are many trace options in SAP systems. (he main ones are listed belo!.
. System Eog /S'1,0
. %ump Analysis /S(110
. System (race /S(-,0
. Performance (race /S(-30
. %eveloper (races /S(,,0
<ou can use the System $og /transaction S'1,0 to detect and correct errors in
your system and its environment. SAP application servers record events and
problems in system logs. Every SAP application server has a local log that
contains the messages output by this server.
#f unpredictable errors occur during runtime !hen you call an ABAP program, a
runtime error that generates a short !ump can occur /transaction S(110.
#f you !ant to record the internal SAP system activities, such as authorization
chec+s, database accesses, +ernel functions, and =: calls, use the System 5race
function /transaction4 S(-,0.
(he Performance 5race /transaction S(-30 allo!s you to record database calls,
loc+ management calls, and remote calls of reports and transactions in a trace file
and to display the logged measurement results as lists. (he Performance (race
also offers e$tensive support for a detailed analysis of individual trace records.
<ou can find all the functions of the Performance (race in the System (race too.
(he Performance (race is a more suitable analysis tool for certain problems, since
the reduced scope of functions ma+es it is easier to handle.
(echnical information about internal SAP problems is logged in !eveloper traces.
System .og
Events and problems are recorded locally on each application server and displayed
in the system log in the SAP system.
#f you are using the 56#9 operating system, you can also !or+ !ith central
logging. #n this case, each application server copies its local logs periodically to
a central log. :entral logging is not possible on 'icrosoft "indo!s and iSeries
hosts. (echnically, the system log is !ritten to a ring buffer. #f this log file reaches
the ma$imum permitted size, the system begins to over!rite the oldest data.
4int" (he system does not display a message !hen an old log file is
replaced.
(o display a log, choose 'ools . Administration . (onitor . S,stem Log or
call transaction S'1,. By default, the system reads the log for the last one to t!o
hours. As !ell as the local system log, you can display system logs for other
application servers in transaction S'1,. (o do this, choose the menu path S,stem
Log . Choose . All Remote S,stem Logs or S,stem Log . Choose . Central
S,stem Log.
#n e$pert mode /menu path Edit . E-pert (ode0, you can e$tend the selection
criteria so that it is possible to search for entries for a particular terminal. (o
do this, choose the Attributes button.
#n 56#9 systems, you can display the status of the send process in the SAP system
!ith transaction S'1, or by choosing En%ironment . Process Status.
<ou can define the path and file names for local and central log files !ith the
follo!ing system profile parameters4
. rslg=local=ile4 =ile name for the local log /%efault4 SEOBOSAPTS<S)
(E'T65'BEP0
. rslg=central=ile4 =ile name for the active central log /%efault4 SEOB;0C does
not apply for 'icrosoft "indo!s 6( and AS82-- platforms
By default, the log files for the local system log are stored in the follo!ing
directory4 =usr=sap=DSIDE=Dinstance/director,E=log. (he central system log is
stored in =usr=sap=DSIDE=S1S=global
<ou can also schedule system logging as a bac+ground job. (here are t!o ABAP
programs provided to do this4
. RSL!@@@@4 (o create the local system log
. RSL!@@@74 (o create the central system log /not on 'icrosoft "indo!s
6( and AS82-- platforms0
Dump Analysis
ABAP programs are chec+ed statically !hen they are created and dynamically
!hen they are running. Errors that are not statically predictable and only occur at
runtime are dynamically identified by the ABAP runtime environment. States of
this type lead to e$ceptions. #f an e$ception is not handled or cannot be handled, a
runtime error occurs. #f a runtime error occurs, the ABAP runtime environment
terminates the e$ecution of the program, generates a short dump and branches to
a special screen for analyzing the short dump. <ou can also find short dumps in
transaction S5;; or by choosing the menu path 'ools . ABAP "orkbench .
'est . Dump Anal,sis.
A short dump is divided into different sections that document the error. (he
overvie! sho!s !hat other information is output in the short dump, such as
contents of data objects, active calls, control structures, and so on. <ou can branch
to the ABAP %ebugger at the termination point from the short dump vie!. (he
follo!ing different error situations e$ist4
. #nternal Error
(he +ernel identifies an error state. #n this case, send a message to notify
SAP.
. #nstallation and Environment8esource Error
#n this case, an error occurred that !as caused by incorrect system installation
or missing resources /such as the database being shutdo!n0.
. Error in Application Program
(ypical causes of errors are4
. :ontent of a numerical field not in the correct format
. Arithmetic overrun
. An e$ternal procedure is not available
. (ype conflict !hen transferring parameters to an e$ternal procedure
By default, short dumps are stored in the system for ,2 days. (he transaction
for managing short dumps is S(11. <ou can delete short dumps in accordance
!ith a time specification using the Reorgani6e function, !hich you can call by
choosing !oto . Reorgani6e. <ou can save a short dump !ithout a time limit
using the <eep function, !hich you can choose from the %etail Iie! under Short
Dump . <eep=Release.
#f problems that you cannot solve yourself occur !ith ABAP programs, you can
send an e$tract of the short dump to SAP. A short dump is the basis on !hich the
SAP Dotline and remote consulting solve problems.
%mportant Characteristics of 0ump Analysis
. #f a runtime error occurs, a short dump is generated. <ou can use transaction
S(11 to analyze this short dump.
. %ump data is stored in the database.
. %ump data can be reorganized.
. #ndividual short dumps can be flagged for retention.
(SAP( System Trace
<ou can use the /SAP0 system trace /.system trace. for short0 to record internal
system activities. (he system trace is primarily used if an authorization trace is
to be created. SAP recommends that you use the system log or the developer
trace for system monitoring and problem analysis. <ou can call the system trace
using transaction S(-, or by choosing the menu path 'ools . Administration .
(onitor . 'races . S,stem 'race. <ou can also use transaction S(-, to display
the inactive trace file.
5he system trace is use! for analyFing"
. Authorization chec+s
. Lernel functions
. Lernel modules
. %B accesses /S>E (race0
. Accesses to table buffers
. Eoc+ operations /client)side0
<ou select the components to be logged on the initial screen. #f the trace is
activated for the authorization chec+, all authorization chec+s performed by the
system are recorded. %uring the evaluation, you can identify !hich authorizations
the system chec+ed at !hich times. (he follo!ing detail information is also
provided4 %ate, time, !or+ process number, user, authorization object, program,
line, number of authorization values, authorization values.
<ou can use the S>E (race to follo! ho! the Open S>E commands in reports
and transactions are converted to standard S>E commands and the parameters
!ith !hich the S>E commands are transferred to the database system in use.
(he results of the S>E command are also logged, such as the return code and
the number of records found, inserted, or deleted by the database. Eogging the
e$ecution time and the callpoint in the application program allo!s you to perform
more advanced evaluations.
"ith the en*ueue trace, you can follo! !hich loc+ instructions the SAP system
performs on !hich loc+ objects, and !hich parameters the system uses for these
loc+s. (he program that triggered the loc+, the o!ner of the loc+, and the time
that the en*ueue server re*uired to release the loc+ again are all also logged in
the trace file.
<ou can use the =: trace to follo! !hich remote calls the SAP system e$ecutes,
and the instance on !hich these calls are e$ecuted. <ou can see from the trace
!hich function modules !ere called remotely by the program that is to be
analyzed, and !hether the =: !as successfully e$ecuted. (he total time re*uired
for the e$ecution of the remote call and the number of bytes sent and received
during the =: are also logged in the trace file.
Performance Trace
5he Performance trace is use! for analyFing"
. %atabase calls
. Eoc+ management calls
. Accesses to table buffers
. emote calls of reports and transactions
. #ndividual trace records
. S>E statements
(he performance trace provides similar trace options to the system trace. #t allo!s
you to record database calls, calls to loc+ management, calls to table buffers, and
remote calls of reports and transactions from the SAP system itself in a trace file.
<ou can call the Performance (race using transaction S(-3 or by choosing the
menu path 'ools . Administration . (onitor . 'races . Perormance 'race.
On the initial screen of transaction S(-3, you can choose the E-plain S:L button
to analyze an S>E statement !ithout branching to a specific trace file.
(he performance trace is integrated into the ABAP "or+bench as a test tool and
can therefore be called there.
Con-guring the Trace *ile
<ou can use system profile parameters to restrict the size of the trace files and
to specify an appropriate path.
(he SAP system trace !rites the trace data to trace files. =or performance reasons,
this is not done directly, but rather using a process)internal buffer. (he profile
parameter rstr=buer/si6e/kB determines the size of the buffer. Since SAP "eb
AS 7.,-, the SAP trace stores the data in multiple files, !hich are !ritten in
turn. (he parameter rstr=ilename defines the base name of these files. (here
is al!ays a file !ith e$actly this name. "hen the file becomes full /parameter
rstr=ma-/ilesi6e/(B0, the file is renamed and a ne! file is generated !ith the
base name. "hen the file is renamed, a number bet!een -- and JJ is added to the
file name. (he parameter rstr=ma-/iles determines the ma$imum total number of
files. #f this value is e$ceeded, the files are over!ritten.
De"eloper Trace
%eveloper traces are recordings that contain technical information and that are
used if errors occur. (his type of process trace is especially useful to investigate
host and internal SAP problems that are affecting your SAP system. %eveloper
traces $e"F I are !ritten to files in the directory /usr/sap/<SID>/<instance
directory>/work of the SAP application server that generated the trace.
<ou can access the developer traces using the operating system, using transaction
AE,,, or from transaction S'3- /"or+ Process Overvie!0. #n transaction S'3-,
you can s!itch to the individual devTQ traces by choosing Process . 'race
. Displa, 3ile. <ou can display additional details in the displayed traces by
e$panding individual entries.
Trou%leshooting Proce$ure
1eneral Approach
#t is part of their nature that errors al!ays occur in places that they should not
occur. #t is therefore only possible to present a general approach. =ront end
printing is used to represent possible errors for e$amples.
<ou !ill run through the steps in the figure .(roubleshooting4 Approach. !hen
troubleshooting.
#solate the problem area4 =irst attempt to isolate the error. "here does it occur,
!hen does it occur, and in !hat conte$t does it occur@ .#t doesnHt print., !ould be
too imprecise here. .=ront end printing on front end $yz does not !or+ !ith any
SAP system., is more e$act. #f you also +no! that front end printing !or+s on
other front ends, you have already isolated the problem.
Problem Analysis4 :hec+ the scenario to find out !hether all re*uired settings,
and so on are correct. :hec+ the application logs, the system log, and the traces
/the developer traces !ill usually be helpful here0, to see !hether they provide any
clues for correcting the error.
Bain additional +no!ledge4 (o interpret the results from the first problem
analysis, it is, of course, necessary that you are familiar !ith the processes and
functions of the area in !hich the error is occurring. #f your e$perience and your
previous +no!ledge are insufficient, you can start a search in the SAP 6otes and
on the SAP Service 'ar+etplace !ith the +ey!ords from the system log or the
trace files. <ou may find a problem solution here, or additional information that
helps you find and correct the error. #f you have not found any suitable SAP 6otes
or suitable search terms, search for composite notes for the topic area. #n this case,
for e$ample, !ith the terms 3ront end printing and composite note. =or additional
bac+ground information for the topic area, see the online documentation and
course materials. #f you still cannot solve the problem !ith this information, use
the comparison bet!een the process !ith errors, and an error)free process.
:ompare error)free and erroneous processes4 <ou can use this to determine
!here there are differences bet!een an erroneous and an error)free process. (his
information helps you to further isolate the problem area and may help you to
solve the problem or to perform ne!, more targeted problem analyses. #f it is not
possible to perform another problem analysis, create a message for SAP on the
SAP Service 'ar+etplace. Enter the information from your troubleshooting /such
as a trace and8or system log information0 !hen doing so.
Lesson 11
/ntro$uction to SAP Software .ogistics
SAP System .an$scape
SAP et!ea"er@ SAP )&P
As a first step, letHs revie! the SAP product portfolio. SAP EP is a SAP
application. SAP offers other SAP applications for the areas of :ustomer
elationship 'anagement /SAP :'0, Supplier elationship 'anagement
/SAP S'0, Product Eifecycle 'anagement /SAP PE'0, and Supply :hain
'anagement /SAP S:'0. All these applications are part of the SAP Business
Suite /formerly +no!n as mySAP.com0. As a result, a customer !ith a SAP
Business Suite license has also the license for the applications that can be seen as
subsets of the mSAP Business Suite.
#nside the SAP applications, SAP offers the SAP components, li+e SAP E::,
SAP S:' /formerly +no!n as APO, Advanced Planner and Optimizer0 or others.
=rom a technology point of vie!, these are the components that a customer installs
or upgrades.
Another important product to mention is SAP 6et"eaver. #t represents the
technology stac+ provided by SAP to support the SAP Business Suite and its SAP
applications, as !ell as other SAP products. =urthermore, SAP 6et"eaver and
its integration capabilities also allo! the integration of non)SAP products. SAP
6et"eaver is delivered !ith all of the SAP applications. As a result, customers
can ma+e use of the SAP 6et"eaver functions for a specific application. SAP
6et"eaver is a set of different components li+e SAP 6et"eaver AS, SAP B#, SAP
6et"eaver Portal, SAP P#, SAP '%' and others. (hese technical components of
SAP 6et"eaver can be installed as needed to serve different re*uirements.
(he SAP for #ndustry applications, !hich are also part of the SAP product
portfolio, can be seen as e$tensions to the SAP Business Suite and its SAP
applications. SAP for #ndustry applications, !hich !ere historically add)ons to
one single component called .SAP 8.., no! provide not just add)ons to SAP
components but also preconfigurations and best practices.
As an e$ample of an SAP application, this figure gives a good overvie! of
the evolution of the EP applications from SAP. After the SAP 8, and SAP
81 products, SAP introduced SAP 8. in ,JJ1. 6o!, there !as a t!o)layer
architecture /SAP Basis and SAP Application0.
"ith SAP EP, !hich has been available since 'arch 1--., SAP offered a bundle
of components supporting EP business processes. At this point, SAP 8.
Enterprise 2.? !as one of those components.
(he SAP EP :entral :omponent /SAP E::0/E::0 represents the ne$t step in
this evolution. As you can see, different soft!are components can be operated
on an SAP E::.
(his slide gets rid of the confusion concerning the different 8., 8. Enterprise,
E::, E$tension Set and EP and Basis, SAP "eb AS, SAP 6et"eaver AS and
SAP 6et"eaver releases.
SAP Systems@ /nstances an$ Ser"ers
. (he #nternet :ommunication 'anager /#:'0 is the interface to the internet.
#t can deal !ith !eb re*uests as server and as client. #t supports several
protocols li+e D((P, D((PS and S'(P. (he SAP 6et"eaver AS can be
used as a !eb server and as a !eb client.
. (he ABAP)%ispatcher dispatches re*uests to the "or+ Processes. #f all
!or+ processes are busy at the moment, the re*uests are *ueued in the
%ispatcher)>ueue.
. (he ABAP "or+ Processes e$ecute the ABAP coding.
. (he 'essage Server e$changes messages and can perform a load balancing
in the SAP system.
. On the ;ava)side of the SAP 6et"eaver AS there are components li+e the
;ava)%ispatcher, Server Processes, the Soft!are %eployment 'anager
/S%'0 and the :entral Services /S:S0.
. (he SAP ;ava :onnector /;:o0 provides communication bet!een the
ABAP)Stac+ and the ;ava)Stac+ of the SAP 6et"eaver AS, in both
directions.
:lient re*uests to the SAP 6et"eaver AS ;ava are handled by the ;ava)%ispatcher.
#t chooses a free Server Process for serving the re*uest and builds up a connection
bet!een the client and the Server Process. (he ;ava)%ispatcher !or+s according
to a Hound obinH algorithm.
(he Soft!are %eployment 'anager /S%'0 is the standard tool !ith !hich ;1EE
components are installed on the SAP 6et"eaver AS ;ava.
(he :entral Services run on one server and forms an o!n ;ava instance. #t consist
of a 'essage Service and an En*ueue Service and are the basis for communication
and synchronisation for the ;ava :luster.
Each instance of a SAP 6et"eaver AS ABAPF;ava contains the ABAP
%ispatcher !ith its "or+ Processes and the ;ava %ispatcher !ith its Server
Processes. One of the instances is usually installed as an ABAP :entral #nstance,
!hich means, that the En*ueue "or+ Process runs here. Alternatively the System
can be installed !ithout a :entral #nstance, but !ith a stand alone En*ueue Server.
(he applications and data for ABAP and ;ava both have their o!n database
scheme in one common database.
5sers can log on and communicate !ith the SAP system either using the SAP
B5# or a !eb client /bro!ser04
. :ommunication using the SAP B5#4 users log on using the 'essage Server
/for load balancing0 or directly log on to a ABAP %ispatcher. (he "or+
Processes e$ecute the re*uests of the users.
. E$ecution of !eb re*uests4 !eb re*uests are handled by the #nternet
:ommunication 'anager /#:'0. (hese D((P/S0 re*uests can be intended
for the #nternet :ommunication =rame!or+ /#:=0, !hich means that they
are e$ecuted by an ABAP "or+ Process /for e$ample BSP applications0.
(hese re*uests can also be ;1EE re*uests for the SAP 6et"eaver AS ;ava.
(he #:' can direct the re*uests according to their 5E.
System .an$scape &ecommen$e$ %y SAP
Drom no/ on /e focus on the SAP 'et&eaver AS ABAP*
(o maintain data security, you should protect application data by using the client
concept, !hich separates data according to clients, and the authorization concept,
!hich separates data !ithin one client according to the users.
#n addition, you should strictly separate the environments for development, *uality
assurance, and production.
(he performance of the production client should not be affected by development
and test activities in the other clients.
:hanges to epository objects are client)independent, and immediately affect
the runtime environment. (herefore, changes have to be tested before being
transported to the production system.
#f you had only one system, no further development !ould be possible after
production had started. :hanges to repository objects could be made only !hen
production operations !ere stopped for development and testing.
A t!o)system landscape is not optimal because development and *uality assurance
testing both ta+e place in the development system.
(o ensure smooth production operation, an SAP system landscape should contain
the three SAP systems, the standard clients, and any re*uired additional clients.
A three)system landscape is recommended and meets the needs of most customers.
%evelopment ta+es place in the development system. :hanged objects are then
released to the *uality assurance system.
#n the *uality assurance system, you can test ne! developments !ithout affecting
the production environment. A *uality assurance system enables you to integrate
development efforts and to chec+ the validity and consistency of transported
objects before moving the objects into production.
All objects imported into the *uality assurance system can also be delivered to one
or more production systems.
(he three)system landscape is also a basis to apply Support Pac+ages or to
perform a release upgrade.
SAP systems in the same system landscape re*uire uni*ue system names.
SAP provides the tools re*uired for the creation, documentation, and distribution
of changes !ithin a system landscape. (o set up the system landscape so that it
supports the management, verification, and testing of all changes4
. A single client is recommended for all customizing !or+. Set client change
options appropriately before using your clients.
. A single SAP system /the development system0 is recommended for all
development !or+. Set the system change options appropriately.
. (o create and assign appropriate user authorizations to developers and
customizers, use the sample profiles included in the SAP system. (hese
authorizations control !hether a user can create, modify, or release change
tas+s and transport re*uests.
. ecord and document all changes to a client or system.
#n SAP elease 2.-, SAP has introduced a revised version of the :hange and
(ransport System /:(S0, comprising the follo!ing tools4
. (he :hange and (ransport Organizer /:(O0 provides functions for
organizing soft!are development projects. #t is designed to support projects
of all sizes, !hether they are carried out centrally or in a distributed
environment.
. (he (ransport 'anagement System /('S0 organizes, monitors, and
performs transports for all SAP systems !ithin a system landscape. #n
addition, ('S is used to configure and manage the setting up of SAP
systems and transport routes !ithin a system landscape.
. Operating system transport tools are e$ecutables that communicate !ith the
SAP system, the database, and files generated during the e$port process.
Lesson 12
Client Concept
Data in an SAP System
%ata in an SAP system can be divided into t!o categories4 client)specific data
and cross)client data.
,. :lient)specific data, such as user master and application data, !hich affects
only one client.
1. :ross)client data, such as cross)client customizing data and all epository
objects, !hich affects the !hole system environment.
(he ABAP %ictionary is a data dictionary that is part of the ABAP epository.
Each piece of the ABAP %ictionary information is entered only once and is then
available any!here in the system at any time. (he ABAP %ictionary automatically
supplies all ne! or changed information, thus providing current runtime objects
and ensuring data consistency and security.
Clients in an SAP System
A client is a self)contained unit in commercial, organizational, and technical
terms, !ith its o!n user master data and set of table +ey ranges.
%ata from different clients is +ept separate at the +ernel level. S>E statements
e$ecuted by an SAP application use the client number in the !here)clause.
Although a table may contain data from several different clients, the !here)clause
limits access to particular clients.
(he follo!ing are e$amples of client)specific data4
. 5ser master data, such as parameters, authorization, user groups
. :ustomizing data, such as organizational units, assignments, and document
types
. Application data, such as business transaction data, and material master data
(he SAP client concept can integrate several companies or subsidiaries in a single
client by using company codes and the SAP authorization concept.
:ompany codes define the smallest corporate organizational units for !hich a
complete self)contained set of accounts can be dra!n up for e$ternal reporting.
(he SAP authorization concept enables the parent company to access all
subsidiaries for report purposes, !hile subsidiary)specific data is protected against
access from other subsidiaries through company code definition.
(he standard client roles fulfill the optimal minimum re*uirements of your SAP
system.
:lient :5S(, development and customizing, is the central customizing client
!here complete adaptation of the SAP system to customer)specific needs ta+es
place. All changes performed in this client are recorded so they can be supplied to
the other clients using the (ransport 'anagement System /('S0.
:lient >(S(, *uality assurance, is used to test and verify the ne! customizing
settings in the application.
:lient PO% or production is the client for production activities, that is, !here
your companyHs business is carried out. :ustomizing changes imported into this
client have to be first tested carefully in the >(S( client in order to ensure that
production operation is free of disruption.
(o realize the full benefit of a three)system landscape, every critical client should
have a separate SAP system.
Additional clients !ithin a system landscape may include4
,. A sandbo$ client to e$periment !ith transactions and settings.
1. A test client to verify customizing changes against sample data in a more
stable environment. (his can be done by HcopyingH customizing settings from
the customizing client to the sandbo$ client. (his is called a unit test.
.. An end)user training environment.
2. A client that satisfies customer)specific re*uirements.
System an$ Client Change Options
System Change Options
(he system change option defines !hether or not epository objects and
client)independent customizing objects are globally modifiable. #f they are
globally modifiable, you can specify !hether or not each soft!are component or
namespace can be modified.
(o reach the system change option use transaction SE-7 and choose S,stem
Change 0ption. A soft!are component is a set of dedicated development classes.
=or the soft!are components, there are four different possible settings4
. 'odifiable
. estricted modifiability /can only create objects as non)originals0
. 6ot modifiableC enhanceable only /changes not allo!edC objects can be
enhanced using the Enhancement =rame!or+ only0
. 6ot modifiableC not enhanceable /changes and enhancements not allo!ed0
<ou can reserve namespaces for soft!are developed by SAP customers and
partners. (hese namespaces are designed for large)scale customer enhancements
as !ell as add)ons developed by partners.
(he synta$ for objects from reserved namespaces is4 =DnamespaceE=Dob5ect
nameE. =or each SAP system, the customer can define !hether or not the objects
contained in the namespaces and name ranges can be changed. (o enable you to
change objects, the SAP system must not be globally loc+ed to changes.
Client Change Options
:lient change options that are found in the clients master table '@@@, can be
maintained by using transaction S::2.
(he t!o settings that must be maintained to implement controls on !here changes
are made and enforce the changes being recorded to change re*uests are4
. :hanges and transports for client)specific objects
. :ross)client object changes
(he follo!ing list gives a brief description of !hat each option allo!s4
. :hanges and transports for client)specific objects4
. Changes #ithout automatic recording
(his flag means that changes in the :ustomizing settings of the client
are permitted. (he changes are not automatically recorded in a change
re*uest.
:ustomizing settings can be e$ported from the client by manual
creation of a transport re*uest. A manual transport can be carried out
in the particular transaction for settings !ith the function 'ransport,
!hich places the selected :ustomizing settings in a transport re*uest.
(his variant ma+es sense for pure test, training or demonstration clients.
. Automatic recording o changes
(his flag means that changes are permitted in the customizing settings
of the client and all the changes are automatically recorded in a change
re*uest.
#t is also possible to e$port independently of the automatic recording
from the client customizing settings by manual creation or recording of
a transport re*uest. A manual transport can be made in the particular
transaction for settings using the function (ransport, !hich places the
selected customizing settings in a transport re*uest.
#n a productive client, settings that can be maintained as Ucurrent
settingsU are e$cluded from automatic recordingC current settings /e.g.
e$change rates, posting periods0 are al!ays modified !ithout recording
the changes.
(his variant can be used for customizing clients and productive clients.
. +o changes allo#ed
(his flag means that changes in the customizing settings of the client
are not permitted /client loc+0.
Do!ever, customizing settings can be e$ported from the client by
manual creation of a transport re*uest. A manual transport can be
carried out in the particular transaction for settings !ith the function
(ransport, !hich places the selected customizing settings in a transport
re*uest.
#n a productive client, the customizing settings that can be maintained
as Ucurrent settingsU are e$cluded from the client loc+C this means that
current settings /e.g. e$change rates, posting periods0 can al!ays be
maintained in the productive client.
(his variant can be used for productive clients, demonstration clients
and training clients.
. Changes #=o automatic recordingJ no transports allo#ed
(his flag means that changes are permitted in the customizing settings
of the client. (he changes are not automatically recorded in a change
re*uest, ho!ever.
6o manual transport of :ustomizing settings from the client is possible.
(his variant can be used for pure test clients.
. :ross)client object changes
(his feature controls in !hich clients you are allo!ed to maintain cross)client
objects.
#t ma+es sense to disallo! cross)client maintenance if the objects to be
maintained in a client are e$clusively application objects /all client)specific0
or client)related :ustomizing objects. #n this case /for e$ample in a test
client0, you must be able to ensure that cross)client functionality cannot
be changed.
:ross)client functions include all cross)client :ustomizing objects /e.g.
factory calendar, definition of price list conditions, printer controls0. But
in particular they also include all objects of the SAP epository /eports,
module pools, screens, %ictionary etc.0.
. Changes to repositor, and cross-client customi6ing allo#ed
(here are no restrictions on the maintenance of cross)client objects for
the client !hen this setting is used. Both cross)client :ustomizing
objects and objects of the SAP epository can be maintained.
5se in customizing8development client only
. +o changes to cross-client customi6ing ob5ects
:ross)client :ustomizing objects cannot be maintained in the client
!ith this setting.
Only use this if development client is separate from customizing client
. +o changes to repositor, ob5ects
"ith this setting, objects of the SAP epository cannot be maintained
in the client.
Only use this if customizing client is separate from development client.
. +o changes to repositor, and cross-client customi6ing ob5ects
:ombination of both restrictions4 6either cross)client :ustomizing
objects nor objects of the SAP epository can be maintained in the
client.
5se this in every client in the landscape e$cept customizing8development
client/s0
#n a customizing project and also during the maintenance of a system all the
customizing changes should be transported and tested in the *uality assurance
system. But certain +inds of customizing changes, +no!n as data)only
customizing changes, need to be carried out in a production client !ithout being
saved as transport re*uests. E$amples of such data include interest rates, health
insurance premiums, pension schemes, ta$ schemes, and currency e$change rates,
!hich may re*uire fre*uent adjustment in SAP systems.
Since these types of changes have a fre*uent change rate and they are not subject
to e$tensive testing li+e other customizing changes, these changes are done
directly in the productive system. (o avoid having to use change re*uests for these
changes, SAP has introduced the Current Settings function.
Current Settings may be used !ithin a production client !ithout impacting
business flo!)related :ustomizing objects.
SAP)approved Current Settings for customizing objects are +ept in the field
CURSE''I+! in the table 0B$&. SAP recommends that no customer changes be
made to the table.
"hen using Current Settings in a production environment4
. :lient role is set to4 Production
. :ross)client object changes are set to4 +o changes to Repositor, and
cross-client Customi6ing ob5ects
. :hanges and transports for client)specific objects are set to4 +o changes
allo#ed.
Lesson 13
Setting +p an SAP System .an$scape
Setting +p the Transport ,anagement System
(T,S(
O"er"iew an$ Prere2uisites
(he follo!ing list gives an overvie! of !hat has to be considered before, during
and after installation of an SAP system.
. Before SAP system and database installation4
. %efine the net!or+ structure for the system landscape.
. #nstall the hard!are and the operating system.
. %uring SAP system and database installation4
. :reate one common transport directory /sometimes you !ant to have
more then one0.
. After SAP system and database installation4
. #f you have set up the system using database copy, initialize the :hange
and (ransport Organizer /:(O0 /transaction SE-70.
. #n any case4 set up the (ransport 'anagement System /('S0.
4int" #f you have performed a database copy, initialize the :hange and
(ransport Organizer /:(O0 using transaction SE-7, choosing Database
Cop, or Database (igration and pressing the Perorm Post-Installation
Actions button.
#n any case you have to configure the system landscape using the ('S
using transaction S('S. (he process of setting up the system landscape
!ith transaction S('S !ill be described in detail in this lesson.
(o set up your system landscape, it is sufficient to start !ith an e$isting SAP
system as a development systemC the *uality assurance and production SAP
systems are not re*uired at this stage. All future systems can be represented at this
stage as .virtual systems.. <ou !ill also have to create a transport directory at
operating system level. (his directory is re*uired for the ('S.
%epending on your e$isting landscape, the global transport directory and all the
necessary subdirectories are created automatically during the installation of the
SAP system /see the installation guide for your SAP system for more details0. (he
amount of dis+ space re*uired depends on the amount of development !or+.
Please refer to the installation guide of your SAP system.
(he SAP system parameter DIR/'RA+S has to point to the path of the transport
directory. =or 5ni$, the default path is =usr=sap=trans. =or "indo!s 6(, the
default path is GGC)SAP'RA+S&0S'*GsapmntGtrans and you must define the
transport host !ith the alias SAP(A6SDOS( on operating system level of the
domain name server.
4int" =or e$ample, in a "indo!s environment the corresponding file
name is K"I+DIRKGs,stem?8Gdri%ersGetcGhosts.
(he subdirectories re*uired in the common transport directory include /among
others04
. bin4 configuration files for tp /(PTOdomain nameP.P=E0 and ('S
/%O'A#6.:=B0.
. buer4 transport buffer for the each system, indicating !hich transport
re*uests are to be imported.
. data4 e$ported data.
. coiles4 command or transport re*uest information files that include
information on the transport type, object classes, re*uired import steps, and
post)processing e$it codes.
. log4 transport logs, trace files, and statistics.
. tmp4 temporary data and log files.
. actlog4 action logs for all tas+s and re*uests.
. sapnames4 information belonging to transport re*uests for each SAP user.
. EPS4 do!nload directory for SAP Support Pac+ages.
'ote" (o enable transports in a heterogeneous operating system
environment, you must set up different transport directories. Do!ever, to
enable transports in a heterogeneous operating system environment using
a single transport directory, refer to SAP 6ote M..1? in the SAP Service
'ar+etplace under the *uic+ lin+ =notes.
(ransporting enables you to synchronize customizing and development in multiple
SAP systems through the transfer of changes from the development system to
do!nstream systems. (ransports along the transport routes must occur in only
one direction.
As mentioned above, transporting re*uires a transport directory to enable SAP
systems in the system landscape to store and access various data files, command
files, and log files.
Physically, changed objects in a three)system landscape are transported in three
steps4
,. All objects in a /transportable0 transport re*uest that are to be released are
e$ported . by being .copied. . from the database of the source system to
the transport directory.
1. (hese objects are imported into the database of the *uality assurance system.
Dere they are tested and validated.
.. After testing and verification, the objects can be imported into the database
of the productive system.
'ote" (he terms .e$port. and .import. are meant as copy, not as move,
of course. At the end, the objects e$ist four times4 in the database of %EI,
>AS and P% and in the transport directoryK
So actually the .truc+. is a very bad visualization4 because it does a
moveK A fa$ machine !ould be much better...
T,S; Concepts an$ Terminology
%epending on the size of an organization and the scope of its SAP implementation,
there can be many different individuals responsible for carrying out customizing
and development projects. Some !ill be involved in customizing specific
application areas, others may be involved in development of ne! ABAP programs,
others in the >A testing and acceptance of changes. (here can be hundreds or
even thousands of changes that have to be transported through the systems in the
landscape. (he transport of these changes !ill be done using the functions of
the ('S /('S0.
(he concepts behind ('S are4
. :entralized configuration of :hange and (ransport System /:(S0 for all
SAP systems
. :entralized management of transport re*uests and especially the import
process
. (ransport strategy based on predefined transport routes
(he purpose of the ('S, accessed via transaction S('S, is to centrally control
the propagation of changes through the system landscape based on predefined
paths. (his is designed to ensure the consistency of the SAP repository and the
contents of the customizing tables in all systems in the landscape. All necessary
activities can be done from !ithin the SAP system /using the SAP authorization
concept0 and there is no need to e$ecute scripts at operating system level by hand.
"ith ('S you are able to
. %efine an SAP systemHs role !ithin a system landscape or transport domain
. :onfigure the transport routes using either an editor or delivered standard
configurations
. :onfigure the transport tool programHs /tp0 parameter profile
. %isplay the import *ueues of all systems in the transport domain
. %efine *uality assurance 8 acceptance procedures in the >A system
. Schedule the import of change re*uests in an import *ueue
. Perform transports bet!een systems !ithout a common transport directory
. Dandle transport proposals of developers
('S thus enables system administrators to centrally manage the transport
configuration of multiple systems by defining transport domains, assigning
domain controllers and defining transport routes.
A transport !omain consists of all systems that you plan to manage using the
same ('S. "ithin the transport domain, all systems must have uni*ue system
#%s /S#%0 and only one of these systems is identified as the /transport0 domain
controller.
(he transport !omain controller is the system !here all ('S configuration
settings are maintained. Any changes to the configuration settings are distributed
to all systems in the landscape. (his ensures that the ('S configuration settings
are consistent throughout the domain. (he domain controller stores the reference
configuration and all other systems receive a copy of the reference configuration.
A system lan!scape is a set of systems that share customizing and repository
objects via transported change re*uests. (he typical landscape is made up of,
but not limited to, a development, a *uality assurance, and a production system.
#n most cases, the system landscape and the transport domain are made up of
the same systems but it is not uncommon to have multiple landscapes !ithin
one transport domain.
E$amples of a single transport domain !ith multiple landscapes are4
. A multi)national company may have separate landscapes for each subsidiary.
%E,, >A,, and P, may be the landscape for the Asian implementation and
%E1, >A1, and P1 may be the landscape for the European implementation.
Even though they are separate landscapes, both can still be controlled
centrally in one domain.
. An SAP customer may have multiple landscapes for different SAP Business
Suite products. %EE, >AE, and PE may be the landscape for the E::
systems, !hile %EB, >AB, and PB may be the landscape for the B#
systems. Again, separate landscapes are controlled centrally using one
transport domain.
A transport domain contains at least one transport group. Iery simply, a
transport group consists of one or more systems that share a common transport
directory. (he follo!ing figure sho!s the relation bet!een a transport domain
and a transport group.
('S supports several transport directories !ithin a transport domain. (his might
be the case e.g. for the multi)national company mentioned above !here each
subsidiary may have its o!n /local0 transport directory. Or thin+ about a transport
domain containing a landscape that has a %EI system !ith its o!n transport
directory and >AS and P% system sharing a common transport directory, for
security reasons. #n this case, the domain !ould consist of t!o transport groups.
'ote" (he terms transport domain, domain controller, and transport
group concern only the systems in the environment. (hey do not include
the transport relationship bet!een the systems, !hich is defined by the
transport routes.
)sta%lishing a Transport Domain
(o set up the transport domain, first determine !hich systems should be included
in the transport domain. (he transport domain should contain all systems in all the
system landscapes that !ill be centrally administered using ('S.
'ote" 6ot all systems need to be installed and present !hen the domain is
first configured but planning !hat the landscape !ill loo+ li+e is necessary.
(hese future systems can be represented by so called virtual systems.
9verview
(he configuration of ('S can be bro+en do!n into three individual steps.
,. :onfiguring the transport domain defines !hich systems !ill be included in
the domain.
1. :onfiguring the transport routes defines the system and client roles !ithin
the landscape/s0.
.. :onfiguring the >A procedure defines !ho is responsible for approving the
acceptance of changes and the promotion of those changes to the delivery
system/s0.
(he follo!ing figure sho!s the three steps. 6ote that the first t!o steps are
mandatory for setting up a system landscape !hereas the last step />A procedure
configuration0 is optional.
;nitiali?ing the transport ,omain 'ontroller
(he first system you configure is automatically selected as the transport domain
controller but you may later s!itch the role of the domain controller to a different
system.
Since certain configuration tas+s that are relevant to the entire transport domain
/e.g. creating transport routes0 can only be carried out on the transport domain
controller, SAP recommends that the system chosen to be the domain controller
have the follo!ing attributes4
. Digh availability
. Digh security precautions
. Dighest level of maintenance
(herefore, a production system might be the ideal choice to be transport domain
controller. Since the development system is usually installed before the *uality
assurance or production systems, the common practice is configuring the
development system as the transport domain controller and then later moving the
assignment of the transport domain controller to the production system. Another
scenario might be to use a system that you use already for central monitoring
and8or central user administration as transport domain controller.
'ote" (he system load on the SAP system caused by !or+ on the
transport domain controller is very lo!.
"hen using ('S for the first time after system installation, you are automatically
prompted to initialize the ('S. <ou must initialize the ('S !hile logged on to
client ---. =or configuring ('S you need the authorization ST:(STA%'#6.
. (ransaction S('S in client --- !ill4
. Assign the SAP system as the transport domain controller
. :reate transport domain name %O'A#6TOS#%P
. :reate transport group BO5PTOS#%P
. :reate system user ('SA%' in client ---
. :reate =: destinations
. Set up file %O'A#6.:=B in directory bin of the transport directory.
"hen you initialize the ('S, the follo!ing actions !ill automatically be carried
out by the SAP system4
. A transport group is created !ith the name BO5PTOS#%P.
. #n client ---, the system user ('SA%' is created.
. (he =: destinations re*uired for the ('S are generated.
. (he ('S configuration file %O'A#6.:=B is stored in the transport
subdirectory bin. (his file contains the transport domain name and
description as !ell as the transport domain controllerHs host name, instance
number, S#%, and transport group.
. (he transport profile for the transport control program tp is generated and
stored in the transport subdirectory bin under the name (PTO%O'A#6P.P=E.
(he parameters in this profile are maintained using the transaction S('S.
'ote" (he name of the transport domain may not contain blan+s and may
not be changed after!ards !ithout reconfiguring the domain controller.
By default, a transport domain !ill have the name %O'A#6TOS#%P,
!here OS#%P is the system #% of the domain controller. (he name of the
transport domain cannot be changed after!ards.
A$$ing a$$itional systems to a $omain
"hen other systems that !ill be part of an e$isting domain are ready for
inclusion in the transport domain, you can e$tend the transport domain by
adding these systems. (o add ne! systems to a transport domain, you must
perform configuration activities on both the ne! system and the transport domain
controller.
On the ne! system being added, the configuration process is +no!n as re*uesting
inclusion. Since configuration of the ('S only occurs on the domain controller,
the domain controller !ould then have to approve the ne! system in the domain.
Each additional SAP system must apply for inclusion to the transport domain
controller. (he transport domain controller then must confirm inclusion for each
SAP system. (he initial screen of transaction S('S indicates if an SAP system is
!aiting for inclusion in the transport domain.
After you have included an SAP system from one of the transport groups in
the transport domain, the description of the transport domain is stored in the
file %O'A#6.:=B in the bin subdirectory of the common transport directory.
All other SAP systems connected to this transport directory read the file
%O'A#6.:=B during S('S initialization to identify the domain controller and
transport group address. #f your SAP systems do not have a common transport
directory, you can manually configure ('S !ith the address of the domain
controller. #n this case choose 0ther coniguration . Include s,stem in domain
!hen entering transaction S('S for the first time. #n the ne$t popup, enter the
target host and the system number of the transport domain controller. #n any
case, !hen an SAP system has been configured for the ('S and approved in
the domain, you !ill find a ne!ly created user ('SA%' and generated =:
destinations re*uired for the ('S.
4int" "hen configuring the ('S on an SAP system, you can specify the
application server /i.e. the instance0 to be used for all ('S functions.
:hoose the instance !ith the highest availability. (his is generally the
instance that provides the en*ueue service, the central instance.
(he systems !ithin a transport domain communicate !ith each other using
emote =unction :alls /=:0. =: communication re*uires user #%s to access
target systems. "hen systems are added to a transport domain, the necessary
(he systems !ithin a transport domain communicate !ith each other using
emote =unction :alls /=:0. =: communication re*uires user #%s to access
target systems. "hen systems are added to a transport domain, the necessary
4int" (he system you select as a bac+up domain controller must be an
e$isting installed systemC it cannot be a virtual or e$ternal system.
(o chec+ the current status of the transport domain configuration for each SAP
System in the transport domain, access the ('S overvie!. =rom the ('S initial
screen, choose 0%er%ie# . S,stems. #n this overvie!, you can also see !hether
the configuration is up to date, and !hether any errors occurred !hen distributing
the configuration.
Con-guring tp
(he transport control program tp re*uires a transport profile that contains
information about establishing the database connection for all SAP Systems in
the transport domain. ('S generates and manages this transport profile as a part
of the transport domain configuration. %o not adjust the transport profile using a
te$t editor at operating system level.
(o display the tp parameters of an SAP System, call transaction S('S. :hoose
0%er%ie# . S,stems. 'ar+ one system and choose SAP S,stem . Displa,.
:hoose the tab 'ransport 'ool. =rom the menu, choose !oto . tp parameters.
(his displays the parameters in (PTOdomain nameP.P=E and the default value
of all parameters used by the programs tp and R?trans. #f a parameter is not
specified, a default value !ill be used. Blobal parameters override defaults. Eocal
parameters override global parameters. =or e$ample, you can specify a global
parameter value for all but one system if a local parameter applies to that system.
<ou can s!itch bet!een the vie!s Displa, All Parameters and Displa, Substituted
Parameters 0nl, /content of (PTOdomain nameP.P=E0. <ou can s!itch by using
the Displa, Less and Displa, Less button.
'ote" #n releases up to 8. 2.7: there !as the configuration file tpparam.
(his is not used anymore. Although it !as more or less o+, to maintain the
tpparam !ith an te$t editor, this is not o+ anymore for the 'P/Ddomain
nameE;P3L
After performing an upgrade from 8. 2.7: to E:: 7.-, for e$ample, you
might !ant to transfer your settings from the old to the ne! configuration
file. <ou can do this in the parameter overvie! by choosing E-tras -E
Cop, Coniguration rom 'PPARA(.
Con-guring Transport &outes
(ransport routes indicate the role of each system and the flo! of change re*uests.
(he transport routes are !hat actually define your system landscape.
O"er"iew
#nitializing the ('S and setting up the transport domain define the physical
systems in the environment only in terms of the transport domain, the domain
controller, and the transport group. 6e$t, you must define the transport relationship
bet!een each of these systems. Although the ('S has been initialized, you cannot
perform transports until the transport routes have been configured and distributed.
After establishing a transport domain, you need to4
,. 'odel transport routes from the transport domain controller, using4
. %efault standard configurations /one), t!o), and three)system
landscapes0
. Braphical editor for non)standard configurations
1. %istribute and activate the ne! configuration data for all SAP systems
!ithin the transport domain
(o reduce the effort of specifying individual transport routes, you can use standard
configurations. (ransport routes for the standard configurations are generated
automatically.
<ou can choose from the follo!ing standard configurations4
Single system
%evelopment and Production System
(hree Systems in Broup
#f you use the standard configuration function, the current configurations for all
SAP systems involved are replaced by the standard settings. E$isting pac+ages,
transport layers, or objects created in the SAP system are not deleted. =or
comple$ system landscapes, define additional consolidation and delivery routes
after setting up the transport route configuration on the basis of one of the standard
configurations.
After you define a transport route, you must activate and distribute it to all systems
in the transport domain.
(here is a version management of the stored configurations. #f you modify and
save an active configuration, the version counter increases. (o activate a stored
version, from the start screen of transaction S('S choose 0%er%ie# . 'ransport
Routes . Coniguration . !et 0ther %ersion. (his displays a list of all versions
of the transport route configuration. Select the version you !ant from the list. (o
activate an older version, use the distribute and activate procedure.
(o ensure consistency, transport routes can be configured only on the domain
controller. (o help define a transport route, the ('S provides a graphical editor
and a hierarchical list editor, !hich can be used interchangeably, as !ell as
standard configurations for a one), t!o), and three)system landscape.
Transport .ayers an$ Transport &outes
As previously stated, transport routes define the flo! of the change re*uests from
one system to the ne$t. (hese routes are called either consolidation or delivery
routes.
A consoli!ation route is an .e$port 8 import. route. (ypically, the consolidation
route proceeds from the development system /!here the transport re*uest is
e$ported from0 to the *uality assurance system /!here the transport re*uested is
imported into0 in a standard three)system landscape. :onsolidation routes have
names in order to be addressed.
A !elivery route is an .another import. route. #n a standard three)system
landscape, the delivery route is specified bet!een the *uality assurance system
and the production system because there is no additional e$port from the *uality
assurance system but another import in the production system. %elivery routes
have no names.
All repository objects are grouped into logical units called pac+ages /formerly4
development classes0. (he definition of each pac+age contains an assignment to a
transport layer. (he transport layer is the name of a consolidation route. Objects,
via the assignment to the pac+age, inherit this transport layer assignment.
All SAP delivered objects are assigned according to their pac+ages to the transport
route SAP.
:ustomizing objects /and others0 are not grouped into pac+ages. (hey follo! the
standard transport route. (his standard transport route is typically named LDSID
o the de%elopment s,stemE.
#n the conte$t of transport routes, an SAP system may play the follo!ing roles4
%ntegration system
(he system !here changes originate and are assigned to transport re*uests.
(he system !here customer changes are integrated !ith the SAP standard,
customer developments and modifications ta+e place.
Consoli!ation system
(he target system of a consolidation route.
0elivery system
(he target system of a delivery route.
<ou need to configure more transport layers and transport routes if you have a
more comple$ landscape and you need to reroute certain objects a!ay from the
standard transport routes. =or e$ample, if a separate training system e$ists and
there are certain programs that are to run there but you do not !ant those programs
getting into the *uality assurance or production systems.
#f the standard configurations delivered by SAP do not meet your landscape needs,
('S has editors available to allo! you to maintain the landscape.
(he graphical editor delivers a visual drag and drop interface, !here the systems
in the domain can be positioned and lin+ed using the mouse. (his is the default
editor in the transaction S('S. #t is sho!n in the follo!ing figure.
(o create transport routes, use the mouse to drag the appropriate SAP systems
from the node area, and drop them in the display area. (o create a transport
route bet!een these SAP Systems, from the screen Displa, 'ransport Routes,
choose the Add 'ransport Route button. (he mouse pointer becomes a stylus.
5sing the stylus, dra! a line connecting the t!o SAP systems bet!een !hich
a transport route is desired. #n the Create 'ransport Route popup, enter the
re*uired information for either the consolidation or delivery route. #n case of
a consolidation route you need to assign a transport layer. <ou can create the
transport layer right here. Save your changes. (he follo!ing figure sho!s a more
comple$ landscape.
Distri%ution an$ Acti"ation of Transport &outes
:hanges in transport route configuration are not valid until distributed and
activated. (o distribute and activate the changes from the ('S editor of the
transport domain controller, choose the Distribute and Acti%ate icon and activate
or follo! Coniguration . Distribute and Acti%ate. =or activation the =:
connections are used, that are created during the setup of the transport domain.
(o avoid any possible inconsistencies, especially if there are any released transport
re*uests !aiting in any import *ueues, ('S performs a number of consistency
chec+s on the version of the transport routes being activated, for e$ample,
!hether the settings of the transport control program tp are consistent !ith the
transport route configuration. (he activation also triggers chec+s to verify that
ne! transport routes do not affect e$isting transport re*uests. #f any problems
e$ist, the configuration !ill not be activated and you !ill receive an error message
indicating the nature of the error.
'ote" Once you have configured the transport routes correctly, the only
reason that changes !ould need to be made !ould relate to a change in
your system landscape, for e$ample, adding a ne! system or ne! clients
to the landscape.
Con-guring JA Appro"al Proce$ure
"hen a transport re*uest is released and e$ported from the development system
/%EI0, the consolidation systemHs />AS0 import buffer is populated. (he import
buffer is a list of transport re*uests !aiting for import. Once the transport re*uest
is successfully imported into the consolidation system, the import buffer for all
delivery systems /P%0 is populated.
"ith the >A Approval Procedure , the buffer of the delivery systems is populated
but the entries are flagged as inactive. #n other !ords, the transport re*uests cannot
be imported until the responsible person/s0 flags the transport re*uest as approved,
!hich results in activating the entries in the delivery systemsH buffers.
('S >uality Assurance increases the *uality and the availability of the production
systems by letting you chec+ transport re*uests in the >A system before they
are delivered to subse*uent systems. (he system for !hich the >A approval
procedure is activated is called the >A system. "hen the >A approval procedure
is activated, a transport re*uest !ill only be imported into the delivery system/s0
if all the >A approval steps are processed in the >A system and the re*uest has
been approved. "hen you configure the >A system, you determine ho! many
>A approval steps have to be processed for each re*uest.
(he figure above sho!s you ho! to activate the >A approval process from the
graphical editor and ho! to define the approval steps.
>erifying the T,S Setup
Once you have configured the ('S, there are some tests that you can perform to
verify that there are no technical problems !ith the ('S configuration4
. =: connection test
. (ransport directory chec+
. (ransport control program /tp0 chec+
Because the domain controller communicates !ith the other systems in the
domain using =:s, you should chec+ the =: connections bet!een the systems
in the domain. (o do this, from the S,stems screen of the S('S, select a system
from the list and choose SAP s,stem . Check . Connection 'est. (his verifies
communications in both directions . to and from the domain controller.
Since e$ports physically !rite files to the operating system /OS0 level and
imports read and update these files, you should verify that the transport directory
is available and has the appropriate OS level permissions. (o do this, from
the S,stems screen of the S('S, choose SAP s,stem . Check . 'ransport
Director,. (his action creates, reads, and deletes a file to each of the transport
directory subdirectories and returns a report on the success or failure of all
subdirectories. #f you receive any errors, the appropriate corrections !ould need
to be made at the operating system level.
Because e$ports and imports are physically e$ecuted by the operating system level
program tp, you should verify that the tp program and its parameter configuration
are consistent. (o do this, from the S,stems screen of the S('S, follo! SAP
s,stem . Check . 'ransport 'ool. (his e$ecutes tests verifying the tp interface,
the transport profile, the =: destinations, and connection to the databases and
returns a report of the results.