1-Basis Technical Overview

Overview

SAP Basis Functions

SAP Technical Overview

Learning ObjectivesWhat the Basis system isHow does SAP handle a transaction requestDifferentiating between the various work processesUnderstanding the basic functions of the Basis Module


The Software-Oriented View of R/3


The SAP R/3 System ArchitectureImplications for Application ProgrammingSeparate presentation and application layers implies that when you run an application program that requires user interaction, control of the program is continually passed backwards and forwards between layers.When a screen is ready for user input, the presentation layer is active, and the application server is inactive with regard to that particular program.As a consequence, the program logic in an application program that occurs between two screens is known as a DIALOG STEP.


Application Layer (cont.)Application ServerR/3 programs run on application serversThe APPLICATION SERVER communicate with the presentation components, the database, and also with each other, using a MESSAGE SERVER.Main components:Work Processes (Dialog, Update, Enqueue, Batch, Spool)DispatcherGatewayMessage Server

The SAP R/3 System Architecture


What happens when I send a request to SAP?


Application ServerPresentation . . . InternetApplicationDatabaseCommunicationSAPGUISAPGUIInternetOfficeWork-processDispatcherTCP/IPRemote SQLIPCLocal Bufferfor R/3 Data,DW-Objects,ABAP-Objects


DispatcherProgram which manages resources of the R/3 applicationsReceives requests from user and passes them to the corresponding work processesOnly one dispatcher per application server


Dispatcher TasksBalances the workload between the processesBuffer management in main memoryConnection with the presentation levelOrganization of the communication processes


Work ProcessResponsible for executing R/3 application tasksDatabase InterfaceTask HandlerABAP/4ProcessorDialogInterpreterWork Process


Different Kind of Work Processes for different TasksDialogSAP DispatcherBatchSpoolUpdateEnqueueSBMGMessageGatewayR/2R/3VE


Dialog Work ProcessesDialogResponsible for the interactive tasks of the R/3 systemDialog work processes execute only one dialog step at a time and are immediately freed for the next user requestConstantly switching between users


Background Work ProcessesResponsible for executing ABAP programs submitted for background executionBatch jobs schedule the sequence of program executionUsed for running long and time consuming programsBatchB


Spool Work ProcessesResponsible for formatting the data for printing and passing it to the host spool systemOnly one spool work process allowed per serverSpool


Enqueue Work ProcessesResponsible for the lock management systemSynchronizes database access for the multiple application servers and work processesOnly one enqueue process per R/3 system to ensure data integrityEnqueueE


Update Work ProcessesResponsible for making database changes requested by dialog and background processesFor better performance, this process should be on the database serverUpdateV


V1 vs. V2 Update ProcessesTime-critical processes are inside V1 and less critical ones within V2Error situations inV1 : changes rolled back and V2 components not executedV2 : only changes of V2 components rolled backUpdateV


Message ServerUsed by different application servers to exchange data and internal messagesRoutes messages, such as update or batch job starts, between application serversOne message server per systemMMessage


Gateway ServerAllows communication between R/3, R/2, and external applicationsExchanges large amounts of information between application serversGateway can reside on any of the connected systemsGGatewayR/2R/3


Work ProcessesNumber of work processes can only be changed after restarting the systemShould have at least two dialog work processesNeed to have at least one V1 and V2 processesNumber of spool processes cannot be changed


Application ServerPresentation . . . InternetApplicationDatabaseCommunicationSAPGUISAPGUIInternetOfficeWork-processDispatcherTCP/IPRemote SQLIPCLocal Bufferfor R/3 Data,DW-Objects,ABAP-Objects


Processing of a SAP Transaction (1)TCP/IPPresentation . . . InternetApplicationDatabaseCommunicationSAPGUIWork-processDispatcherRemote SQLIPCLocal Bufferfor R/3 Data,DW-Objects,ABAP-ObjectsStartTransactionAssign User request to WorkprocessFetch data from buffer/databaseRe-turndatafor nextstep12345


Processing of a SAP Transaction (2)Presentation . . . InternetApplicationDatabaseCommunicationSAPGUIWork-processDispatcherTCP/IPRemote SQLIPCLocal Bufferfor R/3 Data,DW-Objects,ABAP-Objects123568Fetch data frombuffer/database9710Assign Userrequest toWorkprocessRe-turndatafor nextstep


