SAT is the new ABAP Runtime Analysis Tool of the SAP NetWeaver 7.0 EhP2 (successor of the SE30 transaction). This demo explores the SAT tools and shows how to use SAT for typical scenarios of ABAP runtime analysis, such as searching for performance bottlenecks, program flow analysis or memory consumption problems.

Watch the Demo (20 min)

Related posts:

1. Best SAP SDN Blog Posts from 2010
2. Caffeine – ABAP to Go
3. SAPLAB Version 2.0 is on-line!

Caffeine is a toolset that allows execution of the ABAP language on alternative runtimes outside of the ABAP server. As of today, it supports the execution of a subset of ABAP on the JVM (Java), Dalvik VM (Android), iOS (Objective C), and JavaScript. Its core design is centered around high performance, multi platform execution and multi threading.

Caffeine is at the moment a prototype project and proves the claims made. There is currently no relation to any current or future SAP product, but SAP is working on achieving this.

What’s it for?

Caffeine is a technology, not an application, and it can thus be applied to many use cases. Caffeine is not trying to enable the migration of existing ABAP code to other platforms, but is focusing on adding value to SAP’s On-Device, On-Demand, On-Premise strategy by making SAPs business programming language reach into spaces like mobile devices that our customer are looking to unlock and feed with information coming from the customers backend. Caffeine strives to help developers to build business applications that are better integrated from frontend to backend.

Download Full Paper

Related posts:

1. SAPLAB Version 2.0 is on-line!
2. Best SAP SDN Blog Posts from 2010
3. Best of SAP Sites Directory

I ran into a curious post by Sergio Ferrari which allows us to calculate how many lines of ABAP code we have in our systems. More than a curiosity, this simple tool can help us determine if our system is too overloaded with custom code or not.

The author excluded ABAP generated by special frameworks, like Report writer, SAP Query, Web Dynpro, LSMW,  and so on. He opted to do the filtering by Source System, Owner and Package. The release covered by this tool is ECC 6.0 an the following are also out of scope of this tool:

• BSP’s
• Adobe Forms, Smartforms and SAPScript
• XSLT/Web Services

This utility was named ZSDN_simple_ABAP_SLOC_COUNT, and aims to be an an indicator. The author didn’t want to give it too much relevance, the idea is solely to be an useful tool and help us estimate the upgrade effort or to evaluate the amount of work allocated for each of our packages.

As a curiosity, the post also includes the following information, related to lines of code in known software systems:

• Windows XP:      45 million lines of code
• Windows Vista:  50 million lines of code
• Mac OS:              86 million lines of code
• SAP (ABAP):      238 million lines of ABAP

Copy the code from the textearea below and paste it in a new report in transaction code SE38.

*&---------------------------------------------------------------------*
*& Report  ZSDN_SIMPLE_ABAP_SLOC_COUNT
*& Author: Andrea Olivieri, Sergio Ferrari
*&         Techedge SpA
*& Version: 1.0  - 2009/01/20
*& Title   How many lines of custom ABAP code are inside your system?
*&---------------------------------------------------------------------*
REPORT  zsdn_simple_abap_sloc_count_n LINE-SIZE 255.

* Global Data Type [ GDT   ]
TYPES: BEGIN OF ty_repository,
         devclass  TYPE tadir-devclass,
         name      TYPE trdir-name,
         object    TYPE tadir-object,
         srcsystem TYPE tadir-srcsystem,
         author    TYPE tadir-author,
         subc      TYPE trdir-subc,
         sloc      TYPE i,
       END OF ty_repository.
DATA: l_repository TYPE ty_repository.
DATA: t_repository TYPE STANDARD TABLE OF ty_repository.

* defining the selection-screen
TABLES: tadir.
SELECT-OPTIONS: xpack   FOR tadir-devclass,
                xobject FOR tadir-object,
                xauthor FOR tadir-obj_name.

INITIALIZATION.
  PERFORM init_select_options.

START-OF-SELECTION.
  PERFORM get_obj_set.
  PERFORM upd_obj_set_count_class_sloc.
  PERFORM count_prog_sloc.

END-OF-SELECTION.
  PERFORM alv.

*&---------------------------------------------------------------------*
*&      Form  init_select_options
*&---------------------------------------------------------------------*
*       INCLUDE OBJECTS:  PROG, FUGR and CLAS
*       EXCLUDE PACKAGES: $TMP and from A to W
*       EXCLUDE USERS:    SAP, SAP*, DDIC
*----------------------------------------------------------------------*
FORM init_select_options.

* Include objects: PROG, FUGR and CLAS
  IF xobject[] IS INITIAL.
    xobject-sign   = 'I'. xobject-option = 'EQ'. xobject-low = 'PROG'.
APPEND xobject.
    xobject-sign   = 'I'. xobject-option = 'EQ'. xobject-low = 'FUGR'.
APPEND xobject.
    xobject-sign   = 'I'. xobject-option = 'EQ'. xobject-low = 'CLAS'.
