KalviTN

Transaction, In R/3 system is an operation that lets the user to make necessary changes to the database in a consistent way. The entries R/3 system is nothing but set of business transactions. The data transfer from old system to SAP R/3 database or modifying data or deleting data is done through transaction only. For SAP system, Transaction is nothing but sequence of steps called as dialog steps and for user it is sequence of screens which appears one after the other to accept the data which is to be created in the database. The transaction contains two steps which are as following: 1. Interactive phase in this step user enters the data on to the screen, which needs to be inserted, deleted and modified. These can be single screen or multiple screens depending upon the transaction. So this step can consist of single step or multiple steps. In this phase you prepare database record. 2. Update phase This phase processes the database record and updates the database tables....

Events triggered in SAP ABAP: 1.   Initialization . 2.   At Selection screen. 3.   Start of selection. 4.   Get. 5.   Get Late. 6.   End of selection. 7.   Top of page. 8.   Top of page during line selection. 9.   End of page. 10. At line selection. 11. At user command. 12. At PF.

Report is displaying the application data in the required format. Technically speaking, a report is an executable program with three stage function. 1. DATA INPUT (Selection Screen). 2. DATA PROCESSING (Select Statement). 3. DATA OUTPUT (Write, Skip, Uline, Vline). Purpose:   It helps to analyze the current situation and also for decision making. Real time report scenarios :  To stop the purchases from the specific vendors, the purchasing department need a report for vendor evaluation and terminate the employees from the organization the HR department need one report with employee performance.   

Three types of internal tables are in SAP ABAP. Standard Internal Tables: These tables have a linear index and can be accessed using the index or the key. The response time is in linear relationship with number of table entries. These tables are useful when user wants to address individual table entries using the index. Sorted Internal Tables:   These tables also have an index and the key. But the response time is in logarithmic relationship with number of table entries, since it users binary search algorithm instead of linear search. These tables are useful when user wants the table to be sorted while additional entries have to be added. Hashed Internal Tables:   These tables have no index, but have the key. The response time is constant irrespective of number of table entries, since it uses a Hash algorithm. These tables are useful when user wants to access the entries with key only.