Processing of a SAP Transaction (3)Presentation . . . InternetApplicationDatabaseCommunicationSAPGUIWork-processDispatcherTCP/IPRemote SQLIPCLocal Bufferfor R/3 Data,DW-Objects,ABAP-Objects1234568971011121314Update data on databaseEnd transactionRequest for update


SAP Communication InterfacesHighLevelLowlevelSAP TechnologyCommunication InterfaceCommunication SystemMailMAPI SMTPX.400EDI Business APIRFCCPI-CQ-APIIDOCALEOLE


Business FrameworkBusinessComponentBAPIALEBAPIBusinessComponentBusiness Component - contains business functionalityBAPI - interface between the componentsALE - integration of components


Business API (BAPI)Defined method of a business objectStandardized methods allow customers to integrate their software with R/3Object-oriented in natureBAPIs from all development platforms that support the SAP Remote Function Call (RFC) protocol


Other InterfacesApplication Link Enabled (ALE) - Interface that links different SAP systems and external application systemsTransport special data structures known as IDOCS (Intermediate Documents)Object Linking and Enabled (OLE) - enables desktop users to access SAP data from many OLE client programs


Basic Functions of Basis


Basis FunctionsHardware and Database AdministrationUser and Security AdministrationClient MaintenanceCorrection and Transport System (CTS)Data DictionaryOnline Service System (OSS)Performance Monitoring and Tuning


Hardware and Database AdministrationHardware upgrades - adding memory or serversDatabase backup and recoveryDatabase optimizationDisaster Recovery


User AdministrationCreate users and assign profiles Modify, lock and unlock usersDevelop authorizations and profiles


Client MaintenanceCreate clientsCopy and refresh clientsClient imports and exportsDelete and remove clientsModify change options


Correction and Transport SystemR/3 SystemR/3 SystemR/3 SystemDevelopmentProductionQuality AssuranceChangeRequestMoving changes from one R/3 system to another


Online Service System (OSS)OSS is a set of SAPs online services such as bug fixes and useful implementation informationOSS NotesHotpacksRemote ConnectionsSend questions to SAPABAP registration


Performance Monitoring and TuningCheck database usage and storage capabilitiesDialog response timeInvestigate ABAP short dumpsOptimize performance characteristics


Computer Center Management System (CCMS)

Manages the entire system - database, application, operating systemCollection of tools and utilities which allow you to monitor and manage the R/3 systemAllows monitoring of multiple R/3 systems Comes FREE with each SAP system


Computer Center Management System (CCMS) functions

Starting and stopping instancesMonitoring and analyzing workloadAlert capabilitiesOperation modes and work process automatic reconfigurationInstance profile checking and maintenanceLogon load balancing


This slide depicts how an application server works. Users make requests at the presentation layer and through TCP/IP these requests get sent to the application server. The dispatcher then takes the requests and assign them to work processes which handle the requests. More detailed explanations are on the following slides.The dispatcher is a program which manages the resources of the R/3 applications. They are very similar to a police dispatcher who receives requests via 911 and routes it to available officers who are in the area.

The dispatcher receives requests from the many users on the system and passes them along to the corresponding work processes which are free. It also manages the information flow between the app server and the SAPGUI.

Each app server has only one dispatcher because it could get kind of difficult for two dispatchers to route requests to the work processes. The dispatcher is responsible for balancing the workload between the work processes so that processes dont sit idle.Memory management is also one of its duties. The dispatcher must also organize the communication between the work processes and also between the SAPGUI and app server.Work processes are the actual programs which execute tasks. They update the database, run batch programs, and send messages. Work processes are comprised of a task handler, an ABAP/4 processor, dialog interpreter and database interface.They execute dialog steps for a user and typically only do the work of displaying one screen at a time. In other words, work processes present one screen of data, and are immediately freed to handle other tasks. The next screen is then handled by the next available work process.