APPEND xobject.
  ENDIF.

* Exclude packages: $TMP and from A to W
  IF xpack[] IS INITIAL.
    xpack-sign   = 'E'. xpack-option = 'BT'. xpack-low = 'A'. xpack-high
= 'WZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ'. APPEND xpack.
    xpack-sign   = 'E'. xpack-option = 'EQ'. xpack-low = '$TMP'. APPEND
xpack.
  ENDIF.

* Exclude objects belonging to users: SAP* and DDIC
  IF xauthor[] IS INITIAL.
    xauthor-sign   = 'E'. xauthor-option = 'EQ'.     xauthor-low =
'SAP'.  APPEND xauthor.
    xauthor-sign   = 'E'. xauthor-option = 'EQ'.     xauthor-low =
'SAP*'. APPEND xauthor.
    xauthor-sign   = 'E'. xauthor-option = 'EQ'.     xauthor-low =
'DDIC'. APPEND xauthor.
  ENDIF.
ENDFORM.                    "init_select_options

*&---------------------------------------------------------------------*
*&      Form  get_obj_set
*&---------------------------------------------------------------------*
*       Get from TADIR
*----------------------------------------------------------------------*
FORM get_obj_set.
  DATA: l_tadir TYPE tadir.

  SELECT * FROM tadir INTO l_tadir
           WHERE pgmid      EQ 'R3TR'
           AND   obj_name   IN xauthor
           AND   object     IN xobject
           AND   devclass   IN xpack
            AND srcsystem   NE 'SAP'
           AND   author     IN xauthor.               "#EC CI_SGLSELECT
    IF NOT l_tadir-obj_name CP '_______________________________*'.
      MOVE-CORRESPONDING l_tadir TO l_repository.
      l_repository-name     = l_tadir-obj_name.
      l_repository-devclass = l_tadir-devclass.
      APPEND l_repository TO t_repository.
    ENDIF.
  ENDSELECT.
*
  SORT t_repository BY devclass name.

ENDFORM.                    "get_obj_set

*&---------------------------------------------------------------------*
*&      Form  upd_obj_set_count_class_sloc
*&---------------------------------------------------------------------*
*       ...and Compute SLOC for CLAS
*----------------------------------------------------------------------*
FORM upd_obj_set_count_class_sloc.
  TYPE-POOLS: sedi.
  TYPES: BEGIN OF ty_irdir,
          name LIKE trdir-name,
          devc    LIKE tadir-devclass,
        END OF ty_irdir,
        BEGIN OF ty_itab,
          repname LIKE sy-repid,
          devc    LIKE tadir-devclass,
        END OF ty_itab,
        BEGIN OF ty_crdir,
          name LIKE trdir-name,
          subc LIKE trdir-subc,
          devc    LIKE tadir-devclass,
        END OF ty_crdir.

  DATA: save_tabix      TYPE sy-tabix,
        l_class         TYPE sobj_name,
        l_pgmid         TYPE pgmid,
        l_object        TYPE trobjtype,
        class_name      TYPE programm,
        class_pool_name TYPE programm,
        lclskey         TYPE seoclskey.
  DATA: sourceline      TYPE string.
  DATA: l_1st_char      TYPE c.

  DATA: l_irdir         TYPE ty_irdir,
        l_itab          TYPE ty_itab,
        l_itab1         TYPE ty_itab,
        l_crdir         TYPE ty_crdir.
  DATA: t_irdir TYPE STANDARD TABLE OF ty_irdir,
        t_itab  TYPE STANDARD TABLE OF ty_itab,
        t_itab1 TYPE STANDARD TABLE OF ty_itab,
        t_crdir TYPE STANDARD TABLE OF ty_crdir.

  DATA: l_sloc          TYPE i.

  LOOP AT t_repository INTO l_repository.
    save_tabix = sy-tabix.
    CASE l_repository-object.
      WHEN 'PROG'.
        SELECT SINGLE subc FROM trdir INTO l_repository-subc WHERE  name
= l_repository-name.
        IF sy-subrc = 0.
          MODIFY t_repository FROM l_repository INDEX save_tabix
TRANSPORTING subc .
        ENDIF.
      WHEN 'FUGR'.
        CONCATENATE 'SAPL' l_repository-name INTO l_irdir-name.
        l_irdir-devc = l_repository-devclass.
        APPEND l_irdir TO t_irdir.
        l_repository-name   = l_irdir-name.
        l_repository-object = 'PROG'.
        SELECT SINGLE subc FROM trdir INTO l_repository-subc WHERE  name
= l_repository-name.
        IF sy-subrc = 0.
          MODIFY t_repository FROM l_repository INDEX save_tabix
