There are four types of Buffering
1. FULL Buffering
2. Generic Buffering
3. Single Record Buffering
4. No Buffering

This is maintained for each table SE13 refer USR02 Table.
1. Full Buffering: The tables which are frequently used and rarely modified are eligible for buffering. (Also which are small in size)
Eg: T000 have all the clients and required to create a client copy. (This is fully buffered)

2. Generic Buffering: Tables which are relatively large, frequently used, rarely modified using a set of keys (Fields)
Eg: USR02; T001 Company info

3. Single Record Buffering: The tables which are large in size, frequently used and rarely modified are buffered using a primary key.

4. No Buffering: The tables which are large frequently used, and frequently modified are not eligible for buffering.. VBAK (SALES), EKKO (PURCHASE)

Related posts:

1. Purpose of Table Buffering Table buffering is used to increase performance when reading data from database table. Data from a buffered table is read from a local buffer on the application server thus reducing...
2. ABAP Programs: Filling an internal table from a database table REPORT ZSOURCE1203.* Work area for a database tableTABLES CUSTOMERS.* Defining an internal table with header lineDATA ALL_CUSTOMERS LIKE CUSTOMERS OCCURS 100 WITH HEADER LINE.* Filling the internal table (previous content...
3. Add Fields to SAP Table An Append Structure or a customizing include can be used to add fields to the Table. Append structures are created by adding fields to the end of a table while...
4. Creating a table in SAP ABAP Here are the steps required to create a table in SAP ABAP. Step 1: Go to transaction SE11 and input a table name. Step 2: In the Dictionary menu:Select the...

1. Front End Time/ GUI Time : Time taken by the user to reach the dispatcher is called as Front end time. The GUI time should not exceed more than 200 M.Sec. If it exceeds this consider the following.

1. User desktop is slow
2. If this is same with all the users, network might be congested.
3. The user request is expensive (FI and basis will logon to the central instance. Rest of all the users are allowed to login to Dialogue instance)
Note: GUI response time is not considered as a part of the Dialogue response time because the request is not received by the dispatcher.

2. Wait Time: The amount of time the user request sits in the queue. Generally it should not be more than 50 M.Sec or 10% of the response time. If the time exceeds, consider the following.

1. The work process are not sufficient to handle the user requests. (1:5)
2. There are sufficient processes but the existing process are held with expensive request.
Login/disable_multi_gui_login.

3. Roll in Time: The work process copies the Roll in User context into WP task handler. The time taken by the work process to copy the context (Roll In) is referred as Roll in time. Generally it should not be more than 50 M.Sec. If it is more than this consider the following.

1. The user context is heavy to Roll in (User might having more authorizations, parameters)
2. Minimize the authorizations.

4. Roll Out Time: The time taken by the work process to copy the information from its local memory to Roll Area/ Roll File/ User context/ Roll buffer and it should not be more than 50 M. Sec.

5. Roll Wait Time: During the processing when a dialogue process communicates with RFC’s and waiting for the response at this time the user context is copied/ rolled back to BTC —- RFC — Target system.
Roll wait time Sleep
Note: Roll wait time is not considered as a part of response time. If the roll wait time increases consider there is a bottle next on the RFC communication.

6. Processing Time: The time taken by the work process to process the user request using interpreters. The processing time should not be more than 200 M.Sec. If the processing time is more we can consider either ABAP program is expensive, screen is expensive or SQL statements are expensive.

7. CPU Time: When the request are processed using interpreters an amount of CPU is utilized to process the request using CPU resources is referred as CPU time.

As CPU time is included in processing time it is not calculated in the response time.
CPU time should not be more than (40% of the Dialogue response time – Wait time). If CPU time is more consider tuning ABAP Programs Refer to ABAP development team (Also Refer SE30 ABAP Run time Analysis, ST05 Performance Analysis)

8. LG Time: Load and Generation Time: Time required to load the objects such as source code, GUI info, screen info from the database and generate these objects.
(Refer LC10 : Live Cache). It should not be more than 200 M.Sec.
Run SGEN tcode after patch application, upgrade, new installation or when there is a mass change in the programs.

9. Enqueue Time: The time taken by the process to communicate with enqueue for obtaining the lock while updating a record is referred as Enqueue time. Enqueue time should be 5 M.Sec. on a Central instance and 100 M.Sec on a Dialogue instance. If it exceeds more than this time we can consider that the enqueues are not sufficient or Enqueue table overflow. or WP waiting for a lock.

10. RFC or CPIC Time: The time taken by the process to communicate with external interfaces is referred as RFC time. It should be as minimal as possible. (Communication between any BW/ CRM/ SCM system). There wont be any threshold value as it depends on External system.

11. Database Time: The time taken by the process to reach the database and process the request. Generally it should not be more than 40% of (Response time – Wait time). It is similar to the CPU time. IF DB Time is more consider the following.

1. The DB statistics job is not scheduled in DB13.
2. The DB resources are stake(CPU and Memory Utilization) i.e. Resource bottle neck on DB.
3. The DB Buffers are not sufficient.
4. Missing indexes in DB02.

12. Dialogue Response time: The time taken by the Dialogue process to process the request which includes [Wait time ........ To ......... Roll Out Time]

Related posts:

1. BW Performance Tuning How to Help Yourself Overview on most important performance issues Performance Tools in SAP Service Marketplace Please do … Measure the progress of your own performance tuning Measure before tuning...
2. ABAP Performance Tuning ABAP Performance Tuning(PDF) Tips and Tricks on SQL Interface String manipulation Internal Tables Internal tables vs Field group Typing If, Case, Field Conversion Modularization Subroutines Function Modules Tools Static Analysis...
3. Process Flow From SAP Basis Prespective During Logon and Transaction Process Flow (LOGON) 1. User requests 2. Dispatcher handles the request 3. Keeps in queue and assign WP based on FIFO 4. The work process gets the username, password, client,...
4. ABAP FAQs: SQL Performance SAP SQL Performance FAQs...
5. Central Performance History (CPH) CPH: Advantages at a Glance Advantages: Centrally collects monitoring data of the complete system landscape in a performant way Handles minute, quarter-hourly and hourly monitoring data; Deals with time zones...

To identify the systems easily by name
1. Goto > SALE > Basic Settings > Logical System
2. Define Logical System (<SID>CLNT009)
3. Assign logical system to the client.

There should be unique SID in the Landscape.

Defining RFC Connection – SM59
1. SM59 – Provide the name of the logical system
2. Select the connection type ’3′
3. Description about the connection
4. Technical settings (Host name and Instance No)
5. Logon Security (Client, UID, PWD, Logon Language)
6. Save the connection, Test Connection, Remote logon

Related posts:

1. Purpose of Defining Internal Orders An example would help us understand this much better. Lets say in an organization there are various events such as trade fairs, training seminars, which occur during the year. Now...
2. Defining the Fiscal Year Fiscal year variants can be used to define posting periods in relation to calendar months. The fiscal year is usually defined on the basis of 12 periods, which correspond to...

1. Asynchronous RFC
2. Synchronous RFC
3. Transactional RFC
4. Queue RFC

1. Asynchronous RFC – (Like a post card). The sending system may or may not receive it. i.e. there is no acknowledgement from the receiving . The transmission is not reliable.

2. Synchronous RFC – It is not like ARFC. It gets an acknowledgement from the target system. (like a register post).
If the receiving system is not available the process goes into RFC/ CPIC/ Sleep mode and waits until it is wakened by the target system. Target system/ Receiving system may be busy i.e. all the resources are used up. This is reliable but time consuming and expensive (Client Copy) the job should get finished.

Note: SAP uses CPIC protocol SAP specific (Common Programming Interface for Communication) to communicate between system.

3. Transactional RFC – TRFC – It is an advanced version of ARFC and SRFC. The request goes to receiving system if it is not handled a Transaction ID is generated by the source system. A program RSARFCSE is scheduled in the background to run for every 60 seconds. Transaction SM58 is used for Transactional RFC. It is used to document all the transactional ID’s and ensure that they are received by the recipient system. This is consistence and reliable.

4. Queued RFC – It is an advanced version of TRF and ensures that the transaction is committed based on FIFO/ Queue. It ensures transaction consistency of LUW and reliability of data transmission.
SMQ1 – to monitor the outbound queues of a sending system refer SCOTT for FAX…
SMQ2 – Provides interface to monitor Inbound queues.

Related posts:

1. Remote Function Call RFC is a communication interface that provides the ability to call a function remotely from another SAP System or Non SAP System. Each function module has a defined interface through...
2. What is an RFC? A Remote Function Call (RFC) is a call to a function module running in a system different from the calling-system. The remote function can also be called from within the...
3. Call an ABAP program from a BSP Call an ABAP program from a BSP is somehow impossible due to memory context handling for a web transaction like a BSP. If you try, it would lead to an...
4. Configure RFC in BI7 Here is a simple how to guide with screen shots on configuring RFC in BI7 for connecting to ECC6 Server. T-code SM59 Use SAP standard connection for RFC under ABAP:...
5. EDITOR-CALL : ABAP keyword a day EDITOR-CALL Call editor for internal tables - EDITOR-CALL FOR itab. Call editor for ABAP/4 programs - EDITOR-CALL FOR REPORT prog. EDITOR-CALL – call editor for internal tables Basic form EDITOR-CALL...

Gateway listens on port ’3300′+instance number (3300, 3301,3302 where 01, 02 are the instances).

Gateway provides an interface so that the external system can communicate with SAP system on the specified port.

When RFC’s are defined between the systems they use SAP gateway when (ALE, EDI, IDOC are transferring they use gateway)

Related posts:

1. Types of Work Processes Even though the Work processes are unique at OS level SAP differentiated between the work processes based on the nature of work. The process are determined by the instance name...
2. ABAP Programs: Using an alternative work area REPORT ZSOURCE1102.* Work area for a database tableTABLES CUSTOMERS.* alternative work areaDATA MY_CUSTOMER LIKE CUSTOMERS.* Reading all entries of the database tableSELECT * FROM CUSTOMERS INTO MY_CUSTOMER. WRITE: / MY_CUSTOMER-NAME.ENDSELECT....
3. Capital Work in Progress and Assets Capital WIP is referred to as Assets under Construction in SAP and are represented by a specific Asset class. Usually depreciation is not charged on Capital WIP. All costs incurred...
4. ABAP: How to create a dynamic internal table and work area FIELD-SYMBOLS:<fs_table> TYPE STANDARD TABLE, <fs_table_wa> TYPE ANY. DATA: table_ref TYPE REF TO data, wa_ref TYPE REF TO data. DATA: l_structure TYPE dd02l-tabname value 'VBAP'.   CREATE DATA table_ref TYPE STANDARD...

Enqueue is used to provide data consistency while updating the system. It provides locks from a lock table before a record gets updated and ensure that the record is available for display during an update.

There will be 1 One Enqueue process installed during installation. It is also possible to increase Enqueue processes to more than one depending upon the updates but most of the customer environments there will be only 1 One enqueue process.

Enqueue process the locks and unlock the record during an update. Enqueue server maintains the lock table on the shared memory of the Central Instance (or on the instance where it is installed).

It is recommended to increase the Enqueue processes only on the Central Instance. Technically the Message and the Enqueue should reside on the same instance (It is not mandatory). If both are installed on the same machine then it will be more comfortable for message server to communicate with Enqueue process to obtain locks for Dialogue process that are coming from other instances.

No related posts.

Update handles the record and change the status to “RUN”. If the update stays long time in status RUN then any one of these might be the problem you are facing.

1. Longer Update
2. Dead Lock (Needs to inform SAP for Program correction)

Updates which could not be updated will be thrown into ERR Status.
1. Update deactivated in SM14
2. Programming problems in LUW
3. Table Space overflow (ORA-1653; ORA-1654)
4. Max Extents reached (ORA-1631; ORA-1632)
5. Archive Struck (ORA-255; ORA-272)

Each SAP transaction is considered as Single LUW (Logical unit of work) which in turn contains multiple LUW’s needs to be committed to commit the SAP Transaction. If any one of the LUW is failed the entire transaction is rolled back. That is the reason why dialogue updates Temp Table.
1. User submits the request.
2. Dialogue handles the request.
3. Obtains lock from Enqueue so the data consistency is achieved and the records are only for display.
4. Updates the request in Temp tables (VBHDR, VBDATA, VBMOD, VBERROR)
5. Gets the transaction ID from NRIV (Number Range Interval Table)
6. Update gets initiated to update the VB* content permanently into the database.
7. Update inherits the locks.
8. Updates the database based on transaction ID.
9. Update releases the lock from the record.

Related posts:

1. Use of Solution Monitoring Solution Monitoring helps to manage Heterogeneous system landscapes efficiently. It consists of: Service Level Reporting – Used to optimize and simplify long term system monitoring. It is based on SAP...
2. Monitoring SAP R/3 with Perl This paper outlines a solution for monitoring SAP R/3 performance using Perl and Perl/Tk. This solution provides a primitive monitoring application which demonstrates how performance data extracted from SAP R/3...
3. Business Process Monitoring Set-up and User Guideline Business Process Management (BPM), as part of Solution Management, focuses on the operation (rather than on the implementation) of business processes from an application or functional perspective. This includes, basically,...

1. User and password Issues (Authentication/ Authorization) user lock, userid expiry, password change, lack of roles etc.
2. File system problems: BTC reads from the file system to update the database. File not opened, or corrupted, file sharing issues, file came with different characters, file not found as well.
3. Variants are not properly defined.
4. Dead locks issue (Lock mechanism congested)
5. Update mechanism failed
6. Table space over flow (ORA-1653; ORA-1654)
7. Table space max extent reached (ORA-1631; ORA-1632)
8. Archive struck (ORA-255; ORA-272)
9. The memory is not sufficient and errors
(No Roll Area, PXA (Buffer), Page Errors)
10. Problem in the program and inputs (Indefinite loops like 1/0)
11. Dependent jobs/ events failure
12. Target systems are not available to process the jobs.

Related posts:

1. Common SAP FI Terms Business Area An organizational unit that requires audited financial statements for external use. Often this corresponds to a separate operational or responsibility area in the organization at the highest level....
2. Common SAP Definitions Some Common Sap Definitions Client: is the highest level in the organization, it is enterprise which groups several companies. Company Code: a company is a form of business organization, a...
3. Common Controls in SAP Let’s look at a few of the common buttons and controls in the SAP system: On any screen in SAP, the green check mark means enter. If you prefer, you...
4. Common SAP Functional Terms AAA Materials Management Automatic Account Assignment (configured with transaction omwb) Account determination System function that determines automatically the accounts in financial accounting to which the amount(s) in question should be...
5. SAP Common Material Management Terms ABC Classification Web Item to classify objects (Customers, Products or Employees) based on a particular measure (Revenue or Profit) using certain classification rules. Three categories: Important, Less Important, and Relatively...

• Goto – Market place www.service.sap.com/licensekey
• Click on obtain permanent license key
• Select the Installation number based on the component (ERP, NETWEAVER(EP, BI, XI, PI, MI, JDI), SCM, SRM, CRM & Solution Manager).
• Specify the system ID(SID), OS, DB, System Type, purpose(DEV, PRD, QAS, TEST etc)
• Click on continue to display the hardware key input.
• The license key is specific to Customer, Installation number, System Number, Hostname and the Hardware key.
• Hardware key is unique (use command saplicense -key )
• Specify the Hardware key and email-id to generate and send license key to the mail-id specified, Alternatively select the system and click o

Execute [Slicense] Tcode
Click on > New Licenses
Click on > Install license key and it prompts for the path of the license key, provide the downloaded file path and click on OK to apply the license.

No related posts.

1. D – Dialogue
2. V – Update
3. E – Enqueue
4. B – Back ground
5. M – Message
6. G – Gateway
7. S – Spool

1. DIALOGUE ‘D’
It is only the process which communicates interactively with the users. There should be atleast 2 Dialogue work process per instance. Dialogue work process initiates Update, Background and Spool.

2. UPDATE ‘V’
It is used to update the transactions in the database. It is initiated by Dialogue process. There should be atleast 1 Update in the entire system. It is also recommended to have an update process for every 5 Dialogue.

3. ENQUEUE ‘E’
It is used to provide locks for the records that are going to be updated. It ensures consistency for updates. There will be only 1 Enqueue configured in the system during the installation. It is possible to have more than one enqueue provided they are installed or configured on the central instance.

4. BACKGROUND ‘B’
The tasks which are expensive or time consuming are scheduled to run in the background mode non-interactively. There should be atleast 2 background work process in the system

5. MESSAGE ‘M’
There should be only 1 message server in the entire R/3 system. It is used to manage all the dispatchers. It is used to load balance the requests to identify the least loaded dispatcher.
It is also used to provide locks to the request that are coming from Dialogue instances.

6. GATEWAY ‘G’
It is used to provide a means of communication with SAP and NON-SAP systems. There will be only 1 gateway for each instance.

7. SPOOL ‘S’
It is used to print the documents to a printer or output to a fax machine etc. There should be atleast 1 Spool process in the entire system. It is also possible to configure more spool process depending on the print/ spool volume.

Related posts:

1. What is HCM Processes & Forms Framework? The next step in the evolution of Personnel Change Requests (PCRs). Offers an efficient way to manage cross-role processes involving HR Master data. It provides greater flexibility and features such...
2. ABAP Programs: Using an alternative work area REPORT ZSOURCE1102.* Work area for a database tableTABLES CUSTOMERS.* alternative work areaDATA MY_CUSTOMER LIKE CUSTOMERS.* Reading all entries of the database tableSELECT * FROM CUSTOMERS INTO MY_CUSTOMER. WRITE: / MY_CUSTOMER-NAME.ENDSELECT....
3. Capital Work in Progress and Assets Capital WIP is referred to as Assets under Construction in SAP and are represented by a specific Asset class. Usually depreciation is not charged on Capital WIP. All costs incurred...
4. ABAP: How to create a dynamic internal table and work area FIELD-SYMBOLS:<fs_table> TYPE STANDARD TABLE, <fs_table_wa> TYPE ANY. DATA: table_ref TYPE REF TO data, wa_ref TYPE REF TO data. DATA: l_structure TYPE dd02l-tabname value 'VBAP'.   CREATE DATA table_ref TYPE STANDARD...