" The functions Hold data and Set data is used when you want to create a group of objects that contain the same data. The function Hold data can be used to create data that can be changed, for example if you wish to create multiple objects with slight variation in the field values (Sales order or Purchase order) then the function Hold data can be used. If you wish to create multiple objects with exactly the same data without changing any of the filed values then SET data can be used. To hold data on the screen you need to first enter the data in the field and then choose User Profile from the Systems Menu. Now choose Hold data. The data that you hold on the screen can be changed. In case if you wish to hold data on the screen without changing it then select SET data. This way the data will be held but you will not be able to change the contents of the individual fields. You can delete the Data that is held. To do this select User profile from the Systems menu and select the option Delete data. Once the delete Data option is selected no data will be displayed the next time you visit the screen. You may want to work in more than one screen, and would like to store data in each screen, to do this you can press Ctrl+S or click on the save icon while moving between screens. You can also Cancel the data that you have just entered on the screen. To do this press the cancel button. Please note that when using HOLD data and SET data options, the required/Mandatory fields on the screen cannot be ignored. The correct values should be entered in these fields before proceeding to the next screen. Using the menus and functions you can go to the other screens within your task, as well as in related tasks. Check the Goto Extras and Environment menus in the Menu bar to find out the other screens available within your task and related tasks. Depending upon the task the contents also change. "
"The flow of a program is determined by a sequence of screens in a dialog transaction. The screens that are called within a transaction, must belong to a single ABAP program, usually a module pool (Type M). You have to use the transaction maintenance transaction (SE93) to create a dialog transaction. Once you have entered a transaction code and a short description, chose transaction type program and screen. Then enter data on the next screen as required. The transaction code in a dialog program must be linked to the number of its initial screen. Finally enter this number in the screen number field."
Thursday, August 14, 2008
SAP ABAP Important Keywords : The following list displays some of the important Keywords in ABAP
No
Keyword
Description
1
AT END OF … ENDAT
Control group end in LOOP
2
AT Fg … ENDAT
Processing specific to record type in LOOP
3
AT FIRST … ENDAT
Execute processing block within a LOOP before processing single lines
4
AT LAST … ENDAT
Execute processing block within a Loop after processing single lines
5
AT NEW … ENDAT
Control group end during LOOP
6
CALL
Call processing (Program, function module, screen)
7
CHECK
Selection condition, leave loops and subroutines
8
CONTINUE
Exit current loop pass within a DO, WHILE, LOOP or SELECT loop
9
DO … ENDDO
Loop processing
10
EXEC SQL … ENDEXEC
Execute a Native SQL Statement
11
EXIT
Leave loops or subroutines
12
FORM … ENDFORM
Definition of a subroutine
13
IF … ELSE … ENDIF
Conditional processing
14
LEAVE
Leave program processing, go to a transaction, list (or) menu
15
LOOP … ENDLOOP
Loop on a table (or) extract dataset
16
MODULE … ENDMODULE
Definition of a dialog module
17
ON CHANGE OF … ENDON
Processing on field change
18
PERFORM … USING
Call a subroutine
19
SELECT … ENDSELECT
Read database tables
20
STOP
End selection
21
WHILE … ENDWHILE
Loop processing
Wednesday, August 13, 2008
SAP ABAP Function Module to Wrap Long Text
The following function module can be used to wrap long text in ABAP.
SAP ABAP Function Module to Wrap Text
RKD_WORD_WRAP
Find the code below to test the above Function Module.
Always specify your conditions in the Where-clause instead of checking
them yourself with check statements. The database system can then use an index
(if possible) and the network load is considerably less.
Always use Pretty Printer and Extended Program Check before releasing the code.
Do not leave unused code in the program. Comment the code thoroughly. Align the comments and the Code. Follow the SAP Standards and SAP Best Practices guidelines. It’s a good practice to take a dump of the code on your local drive.