TRANSPORTING name object subc.
        ENDIF.
        CLEAR l_irdir.
      WHEN 'CLAS'.
        DATA source_new TYPE sedi_source.
        DATA l_inctype(5).

        class_name = l_repository-name.
        l_pgmid = 'R3TR'.
        l_object = l_repository-object.
        l_class = class_name.
        CALL FUNCTION 'SEO_CLASS_GET_CP_NAME'
          EXPORTING
            pgmid                 = l_pgmid
            object                = l_object
            obj_name              = l_class
          IMPORTING
            progname              = class_pool_name
          EXCEPTIONS
            no_class_or_interface = 1.

        IF sy-subrc = 0.
          SELECT SINGLE subc FROM trdir INTO l_repository-subc WHERE name
= class_pool_name.
        ENDIF.

        lclskey-clsname = cl_oo_classname_service=>get_clsname_by_include(
class_name ).

        CLEAR l_class.
        CONCATENATE l_repository-name '%' INTO l_class.

        SELECT name FROM  trdir INTO TABLE t_crdir WHERE  name  LIKE
l_class.
        IF NOT t_crdir[] IS INITIAL.
          LOOP AT t_crdir INTO l_crdir.
            l_inctype = l_crdir-name+30(5) .
            REFRESH source_new.
            CALL FUNCTION 'SEO_CLASS_GET_INCLUDE_SOURCE'
              EXPORTING
                clskey                       = lclskey
                inctype                      = l_inctype
              IMPORTING
                source_expanded              = source_new
              EXCEPTIONS
                _internal_class_not_existing = 1
                not_existing                 = 2
                OTHERS                       = 3.
            CHECK sy-subrc = 0.

*           Compute SLOC !
            LOOP AT source_new INTO sourceline.
              l_1st_char = sourceline.
              IF    sourceline IS INITIAL
                 OR l_1st_char = '*'.
                DELETE source_new INDEX sy-tabix.
              ENDIF.
            ENDLOOP.
            l_sloc = LINES( source_new ).
            ADD l_sloc TO l_repository-sloc.
          ENDLOOP.
          MODIFY t_repository FROM l_repository INDEX save_tabix
TRANSPORTING sloc subc.
        ENDIF.
      WHEN OTHERS. CONTINUE.
    ENDCASE.

  ENDLOOP.

  IF t_irdir[] IS NOT INITIAL.
    LOOP AT t_irdir INTO l_irdir.
      REFRESH t_itab1.
      CALL FUNCTION 'GET_INCLUDES'
        EXPORTING
          progname = l_irdir-name
        TABLES
          incltab  = t_itab1.

*     append lines of t_itab1 to itab.
      LOOP AT t_itab1 INTO l_itab1.
        l_itab-repname = l_itab1-repname.
        l_itab-devc    = l_irdir-devc.    "Sometimes it's false
        APPEND l_itab TO t_itab.
        CLEAR l_itab.
      ENDLOOP.
    ENDLOOP.
  ENDIF.

  DATA: l_trdir TYPE trdir.

  LOOP AT t_itab INTO l_itab.
    SELECT SINGLE * FROM  trdir INTO l_trdir
           WHERE  name  = l_itab-repname
            AND    cnam  NOT LIKE 'SAP%'
            AND    cnam  <> 'DDIC'.
    CHECK sy-subrc = 0.

    MOVE-CORRESPONDING l_trdir TO l_repository.
    l_repository-devclass = l_itab-devc.
    l_repository-object   = 'PROG'.
    APPEND l_repository TO t_repository.

  ENDLOOP.

  SORT t_repository BY name object devclass.
  DELETE ADJACENT DUPLICATES FROM t_repository COMPARING name object
devclass.

ENDFORM.                    "upd_obj_set_count_class_sloc
*&---------------------------------------------------------------------*
*&      Form  count_prog_sloc
*&---------------------------------------------------------------------*
*       text
*----------------------------------------------------------------------*
FORM count_prog_sloc.
  DATA: l_prog     TYPE c LENGTH 30.
  DATA: isource    TYPE TABLE OF string.
  DATA: l_1st_char TYPE c.

  LOOP AT t_repository INTO l_repository WHERE object = 'PROG'.
*   Compute SLOC !
    l_prog = l_repository-name.
    READ REPORT l_prog INTO isource.
    DATA: l_source_line TYPE string.
    LOOP AT isource INTO l_source_line.
      l_1st_char = l_source_line.
      IF    l_source_line IS INITIAL     "Empty
         OR l_1st_char = '*'.            "Comment
        DELETE isource INDEX sy-tabix.
      ENDIF.
    ENDLOOP.
    l_repository-sloc = LINES( isource ).

*   Update SLOC into t_repository
    READ TABLE t_repository WITH TABLE KEY name     = l_repository-name
                                       devclass = l_repository-devclass
                                       object   = l_repository-object
                                       srcsystem = l_repository-srcsystem
                                       author    = l_repository-author
                                       subc      = l_repository-subc
                        TRANSPORTING NO FIELDS.
    IF sy-subrc = 0.
      MODIFY t_repository FROM l_repository INDEX sy-tabix TRANSPORTING
sloc.
    ENDIF.
  ENDLOOP.
