Big4Guy

In SAP, data is stored in backend database tables. Such data may include master data, transactional data, configuration data and so on. In order to ensure that ABAP programs get the right access to the database table, the runtime object for the table should be in sync with the structure of the table in the database. Changes to Database tables can be made in the ABAP dictionary. One key point which the ABAPPER must check is that each time a table is changes in the ABAP dictionary, there is also an adjustment which is made to the database structure of the table.

In SAP, once changes are made to tables, the ABAP dictionary will have an active and an inactive version of the table. These active and inactive version are nothing but the old and new versions of the table. The database table has to be adjusted so that it is in line with the changed definition in the ABAP dictionary in three different ways:

1) The most cumbersome way of adjusting a structure is by converting the table itself.

2) Alter table i.e. by changing the database catalog. In this case, simply the definition of the table in the database is changed. All the existing data in the table is maintained and indexes of the table require to be built.

3) The easiest way of changing the definition of the ABAP dictionary is by deleting the database table and creating it from scratch. The table on the database is deleted. After this is done, the inactive table is activated in the ABAP dictionary and the table is created again in the database. However, the downside of all this is that the existing data in the table is wiped away and is not recoverable.

Read More Such Posts

SAP Solution Configuration Realisation Phase
SAP Go-Live Date Top Tips
How to Close Periods in SAP ECC
SAP R/3 Implementation Milestones

The ABAP runtime analysis can be used to analyze the total run time required for individual SAP transaction codes, sap programs or even SAP function modules. Individual ABAP objects can put a heavy load on the system resources such as CPU and memory, ABAP runtime analysis is especially useful in such case to perform analysis and find the root cause of the problem.

ABAP runtime analysis can be performed using transaction code SE30 or via the menu path: SAP Menu >> Tools >> ABAP Workbench >> Test >> RunTime Analysis SE30. Runtime analysis is performed in three steps which are:

1. Deciding on the data to be measured - As a first step in runtime analysis, the ABAPPER needs to decide which object needs to be analysed. Other important criteria at this stage includes which aggregation should be used whether to use full aggregation, aggregation based in calling position, or no aggregation. Similarly, filters can be used based on modularization and commands. Deciding the data to be ameasured upfront is key to successful runtime analysis.

2. Measuring the Data - The next important step is the measurement of the runtime data. This can be performed in the same user session in which the ABAP runtime analysis is getting completed or can be performed in a new user session using tcode /OSE30. Analysis can also be performed to measure the runtime data for an object that is processed by that work process.

3. Analyzing the Data - In case of data aggregation, the runtime analysis can be seen in the hitlist and in case of aggregation on calling position, this can be seen via call hierarchy or modularization units. Once the runtime analysis is complete, this can be saved on the application server or it can also be sent to the front end. For further analysis, SAP R/3 provides the option to the abapper to saved the data to a specified path and also allocate the memory that the system will use for saving the file.

Related Posts

SAP Function Groups - Finance ABAP
ABAP Authority Check in SAP ECC
ABAP Programming Basic Concepts
SAP WebDynpro ABAP User Interface