google-site-verification: googlec13b2b482d5c880f.html google-site-verification=xvpB8nL6YB3BPAToMAY3GNAGNbLmIfrPxNd-W40DMfY

Thursday 23 January 2014

Learn SAP ABAP in 20 days part 7.

Performance Tunning:-
3 MAJOR AREAS:-
   1.SELECT STATEMENT
   2.INTERNAL TABLE USAGE
   3.DATABASE INDEX
   FOR SELECT STATEMENT:-
Ensure that data is selected with primary key /secondary index support with the fields in the select statement’s WHERE clause in the same order as fields in the index
Avoid negative WHERE clause (“NE”) because negative where clauses disable the index
Avoid long selects within AT SELECTION-SCREEN event
   for internal table usage:-
Check whether the internal table has records in it before executing the validation checks and related processing steps for that internal table. Example – before ‘for all entries in itab1’, ‘loop at itab1’
It is more efficient to use the AT statements ( AT NEW, AT END OF, AT LAST ...) for summing and control breaks purpose. Avoid using ON CHANGE OF
If using loop at WHERE statement never use internal tables events such as AT new inside the loop…Endloop
   for database index:-
   The purpose of an index is to quicken the scanning process when searching for specific records in a table.
An index is a copy of a table reduced to particular sorted fields to enable faster access to needed data.




Transport request:-
CREATING REQUEST:-
You can create a request in the following ways:
Creating a request by editing an object
When you create or modify objects in the ABAP workbench or customizing, a window appears asking you to assign the object to an existing change request (own requests) or to create a new change request (create request).
The request type is defined automatically.
Creating a request in the transport organizer
Use the function create request in the initial screens and the request overview of the transport organizer (SE09 or SE10).


File Handling:-
SOME COMMONLY USED FILE TYPE:-
   1.TAB DELIMITED
   2.COMMA SEPARATED
   3.FIXED LENGTH.
   UPLOAD AND DOWLOAD FILE:-
   Using the function module DOWNLOAD you can transfer the contents of an internal table to a local file.
Using the function module UPLOAD you can transfer the contents from a local sequential file into an internal table.
Enter the whole file path and name of the local file (e.G. '/tmp/myfile' for a Unix file and e.G. 'C:\ MYFILE.TXT' for a PC file).
The presentation server must know the directory.
Customers can choose an appropriate file name.
The system asks you for the file name and file type.
The data is then converted into the appropriate file type

 
    

No comments:

Post a Comment