ENDFORM.                    "count_prog_sloc

*&---------------------------------------------------------------------*
*&      Form  alv
*&---------------------------------------------------------------------*
*       text
*----------------------------------------------------------------------*
FORM alv.
  DATA: gr_table     TYPE REF TO cl_salv_table,
        gr_display   TYPE REF TO cl_salv_display_settings,
        gr_functions TYPE REF TO cl_salv_functions,
        gr_sorts     TYPE REF TO cl_salv_sorts,
        gr_agg       TYPE REF TO cl_salv_aggregations.
  TRY.
*     Create ALV table
      cl_salv_table=>factory( IMPORTING r_salv_table = gr_table CHANGING
t_table = t_repository ).
*     Set zebra layout
      gr_display = gr_table->get_display_settings( ).
      gr_display->set_striped_pattern( cl_salv_display_settings=>true ).
*     Display all standard function
      gr_functions = gr_table->get_functions( ).
      gr_functions->set_all( abap_true ).
*     Sort
      gr_sorts = gr_table->get_sorts( ).
      gr_sorts->add_sort( columnname = 'DEVCLASS' subtotal = abap_true ).
      gr_sorts->add_sort( columnname = 'NAME'     subtotal = abap_false ).
*     Totals
      gr_agg = gr_table->get_aggregations( ).
      gr_agg->add_aggregation( 'SLOC' ).
*     Display table
      gr_table->display( ).
    CATCH cx_salv_msg.
      WRITE: / 'Exception CX_SALV_MSG'.
    CATCH cx_salv_not_found.
      WRITE: / 'Exception CX_SALV_NOT_FOUND'.
    CATCH cx_salv_data_error.
      WRITE: / 'Exception CX_SALV_DATA_ERROR'.
    CATCH cx_salv_existing.
      WRITE: / 'Exception CX_SALV_EXISTING'.
  ENDTRY.
ENDFORM.                    "alv

Additional links and resources:

• Source lines of code (wikipedia)

Related posts:

1. How to Send a System Message to another SAP User
2. One Minute, One Great ABAP Tip
3. TIP: Overide Lack of Authorization on a Transaction Code

Well I can say that this is a long awaited SAP launch and that will provide help to many users worldwide. If you’re like me, at a certain point in your SAP career, you felt the need to have your own SAP sandbox. Being for professional purposes or for your own personal skillset build, an SAP sandbox system is always handy and you can’t well perform this kind of experiments on your client development system.

Up until now, there weren’t many (viable) available solutions. There are some companies that provide you a paid service for you to have your own SAP system/client but usually expensive for most of us.

This month Learning on Demand by SAP launched a new service called SAP Sandbox onDemand, which consists of an SAP ECC 6.0 system with sufficient basic data, such as customer and vendor master data, to enable substantial experimentation.

Using this system, users can access the core ERP functionality of modules such as FI and CO, SD, HR and MM and can write and test ABAP code and modify SAP Netweaver settings and configurations. This offering will provide interested individuals with the ability to reinforce their existing SAP ERP knowledge and skills through experimentation in a live but safe environment. It will also enable you to clarify areas of ambiguity in your knowledge or to test new functionality that they may be considering for an existing or new client.

Given that the SAP Sandbox onDemand is accessed via an SAP WebGUI, there is no need to install any client-side software on your PC, so you can start using the system immediately after receiving your access details.

Comparing with other and existing offers, SAP Sandbox onDemand has a fair price in my perspective: US$80 for 30 days access.

Click here for more info and start playing now!

Related posts:

1. Best of SAP Sites Directory
2. SAPLAB Version 2.0 is on-line!
3. 22 SAP How To’s you can’t miss!

Hi everybody. As Web Dynpro evolves, so does ABAP programmers’ interest over it. I keep receiving emails from professionals that want to start hands-on towards ABAP Web Dynpro but, mainly due to day-to-day engagement on their projects, they can’t start and end up delaying it.

My suggestion is whenever you have 30 minutes, start from the Basics and build your knowledge starting from here. In this post I include links to 7 basic tutorials and explanations, linking to SDN files, hoping they will help anyone wanting to start on ABAP Web Dynpro.

1 – Create a Simple Web Dynpro Application

In this step-by-step tutorial you will create a simple Web Dynpro component, which consists of one view. For the view, you will create a view context, which is linked to a table element on the view layout and which contains the data from table SFLIGHT. This table will be displayed in the browser at runtime. Furthermore, you will create a Web Dynpro application for this simple Web Dynpro component, which can be run in the browser.

Author(s): SAP AG

2 – BAPI Usage

This exercise demonstrates the usage of BAPIs and how to implement a view with input fields and a result table.

Author(s): SAP AG

3 – Navigation

This tutorial demonstrates how easy it is to navigate between different views of the same Web Dynpro Application. It is shown by extending tutorial Web Dynpro for ABAP – BAPI Usage with additional view in order to display a message in the case that no flights are available for a particular start and destination combination. Of course, you will be able to return back to search for a new combination.

