1. shifting strings by a given number of places
2. shifting up to a given string
3. shifting a string depending on the first or last sign
4. replacing values
5. translating signs
6. overlaying strings
7. searching strings
8. length of a string
9. condensing strings
10. concatenating strings
11. splitting strings
12. moving parts of strings

DIV, Mod, MULTIPLY-CORRESPONDING, Add, COS, ABS, SIGN, CEIL, FLOOR, TRUNC, FRAC

Full type specification 

REPORT demo_field_symbols_type .

DATA: BEGIN OF line,
         col1(1) TYPE c,
         col2(1) TYPE c VALUE 'X',
       END OF line.

FIELD-SYMBOLS <fs> LIKE line.

ASSIGN line TO <fs>.

MOVE <fs>-col2 TO <fs>-col1.

WRITE: <fs>-col1, <fs>-col2.

The following is a list of fields in VBFA with the check table for VBTYP_N and VBTYP_V for easy reference.

PS: There is a good function module that pulls all the document flow (doc flow / order flow) for you called RV_ORDER_FLOW_INFORMATION

AL08 - Shows current logged on users
AL11 - Browse SAP directories at OS level
AMEN - ABAP Tools menu

• Quicklinks to sysntax trace,
• code analysis,
• coverage analyzer,
• extended check,
• runtime analysis,
• tips and tricks,
• exception text checks,
• BSP page display,
• syntax diagram display

General flow of a BDC program is like this....

1) First create recording for the T code which you want to make BDC for... Use T code SHDB for recording.

2 ) Now save that recording and create pogram from that recording using Create Program button. give the BDC driver program name and create.

3 ) Now the general logic of BDC program goes like this....

 - Upload Flat file into and internal table using function module "UPLOAD"
 - OPEN BDC GROUP.
 - Now loop at that internal table which contains the data from flat file.
 - move data from internal table to fields of BDCDATA using automatically gebnerated code from BDC.
 - CALL TRANSACTION <T CODE> using BDCDATA...
 - CLOSE BDC GROUP

A sample program for the same is attatched here for your referance... just go through it..

1. dialog
2. system
3. communication
4. service
5. reference

1. Check whether your user has debugging authority. Auth. object S_DEVELOP has to contain 'DEBUG'
   1. Use su01; ROLES
   2. Double click the different roles ->
   3. new session will open
   4. Choose Authorizations -> Display Authorization Data
2. go to the ABAP coding
3. go to the menu Utilities -> Settings / choose tab "ABAP editor " / choose tab "Debugging" check the chek - box "Actv." in the User field enter the user used in the Java logon (not the alias of the user!! e.g. for user XYZS enter "3B1968D7DD1")
4. Press enter or choose OK to get back to your source code
5. If you set you next break-point a pop-up will occur to ask you if you want to set an external break-point or a session break-point --> click external break-point (= former HTTP break-point) -->