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.

In this post I include some links to external sources like SDN, as well as some links to some of my own posts, hoping to help anyone who’s trying to accomplish an SAP product installation end to end.

1. Netweaver Sneak Preview (NSP) installation – Part 1

Gingle starts his series of posts by explaining which components are necessary, how and where to download them and how to unzip them, etc. The post includes a series of comprehensive screenshots and step-by-step approach to guide you into success.

2. Logical System & Virtual Machine – Part 2

Continuing his previous post as described in point 1., Gingle explains how to setup the Logical System and Virtual Machine. Again, Gingle was thorough in his explanation, including step by step details and lots of screenshots to help us progress.

3. License & Profiles – Part 3

In this post, the whole License and Profiles procedure is well explained and documented. Well done Gingle!

4. Transport System – Part 4

Probably as a SAP Consultant, you never had to deal with this kind of configuration. Just in case you need it.

5. HTTPS & Sapcrypto – Part 5

What is HTTPS & Sapcrypto? Learn about and also why and how you should configure it.

6. SPAM & Kernel – Part 6

Gingle intended on importing some transports and performing some upgrades, SAP always recommends the Support Package Manager – SPAM, to be the latest. Learn how.

7. Upgrade to SP6 – Part 7

This post explains which component versions to consider, how to download them and how to install them. Again, step by step approach and lots of screenshots.

8. BI Content – Part 8

According to the author (Gingle), after a successful upgrade to SP6, it seemed only natural to attempt to install BI Content.

9. The CE2 Installation- Part 9

In this post, Gingle explains how to install the Netweaver Composite Environment 7.2 Trial Version.

10. Install a Local SAP Netweaver Developer Workplace

A detailed explanation on how to successfully install your own local SAP Netweaver Developer Workplace. Please be sure to go through the necessary prerequisites.

11. How To Do a Support Package Stack Upgrade – Part 1

Learn how to apply a Support Package upgrade on your system.

12. How to Tune the Performance of KM

This SAP How-to guide provides recommendations for improving the performance of Knowledge Management (KM) in SAP NetWeaver 2004.

13. TREX Installation on EP7

This how-to tutorial explains the TREX Basis Installation as well as the some post configuration activities, needed for the TREX to work.

14. How to Use Portal Session Notification with Your Own Custom Applications

The SAP Enterprise Portal offers a mechanism called Session Release Notification. This feature is used by SAP applications running inside the portal to close their sessions in case the user closes the browser window, navigates away from the application or logs-off from the SAP Portal.

15. How to Install a SAP (Max)DB Instance

Learn how to easily install a SAP MaxDB Instance.

16. Configure Single Sign-On (SSO) on the Portal and the ERP

Learn how to easily configure Single Sign-On (SSO) on the Portal and the ERP.

17. How Many Lines of ABAP Code In Your System?

This is just a fun and easy way to benchmark how many lines of ABAP code exist in your system.

18. How to do a System Trace?

When you work with SAP Enterprise Portal, sometimes it’s useful to use the System Trace tool, enabled by the ERP system.

19. Single Sign-On with your SAP OSS User

If you have a company issued SAP OSS user and use it all the time (like myself), this post is for you.

20. Configuring SAP Connect (SCOT)

From SAP WAS 6.10, SAP directly supports SMTP (Simple Mail Transfer Protocol). This means that the emails can be exchanged directly between SAP system and any SMTP compliant mail server. Learn how to configure it.

21. Configuring UWL for Guided Procedures on C.E.

This tutorial covers the configuration of the Universal Worklist (UWL) for Guided Procedures actions. It shows how to configure the UWL in the SAP NetWeaver Composition Environment when the Guided Procedures are executed locally.

22. Configuring UWL for Guided Procedures on C.E.

This tutorial covers the configuration of the Universal Worklist (UWL) for Guided Procedures actions. It shows how to configure the UWL in the SAP NetWeaver Composition Environment when the Guided Procedures are executed locally.

Please comment if you found this post useful! Many thanks in advance.

The result and feedback has been good and now I’ve decided to raise this project to a new level. Besides the new look and feel, which is now more web 2.0 friendly, new functionalities will come and also more posts in the following weeks. Please be aware and keep visiting the blog! Please click here to subscribe the newsletter, which will bring updates to your e-mail.