Author(s): SAP AG

4 – Display Bookings for Selected Flights

In this tutorial, the BAPINAV component from Web Dynpro for ABAP – BAPI Navigation tutorial will be further enhanced to display a list of bookings for a selected flight. The context which contains the flights information will be enhanced with a sub node for the corresponding bookings. We will also show how the booking information is retrieved in a so called supply function and the context node bound to a new table UI element in the Main View.

Author(s): SAP AG

5 – Component and Application Configuration

In Tutorial 3 you enhanced the Web Dynpro flight sample with a navigation to a separate view including a message for the case where no flights are found for a given search query. But some of your customers might prefer the former solution where the empty result table is displayed instead of jumping to a new view.

One possibility would be to have two slightly different Web Dynpro components. But it would obviously be better to have just one Web Dynpro component which can be configured somehow to behave in one or the other way. You can imagine that a real life application can have several such switches or parameters to steer the behavior of such a flexible application.

Therefore, Web Dynpro provides several techniques, such as configuration, personalization, or customization, in order to modify the UI or the navigation path of a delivered Web Dynpro application or component at the customer’s site.

This tutorial shows how to implement such a configuration for this simple example with two different possibilities to handle the case of no found flights.

Author(s): SAP AG

6 – Component Usage

Prerequistes are Tutorial 3 – Navigation and Tutorial 4 – Display a list of bookings for a selected flight.
Just to review back Tutorial 4, we created a context Flight_List which contains the flight information and it was advanced with sub-node BOOKINGS for the corresponding bookings. Automatically, the booking information was retrived in a new table (using supply function) which shows a list of bookings for a selected flight.

Author(s): SAP AG

7 – Column Coloring in ALV

The article aims to help the professionals who have only ABAP knowledge and passion to develop their Web Dynpro knowledge in ABAP. This article provides the knowledge for understanding ALV in Web dynpro and coloring a column in ALV.

Author(s): J.Jayanthi

Related posts:

1. Internationalization with Web Dynpro ABAP
2. How to Send a System Message to another SAP User
3. 22 SAP How To’s you can’t miss!

Imagine that you’re working configuring a certain SAP module, touching several tables and configuration spots. Sometimes it might happen that someone else is maintaining the same table that you need access. This standard Function Module could be useful in these cases, since you might not know an alternative way to contact the user locking the table or other SAP object. Since the system will display who is locking the table, you will know for whom to send the message.

Here’s how it goes.

Trying to access the table

When trying to maintain a certain table, the user will receive the following warning:

Sending a system message using a standard SAP function module

Once you’ve identified the user, access SE37 – assuming you have permission! In SE37 call SAP standard function module TH_POPUP.

Fill in the following input parameters:

- CLIENT: the system client on which you’re working on. If you don’t know this, take a look at the lower right status bar;
- USER: the user for which you want the message to be delivered;
- MESSAGE: the text message you want to deliver to the user;
- MESSAGE_LEN: allows you to define a message length. Leave it empty;
- CUT_BLANKS: allows you to specify if you want to trim existing spaces. Leave it empty.

To submit the message just hit “Execute (F8)”

What the user receives

When you click on “Execute (F8)”, the destination user receives the following message as a pop-up:

This is just a simple system tool that can help you in a day to day basis, working with SAP.

Related posts:

1. How To Do A System Trace
2. TIP: Overide Lack of Authorization on a Transaction Code
3. Single Sign-On with your SAP OSS User

The Best of SAP Sites Directory is a great resource if you’re looking for information on SAP, ABAP, Netweaver, FICO, SD, MM, PP, downloads and other SAP tutorials and user guides.  The Best of SAP Sites Directory blog is owned by eddai, who is also blogger and owner of SAP DOCS.

The Best of SAP Sites Directory is a SAP topics aggregator since it displays headlines from the most popular SAP sites on the internet.

Eddai leaves his welcome message:

This site is the dashboard for the latest web-buzz, a single page that encapsulates up-to-the-minute headlines from the most popular SAP sites on the internet with a purpose of getting a quick glance on updates over various categories. The lists will be enhanced in each categories by day. Hope you find this site useful.

Click here to enter Best of SAP Sites Directory

Related posts:

1. Tools for SAP Portal
2. Best Practices for SAP Netweaver Portal 7.0
3. 15 SAP Frequently Asked Questions (FAQ)

When you just need to look on a specific transaction and you don’t have permission?
Wait no more, this is a good and quick work-arround:

- Go to transaction SE37, display the function module RS_TRANSACTION_TEST and place a break-point after instruction ( CALL ‘AUTH_CHECK_TCODE’ ID ‘TCODE’ FIELD objectname. ).

- Go to transaction SE93, fill the transaction code that you need to execute and press the test Button (F8).

The debug window will pop-up and you will find yourself on the breakpoint that you placed on the function module RS_TRANSACTION_TEST. Change the system variable SY-SUBRC to ’0′ and press F8. And then you will find yourself in the transaction that you needed.

