An object requiring analysis can be a report, a transaction, or a series of reports or transactions, which form a business process or part of a business process.
The single-object analysis can be performed proactively in the quality assurance system for non-production objects or reactively in the production system for production objects.
The analysis of individual objects may be performed by the developer of the object or by the performance analyst. The person assuming the role of performance analyst must be familiar with ABAP and R/3 Basis.
The analysis of individual objects is performed proactively in quality assurance testing before the object is used in production and reactively typically after an R/3 system analysis (see Unit 5).
A prerequisite for performing the analysis of individual objects is that there are no fundamental problems with R/3 Basis. To ensure this, use the SAP services, GoingLive and EarlyWatch.
To analyze individual objects, representative business data must be available in the quality assurance system. In the production system, individual objects should be analyzed at times of representative user activity.
Contact the person responsible for the business process or the programmer if you have business-oriented or technical questions.
Analyzing Transaction Steps
During dialog processing, a transaction step corresponds to a change of screens. During an update or spool process, each request counts as a transactions step. Background processing can consist of one or more transaction steps such as the following:
1) Sending the user request to the application server
2) Placing the user request in the dispatcher queue if all R/3 work processes are occupied
3) Assigning the user request to an R/3 work process
4) Rolling the user context in to the R/3 work process
5) Attempting to satisfy the SQL statement from the R/3 buffers
6) Sending the SQL statement to the database server
7) Attempting to satisfy the SQL statement from the database buffer
8) Importing from the database the data blocks missing in the database buffer
9) Displacing data blocks from the database buffer
10) Sending the results of SQL statements to the application server
11) Changing buffered table content following database table changes
12) Sending the results of the user request to the presentation server
13) Rolling the user context out of the R/3 work process
RELATED POST
CLIENT SERVER TECHNOLOGY OVERVIEW
SAP ABAP BDC PART 6
SAP ABAP BDC PART 7
SAP ABAP BDC PART 8
SAP ABAP BDC PART 9
SAP ABAP BDC PART 10
No comments:
Post a Comment