Author:
James Vander Heyden

Do you want to squeeze more performance out of your Internal Table processing? The new ABAP object extensions in SAP require internal table definitions to look a little different. With this new style of definition comes many options for better performance like hash tables and sorted tables. The use of field symbols takes this performance concept one step further.

The new style of definition of internal tables usually doesn’t include a header area for the internal table. Furthermore, ABAP Objects will not allow internal tables with header lines. For added performance, instead of declaring a work area–use a field symbol. The work area concept and header line format both require data to be moved from the internal table to the work area or header area. A field symbol is just a pointer that will point to the proper line of the itab. With field symbols, no data needs to be moved. The field symbol just stores the proper memory address to point at the right line. The field symbol can have structure and be made up of fields similar to a work area or header line. Because no data needs to be copied, processing is much faster.

The keys to the usage are:

1) Defining the table records and the field symbol in a similar type.

* just an ordinary standard table

TYPES: BEGIN OF it_vbak_line,
vbeln LIKE vbak-vbeln,
vkorg LIKE vbak-vkorg,
vtweg LIKE vbak-vtweg,
spart LIKE vbak-spart,
kunnr LIKE vbak-kunnr,
END OF it_vbak_line.

DATA: it_vbak TYPE TABLE OF it_vbak_line.
FIELD-SYMBOLS: <it_vbak_line> TYPE it_vbak_line.

* or as a screaming fast hash table for keyed reads

TYPES: BEGIN OF it_vbpa_line,
vbeln LIKE vbak-vbeln,
kunnr LIKE vbak-kunnr,
END OF it_vbpa_line.

DATA: it_vbpa TYPE HASHED TABLE OF it_vbpa_line
WITH UNIQUE KEY vbeln.
FIELD-SYMBOLS: <it_vbpa_line> TYPE it_vbpa_line.

2) In ITAB processing, utilize the ASSIGNING command.

* loop example

LOOP AT it_vbak ASSIGNING <it_vbak_line>.

* look at records – populate it_zpartner
* read example

READ TABLE it_vbpa ASSIGNING <it_vbpa_line> WITH TABLE KEY vbeln = <it_vbak_line>-vbeln.

3) Refer to the field symbol’s fields in the loop or after the read.

wa_zpartner-vkorg = <it_vbak_line>-vkorg.
wa_zpartner-vtweg = <it_vbak_line>-vtweg.
wa_zpartner-spart = <it_vbak_line>-spart.
wa_zpartner-kunag = <it_vbak_line>-kunnr.
wa_zpartner-kunwe = <it_vbpa_line>-kunnr.

Pros:
BADIs can be used any number of times, whereas USER-EXITS can be used only one time.
BADIs are based on Object-Oriented-Programming with fixed structure -> Therefore SAP guarantees
the upward compatibility of all Business Add-In interfaces.

Cons:
It’s difficult to say, when using a transaction, whether BADI is used or not.

Solution:

1, Go to transaction SE37 and put a breakpoint on function SXV_GET_CLIF_BY_NAME.
2, Set a breakpoint on a call of the only function included.
3, Open another session and set YOUR transaction. The debugging mode opens with info
on BADIs. Name = BADI, Clif = implementation of a BADI.


FUNCTION sxv_get_clif_by_name .
*"----------------------------------------------------------------------
*"*"Lokale Schnittstelle:
*" IMPORTING
*" VALUE(NAME)
*" VALUE(PREFIX) TYPE SEEX_CLIF_PREFIX
*" EXPORTING
*" VALUE(CLIF) TYPE SEOCLSNAME
*"----------------------------------------------------------------------
CALL FUNCTION 'SXV_ADD_PREFIX'
EXPORTING
name = name
prefix = prefix
IMPORTING
new_name = clif.
ENDFUNCTION.


In SE37 you can find a function module called “CH_SPLIT_FILENAME”, that does the very thing.

CALL FUNCTION 'CH_SPLIT_FILENAME'
EXPORTING
complete_filename = lv_filename
* CHECK_DOS_FORMAT =
IMPORTING
* DRIVE =
extension = lv_doc_type
* NAME =
* NAME_WITH_EXT =
* PATH =
EXCEPTIONS
invalid_drive = 1
invalid_path = 2
OTHERS = 3.

Find out for yourselves:

Basic ABAP OO eLearnings

Solution: Keep on-line with ABAP programm running in background.

Step by step:

1. Go to transaction SE38.
2. Type “ZKEEP” into the input field.
3. Click on “Create”.
4. Paste the following code.
5. Activate!

*&---------------------------------------------------------------------*
*&                              Report  ZKEEP                          *
*&---------------------------------------------------------------------*
REPORT  ZKEEP                                  .
start-of-selection.
do.
wait up to 15 seconds.
CALL FUNCTION 'PROGRESS_INDICATOR'
EXPORTING
I_TEXT = 'Keeping...'.
enddo.

Next time you log in to SAP, just open two sessions and in one go to SE38 and run this programm. You can than work in the other session (first one will be taken by the ZKEEP report).

That’s it for today.

1, Clean your layout design – SAP GUI sometimes keep the layout and displays it without notice.

• Go to Settings -> Layout -> Layout management
• Delete all the current layouts within the manager
  

  Layout management

2, Clean buffer No.I – run program BALVBUFDEL
3, Clean buffer No.II – run program BCALV_BUFFER_DEL_SHARED
4, Run FM ‘STATUS_BUFFER_REFRESH’ – this helps for IE05, IE08 & other MM reports
5, You can try refresh tab & system buffers – run “/$TAB” & “/$SYNC” in transaction entry field

Now it’s the time to try again! Did it help? If it didn’t, try to check your code once again.