I’d also like to take this opportunity to thank all returning visitors, as well as new visitors landing in SAPLAB. Please take your time to browse through the blog and don’t forget to leave your comments. It’s what gives life to this project!

Sincerely, kind regards.

Antonio Caldas

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

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)

1. Create the Report, transaction code SE38

2. In the example, I named the report ZHCM_ABAP_TO_EXCEL. Click on Create

3. Next you should type in some normal report creation parameters

4. Hit Save, choose your development package and you’re ready to start editing your report source code

5. Copy and paste the source code available for download here

6. Hit Activate and click on F8 or the Direct Processing button

7. Upon executing the report, you will need to define the name and location of the result Excel file. On the example defined in a folder \test-excel\test-excel.xls. Hit Save

8. Back on the selection screen, confirm your entries and execute the Report

9. The result will be something like

Additional links and resources

• Original post by Alvaro Tejada Galindo
• An Easy Reference For OLE Automation

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.

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.

SCAM – CATT Management
SCAT – Computer Aided Test Tool
SE09 – Workbench Organizer
SE10 – Customizing Organizer
SE11 – ABAP/4 Dictionary Maintenance
SE12 – ABAP/4 Dictionary Display
SE13 – Maintain Technical Settings (Tables)
SE14 – Utilities for Dictionary Tables
SE15 – ABAP/4 Repository Information System
SE16 – Data Browser
SE17 – General Table Display
SE30 – ABAP/4 Runtime Analysis
SE32 – ABAP/4 Text Element Maintenance
SE35 – ABAP/4 Dialog Modules
SE36 – ABAP/4: Logical Databases
SE37 – ABAP/4 Function Modules
SE38 – ABAP/4 Program Development
SE39 – Splitscreen Editor: Program Compare
SE41 – Menu Painter
SE43 – Maintain Area Menu
SE51 – Screen Painter
SE54 – Generate View Maintenance Module
SE61 – R/3 Documentation
SE62 – Industry utilities
SE63 – Translation
SE64 – Terminology
SE65 – R/3 document. short text statistics
SE66 – R/3 Documentation Statistics (Test!)
SE68 – Translation Administration
SE71 – SAPscript layout set
SE72 – SAPscript styles
SE73 – SAPscript font maintenance (revised)
SE74 – SAPscript format conversion
SE75 – SAPscript Settings
SE76 – SAPscript Translation Layout Sets
SE77 _- SAPscript Translation Styles
SE80 – ABAP/4 Development Workbench
SE81 – SAP Application Hierarchy
SE82 – Customer Application Hierarchy
SE84 – ABAP/4 Repository Information System
SE85 – ABAP/4 Dictionary Information System
SE86 – ABAP/4 Repository Information System
SE87 – Data Modeler Information System
SE88 – Development Coordination Info System
SE91 – Maintain Messages
SE92 – Maintain system log messages
SE93 – Maintain Transaction Codes
SEU – Object Browser
SHD0 – Transaction variant maintenance
SQ00 – ABAP/4 Query: Start Queries
SQ01 – ABAP/4 Query: Maintain Queries
SQ02 – ABAP/4 Query: Maintain Funct. Areas
SQ03 – ABAP/4 Query: Maintain User Groups
SQ07 – ABAP/4 Query: Language Comparison

ABAP used to be an abbreviation of Allgemeiner Berichtsaufbereitungsprozessor, the German meaning of “generic report preparation processor”, but was later renamed to Advanced Business Application Programming. ABAP was one of the first languages to include the concept of Logical Databases (LDBs), which provides a high level of abstraction from the basic database level.

The ABAP programming language was originally used by developers to develop the SAP R/3 platform. It was also intended to be used by SAP customers to enhance SAP applications – customers can develop custom reports and interfaces with ABAP programming. The language is fairly easy to learn for programmers but it is not a tool for direct use by non-programmers. Good programming skills, including knowledge of relational database design and preferably also of object-oriented concepts, are required to create ABAP programs.