Simple and Easy!

Related posts:

1. SAP ABAP Transaction Codes
2. Batch Input Concept

Once upon a time, there was a very clever person at Waldorf that decided that SAP standard coding could be possible to enhance without actually changing the standard code. A then Enhancement Framework was born.

The approach that I usually take on the SAP training sessions that I provide is to highlight the Enhancement Framework as a second layer of code sitting on top of SAP standard code. The two layers connect through anchor points. These anchor points are the BADIs, the enhancement points, sections etc.
The real great advantage of using the Enhancement Framework is that upon an upgrade or installation of support packages, the new standard code enters directly on top of the standard layer without touching anything on the enhancement layer.

1. Explicit VS Implicit Enhancement

Implicit enhancement options are already in a predefined place attached to the standard code, they are provided by the framework. Explicit enhancement options need to be inserted explicitly.

2. Explicit Enhancement

• BADIs – The interface of the BADI is already defined (attributes, methods, etc). It’s up to the developer to create one or more implementations for this interface. BADIs execution can be subjected to filters and there are old and new BADIs. The old ones are based at code level where implementations are searched by means of code execution, they are performance costly and should be avoided. The new ones are based on the kernel level and give the ability of a fast run and low level of impact on performance.
• These explicit enhancements that are new to this ECC6 framework are the ones which can be provided at a specific place – called Enhancement Point, and another which can be used to replace a set of statements – called Enhancement Section.

3. Implicit Enhancement

These enhancements are available at certain pre-defined places. For example:

• At the end of all the programs (Includes, Reports, Function pool, Module pool, etc.), after the last statement
• At the beginning and end of all FORM subroutines
• At the end of all ABAP Function Modules
• At the end of all visibility areas (public, protected and private) of local class

Using these Enhancement Framework enhancing function modules, class-methods interfaces are also quite easy to perform. On our next posts we will approach all thes features and a less known one, the Dark Side of the Enhancement Framework.

See you next time, on the dark side!

About the author

Helder Goncalves (hfgoncalves) has been working with ABAP development for more than 9 years, covering all major modules, releases and technologies. Click here to view Helder’s full profile.

No related posts.

This is my first post for SAPLAB.org, so I’ve decided to write about something really simple yet powerful – building ABAP Dynamic Tables using RTTS ( From Release 6.40). RTTS stands for Run Time Type Services.

Creating dynamic internal tables in ABAP programs can be very useful, dynamic coding can provide fast program running and easier maintenance. From release 6.40, RTTS has provided a new approach to dynamic table programming. Here’s an example of what I mean:

REPORT Z_1MIN_1GREATTIP_RTTS.

TABLES PA0002.

* Table type
TYPES: BEGIN OF TY_PERNR_LIST,
         PERNR TYPE PERNR_D,
         BEGDA TYPE BEGDA,
         ENDDA TYPE ENDDA,
       END   OF TY_PERNR_LIST.

* Dynamic Table
DATA: LO_STRUCTDESCR   TYPE REF TO CL_ABAP_STRUCTDESCR,
      LO_ELEMDESCR  TYPE REF TO CL_ABAP_ELEMDESCR,
      LO_STRUCTDESCR_NEW TYPE REF TO CL_ABAP_STRUCTDESCR,
      LO_TABLEDESCR  TYPE REF TO CL_ABAP_TABLEDESCR,
      LO_DATA     TYPE REF TO DATA,
      LT_COMPONENT     TYPE CL_ABAP_STRUCTDESCR=>COMPONENT_TABLE,
      LT_TOT_COMPONENT TYPE CL_ABAP_STRUCTDESCR=>COMPONENT_TABLE,
      LA_COMPONENT     LIKE LINE OF LT_COMPONENT.

* Dynamic Selection fields
TYPES: BEGIN OF TY_FIELDCATALOG,
         FIELDNAME TYPE CHAR30,
       END   OF TY_FIELDCATALOG.
*
DATA:  LT_FIELDCATALOG TYPE STANDARD TABLE OF TY_FIELDCATALOG,
       LA_FIELDCATALOG TYPE TY_FIELDCATALOG.

* field symbols to access the dynamic table
FIELD-SYMBOLS:    TYPE ANY TABLE,
                 TYPE ANY,
                TYPE ANY.
*
* Selection Screen
SELECT-OPTIONS: SO_PERNR FOR PA0002-PERNR.

START-OF-SELECTION.

* 1- Getting Components of type
  LO_STRUCTDESCR ?= CL_ABAP_TYPEDESCR=>DESCRIBE_BY_NAME( 'TY_PERNR_LIST' ).
  LT_COMPONENT  = LO_STRUCTDESCR->GET_COMPONENTS( ).
  APPEND LINES OF LT_COMPONENT TO LT_TOT_COMPONENT.

*   Element Description Last Name
  LO_ELEMDESCR ?= CL_ABAP_ELEMDESCR=>DESCRIBE_BY_NAME( 'PAD_NACHN' ).
