Professional Documents
Culture Documents
Presentation Server
The presentation server is actually a program named sapgui.exe. It is usually installed on a user's workstation. To start it, the user double-clicks on an icon on the desktop or chooses a menu path. When started, the presentation server displays the R/3 menus within a window. This window is commonly known as the SAPGUI, or the user interface (or simply, the interface). The interface accepts input from the user in the form of keystrokes, mouse-clicks, and function keys, and sends these requests to the application server to be processed. The application server sends the results back to the SAPGUI which then formats the output for display to the user.
Application Server
An application server is a set of executables that collectively interpret the ABAP/4 programs and manage the input and output for them. When an application server is started, these executables all start at the same time. When an application server is stopped, they all shut down together. The number of processes that start up when you bring up the application server is defined in a single configuration file called the application server profile. Each application server has a profile that specifies its characteristics when it starts up and while it is running. For example, an application sever profile specifies: Number of processes and their types Amount of memory each process
NOTE
When speaking to a Basis consultant, you might hear the term roll area used to refer to all roll areas for one user or even all roll areas on one application server. You usually can determine the intended meaning from the context in which it is used.
NOTE
A dialog step is used by Basis consultants as the unit of measure for system response time.
SAP Technical Tutorials ABAP DICTIONARY INTERNAL TABLES ALV Reports SAPSCRIPTS SMARTFORMS LSMW BDC ALE IDOC USER EXITS TRANHYPERLINK "../../../TUTORIALS/TECHNICAL/Transporting_tutorial.html"SPORTING ITS
SAP Functional Tutorials FI (HYPERLINK "../../../TUTORIALS/FUNCTIONAL/FI_tutorial.html"Financial) CO (HYPERLINK "../../../TUTORIALS/FUNCTIONAL/CO_tutorial.html"Controlling) HR (HYPERLINK "../../../TUTORIALS/FUNCTIONAL/HR_tutorial.html"Human Resource) LO (HYPERLINK "../../../TUTORIALS/FUNCTIONAL/LO_tutorial.html"Logistics) MM (HYPERLINK "../../../TUTORIALS/FUNCTIONAL/MM_tutorial.html"Materials Management) PP (HYPERLINK "../../../TUTORIALS/FUNCTIONAL/PP_tutorial.html"Production Planning) QM (HYPERLINK "../../../TUTORIALS/FUNCTIONAL/QM_tutorial.html"Quality Management) SD (HYPERLINK "../../../TUTORIALS/FUNCTIONAL/SD_tutorial.html"Sales and Distribution) TR (HYPERLINK "../../../TUTORIALS/FUNCTIONAL/TR_tutorial.html"Treasury and cash) WM (HYPERLINK "../../../TUTORIALS/FUNCTIONAL/WM_tutorial.html"Warehouse Management) PS (HYPERLINK "../../../TUTORIALS/FUNCTIONAL/PS_tutorial.html"project Systems) PM (HYPERLINK "../../../TUTORIALS/FUNCTIONAL/PM_tutorial.html"plant Maintenance) CA (HYPERLINK "../../../TUTORIALS/FUNCTIONAL/CA_tutorial.html"Cross Application)
SAP
Interview questions
Architecture faqs BDC faqs DATADICTIONARY faqs Logical Database Faqs Modularization Faqs Reports Faqs Transactions Faqs
SAP References
transaction codes System Fields Function Modules SAP TABLES code optimization
TOOLS SQL Trace tool Runtime Analysis LSMW ABAP Query CTS
SAP Certification SAP Download SAP Books SAP APO SAP BW SAP BI SAP CRM SAP EP SAP XI SAP MANUFACTURING SAP MDM SAP KW SAP PLM SAP IDES SAP NETWEAVER SAP PORTAL SAP Retail A dialog step is the processing needed to get from one screen to the next. It includes all processing that occurs after the user issues a request, up to and including the processing needed to display the next screen. For example, when the user clicks the Enter key on the Change Vendor: Initial Screen, he initiates a dialog step and the hourglass appears, preventing further input. The sapmf02k program retrieves the vendor information and displays it on the Change Vendor: Address screen, and the hourglass disappears. This marks the end of the dialog step and the user is now able to make another request. There are four ways the user can initiate a dialog step. From the SAPGUI: Press Enter. Press a function key.
It is important for an ABAP/4 programmer to know about dialog steps because they form a discrete unit of processing for an ABAP/4 program.
All requests pass through the task handler, which then funnels the request to the appropriate part of the work process. The interpreters interpret the ABAP/4 code. Notice that there are two interpreters: the ABAP/4 interpreter and the screen interpreter. There are actually two dialects of ABAP/4. One is the full-blown ABAP/4 data processing language and the other is a very specialized screen processing language. Each is processed by its own interpreter. The database interface handles the job of communicating with the database.
E (Enqueue) M (Message)
Logical lock requests Routes messages between application servers within an R/3 system Funnels messages into and out of the R/3 system
G (Gateway)
Jane sets up data for her test run, executes her report and obtains output. Jim works in the next cubicle, but due to his antisocial tendencies is blissfully unaware that his transaction uses the same tables as Jane's report. He runs his transaction and updates the data. Jim got what he wanted, but Jane then modifies her code and runs her program again. Her output differs from the last run, and the differences many not result from her changes, but rather they may result from Jim's changes. What we have here is a failure to communicate. If the tables used by Jim and Jane's programs were client-dependent, they could each log in to separate clients, set up independent sets of data, and test their programs without ever talking to each other. They could perform all of their testing in the comfort of their cubicles and in isolation from their coworkers. To make their tables client-dependant, they only need mandt as the first field and the R/3 system will take care of the rest. When records are added to the table, the system automatically moves the current logon client into the mandt field when the record is send to the database. Their Open SQL select statements will only return rows where the client number in the table is equal to the their current logon client number. The Open SQL database statements insert, update, modify, and delete also provide automatic client handling. If the tables involved are all client-dependent, there can be more than one group of testers working at a time in one test system. Two teams of testers can test divergent functionality in the same set of programs at the same time provided they log on to different logon clients. The updates done by one team will not change the data belonging to the other team. A training client could also exist on the test system. The students could log on to one client and the testers could log on to another. Both would run the same set of programs, but the programs would access independent sets of data. NOTE The average R/3 installation has three systems: development, test, and production. By default, each system comes with three clients installed: 000, 001, and 066. It is common to have from three to six clients in the development and test systems, but rarely will you see more than one client in production.