ABAP remains the language for creating programs for the client-server R/3 system, which SAP first released in 1992. As computer hardware evolved through the 1990s, more and more of SAP’s applications and systems were written in ABAP. By 2001, all but the most basic functions were written in ABAP. In 1999, SAP released an object-oriented extension to ABAP called ABAP Objects, along with R/3 release 4.6.

SAP’s most recent development platform, NetWeaver, supports both ABAP and Java.

Where does the ABAP program run?

All ABAP programs reside inside the SAP database. They are not stored in separate external files like Java or C++ programs. In the database all ABAP code exists in two forms: source code, which can be viewed and edited with the ABAP Workbench tools, and generated code, a binary representation somewhat comparable with Java bytecode. ABAP programs execute under the control of the runtime system, which is part of the SAP kernel. The runtime system is responsible for processing ABAP statements, controlling the flow logic of screens and responding to events (such as a user clicking on a screen button). A key component of the ABAP runtime system is the Database Interface, which turns database-independent ABAP statements (“Open SQL”) into statements understood by the underlying DBMS (“Native SQL”). The database interface handles all the communication with the relational database on behalf of ABAP programs; it also contains extra features such as buffering of frequently accessed data in the local memory of the application server.

SAP has three different layers as presentation layer (GUI), application layer (programs run on this) and data base layer where all data is stored and retrieved from user driven conditions, commands given by end user programmer through presentation layer.

GUI Examples

• Figure – Transaction code SE38 – use it to build Reports and ALVs

• Figure – Transaction code SE37 – use it to build Function Modules

• Figure – Transaction code SE80 – use it to build Function Modules and manage Function Groups

SAP Basis

The ABAP language environment, including the syntax checking, code generation and runtime system, is part of the SAP Basis component. SAP Basis is the technological platform that supports the entire range of SAP applications, now typically implemented in the framework of the SAP Web Application Server. In that sense SAP Basis can be seen as the “operating system” on which SAP applications run. Like any operating system, SAP Basis contains both low-level services (for example memory management, database communication or servicing Web requests) and high-level tools for end users and administrators. These tools can be executables (“SAP kernel”) running directly on the underlying operating system, transactions developed in ABAP, or Web-based interfaces.

SAP Basis also provides a layer of abstraction between the business applications and the operating system and database. This ensures that applications do not depend directly upon a specific server or database platform and can easily be ported from one platform to another.

SAP Basis currently runs on UNIX (AIX, HP-UX, Solaris, Linux), Microsoft Windows, i5/OS on IBM System i (formerly iSeries, AS/400) and z/OS on IBM System z (formerly zSeries, S/390). Supported databases are DB2, Informix, MaxDB, Oracle and Microsoft SQL Server (support for Informix was discontinued in SAP Basis release 7.00).

SAP systems and landscapes

All SAP data exists and all SAP software runs in the context of an SAP system. A system consists of a central relational database and one or more application servers (“instances”) accessing the data and programs in this database. An SAP system contains at least one instance but may contain more, mostly for reasons of sizing and performance. In a system with multiple instances, load balancing mechanisms ensure that the load is spread evenly over the available application servers.

Installations of the Web Application Server (landscapes) typically consist of three systems: one for development, one for testing and quality assurance, and one for production. The landscape may contain more systems, e.g. separate systems for unit testing and pre-production testing, or it may contain fewer, e.g. only development and production, without separate QA; nevertheless three is the most common configuration. ABAP programs are created and undergo first testing in the development system. Afterwards they are distributed to the other systems in the landscape. These actions take place under control of the Change and Transport System (CTS), which is responsible for concurrency control (e.g. preventing two developers from changing the same code at the same time), version management and deployment of programs on the QA and production systems.

The Web Application Server consists of three layers: the database layer, the application layer and the presentation layer. These layers may run on the same or on different physical machines. The database layer contains the relational database and the database software. The application layer contains the instance or instances of the system. All application processes, including the business transactions and the ABAP development, run on the application layer. The presentation layer handles the interaction with users of the system. Online access to ABAP application servers can go via a proprietary graphical interface, the SAPGUI, or via a Web browser.

Additional links and resources

• ABAP in SDN Network
• ABAP e-Learning
• ABAP Objects
• ABAP in the Open Directory Project
• The ABAP Wiki Project
• ABAP Forums
• ABAP Tutorials

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 found