*
*   Field name
  LA_COMPONENT-NAME = 'NACHN'.
*
*   Field type
  LA_COMPONENT-TYPE = CL_ABAP_ELEMDESCR=>GET_C(
                    P_LENGTH   = LO_ELEMDESCR->LENGTH ).
*
*   Filling the component table
  APPEND LA_COMPONENT TO LT_TOT_COMPONENT.
  CLEAR: LA_COMPONENT.

*   Element Description First Name
  LO_ELEMDESCR ?= CL_ABAP_ELEMDESCR=>DESCRIBE_BY_NAME( 'PAD_VORNA' ).
*
*   Field name
  LA_COMPONENT-NAME = 'VORNA'.
*
*   Field type
  LA_COMPONENT-TYPE = CL_ABAP_ELEMDESCR=>GET_C(
                     P_LENGTH   = LO_ELEMDESCR->LENGTH ).
*
*   Filling the component table
  APPEND LA_COMPONENT TO LT_TOT_COMPONENT.
  CLEAR: LA_COMPONENT.

*
* 3. Create a New Type
  LO_STRUCTDESCR_NEW = CL_ABAP_STRUCTDESCR=>CREATE( LT_TOT_COMPONENT ).
*
* 4. New Table type
  LO_TABLEDESCR = CL_ABAP_TABLEDESCR=>CREATE(
                  P_LINE_TYPE  = LO_STRUCTDESCR_NEW
                  P_TABLE_KIND = CL_ABAP_TABLEDESCR=>TABLEKIND_STD
                  P_UNIQUE     = ABAP_FALSE ).
*
* 5. data to handle the new table type
  CREATE DATA LO_DATA TYPE HANDLE LO_TABLEDESCR.
*
* 6. New internal table in the fieldsymbols
  ASSIGN LO_DATA->* TO .
*
*$*$*...............Dynamic Selection.............................*$*$*
* Filling up the table for the Selection fields of Select Query
  LOOP AT LT_TOT_COMPONENT INTO LA_COMPONENT.
    LA_FIELDCATALOG-FIELDNAME = LA_COMPONENT-NAME.
    APPEND LA_FIELDCATALOG TO LT_FIELDCATALOG.
    CLEAR: LA_COMPONENT, LA_FIELDCATALOG.
  ENDLOOP.
*
* Selecting data
  SELECT (LT_FIELDCATALOG)
         INTO  TABLE 
         FROM  PA0002
         UP TO 10 ROWS
         WHERE PERNR IN SO_PERNR.
*
*$*$*...............Accessing dynamic table.......................*$*$*
  LOOP AT  ASSIGNING .
    ASSIGN COMPONENT 'VORNA' OF STRUCTURE  TO .
    CONCATENATE 'Mr.'  INTO  SEPARATED BY SPACE.
  ENDLOOP.
*
*
*$*$*...............Displaying using SALV model...................*$*$*
*
  DATA: LO_ALV TYPE REF TO CL_SALV_TABLE.
*
  TRY.
      CL_SALV_TABLE=>FACTORY(
        EXPORTING
          LIST_DISPLAY = ABAP_FALSE
        IMPORTING
          R_SALV_TABLE = LO_ALV
        CHANGING
          T_TABLE      =  ).
    CATCH CX_SALV_MSG .
  ENDTRY.
*
  LO_ALV->DISPLAY( ).

This is a good and quick way to create a dynamic ALV report in just a few lines of code. Please be sure to read up next on “1 minute – 1 Great Tip”: ECC6 Enhancement Framework in 100 lines.

About the author

Helder Goncalves (hfgoncalves) has been working with ABAP development for more than 9 years, covering all major modules, releases and technologies. Click here to view Helder’s full profile.

Related posts:

1. ALV Report Sample

SAP provides a set of ALV (ABAP List Viewer) function modules which can be used to enhance the output of a Report. An ALV is a tool which enables the display of data in a grid, combining a better readability along with greater functionality, like sorting, filter, searching, exporting to Excel, etc. The included sample code is for a simple ALV which will display materials based on a selection screen “From…To”.

Steps to get this ALV running

1. Enter transaction code SE38

2. Create a new Report (in the example called ZHR_MYALV)

3. Copy and paste the code below:

REPORT ZHR_MYALV.
*******************************************************************
*Simple example to use ALV and to define the ALV data in an internal
*table
********************************************************************
*data definition

tables:
marav. "Table MARA and table MAKT

*---------------------------------------------------------------------*
* Data to be displayed in ALV
* Using the following syntax, REUSE_ALV_FIELDCATALOG_MERGE can auto-
* matically determine the fieldstructure from this source program
Data:
begin of imat occurs 100,
matnr like marav-matnr, "Material number
maktx like marav-maktx, "Material short text
matkl like marav-matkl, "Material group (so you can test to make
                        " intermediate sums)
ntgew like marav-ntgew, "Net weight, numeric field (so you can test to
                        "make sums)
