Netweaver Trainig Manual(1)

8/11/2019 Netweaver Trainig Manual(1)

1/194


2/194

SAP Business ByDesign

SAP Business By%esign is based on an entirely ne!ly developed, designedapplication platform. Business applications have been programmed ane! fromscratch 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. Butthis is not the definition of an Enterprise Service Oriented Architecture /EnterpriseSOA0. #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 toimprove their core processes and at the same time benefit from lo!er entry andoperating costs. #t is aimed, in particular, at midmar+et companies !ho are notusing 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 demandsolution. An on demand solution that distinguishes itself through integratedservice and support, adaptability and more user friendliness and also guaranteestransparency and the observation of legal re*uirements ) all this on the basis ofan Enterprise SOA by design. SAP Business By%esign the most complete, fullyintegrated on demand solution. 'ore than a pure niche solution, it supports there*uirements of midsize companies in all areas such as effective management offinances, human resources, projects, production as !ell as supplier and customerrelationship management as !ell as regional and local legal re*uirements andcompliance management as core design principles. #t !as not developed !iththe traditional categories of business applications or customer relationshipmanagement and others. #t !as rather developed for business processes in theentire 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 !ithfe! employees and comparatively stable processes can use preconfigured SAPsystems. SAP All)in)One is the brand name for vertical /industry)specific orcountry)specific0 applications that are based on the technology of SAP 6et"eaverand !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 orhosted by a partner and is based on SAP EP. #t provides an industry)specificfunction portfolio based on SAP Best Practices. #t is made available through 77-midmar+et solutions by more than ,--- partners. SAP Business All)in)One isaffordable and can be planned and than+s to preconfigured business scenarios andimplementation accelerators it can be implemented s!iftly /2 to 7 !ee+s0. SAPBusiness All)in)One is currently being used by more than -,--- customers inover 3- countries.

SAP Business Suite in Detail

(he SAP Business Suite, !hich has evolved from older 8 releases or SAPsystems, is not Enterprise SOA by design but by evolution. Put differently4 the


3/194

ability to use Enterprise Services !ill be .enabled. subse*uently, but this !asnot a design principle from the start. Of course, SAP EP 7.- !ill also enableEnterprise SOA integration scenarios, especially by means of the 9# EnterpriseService epository.(his remar+ is intended as bac+ground information for the instructor and shouldonly 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 businessapplications provide users !ith consistent results throughout the entire companynet!or+ and give your company the fle$ibility it needs in today.s dynamic mar+etsituations. (he application consists of a number of different products that supportcross)company processes.

SAP.s soft!are portfolio is constantly e$tended, optimized, and tailored to theneeds of the mar+et and of customers. SAP has therefore, for e$ample, developedmany industry)specific applications over the years. (he topic of integratingdifferent business systems /even from different vendors and across company

boundaries0 has become increasingly important recently. Products for small tomidsize 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 thecomprehensive and fle$ible business applications !ith highly evolved functions4complete integration, industry)typical functions, unlimited scalability and smoothcollaboration via the internet.

(he SAP Business Suite provides4. A complete spectrum of business solutions. A technological infrastructure that combines openness and fle$ibility !ithmaturity and stability

. #nterfaces for integrating non)SAP products. :omponents that can be adapted to meet multiple business re*uirements

. 6umerous industry)specific functions


4/194

Business Process Platorm (BPP)

A Business Process Platform is the prere*uisite for the deployment ofa service)oriented architecture for business applications /EnterpriseService)Oriented Architecture, Enterprise SOA0. (he SAP BPP is composedof the follo!ing modules4

SAP et!ea"er

SAP 6et"eaver is an open integration and application platformfor 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 andtechnology)independent integration and coordination of employees,information and business processes. (han+s to open standards,information and applications from any source and based on anytechnology 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 platformprovides a ma$imum of reliability, security and scalability ensuring thatbusiness 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 recentSAP applications use the Enterprise Service Repository, repositoryfor processes and Enterprise Services. Enterprise Services map

business processes using open standards.Both SAP 6et"eaver and the SAP applications are continuously enhancedthrough Enhancement Packages. Enhancement pac+ages are shippedat regular intervals in order to ma+e it possible to respond to mar+etre*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., !hichyou can use to promote improvements and innovation in your company moreeasily. "ith their ability to combine e$isting, heterogeneous systems toform cross)functional processes, SAP $Apps :omposite Applications bring

people, information, and business processes together to ma+e your companymore dynamic and competitive. (his fle$ibility enables you to implement

business)!ide strategies more easily and efficiently. SAP $Apps increasethe value of e$isting investments in the core business area and ma$imize thereturn on strategic investments4 employees, +no!ledge, products, businessrelationships, and information technology.


5/194