The task handler coordinates the activities of the work process. The database interface allows for the work process to directly access the database. The dialog interpreter is used to coordinate presentation information and the ABAP/4 processor is useful when running programs.There are seven different types of work processes which will be described in detail in the following slides. The five work processes in the middle around the dispatcher are the main work processes in use in the application servers. The two work processes on the outside are used for communication methods within the systems.The dialog work process is typically the most common work process. It handles all the interactive requests of the R/3 system. Any time a user sends a request the dialog work process plays a part in the work. Dialog work processes handle just one dialog step and are immediately freed to handle other requests. So these work processes are constantly switching between users. This limits the number of dialog work processes, as you would need the same number of work processes as users otherwise.Background work processes execute long running and CPU intensive programs which are required to be run. Some examples include client copies and long listing reports.

Background jobs can also be set to run at specific times.In charge of formatting data for printing and sending it to the host spool system. Only one spool work process per host.In order to ensure the integrity of the database, the enqueue work process is responsible for the lock management system. There is only one enqueue work process per system as it synchronizes the data access for multiple application servers and work processes. When a work process is accessing data for possible manipulation it is locked so that other work processes cannot access the data until it is released. Update work processes actually manipulate the database, so they would be better served to be on the actual database server. They make all the changes to the database within the R/3 system.SAP makes distinctions between the V1 and V2 component. V1 contains the time critical processes that require immediate updating whereas V2 processes are less critical. During updates there can be a combination of V1 and V2 updates. When errors occur during the V1 update, all changes are rolled back and any subsequent V2 components are not executed. Errors occurring the the V2 phase requires that only changes in the V2 component be rolled back.This single message server per system sends messages between the various application servers. Messages include update or batch job starts. The communication is setup through the dispatchers and is used for small internal messages.Gateways connect the R/3 system to other systems such as R/2 or other external systems. They facilitate the transfer of large amounts of data through the use of TCP/IP.In order to change the number of work processes, you must change the system profile and restart the system.A system should have at least two dialog work processes at all times to ensure correct usage. In case something is wrong, an administrator would need to be able to interactively log on to the system.You need to have at least one V1 and V2 work processes in order to make updates.Back to our picture.The following outlines the course of events for an application:1) The user sends a request to the app server.2) The dispatcher receives the request and assigns it to a work process. 3) The work process looks in its buffer for the requested data.4) It finds the data and once it finishes handling the request it sends the result back to the dispatcher.5) The dispatcher formats the results and sends it back to the SAPGUI.6) The user makes another request of the system.7) The dispatcher receives the request and assigns it to a work process8) The work process retrieves data from the buffer or the database9) The work process handles the request by interacting with the database and sends it back to the dispatcher10) The dispatcher sends the data back to the user11) Say the user requests an update. A request is sent to the dispatcher.12) The dispatcher sends the request to the work process.13) The work process makes the change to the database14) The transaction ends.This slide shows the various communication interfaces in the R/3 system. The ones closer to the top are the ones which implementers are most likely to work directly with. The ones at the bottom are more of internal SAP communication interfaces.The Business Framework - the open, component-based architecture, which allows software components from SAP and third parties to interact and integrate with each other, is gaining more and more momentum.

Business Components cover a broad range of business data and processes. Examples include customer order management, purchase requisitions, and invoices.

Business API (BAPI) are methods which allow interfacing between the various business componenets.

ALE - provides an interface between the various componentsBAPIs are merely methods within Business components. They allow outside applications to access those Business componenets. They are standardized methods which allow integration. Its also object oriented in nature.Here are some of the most important functions of Basis personnel.Some of the responsibilities of Basis personnel include the maintenance and upkeep of the hardware and database as other typical system administrators do. Typically, sizing, upgrading, backup and recovering are some of the issues that are dealt with.One of the big tasks of Basis personnel is User Administration. Users must be made and assigned the correct profiles so that they can do their job and not have any extra access to other transactions that they should not be able to view.Client maintenance involves the creating of clients and running client copies and refreshes.

Client exports and imports occurs when you wish to take a client from one system and move it to another. Exports make a file at the operating system level, which can then be imported into the target system.

When clients are obsolete, they must be deleted in order to be more efficient with memory.CTS is the notion of moving changes from one system to another. In the typical Development-Testing-Production environment, CTS is the mechanism of moving changes and modifications through the systems.OSS is SAPs online service system, which contains known problem, bug fixes, and news. Its a great source of information to find answers to your problems, and even affords you the opportunity to send SAP questions that have stumped you. OSS also plays a role in ABAP development, as all ABAP programmers must be registered through OSS.

1-Basis Technical Overview

Documents

Transcript of 1-Basis Technical Overview