gewei like marav-gewei, "weight unit (just to be complete)
end of imat.

*---------------------------------------------------------------------*
* Other data needed
* field to store report name
data i_repid like sy-repid.
* field to check table length
data i_lines like sy-tabix.

*---------------------------------------------------------------------*
* Data for ALV display
TYPE-POOLS: SLIS.
data int_fcat type SLIS_T_FIELDCAT_ALV.

*---------------------------------------------------------------------*
select-options:
s_matnr for marav-matnr matchcode object MAT1.

*---------------------------------------------------------------------*
start-of-selection.

* read data into table imat
  select * from marav
  into corresponding fields of table imat
  where
  matnr in s_matnr.

* Check if material was found
  clear i_lines.
  describe table imat lines i_lines.
  if i_lines lt 1.
*   Using hardcoded write here for easy upload
    write: /
    'No materials found.'.
    exit.
  endif.

end-of-selection.

* To use ALV, we need either a reference to a structure defined in
* the SAP Data Dictionary (DDIC) or an in-program structure called
* the Field Catalog.
* The Field Catalog can be declared explicitly or generated by FUNCTION
* 'REUSE_ALV_FIELDCATALOG_MERGE' from an internal table from any
* report source, including this report.
*---------------------------------------------------------------------*

* Store report name
  i_repid = sy-repid.

* Create Fieldcatalogue from internal table
  CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'
    EXPORTING
      I_PROGRAM_NAME         = i_repid
      I_INTERNAL_TABNAME     = 'IMAT'  "capital letters!
      I_INCLNAME             = i_repid
    CHANGING
      CT_FIELDCAT            = int_fcat
    EXCEPTIONS
      INCONSISTENT_INTERFACE = 1
      PROGRAM_ERROR          = 2
      OTHERS                 = 3.
*explanations:
*    I_PROGRAM_NAME is the program which calls this function
*
*    I_INTERNAL_TABNAME is the name of the internal table which you want
*                       to display in ALV
*
*    I_INCLNAME is the ABAP-source where the internal table is defined
*               (DATA....)
*      CT_FIELDCAT contains the Fieldcatalouge that we need later for
*      ALV display

  IF SY-SUBRC <> 0.
    write: /
    'Returncode',
    sy-subrc,
    'from FUNCTION REUSE_ALV_FIELDCATALOG_MERGE'.
  ENDIF.

*This was the field catalog
*---------------------------------------------------------------------*
*

* Call for ALV list display
  CALL FUNCTION 'REUSE_ALV_LIST_DISPLAY'
    EXPORTING
      I_CALLBACK_PROGRAM = i_repid
      IT_FIELDCAT        = int_fcat
    TABLES
      T_OUTTAB           = imat
    EXCEPTIONS
      PROGRAM_ERROR      = 1
      OTHERS             = 2.

*explanations:
*    I_CALLBACK_PROGRAM is the program which calls this function
*
*    IT_FIELDCAT (just made by REUSE_ALV_FIELDCATALOG_MERGE) contains
*                 now the data definition needed for display
*
*    I_SAVE allows the user to save his own layouts
*
*      T_OUTTAB contains the data to be displayed in ALV

  IF SY-SUBRC <> 0.
    write: /
    'Returncode',
    sy-subrc,
    'from FUNCTION REUSE_ALV_LIST_DISPLAY'.
  ENDIF.

4. Activate the report and click on “Direct Processing (F8)”

5. The selection screen will appear:

6. Fill in some data parameters and click on “Execute (F8)” to display the result.

This is an example that you can use and adapt to build your own ALV reports.

Related posts:

1. Batch Input Concept

A batch input session is a set of one or more calls to transactions along with the data to be processed by the transactions. The system normally executes the transactions in a session non-interactively, allowing rapid entry of bulk data into an R/3 System.

A session records transactions and data in a special format that can be interpreted by the R/3 System. When the System reads a session, it uses the data in the session to simulate on-line entry of transactions and data. The System can call transactions and enter data using most of the facilities that are available to interactive users.

For example, the data that a session enters into transaction screens is subject to the same consistency checking as in normal interactive operation. Further, batch input sessions are subject to the user-based authorization checking that is performed by the system.

There are three batch input methods:

1. In the Direct Input Method, the programs are provided by the SAP system. These programs are available for Standard Applications. Under this method, the data base is updated using a Function Module, which is responsible for executing the appropriate consistency checks.
2. In the Call Transaction Method, the ABAP Program reads the external data which is present on the Application or Presentation Server, and uses the ABAP Statement CALL TRANSACTION USING to run a SAP statement.
3. In the Session Method the program reads the data and the SAP system stores the data in a “Batch Input Session”. The session records the actions that are required to transfer data into the system using normal SAP transactions.

Figure – Batch Input Session

Copyright (c) 2009 – saplab.org.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free documentation License, Version 1.2 or any later version published by the Free Software Foundation, with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. Source: wikipedia.

No related posts.