(his graphic is still brand ne! /in > 1--?0 and differs significantly from earliergraphics. One reason !as to bring the product vie! /."hat SAP products [email protected] and the license vie! /."hat can you buylicense from [email protected] closer(ogether.(he follo!ing list should help to e$plain !hat is behind the individual terms. #nSAP(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 individualapplications. #f they are still valid, the specified lin+s provide additional#nformation.

Applications for Governance Risk an! Compliance (GRC)" Applicationsfor governance /SAP : epository0, ris+ management /SAP : is+'anagement0 and compliance !ith legal re*uirements /SAP : Access:ontrol, SAP : Process :ontrol, SAP : lobal (rade Services, SAPApplications for environment, health, and safety compliance management,: composite applications by SAP and :isco0C for more information see

Applications for Performance #anagement" Applicationsfor performance management /SAP Strategy 'anagement, SAPBusiness Planning and :onsolidation, SAP Business Profitability'anagement by Acorn, SAP $App Analytics0.

SAP Enterprise Resource Planning (SAP ERP)" Applications forsupporting resource planning across an entire enterprise. SAP EP Duman :apital 'anagement. SAP EP =inancials. SAP EP Operations


6/194

. EP :orporate Services

SAP Customer Relationship #anagement (SAP CR#)" Applications forend)to)end, customer)oriented business processes.

SAP Supplier Relationship #anagement (SAP SR#)" SAP S'integrates strategic purchasing processes such as vendor *ualificationand vendor management, electronic invitations for tender and auctionsor contract management !ith the other core processes in your companyand !ith the processes of your suppliers.

SAP Supply Chain #anagement (SAP SC#)" Applicationsfor managing the entire logistical chain to synchronize supplyand demand across company borders.

SAP Pro!uct $ifecycle #anagement (SAP P$#)" Applicationsfor 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

. ogistics 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

. ife sciences

. Oil and gas industry

SAP xApps Composite Applications" :omposite applications that coverseveral 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 ean Planning and Operations /SAP $PO0. 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 employeesaccess to company data and business processes anytime and any!here


7/194

. %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 SAPapplications. 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 o Applications an$ Components

6umerous applications for business challenges are provided in the conte$t ofthe SAP Business Suite. Do!ever, many applications have similar or identicalre*uirements for business functions in subareas. %ifferent applications thereforecontain 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 oralso an SAP 6et"eaver portal system. (he graphic provides an overvie! ofthis hierarchy /components as building bloc+s of solutions0 using the SAP S:'application as the e$ample.

Possi%ilities with SAP Business Suite


8/194

(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 Businesssuite 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.


9/194

'istory o Selecte$ Sotware 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 SAP80, the development of the /technical0 basis !as closely lin+ed to applicationdevelopment. (he release names of the SAP Basis corresponded to the SAP 8version, for e$ample, SAP Basis 2.-B !as the technical basis for SAP 8 2.-BAround the turn of the millennium, the SAP portfolio gre! significantly, ne!

products !ere created that re*uired more fre*uent changes and enhancements ofthe SAP Basis than SAP 8. (his mar+s the transition from the classical SAPBasis /last version4 SAP Basis 2.7%0 to SAP &e Application Server /SAP "ebAS0. 6e! internet technologies /#nternet :ommunication 'anager from SAP"ebAS 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 SAP6et"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&eaverApplication 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


10/194

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 applicationdevelopment !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 conceptof SAP 8 Enterprise E$tensions !as introduced.A central application /previously4 solution0 of the SAP Business Suite is SAPEP for Enterprise esource Planning. (he central soft!are component of SAPEP 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 isSAP 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 madeavailable 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 asSAP 6" Process #ntegration /P#0 and SAP 6" :omposition Environment /:E0already 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 offeredto customers in t!o phases.


11/194

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. (heRelease to Customer date mar+s the start oftheRestricted Shipment Phase.%uring the restricted shipment phase, the ne! soft!are release passes through a

standardized process, theRamp-Up. :haracteristics of the ramp)up process are4. amp)up is the name for the mar+et introduction process of ne! productsor 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 ofcustomers, customers .apply. to SAP to participate in a ramp)up.. (he ramp)up serves to ta+e customer !ishes into consideration before therespective SAP soft!are is generally available.. Participants in the ramp)up are given direct contact to the SAP developmentand 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. AftertheDeault Release Date all customers can re*uest the ne! soft!are !ithoutrestrictions.(he respective latest, generally available version of SAP soft!are is calledDeault

Release. "hen SAP customers order soft!are from SAP, they are usually giventhe current default release.

,aintenance


12/194

via the SAP Service 'ar+etplace. Support Pac+ages solve /component)dependent0problems that can result !hen using the SAP soft!are. SAP provides theseSupport 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 productsthat are based on SAP 6et"eaver. (his 3))1 maintenance strategy offersmaintenance for five years for the mainstream maintenance, follo!ed by one yeare$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 thestandard 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 timeand 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 /F1Gfor year, F2G for 1 years0.

Customer-specic maintenance

=rom a certain point in time during the lifecycle of a release, this releaseis no longer adjusted to meet e$ternal re*uirements. Such re*uirementsare, for e$ample, the implementation of legal changes or the support ofne! technologies. (he time in *uestion is mar+ed by the end of e$tendedmaintenance or the end of mainstream maintenance, if no e$tendedmaintenance is offered. :ustomer)specific maintenance starts at this pointin time.

'ote" See http488service.sap.com8maintenance for additional informationon the maintenance strategy. SAP note 313-3 deals specifically !ith the

particularities of customer)specific maintenance.


13/194

+pgra$e


14/194


15/194

the 9' and ;ava !orld to do so.

Application Platorm

(he SAP 'et&eaver Application Serverprovides a proven infrastructurefor operating business applications that are based on +ey technologies suchas ;1EE or ABAP. Besides the runtime environment for ;1EE and ABAP

applications, the corresponding development tools are also shipped and helpyou implement your applications. Open standards, bro!ser)based access toapplications and !eb services complete the application platform and serve asan important instrument for the enterprise service architecture.Beyond these four steps and in parallel to them, SAP 6et"eaver offers ifecycle'anagement and the :omposite Application =rame!or+4

.iecycle ,anagementifecycle 'anagement supports design, development, deployment andchange management of the entire solution and thus meets the re*uirementsin 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, rulesand methods to create ne! applications that are based on business processesacross function areas.

SAP et!ea"er Application Ser"er (SAP et!ea"erAS

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 theapplication platform of SAP 6et"eaver.


16/194

SAP 'et&eaver AS is the logical result of the further development of theSAP Application Server (echnology /previously4 SAP Basis0, !hereby special


17/194

attention is paid to !eb)based applications.SAP 6et"eaver AS offers4. A reliable and e$tensively tested runtime environment, !hich has beendeveloped further continuously over more than ten years. A frame!or+ for e$ecuting comple$ business processes that meet the highestsecurity standards. A reliable and user)friendly development environment

. Support for open standards, including D((P, D((PS, S'(P, "eb%AI,SOAP, SS, SSO, 9.3-J, 5nicode, D(', 9' and "'. Digh scalability. Support for different operating system and database platforms

Since the applications delivered by SAP do not al!ays re*uire both runtimeenvironments, that is, ABAP and ;ava, there are different installation options forSAP 6et"eaver AS. (hese are4. SAP 'et&eaver AS ABAP" :omplete infrastructure in !hich ABAP)basedapplications can be developed and used.. SAP 'et&eaver AS 1ava" :omplete infrastructure in !hich ;1EE)conformapplications can be developed and used.

. SAP 'et&eaver AS ABAP21ava" :omplete infrastructure in !hichABAP)based and ;1EE)based applications can be developed and used. (hisinstallation emphasizes the seamless ;ava)ABAP integration.


18/194

Lesson 3

a"igation

a"igation in 1eneral

Diferent +ser /nteraces in the SAP )n"ironment

(here are numerous different types of SAP systems, such as .classical. EPsystems, 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, thesedifferent 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 notall possible /K0 access technologies are listed in all cases. =or e$ample, an SAPE:: 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 /raphical 5ser #nterface0 enables the userto interact !ith the SAP system and enter or display data.SAP !UI implements the graphical user interface using the functions provided bythe relevant presentation environment. SAP 5# is based on the "indo!s Styleuide and is available for several platforms, providing the same functions foreach. #f you learned to use SAP !UI on one platform, you can use the system onanother platform e$actly the same as before, !ith the e$ception of a fe! small

platform)specific 5# 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


19/194

. SAP !UI for the ;ava Environment

. SAP !UI for D('

'ote" #n the above list, the official terms of the SAP !UI are usedC theseare only available in English. :ollo*uially, the follo!ing terms are usedsynonymously /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 5# are suitable only for!or+ing !ith ABAP)based SAP systems /including the SAP 5# 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/s0is the SAP !UI implementation in a 'icrosoft "indo!s environment. SAP 5#for "indo!s is !ritten in : or :FF, runs on "indo!s)based platforms, andsupports all transactions in an SAP system.

(he data flo! bet!een the presentation layer and the application layer does notconsist of prepared screens, but rather of logical, compact information aboutcontrol elements and user input /%#A protocol0. (he volume of data transferredfor each screen change is generally a fe! LB.


20/194

'ote"


21/194


22/194

5ser data is stored in the system by client, that is, you can, for instance, log onto client -- in your system, but you !ill not have a user for client 1--, even ifyour system has a client 1--. (he data for a particular user !ithin a client iscalled the user master recor!.'ultiple logons to SAP systems are logged. (his is for reasons of both securityand licensing. #f the same user logs on more than once, then for each subse*uentlogon, the system displays a !arning message that offers the user the follo!ingthree options4. :lose all e$isting session/s0 and log on again. Leep e$isting session/s0 open, and open an additional session /this isrecorded 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 thefirst 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.


23/194

Changing the Change$ Passwor$ Again Prere2uisites

4int" 5sers can change their pass!ord no more than once a day on theinitial screen. #n contrast, user administrators !ith authorization fortransaction S3+8can change a userHs pass!ordas 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#ordpushbutton.. :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 systemappearsC 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 leftside of the screen contains a tree hierarchy of the menus available to you in theSAP systemC you can use the right side of the screen to display your companylogo. (his graphic is made available centrally by your system administrator andcannot be customized by individual users.


24/194


25/194

An SAP user interface can contain the follo!ing simple screen elements, fore$ample4. :ommand field. 'enu bar, system function bar, title bar, application toolbar, status bar. :hec+ bo$es. adio buttons

. (ab


26/194

(he title ar is the function that you are currently in.(he application toolar sho!s the pushbuttons available in the application thatyou are currently in.(he Status ar displays information on the current system status, such as!arnings and errors.


27/194

sessions !ith the means of the operating system, such as by usingthe +ey combinationAlt234. "hen you close the last !indo! ofyour 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 representsthe standard access point to an SAP system for the SAP 5# 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.


28/194

Easy Access /and the other notes listed therein0 for information on identifying anddeleting duplicates, and related *uestions.

4int" As long as you have the appropriate authorization, you can alsodisplay user menus other than the ones assigned to you in your user masterrecord. (o do this, choose 0ther menu. 5se Create role to start the role

maintenance transaction, P=:.

(he user and SAP menus can be structured in a pretty comple$ !ay. #t is thendifficult to remember the e$act path for the transaction you are loo+ing for. As longas the transaction has not been copied into the favorite area, you can find it moreeasily !ith special search transactions. (he transactions SEARC49SAP9#E'3and SEARC493SER9#E'3 search the corresponding menus for the predefinedte$t pattern. (he search result is prepared in a list vie! from !hich you can ta+ethe navigation path. (he transactions found cannot be started directly !ith adouble)clic+.

*a"orites ,anagement

#n addition to the area menu or SAP menu, the user is also provided !ith functionsin the favoritesH area. in+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 tointernet content or to files on the end userHs front)end computer. (he favoriteslist, !hich is initially empty, can be edited by each end user in accordance !ithhis or her preferencesC you can only vie! your o!n favorites list. Since data onthe favorites is stored !ithin the SAP system, each user might have differentcollections of favorites in different systems.

4int" :omplete favorites menus, incl. the folder structures, can be easilycopied by uploading or do!nloading from one SAP system to another. (hedo!nloaded favorites menus are stored temporarily on the front)end P:.(o improve the structuring, sort the favorites in o!n folders.


29/194


30/194

= +ey to display possible entries for this important field. (he follo!ing entriesare 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, Accessscreen.. 3o to display the overvie! of o!n sessions

. 3o8888 to call transaction 9999 in a ne! session directly from anothertransaction. 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 doesnot display the input help. (he =2 +ey in the OL :ode field lists the last3 different entries in the OL :ode field. (his list is stored in the registryon the front end and is valid for all sessions on the front end /regardlessof the system used0.

'elp Options

(he SAP system provides you !ith various help options, !hich !ill be introducedin the follo!ing section.

*9 'elp


31/194


32/194

(he =2 help displays a list of possible entries for a field. #f there are a largenumber of possible entries, a separate selection screen is displayed. #f there is along hit list, the =2 help only displays as many entries as the user has specified onthe34 &elp tab page under&elp ./// Settings. (he default value for the ma$imumnumber of displayed hits is 3--. (a+e the time to familiarize yourself !ith theother settings you can ma+e here.

4int" 5sers can also create personal values lists. An S&% employee !hois only responsible for 'unich, for e$ample, only !ants to see the 'unichclients and defines a corresponding personal value list. Do!ever, despitethis, the employee still has the option at all times of s!itching to the totalvie! of all customers or of updating or completely deleting the values list.

SAP .i%rary (Online Documentation

(he SAP $irary is a useful aid to getting to +no! system functions. #t allo!syou to access the online documentation. (he information stored here does notsimply describe ho! to use system functions, it also e$plains system architectureconcepts, gives e$amples of ho! you can configure various processes, and !arnsyou about possible user errors and their conse*uences. (he online documentationalso contains several tips and tric+s to help you carry out common tas+s moreeasily and *uic+ly.


33/194

4int"


34/194


35/194

Lesson 4

Principal Architecture o the SAP et!ea"erApplication Ser"er

/ntro$uction

SAP systems are used for mapping business processes or business applications.(hese applications should be implemented independent of the hard!areenvironment used /operating system, database0 to the greatest e$tent possible. (odo so, SAP +et"ea%erprovides t!o different runtime environments4 an ABAPruntime environment /usage typeAS ABAP0 and a ;ava runtime environment/usage typeAS $a%a0.0.ABAP /Advanced Business Application Programming0 is a programminglanguage 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 developingcompletely ne! applications as !ell as enhancing and modifying SAP standardapplications. #n doing so, the entire, mighty infrastructure of the AS ABAP can

be used, !hich also supports the creation of the most comple$ applications bylarge groups of developers. (he Application Server ABAP provides the runtimeenvironment for programs !ritten in ABAP.

SAP not only provides a runtime environment for ABAP programs but alsoa runtime environment for 1avaprograms.AS $a%a is an application serveraccording to the ;ava 1 Enterprise Edition /;1EE0 standard.(he 1avaprogramming language !as first introduced by Sun 'icrosystems#nc.. in JJ3. ;ava is an object)oriented and platform)independent programminglanguage that has spread across many areas. (he ;ava concept enables thedevelopment of a large range of different application types ) from classicalapplications to applets used in !ebsites to client8server applications.1ava ; Platform Enterprise E!ition (1;EE) is a vendor standard for a !holerange of soft!are components that are primarily created in the ;ava programminglanguage. 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+ forusing modular components to develop distributed, multi)level applications. "iththe ;1EE specification, Sun !ants to ensure that conform "eb applications run onall ;1EE compatible servers. According to the ;1EE specification the application

logic is pac+aged in Enterprise 1avaBeans /E;B0. (hey represent ;ava programcomponents. A container implicitly provides the components !ith the servicesof the runtime environment.

Client an$ Ser"er; Terminology Denition

Before !e discuss various client8server configurations in the conte$t of SAPsystems, !e first need to define the concepts client and server. (here are basicallyt!o !ays of doing this.#n the har!/are6oriente! vie!, the term server means the central server in anet!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 processlevel /service0. A service in this conte$t is a service provided by a soft!arecomponent. (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


36/194

that service. Soft!are components that use a service are called clients. At thesame 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 asdefined in the soft!are)oriented vie!.

Client3Ser"er Conguration or 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 numberof 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 classicmainframe processing.. (!o)tier configurations are usually implemented using special presentationservers that are responsible solely for formatting the graphical interface.. #n a three)tier configuration, each layer runs on its o!n hosts. 'any differentapplication servers can simultaneously !or+ !ith the data of a databaseserver.


37/194

Single)tier configurations are generally used for tests and demonstrations /fore$ample, an SAP system on a laptop0. #f many users !ant to !or+ on a systemconfigured in this !ay, then the e$tra hard!are costs for each additional user

become greater than the costs associated !ith implementing additional hard!arelevels /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 highernumber of users, !ithout substantially increasing the hard!are costs. (he loadresulting from the presentation processes is distributed to the various front)endcomputers 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 bydistributing the application)layer processes to several hosts. Another advantage ofadding a hard!are layer specifically for application processes is that it facilitatesscalability. #f the number of SAP users in a system increases over time, negativelyaffecting system performance, then this problem can, in most cases, be solvedsimply by adding another host for application processes.

An alternative t!o)tier configuration is to install po!erful des+top systems andto use these for presentation and applications /t!o)tier client8server0. (heseconfigurations are especially suited to applications !ith high processor demands/for e$ample, simulations or for soft!are developers0, but are not implementedin the SAP environment, other than for test purposes, due to the additionaladministration re*uired.

#n the SAP Business Suite environment, more comple$ client8server configurationsconsisting 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 /nstanceAn instance is an administrative unit that combines SAP system components

providing one or more services. (he services provided by an instance are started


38/194

or stopped together.


39/194

Processes o 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 AAP 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!areresources4. (he!ispatcher distributes the re*uests to the !or+ processes.. 0ialog /ork processes fulfill all re*uests for the e$ecution of dialog stepstriggered by an active user. Every dispatcher re*uires at least t!o dialog!or+ processes.. Spool /ork processespass se*uential data flo!s on to printers. At leastone spool !or+ process is re*uired for each SAP system. #t is possible toconfigure 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, andyou can configure more than one per dispatcher.. Backgroun! /ork processes e$ecute programs that run !ithout interacting!ith the user.


40/194

(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 thenumber of different !or+ processes.

#n addition to the !or+ processes, the ABAP runtime system provides additionalservices /these are not !or+ processes0 for internal and e$ternal communication4. (he#essage Server /'S0 handles communication bet!een the distributeddispatchers !ithin the AS ABAP, thereby enabling scalability of several

parallel application servers. (he message server is configured only onceper SAP system.. (hegate/ay reader /"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 #:' receivesre*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 acall 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 andsend the response bac+ to the SAP system.


41/194

(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 ismulti)threaded and can thus process a large number of re*uests in parallel /incontrast to the ABAP !or+ processes0. =or each dispatcher there is at leastone server processes and there can be up to 7 server processes.

. (he ;ava message service manages a list of ;ava dispatchers and serverprocesses. #t is responsible for the communication !ithin the ;ava runtimeenvironment.. (he ;ava en


42/194

can access the ABAP schema of the database, and the ;ava runtime environmentcan access the ;ava schema. #n the ABAPF;ava system, the different runtimeenvironments 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 systemare usually called dialog instances. Alternatively, the instances are also namedafter 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, fore$ample, as a dialog server and simultaneously as an update server, if it providesseveral dialog !or+ processes and at least one update !or+ process.

'ote" An overvie! of the AS ABAP instances is available in S'3 /inSAP Easy Access under 'ools ./// Administration ./// (onitor ./// S,stem

(onitoring./// Ser%ers.


43/194

'ote" An overvie! of users !ho are logged on the the instance to !hichyou are also logged on, is available using transaction S'-2 /'ools.

Administration ./// (onitor./// S,stem (onitoring./// User 0%er%ie#0.


44/194

#n the AS ;ava, the en*ueue service holds logical loc+s. Each node of the ;avacluster can communicate directly !ith the en*ueue service."hen the AS ;ava is accessed using a bro!ser, the ;ava dispatcher receivesre*uests, !hich are then processed by the server processes.

AS ABAP4


45/194

one of the server processes responds to the re*uest.#n an AS ABAPF;ava system, data is also +ept in separate database schemas /butin the same database installation0. (hat is, !or+ processes can only access ABAPdata and server processes can only access ;ava data. #n the data e$change, bothruntime environments then communicate using the SAP 1ava Connector /;:o0.(his communication is necessary, for e$ample, if billing data that is stored in theABAP 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 ;avasystem has to communicate !ith a remote AS ABAP system.

AS ABAP Processes

Processing o &e2uests in AS ABAP

(he users can log on to the SAP system using either the SAP 5# or a "eb client/bro!ser0. "hen logging on via the SAP 5#, user re*uests are processed by theABAP runtime environment, !hen logging on via a bro!ser, processing can bedone 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 logondirectly 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, involvesdifferent processes on all three layers /presentation, application and databaselayer04

(he screen entries of a user are accepted by the SAP presentation programSAP G3% /SAP raphical 5ser #nterface0, converted to an internal format andfor!arded to AS ABAP.


46/194

(he /ABAP0 !ispatcher is the central process of AS ABAP. #t manages theresources for the applications !ritten in ABAP in coordination !ith the respectiveoperating system. (he main tas+s of the ABAP dispatcher include the !istriutionof the re


47/194

interpreter. (he screen processor tells the ABAP processor !hich subprogramneeds 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 userconte$t first. (hat is, the data that contains the current processing status of arunning program as !ell as data that characterizes the user is made +no!n tothe !or+ process. (he !or+ process then processes the user re*uest, !hich mayinvolve, 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 sharedmemory, and is no! available again for a ne! user re*uest from the re*uest *ueue.(he result is transferred to the SAP 5# and the user sees the ne! screen.

elational %atabase 'anagement Systems /%B'S0 are generally used tomanage large sets of data. An %B'S saves data and relationships bet!eendata in the form of t!o)dimensional tables. (hese are +no!n for their logicalsimplicity. %ata, tables, and table relationships are defined at database level in thedatabase catalog /the data dictionary0 of the %B'S."ithin the SAP programming language ABAP, you can use ABAP Open S>/S> Structured >uery anguage, database *uery language0 to access theapplication data in the database, regardless of the %B'S used. (he database

Data%ase /nterace o AS ABAP

interface, !hich is part of every !or+ process of AS ABAP, translates OpenS> statements from ABAP into the corresponding S> statements for thespecific database used /6ative S>0. (his allo!s ABAP programs to be!ataase6in!epen!ent.

'ote" ABAP Open S> is a database *uery language based on the /#SO0S> standard that also contains enhancements that are not included inthe standard.

"hen interpreting Open S> statements, the SAP database interface chec+s thesynta$ 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*uentlyre*uired by the applications is stored in these buffers so that the system does nothave 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 anoperational system and are therefore ideally suited to buffering.


48/194

=urthermore, native S> commands can be used directly in ABAP, that is,!ithout using the local buffers and !ithout the database interface interpreting thecommands. , you can nolonger 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 duringe$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 usersand programs.(his is illustrated by the follo!ing figure.


49/194

SAP application programs differentiate bet!een user interaction and processinglogic. (he user actions are technically realized using screens, also called !ynpros/from dynamic programs0, !hich consist of a screen image and the underlyingflo! logic. (he dynpro processor of the !or+ process e$ecutes the screen flo!

logic of the application program, calls processing logic modules, and transfersfield content to the processing logic. (he screen flo! logic itself is further dividedinto PB7 /Process Before Output0, !hich is processed before the screen image issent, and PA% /Process After #nput0, !hich is processed after a user interaction onthe screen. (he PA# part of a dialog step logically belongs to the preceding screenimage, !hile the PBO part logically belongs to the subse*uent screen image. (heactual processing logic of ABAP programs is e$ecuted by the ABAP interpreter.(he screen processor tells the ABAP processor !hich subprogram needs to bee$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, !hichenables 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 havefour principal characteristics. (he initial letters of these characteristics togetherform the acronym AC%0 .. Atomic. :onsistent

. #solated

. %urableAtomic means that a transaction is either fully successful or does not have anyeffects at all. #f a transaction)oriented system goes do!n, you need to ensure that


50/194

inconsistent, partial results are not stored.Consistent means that the system status changes from one that is accurate andconsistent 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 byother transactions, even those that run simultaneously, after the final confirmation

/.:ommit.0.(he results of a transaction are !uralebecause after the final confirmation theyare stored permanently in the database.

Data%ase Transactions an$ ABAP Transactions

Every !or+ process is connected to a specific communication partner at databaselevel for the duration of an SAP instanceHs runtime. "or+ processes cannote$change communication partners at runtime. (his is !hy a !or+ process can onlyma+e changes to the database !ithin one database transaction.A database transaction is, in accordance !ith the A:#% principle, a non)divisiblese*uence of database operations, at the beginning and end of !hich the dataset onthe database must be consistent. (he beginning and end of a database transactionare defined by a commit command /.database commit.0 to the database system.%uring a database transaction /bet!een t!o commit commands0, the databasesystem itself ensures that the dataset is consistent. (he database system itself ta+eson the tas+ of restoring the dataset to its previous state after a transaction hasterminated !ith an error /.rollbac+.0.Business transactions are processing units grouped to provide a specific functionCthese processing units e$ecute changes to the database that are consistent andma+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 relevantmaterials. :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 thatare consistent in business terms. Every user dialog step is represented by onescreen image.


51/194

SAP transactions are not necessarily e$ecuted !ithin one single dialog !or+process. "ithin a transaction that changes data on the database, the userre*uests database changes using the displayed individual screens. Once thetransaction 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 forunrelated 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 illustratedin the graphic .elationship bet!een database transactions and SAP transactions..

.oc0 ,anagement

(o ensure data consistency !ithin an SAP system, you must ensure that datarecords 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 unit4the !ataase transaction.. (he database loc+ administration can only coordinate

this type of database transaction. =rom an SAP point of vie!, ho!ever, this isnot sufficient, because SAP transactions, !hich are formed from a se*uence of

logically related !or+ steps that are consistent in business terms, are generallymade up of several dialog steps. SAP systems need to have their o!n lockmanagement. (his is implemented using the en*ueue !or+ process. (his alsoensures 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 tale. oc+ entries can only bemade if none already e$ist for the table entries to be loc+ed.(he en


52/194

+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 canaccess the loc+ table directly. #t no! chec+s !hether a ne! loc+ can be generatedCthat 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 theloc+ +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+ processescommunicate through the message server. #n this case, the loc+ re*uest isfor!arded from the dialog !or+ process to the en*ueue !or+ process via thedispatchers 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 viadispatcher 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 containscorresponding entries, the loc+ re*uest is refused. (he application program canthen 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 byone user. (he re*uests for another !rite loc+ and another read loc+ arerejected. 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 theloc+ed data at the same time. (he re*uests for additional read loc+s areaccepted, even if they are from other users. A !rite loc+ is rejected.


53/194

. Enhanced !rite loc+s /loc+ mode e:clusive noncumulative0C !hile !riteloc+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 sametransaction. All other re*uests for loc+s are rejected.. Optimistic loc+s /loc+ mode 7ptimistic0C optimistic loc+s respond li+e readloc+ at first and can be changed to !rite loc+s. An optimistic loc+ is set if theuser 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 optimisticloc+ must be changed to a !rite loc+ /mode E0. /(his fails if someone seta non)optimistic loc+ on the object before.0 Other optimistic loc+s on theobject are deleted in the process.oc+s set by an application program are either released by the application programitself or by the update program once the database has been changed. oc+s thathave been passed on to an update !or+ process in this !ay are also !ritten to afile at operating system level and can therefore be restored if the en*ueue servergoes do!n.(ransaction S'1 /'ools ./// Administration ./// (onitor./// Lock Entries0 displaysthe 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!nerleaving 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 recordssimultaneously.

Caution" Before deleting loc+s, the system administrator must firstchec+ ) susing transaction S'-2 ) !hether the user !ho o!ns the loc+is still logged on to the system.


54/194

changes effected by this process are supposed to be e$ecuted completely or not atall in the database. #f the operation is terminated during the transaction or an erroroccurs, the transaction is not supposed to ma+e any database changes at all. (heSAP update system, !hich is described belo!, ta+es care of this.(he update system also offers increased security, performance and restorabilityin the e$ecution of database changes.

(he updating system is a technology !hich allo!s SAP transactions to off)loadtime)intensive database changes. (hese are then carried out asynchronouslyin special up!ate /ork processes. #t also circumvents the roll)bac+ problemscaused by the difference in the conception of the logical unit of !or+ /5"0 in anSAP transaction and in the database.#f, during a dialog !or+ process, data temporarily stored for processing is passedto an update !or+ process for further processing, the dialog !or+ process doesnot !ait for the update re*uest to be completed4 the update is asynchronous /notsimultaneous0. (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


55/194

#f users !ant to change a data record in an SAP transaction, they call thecorresponding transaction in the dialog, ma+e the appropriate entries on thescreens and then initiate the update process by saving the data. (his processtriggers 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 ifappropriate0. (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 thedata 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 therecord to be changed from the database and the user can change the recordon the screen image of the SAP transaction.. #n the active dialog !or+ process, the program calls a function module usingCALL 3U+C'I0+ ;;; I+ UPDA'E 'AS< and !rites the change re*uestto database update tables. (hese are also called IBQ tables, because theirnames 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 tablesin the database /in a single database transaction0.

2. At the end of the dialog part of the transaction /for e$ample, !hen the usersaves the data . possibly after completing other dialog steps0, the programinitiates the close of the transaction !ith the C0((I' "0R< statement.(he !or+ process that is handling the active dialog step completes the updateheader and triggers an update !or+ process.3. Based on the information /+ey of the update order, loc+ +ey0 transferred fromthe 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 theIBQ tables to the database as a change re*uest and evaluates the databaseresponse. #f the changes !ere successfully !ritten to the target tables, theupdate !or+ process triggers a database commit after the last change to the


56/194

database and deletes the entries from the IBQ tables. #f an error occurs, theupdate !or+ process triggers a database rollbac+, leaves the log records inthe 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 useasynchronous updates !hile programming the transaction. Besidesthe asynchronous update, there are some other update techni*ues /fore$ample, synchronous or local0.(o increase performance further, application developers can configuredifferent types of updates4. time)critical, primary =8 up!ates. (hey are relevant to objects thathave a controlling function in the SAP system, such as a change tothe material stoc+ or an order creation.. non)time)critical, secondary =; up!ates that depend on the Iupdates. (hese are, for e$ample, purely statistical updates such asthe 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 asingle update !or+ process. #f your SAP system has a !or+ process forI1 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)criticalI updates, and that the relevant loc+ entries are deleted sooner. #f youhave 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 /reportRS(7?@@0 triggers the update. All calls ofthe 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 updatecomponent terminates. 5sers can be notified automatically by e$press mail !henan 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 automaticallydeleted the ne$t time you start the system or they can be deleted manually. (heapplication 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 anentry already e$ists in the table under this +ey. (herefore, the corresponding datarecord cannot be !ritten to the database table more than once."hen an update terminates, the system sends an e$press mail to the user !hotriggered the update. Any additional steps must be carried out by the systemadministrator. (ransaction S' /update re*uests0 provides system administrators!ith analysis tools to handle terminated updates. Once the error that caused thetermination has been corrected /for e$ample, hard!are damage repaired0, theend user should restart the processing.

PrintingSAP systems provide a !ide variety of options for representing business and otherdata. (his data, created and formatted in a dialog step, can then be sent to printers


57/194


58/194


59/194

(he end user can usually schedule the program to be started in the bac+groundas a>o from the application transaction. (he job then .!aits. for the plannede$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 displaythe result in the application transaction or, in case of list generating programs, loo+

at the spool re*uest belonging to the job /seePrinting section0. (o display youro!n jobs, choose S,stem ./// 0#n $obs /transaction code S'90.(he system administration and the !or+ preparation have access to a tool forscheduling different types of bac+ground ta+es !ith transaction S'7 /'ools .CC(S ./// Background Processing./// Deine $obs0. (he system)!ide monitoringof jobs ta+es place !ith transaction S(? /'ools ./// CC(S ./// Background

Processing./// $obs - 0%er%ie# and Administration0.=or cross)system scheduling and monitoring of bac+ground tas+s, you can useSAP :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 thecommunication 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 justcalled gate!ay0 is the main process of the gate!ay system. (he dispatcher startsit and chec+s it periodically.

Figure 16: atewa Communi'ation

#n the communication bet!een instances of a system or systems using remotefunction 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 thenta+es care of the communication !ith the remote system. (he gate!ay for!ardsthe re*uest to the gate!ay of the remote system. (he remote gate!ay transfersthe re*uest to the dispatcher. (his in turn for!ards the re*uest to one of its !or+


60/194

processes, !hich then communicates directly !ith .its. gate!ay.#nbound =: connection are therefore al!ays received by the gate!ay. Outboundconnections 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 /fore$ample, ABAP !eb dynpro applications0 or for!arded to AS ;ava in an ASABAPF;ava system /for e$ample, ;ava !eb dynpro applications0. (he #:' canuse the 5 to decide to !here it for!ards the re*uest /if it cannot reply to there*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 ;avadispatcher process to send the response bac+ to the #:'. =inally, the #:' sendsthe 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 theABAP dispatcher /1a0, !hich then handles it li+e a typical SAP 5# re*uest /see

previous section0. (he !or+ process that processes the en*uiry no! communicatesdirectly !ith the #:' /2a0. (he #:' returns the response to the user !ho sentthe re*uest /30.

AS


61/194

A !eb bro!ser is the standard user interface for AS ;ava. A user re*uest forAS ;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 processesof .its. instance.

(he actual processing ta+es place in the serverprocess, !hereby the user !ho sentthe 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 nodesof AS ;ava are multithrea!e!. (his means that an AS ;ava process consists ofmany threads and one re*uest can be processed in each thread. Dence, one serverprocess al!ays processes many user re


62/194


63/194

means of the ;(A interface.#n the ;1EE standard, much of the implementation of the transaction logic isleft to the respective database used. Dence, a transaction at application leveloften corresponds e$actly to one database transaction in the ;1EE standard. (hefollo!ing figure illustrates the correlation using a ;SP application as the e$ample.

Figure "7: ransa'tions in AS 5ava#n AS ;ava, changes and entries in the user interface /in the !eb bro!ser0 are notmade persistent immediately in the database. "hen the user saves his entries, the;ava transaction is completed immediately and the data is made persistent in adatabase transaction. A ;ava transaction thus consists of a database transaction.

PersistenceSAP has created 7pen S?$ for 1ava frame!or+ for AS ;ava. Dence, ;avaapplication developers have access to various database)independent programmingtechni*ues as !ell as important functions for improved performance and troubleshooting.


64/194

Figure "(: 9pen S. for 5ava

#f the ;ava program is supposed to be portale, that is, run !ith a database otherthan the one used originally, developers can choose bet!een Open S>8;%B:,Open S>8S>;, E;B /Enterprise ;avaBeans0 and ;%O /;ava %ata Objects0. #f

developers use 6ative S> in the program, they loose the portability and cannotuse the table buffer of Open S> for ;ava =rame!or+s.

.oc0 ,anagement

(he loc+ concept of the database is used in the ;1EE standard. So if applicationdevelopers ma+e sure that they implement database)independent databaseaccesses, the application !ill be portable but !ill respond semantically differenton different database platforms. =or this reason and to improve response times,SAP introduced the concept of the en*ueue service analogous to AS ABAP.


65/194

#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 Serviceto re*uest a logical lock.

(he re*uest is for!arded to the En


66/194

or ;ava instances, or instances !ith ABAP and ;ava infrastructure.(he :entral Services form a special ;ava instance. (hey provide the basis ofcommunication and synchronization !ithin a ;ava cluster. (he central instance isanother 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 systemcan be scaled using the number of server processes for each instances or using

the number of instances.


67/194

The


68/194

"ithin the ;ava dispatcher, the connection re*uest handler receives the very firstre*uest from a client. #t initializes a connection object, !hich is then assignedto this connection. (he connection re*uest handler then uses load balancing todetermine !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 selectsthe re*uired session service /such as D((P0 on the basis of the re*uest type. (here*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 tothe structure of the ;ava dispatcher. (he server processes are implemented asmulti)threaded servers and can therefore process multiple re*uests in parallel. (hesystem 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. (heyconsist of the message service and the en*ueue service.

(he :entral Services provide the basis for communication and synchronization forthe ;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 loadbalancing information for the SAP "eb %ispatcher.. (heen


69/194

are started !ith the program ;:ontrol /see the unit Starting and Stopping a SAP6et"eaver AS ;ava0.

,essage Ser"ice

(he message service is a separate program that allo!s communication bet!een theelements 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 inthe 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 ofthe 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

. uaranteed message transmission. E$change of cache information in the clusterBy using the message service, you can avoid performance problems that occur ifall the cluster elements are connected !ith each other and e$change data !ith eachother. (his previously lead to significant performance problems, particularly !ithlarge clusters. (he same technology is used as !ith the SAP 'essage Server forthe 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. #tmanages the loc+ table in the main memory and receives re*uests for setting orreleasing 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 inthe training material. (o be precise, the en*ueue server is the program or processthat 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*ueueservice processes these re*uests and manages the loc+ table !ith the e$istingloc+s.


70/194


71/194

bac+ground, independently of SAP instances. (his program collects dataabout operating system resources and ma+es this data available through theshared memory of all SAP instances.

'ote" #f you later discover that SAPOS:O has not been started,you can start it at any time by calling transaction S(-7 and choosingthe pathDetail 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, thedispatcher also starts the #nternet :ommunication 'anager /#:'0 and the

processes of AS ;ava /if it is installed0.


72/194

service interface contains a number of functions for administrating andmonitoring an SAP instance, in particular the SAP 'anagement :onsole/SAP ':0.sapstartsr% also has a limited "eb server function that allo!syou to do!nload all files underDIR/E9ECU'BALE=ser%icehttpby !ay ofD((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 5 is specified /fore$ample, http488hostname43RR0, the system automatically redirects you to

http488hostname43RR08servicehttp8sapmc8sapmc.html, for e$ample, to startthe SAP':.

sapstartsr% manages an internal list of protected operations. (hese can be changed,if necessary, !ith the start profile parameterser%ice=protected#ebmethods. "iththe start profile parameterser%ice=hostname you can also determine the #P address8 host name to !hich the "eb service port should be connected /default4 all 8-.-.-.-0, to limit accessibility in the net!or+.


73/194


74/194

. :hec+ the error filesstderrn 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%/#m /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 systemusing transaction S'1.

Sstem Shut,own:


75/194

5se the 5pdate Overvie! /S'0 to chec+ !hether update processes areterminated by the system stop. (hese update records are rolled bac+ duringthe stop, and are set to the status .init.. (hese records are then updatedagain 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 -0 by choosingControl ./// Stop SAP Instance.. #n the 'icrosoft 'anagement :onsole, right)clic+ to sho! the conte$t menuand choose the Stop function. %epending on !hether you have selected anindividual 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 ::'Sand then stops the SAP system. (he service itself does not stop.(he services themselves can be stopped and restarted !ith the correspondingoperating system tools, such as the "indo!s Service :ontrol 'anager.(he database is stopped using the relevant database system tools.


76/194

og on in 56#9 as a user !ith SAP administrator authorization /sidadm0.(o start the central instance, call the shell scriptstartsap__ in the home directory

of the sidadm user. #f there is only one instance for each application server, thealias startsap references the script startsap__.

(he script startsap first starts thesaposcolprocess !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 scriptstartdb 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.


77/194


78/194


79/194

#n principle, the starting of the system is performed in multiple steps, and is thetas+ of the operating system user @si!a!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*ueueserver. (he cluster elements e.g. ;ava)dispatcher and ;ava)server connect tothe ;ava message server during their o!n start process.. Starting the :entral #nstanceAfter 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 centralinstance.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 !ithpurely ;ava instances /!ithout ABAP0 and mi$ed instances /;ava and ABAPstac+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 dialoginstances are al!ays stopped first, and then the central instance.

=or SAP system installations on the 'icrosoft "indo!s operating system, thedatabase is not stopped at the same time. (his can be done !ith the tools of therelevant database. #n the case of SAP system that are installed on 56#9 operatingsystems, the database is generally stopped at the same time.


80/194

Starting an$ Stopping an SAP et!ea"er AS ABAP4


81/194

'anagement :onsole /SAP '':0 under "indo!s as !ell as the scriptsstartsap and stopsap under 56#9.

Tools or Starting an$ Stopping

Starting an$ Stopping an SAP et!ea"er AS ABAP4


82/194

Figure -): Starting an, Stopping instan'es of SAP *et+eaver AS AAP >5ava

#nstances of SAP 6et"eaver AS ABAP F ;ava can be started and stoppedindependently of the operating system using the SAP 'anagement :onsole /SAP':0.

As of SAP 6et"eaver release 1--2, a ne! operating system)independentapplication is supplied !ith the SAP 'anagement :onsole /SAP ':0 /see SAP

6ote -22M-0. (his allo!s you to display monitoring

Documents

Netweaver Trainig Manual(1)