ABAP Thinkers

How to download the data structure of tables in SE11?

2013-11-09T02:45:00.002-08:00

Good morning people around the world. Its me again doing some blogs. Sharing to you some tips and tricks in the SAP world. Well, before I start my topic today, just want you to know that our country was hit by one of the strongest typhoons on earth this year named "Yolanda". Thank God and it did not hit directly Manila, the capital of the country where millions of people are living. Just recently, Bohol in the Visayan island was hit another 7.2 magnitude earthquake which causes more than 200 people died. Anyway, let us pray together to all our brethren who were in the midst of this natural calamity.

So to begin my discussion today, I will share to you a great tutorial which I know it will be beneficial to all. Many SAP systems have customized developments. In relation to it, there are custom tables also that were created by the ABAP developers. Now, the question of many developers is, how can they back up their tables into their laptops or computers? Just like in my previous blog which I tackled on how to download your ABAP code into PDF file, now what we want to download into our own computer is the structure of our custom table that we created?

Why do we need to download the structure of our custom tables? Basically, we need to have a copy of it as for our future reference. Actually, in other databases like MySQL, there is that functionality of IMPORT/EXPORT which you can download the whole database into your computer. But in SAP, this feature is not supported. What SAP offers is the transport system from one system to another but not into your own computer.

So in this tutorial, I will discuss to you a simple way to back-up your custom tables into your local drive. Just follow the steps below:

Steps:

1. First, open your custom table using SE11. What I used as an example here is EKKO which is a standard table.

2. In the file menu, click Utilities->Database Object->Display.

3. A new screen like this one below appears showing the structure of the table. Please take note that the data elements were replaced with elementary data types.

4. Normally, when we download, we go to System ->List->Save. But as you can see, all options are disabled.

5. In order to download it, put your mouse cursor anywhere in the table then right-click it. From the context menu, select View Source.

5. A notepad then appears displaying the source code of the table. This is an HTML format.

6. Click the Save in the file menu. This dialog appears. Then save your file anywhere now into your local drive. Remember, since this is an HTML file, save this way, your filename must end with .html, so example, table_ekko.html. And the last reminder is, change the "Save as type" into "All files" (Please refer to screenshot below).

7. Congratulations. you have now a copy into your local drive the custom table you created. Go to the directory where you save your file. Open it and it will look the same as the one in SAP.

Sample Result:

How to download your ABAP Codes into PDF file?

2013-11-04T05:27:00.000-08:00

It's my first day of work again after suffering a long week of vacation due to influenza. Ouch. Well, no one wants to get sick. Im just so lucky enough it was not a dengue or whatsoever complicated illness but its a plain flu which needs a bed rest. In effect, my ABAP developments were curtailed and postponed for its delivery. Thanks a lot to my Project Manager for her kind considerations.

So today, I finished doing my task assigned to me the previous week. Actually, it just a finishing touch producing the desired result. After a couple of hours doing it, its done and ready for testing. After I test and it passes with all the requirements and conditions set in the functional design, I decided to download the ABAP codes I did for future reference since it uses a dynamic internal table that has a static fields.

Normally, when I backup my ABAP codes, I just COPY-PASTE it in a notepad or in a word document. This technique is ok. But now I want to have a PDF file so I can save it into my mobile phone in order to view it anywhere at any given time.

Well, this is now the solution I discovered which I want to share to everyone.

Steps:
1. At the lower right part of the ABAP editor, you will see this button in yellow. That button is below the vertical scroll bars. Click this button to view the different options.

2. From the options, click keyboard. Then select File.ExportPDF from the command list. Please refer from the screenshot below.

3. On the input box, New Shortcuts, type CTRL + ATL + L. Then click the button Assign. By the way, the combination of the keys can be different from yours as long as it is available. It so happened that this key combinations are available so I used in this tutorial. After clicking the Assign button, you will see the keys reflected in the Shortcuts for selected commands textbox. Then click the Save button afterwards.

4. Once you save the settings you did above, you will be back into your ABAP editor. Now, in your editor, pressed the key combination you set. In my case, I will press

CTRL + ATL + L. Immediately, the Save dialog box will be prompted like this one. Type the filename of your file and locate the directory where you want to save. Finally, click the Save button to create the PDF file.

So that's how simple to create a PDF file for your ABAP codes. I hope you like this tutorial.

Sample PDF Output:

How to create a number range in SAP using SNRO?

2013-10-22T22:36:00.001-07:00

During ABAP development, sometimes we need to generate a unique ID which is needed as primary key for a custom table we created. Unlike in other databases such as mySQL that a field can be set as auto-increment once defined as primary key. In SAP environment, this feature is missing in table creation so we need to setup a number range that generates distinct number which increments and used as primary key.

A Number Range is a sequence of numbers with a start and an end. It shows the current number that is being used in your program. Letters cannot be added as a prefix or suffix in generating number ranges like, A-001, A-002, etc.

So in this tutorial, I divided into four parts which I will discuss one by one. It includes the following topics:

Setting the number range definition

Setting the number range object

Transporting the number range to other system

Implementing the number range in a program

Steps:

Setting the Number Range Definition
First, type the tcode SNRO into the command prompt.

Then, enter a name in the input field for your number range object. Note that it must begin with Y or Z just like in other objects that indicates it is a customer development. After which, click the Create button .

In this next screen, set the following parameters:

a. Short Text – short description for the number range (20 characters).

b. Long Text – long description for the number range (60 characters).
c. Number length domain – Name of the domain, which determines the length of the number range number
d. Warning % - Percentage of no remaining in a number range, upon reaching which in number assignment is given. Example, you have defined an interval of 1 to 1000. If you want to issue a warning at the number 900, enter 10% here.

Click on the Save button in the toolbar menu to save the number range definition. A popup screen will be displayed which you need to add a package. But for this tutorial, just click the Local Object below.

Setting the Number Ranges Interval

After creating the number range definition, the next step is to set the intervals for this object. Go back to the main window, click the button Number Ranges button on the toolbar.

Then in this screen, click the button Change Intervals.

Then click the Add Interval button on this screen.

Enter an integer for the column “No”, “From Number” and “To Number”. This is the number range interval set for this object. Then press enter and click the check button .

Click on "Save" button. And the number range interval you have just declared will be listed in the Number Range object 's number intervals list. You can declare multiple intervals but be sure there will be no overlapping between intervals.

Transporting the number range to other system

The following warning screen is displayed once you save the number ranges. It states that the interval is not automatically added on the transport request no. So we need to add the intervals manually on the transport request number in order to be transported to other system.

Go back again into the main screen. On the file menu, click menu Interval->transport as seen below.

This transport message appears afterwards. Just click the Yes button below to include the intervals in a transport request no.

After which, it will create a transport request number which adds the number range interval. Thereby, it can be transported now to other system.

Implementing the number range in a program
After defining the number range object, it’s time to discuss how to use number range object in ABAP code. The following function modules are used in implementing the number range object:

NUMBER_RANGE_ENQUEUE -function sets a lock on the number range object.
NUMBER_GET_NEXT - function call the next number in the number range interval is read and passed into an ABAP variable.
NUMBER_RANGE_DEQUEUE - function and removing the lock on the relate SAP number range object.

Complete Sample Code:

DATA: gv_id TYPE i.
CONSTANTS:
   c_obj TYPE inri-object     VALUE 'ZNEWTEST',
   c_no  TYPE inri-nrrangenr  VALUE '01'.

START-OF-SELECTION.
  PERFORM f_getnextnum USING gv_id c_obj c_no.
  WRITE gv_id.

*&---------------------------------------------------------------------
*& Form f_getnextnum
*&---------------------------------------------------------------------
* text
*----------------------------------------------------------------------
FORM f_getnextnum USING
      p_nextnum TYPE i
      p_rangeobj TYPE inri-object
      p_rangeno TYPE inri-nrrangenr.

  CALL FUNCTION 'NUMBER_RANGE_ENQUEUE'
    EXPORTING
      object           = p_rangeobj
    EXCEPTIONS
      foreign_lock     = 1
      object_not_found = 2
      system_failure   = 3
      OTHERS           = 4.
  IF sy-subrc NE 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
    WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
  ENDIF.

  CALL FUNCTION 'NUMBER_GET_NEXT'
    EXPORTING
      nr_range_nr             = p_rangeno
      object                  = p_rangeobj
    IMPORTING
      number                  = p_nextnum
    EXCEPTIONS
      interval_not_found      = 1
      number_range_not_intern = 2
      object_not_found        = 3
      quantity_is_0           = 4
      quantity_is_not_1       = 5
      interval_overflow       = 6
      buffer_overflow         = 7
      OTHERS                  = 8.
  IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
    WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
  ENDIF.

  CALL FUNCTION 'NUMBER_RANGE_DEQUEUE'
    EXPORTING
      object = p_rangeobj.
  IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
    WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
  ENDIF.
ENDFORM.

How to delete Implicit Enhancement Implementation?

2013-10-21T22:21:00.000-07:00

Yesterday, I am testing the implicit implementation that I did few weeks back. After all of a sudden, I noticed that the name of the implementation I created is not the one specified in the functional design. So if my functional counterpart will test it and find the name is not the one specified in the functional design, I might be in trouble then.

I paused for a moment and think what to do. After a couple of minutes, I decided to delete my existing implementation and create a new one which name will be in accordance to the name specified in the functional document. But my problem is, how to delete this existing implicit implementation and replaced its name? If you see below, the name of the implementation is that in RED line just after the keyword ENHANCEMENT 318.

Now, I go back to the application menu to look for some links on how to delete this implementation and create a new one. But as you can see from this EDIT menu, you cant see any delete option for the existing implementation. What you see is CREATE, UNDO, REPLACE and CHANGE. All of these options are related to the ABAP codes and NOT on the name of the implementation.

After searching the net I find the solution. In order to solve this problem, you should go to transaction code SE80. Select package and enter the name of your package. From the list of object name is enhancement implementations. Scroll down and you will see the list of all enhancements under the same package. From the list, choose the name of your implementations. Right click it using your mouse and from the context menu, select DELETE. Take note, it must be ACTIVE and it is NOT currently open.

This is a simplest way to delete implicit implementations. If you want to read also my blog on how to create a new implementations, please click it here.

Again, enjoy and keep on visiting my blogs. Until next post again... :)

How to implement an Implicit Enhancement in SAP objects?

2013-10-11T19:33:00.002-07:00

Hello dearest ABAPers all over the world. It's Saturday today and its my rest day. Its me again sharing to you what I learned over the past few days of work. It was so busy week doing some developments on reports and enhancements as we are implementing a big project in Singapore. Well I do believe then that everyone of you have experiences now with these objects.

Yesterday, I was assigned an object with our Project Manager. When I read the Functional design, it was an EXIT. Ohhh, it was an enhancement again. Upon checking the detail, I need to implement this exit - USEREXIT_NUMBER_RANGE. Since I am not sure with the project to implement, I made a google to find out what Include program handles this exit. Thats the amazing google can do for us... If you have questions, asks uncle Google not uncle Sam. :) hehehe....

In an instant, I got the result... It was MV45AFZZ handles this exit. Normally, an exit is an Include program called inside a Function Module. But in this case, this exit is a subroutine inside an Include program.

So my next question now is, how can I modify this object (MV45AFZZ) since this is a SAP standard object? As you can see on the screenshot below, when clicking the edit button on the editor, it asks an access key. An access key is generated on the SAP market place.

But how about if you dont have an access in the SAP market place? Then how can you edit this exit then?

So the most possible solution is Enhancement. It is a method develop by SAP to modify standard objects. So in this tutorial, I will discuss to you how to implement an enhancement. By the way, there are two types of enhancements. We have Implicit and Explicit enhancements. The simple difference I can say between the two are, Implicit enhancement is an enhancement that you declared (its not SAP who did). In short, this is a type of enhancement which has a Z* type object. Unlike with Explicit enhancement, it was SAP who defined this enhancement point. Do you get the difference between the two types of enhancement? I hope so. :) If not, just leave a message below and I will answer you the best I can.

So lets continue with this tutorial now. What I will discuss in details is how to implement an Implicit Enhancement. So just follow the steps and you will implement this type of enhancement into your next projects. Alright? So here are now the steps to do:

How to implement an Implicit Enhancement?

Steps:

1. In your editor, locate the "Enhance" button just like the one below. Click this button. Since what I am editing is an include program MV45AFZZ, I opened this in SE38 transaction code. By the way, you can implement any enhancements whether that is a Function Module, Class, Methods, BADI, BAPI, etc as long as you can see that "Enhance" button, implicit enhancement is possible.

2. Once clicked the enhance button, the editor changes something like this one below. The editor looks grayed and the two buttons above Active<->Inactive and Enhancements appear in the application toolbar. The first button, Active<->Inactive is used to changed mode from the normal editor to enhancement editor. Try to click one at a time and you will see the difference between the two editor mode. The second button, Enhancement is used to activate any enhancement implementations. You will used this in the later part of this tutorial.

3. The next step is to display those enhancement options. In order to do so, follow this path. On the menu, click Edit->Enhancement Operations -> Show Implicit Enhancement Options. This step is important because it shows where you can insert enhancement implementations. Otherwise, you cannot implement any implicit enhancement if you will not do this step.

4. As you can see below, two bold arrows were shown at the left side of the editor. This signifies the start and end points where you can add enhancement points. However, please note that this step is only showing where an enhancement can be positioned. We can not add yet our own ABAP codes at this time. If you noticed, the editor is still grayed. We still need to create an enhancement implementations just like a normal EXIT or BADI. I know you are now eager to write your ABAP programs. Before you can create an enhancement implementation, position your cursor at the starting line just like this screenshot below. This is a MUST to-do since you cannot create a new enhancement implementations if your cursor is not positioned correctly.

5. To create an enhancement implementation, go to the Menu again and follow this path.

Edit -> Enhancement Operations -> Create.

6. On this pop up screen, it will first asks you the type of enhancement between declaration and code. Choose code in here as we will write ABAP codes. Honestly, I am not sure yet the difference between the two. But once I got a chance and time again, I will discover what this two is all about and add in this blog. But if you know now what makes them differ, please leave a message below for everyone else. I will be grateful to you.

7. On this next pop up screen, you are required to select the enhancement implementation. Since this is a new implementation, we will create our own. Click the button at the right-bottom of the window. Its like a white folder paper.

8. This is the window where you will define the name of your enhancement implementation. Remember, it must begin with a Z* or Y* as this is a customized (Implicit) enhancement implementation. Also, give a short description for it. It must be descriptive. For the third parameter (composite enhancement implementation), just leave it blank. Then click the OK button after you are done.

9. Since we are creating a new implicit enhancement implementation, it will ask you to save in a transport no. Just select your package and add this into your transport no if you want to move it to another system. But if you are just making a test, then saving as local object would suffice.

10. After adding it into your transport, select from the list of implementation the one you created. Just like in my case, I highlighted it then click the Ok buttom below. Congratulations as you are almost done implementing an Implicit enhancement.

11. Finally and there you are, you can now add ABAP codes into our exit, USEREXIT_NUMBER_RANGE. As you can noticed, the grayed area while ago turns now into white which means we can write now our own ABAP Codes. Sorry but I did not write anything yet here since we will have a different logic to implement. You can also see the keywords ENHANCEMENT No. <name of enhancement implementation> and END ENHANCEMENT. Inside this keyword, you can write your own ABAP logic.

12. And lastly, dont forget to click this button on the application toolbar. This is the activate button for the enhancement. Remember that any objects that is not activated will not take effect. Once done, you will see your object being activated. So if you want to go back to the normal editor, click the button, Active<->Inactive button.

13. As a sidenote, If you want to go back again to your enhancement implementations, let say after one month there was a bug within your code, just do the same process. But rather clicking the create button, this time, click the change button to modify the existing implicit enhancement. Just follow this path to change:

Edit -> Enhancement Operations -> Change.

Congratulations. You can now implement an Implicit Enhancement into your projects. If you have further questions, please leave a message below. Until next week again.

Enjoy :)

ABAP Syntax Highlighter that works

2013-09-27T17:36:00.000-07:00

Good morning to all... After several months of being quite in this blog due to my developments with my PHP programming, I am back again to share with you what I learned and found out across the web. First is this, syntax highlighters for ABAP programming language. Well as you know, this blog is dedicated for ABAP programmers. So basically, ABAP source code is important to share. And one way to present it to the public is to use a syntax highlighter just like SE38 or simply the standard ABAP editor of SAP.

Long time ago, I am curious how does other blogs present ABAP codes in a manner that it is like that on the ABAP editor. So today, I gave myself a try to do it here in my blog. After a couple of hours searching the web, and testing several sites which focuses on syntax highlighting, I found out and tested here in Blogger the one that works here and I would like to share with you how to implement it into your blogs as well. Please take note that this tutorial is only for Blogger platform as this is the platform where I am writing my blogs.

By the way, I would like to share with you also the following sites which I tested and no success after implementation. First is this github from Christian Jianeli. Actually, thanks to this man for sharing this brush for ABAP. Two thumbs up to you man. The way I look with the source code, it is patterned with Alex Gorbatchev. After embedding this into my blogger template and adding the html PRE tag which brush = abap, my ABAP codes still looks the same. Nothing changes. Definitely I think that I need to download this github and upload it into my own hosting. In that manner, it will work. But since I am using the Blogger Platform, I dont need to download it but what I need is to link the syntax highlighter and use it into my blogs.

The second try that I used and tested is the one created by Alex Gorbatchev. Thanks to this man also for his wisdom in sharing his knowledge in creating this tool. You can download the whole package here. Actually, Alex made a awesome tool which I know many developers are using it now in their websites to highlights their own source code. The reason why this tool of Alex didn't work in my blog is, ABAP is not supported in his lists of brushes. If I am not wrong there are about more than 10 brushes which he is supporting but not among them is ABAP. I added actually all the brushes in my templates and made a try using XML brush and it works. However, since this blog is intended for ABAP developers, what I need is to have a brush that caters ABAP programming language where the ABAP syntax will be highlighted according to the ABAP editor looks. How I wish, Alex will read this blog and someday he will add ABAP as one of the brushes in his collections.

The last try that I use was Hilite.me. And here I got the result that I want to share with you. Well, steps to undertake is just simple. And here it is, just five steps:

1. Copy your ABAP source code and paste it in hilite.me

2. From the language option, select ABAP. You can also try to choose which style you want. Also, you can click the checkbox Line number if you want to add line numbering into your code. Afterwhich, hit the highlith! button. And there you are, an HTML code is generated which you will copy it to paste into your blogger account.

3. Now into your blogger account, go to your post. Create one post to try. Click the HTML button. It is besides the button Compose.

4. After clicking that HTML button, paste you HTML codes you copied from Hilite.me (step 2).

5. There you go. Its done. Save your post and publish it. The result of this ABAP Syntax highlighter would be something like this. I hope you enjoy this blog. Please share to your friends via the social bookmarks at the left side of this blog.

class screen_init definition create private.
 
  public section.
 
    class-methods init_screen.
 
    methods constructor.
 
  private section.
 
    data: splitter_h type ref to cl_gui_splitter_container,
 
          splitter_v type ref to cl_gui_splitter_container,
 
          picture type ref to cl_gui_picture,
 
          tree type ref to cl_gui_simple_tree.
 
    methods: fill_tree,
 
             fill_picture.
 
endclass.

ABAP Code: Append/ Delete Row in ALV

2013-05-28T06:46:00.001-07:00

This sample program illustrates how to add and remove lines to a table using the ALV Grid Control and how to implement the saving of the new data.

In order to implement such requirement, here are the steps to undertake:

1.Lock your database table accordingly;
2.Set status of columns to editable;
3.Set all cells of the table non-editable by using the style table;
4.Define internal tables to remember inserted and deleted lines,
thus the delta between input made after the last saving;
5.Check if there exist already other records with equal key fields;
6.Use protocol attributes MT_DELETED_ROWS and MT_INSERTED_ROWS
to remember which lines where deleted or inserted. Save this
information in your internal tables;
7.Check if any errors exist in protocol by using method
CHECK_CHANGED_DATA of your ALV Grid instance;
8.When all values are valid, use your internal tables to update your table on the database;
9.Refresh your internal tables;
10.Unlock your database table;

Sample Code:

* Classes ****************************************

class screen_init definition create private.
  public section.
    class-methods init_screen.
    methods constructor.

  private section.
    data: splitter_h type ref to cl_gui_splitter_container,
          splitter_v type ref to cl_gui_splitter_container,
          picture type ref to cl_gui_picture,
          tree type ref to cl_gui_simple_tree.
    methods: fill_tree,
             fill_picture.
endclass.


class screen_handler definition.
  public section.
    methods: constructor importing container
               type ref to cl_gui_container,
             handle_node_double_click
               for event node_double_click
               of cl_gui_simple_tree
               importing node_key.
  private section.

    data: html_viewer type ref to cl_gui_html_viewer,
          list_viewer type ref to cl_gui_alv_grid.

    methods: fill_html importing carrid type spfli-carrid,
             fill_list importing carrid type spfli-carrid
                                 connid type spfli-connid.
endclass.


class screen_init implementation.
  method init_screen.
    data screen type ref to screen_init.
    create object screen.
  endmethod.

  method constructor.
    data: events type cntl_simple_events,
          event like line of events,
          event_handler type ref to screen_handler,
          container_left type ref to cl_gui_container,
          container_right type ref to cl_gui_container,
          container_top type ref to cl_gui_container,
          container_bottom type ref to cl_gui_container.

    create object splitter_h
           exporting
           parent = cl_gui_container=>screen0
           rows = 1
           columns = 2.

    call method splitter_h->set_border
         exporting border = cl_gui_cfw=>false.

    call method splitter_h->set_column_mode
         exporting mode = splitter_h->mode_absolute.

    call method splitter_h->set_column_width
         exporting id = 1
         width = 107.

    container_left  = splitter_h->get_container( row = 1 column = 1 ).

    container_right = splitter_h->get_container( row = 1 column = 2 ).

    create object splitter_v
           exporting
           parent = container_left
           rows = 2
           columns = 1.

    call method splitter_v->set_border
         exporting border = cl_gui_cfw=>false.

    call method splitter_v->set_row_mode
         exporting mode = splitter_v->mode_absolute.

    call method splitter_v->set_row_height
         exporting id = 1
         height = 160.

    container_top    = splitter_v->get_container( row = 1 column = 1 ).

    container_bottom = splitter_v->get_container( row = 2 column = 1 ).

    create object picture
           exporting parent = container_top.

    create object tree
           exporting parent = container_bottom                     node_selection_mode =
                            cl_gui_simple_tree=>node_sel_mode_single.
    create object  event_handler
           exporting container = container_right.

    event-eventid = cl_gui_simple_tree=>eventid_node_double_click.

    event-appl_event = ' '.   "system event, does not trigger PAI
    append event to events.
    call method tree->set_registered_events
         exporting events = events.
    set handler event_handler->handle_node_double_click for tree.

    call method: me->fill_picture,
                 me->fill_tree.
  endmethod.

  method fill_picture.
    types pict_line(256) type x.
    data  pict_tab type table of pict_line.
    data  url(255) type c.

    import pict_tab = pict_tab from database abtree(pi) id 'FLIGHTS'.

    call function 'DP_CREATE_URL'

         exporting

              type    = 'IMAGE'

              subtype = 'GIF'

         tables

              data    = pict_tab

         changing

              url     = url.


    call method picture->load_picture_from_url exporting url = url.

    call method picture->set_display_mode

         exporting display_mode = picture->display_mode_fit_center.

  endmethod.


  method fill_tree.

    data: node_table type table of abdemonode,

          node type abdemonode,

          spfli_wa type spfli,

          spfli_tab type sorted table of spfli

                    with unique key carrid connid.


    select carrid connid

      from spfli

      into corresponding fields of table spfli_tab.


    node-hidden = ' '.                 " All nodes are visible,

    node-disabled = ' '.               " selectable,

    node-isfolder = 'X'.                                    " a folder,

    node-expander = ' '.               " have no '+' sign for expansion.

    loop at spfli_tab into spfli_wa.

      at new carrid.

        node-node_key = spfli_wa-carrid.

        clear node-relatkey.

        clear node-relatship.

        node-text = spfli_wa-carrid.

        node-n_image =   ' '.

        node-exp_image = ' '.

        append node to node_table.

      endat.

      at new connid.

        concatenate spfli_wa-carrid spfli_wa-connid into node-node_key.

        node-relatkey = spfli_wa-carrid.

        node-relatship = cl_gui_simple_tree=>relat_last_child.

        node-text = spfli_wa-connid.

        node-n_image =   '@AV@'.       "AV is the internal code

        node-exp_image = '@AV@'.       "for an airplane icon

      endat.

      append node to node_table.

    endloop.


    call method tree->add_nodes

         exporting table_structure_name = 'ABDEMONODE'

                   node_table = node_table.

  endmethod.


endclass.


*


class screen_handler implementation.


  method constructor.

    create object: html_viewer exporting parent = container,

                   list_viewer exporting i_parent = container.

  endmethod.


  method handle_node_double_click.

    data: carrid type spfli-carrid,

          connid type spfli-connid.


    carrid = node_key(2).

    connid = node_key+2(4).

    if connid is initial.

      call method: fill_html exporting carrid = carrid,

                   html_viewer->set_visible exporting visible = 'X',

                   list_viewer->set_visible exporting visible = ' '.

    else.

      call method: fill_list exporting carrid = carrid

                                       connid = connid,

                   list_viewer->set_visible exporting visible = 'X',

                   html_viewer->set_visible exporting visible = ' '.

    endif.


    call method cl_gui_cfw=>flush.

  endmethod.


  method fill_html.

    data url type scarr-url.


    select single url

    from   scarr

    into   url

    where  carrid = carrid.


    call method html_viewer->show_url exporting url = url.

  endmethod.


  method fill_list.

    data: flight_tab type table of demofli,

          begin of flight_title,

            carrname type scarr-carrname,

            cityfrom type spfli-cityfrom,

            cityto   type spfli-cityto,

          end of flight_title,

          list_layout type lvc_s_layo.


    select   single c~carrname p~cityfrom p~cityto

    into     corresponding fields of flight_title

    from     ( scarr as c

               inner join spfli   as p on c~carrid = p~carrid )

    where    p~carrid = carrid and

             p~connid = connid.


    select   fldate seatsmax seatsocc

    into     corresponding fields of table flight_tab

    from     sflight

    where    carrid = carrid and connid = connid

    order by fldate.


    concatenate flight_title-carrname

                connid

                flight_title-cityfrom

                flight_title-cityto

                into list_layout-grid_title separated by space.


    list_layout-smalltitle = 'X'.      "The list title has small fonts,

    list_layout-cwidth_opt = 'X'.      "the column width is adjusted,

    list_layout-no_toolbar = 'X'.      "the toolbar is suppressed.


    call method list_viewer->set_table_for_first_display

         exporting i_structure_name = 'DEMOFLI'

                   is_layout = list_layout

         changing  it_outtab         = flight_tab.

  endmethod.


endclass.



* Program execution ************************************************


load-of-program.

  call screen 100.


* Dialog Modules PBO


module status_0100 output.

  set pf-status 'SCREEN_100'.

  set titlebar 'TIT_100'.

  call method screen_init=>init_screen.

endmodule.


* Dialog Modules PAI


module cancel input.

  leave program.

endmodule.

ABAP Code: Editable ALV

2013-05-10T00:52:00.002-07:00

This report illustrates how to set chosen cells of an ALV Grid Control editable. Below are the essential steps undertaken:

1.Extend your output table for a field, e.g., CELLTAB, that holds information about the edit status of each cell for the corresponding row (the table type is SORTED!).
2. After selecting data, set edit status for each row in a loop according to field SEATSMAX.
a.Use attribute CL_GUI_ALV_GRID=>MC_STYLE_ENABLED to set a cell to status "editable".
b.Use attribute CL_GUI_ALV_GRID=>MC_STYLE_DISABLED to set a cell to status "non-editable".
c.Copy your celltab to the celltab of the current row of gt_outtab.
3.Provide the fieldname of the celltab field by using field STYLEFNAME of the layout structure.

Sample Code:

data: ok_code like sy-ucomm,
      save_ok like sy-ucomm,
      g_container type scrfname value 'BCALV_GRID_DEMO_0100_CONT1',
      grid1  type ref to cl_gui_alv_grid,
      g_custom_container type ref to cl_gui_custom_container,
      gs_layout type lvc_s_layo.
*      g_max type i value 500.

*§1.Extend your output table for a field, e.g., CELLTAB, that holds
*   information about the edit status of each cell for the
*   corresponding row (the table type is SORTED!).
data: begin of gt_outtab occurs 0, "with header line
        count type int2.
        include structure sflight.
data: celltab type lvc_t_styl.
data: end of gt_outtab.

data: gs_fieldcat type lvc_s_fcat,
      gt_fieldcat type lvc_t_fcat.

parameters: g_max type i default '600',
            g_rstyle type char1 as checkbox,
            g_rowins type char1 as checkbox. "default 'X'.  "key active

*---------------------------------------------------------------------*
*       MAIN                                                          *
*---------------------------------------------------------------------*
call screen 100.

*---------------------------------------------------------------------*
*       MODULE PBO OUTPUT                                             *
*---------------------------------------------------------------------*
module pbo output.
  set pf-status 'MAIN100'.
  set titlebar 'MAIN100'.
  if g_custom_container is initial.
    create object g_custom_container
      exporting
        container_name = g_container.
    create object grid1
      exporting
        i_parent = g_custom_container.

* select data, set styles
    perform select_data_and_init_style.

*§3.Provide the fieldname of the celltab field by using field
*   STYLEFNAME of the layout structure.
    gs_layout-stylefname = 'CELLTAB'.
    gs_layout-sel_mode   = 'D'.
* short key 'Delete row' active?
    if g_rowins is not initial.
      gs_layout-no_rowins = 'X'. "not allowed
    endif.

* fieldcat
    perform set_fieldcat using gt_fieldcat.

    call method grid1->set_table_for_first_display
      exporting "i_structure_name = 'SFLIGHT'
        is_layout       = gs_layout
      changing
        it_outtab       = gt_outtab[]
        it_fieldcatalog = gt_fieldcat.

  endif.
endmodule.
*---------------------------------------------------------------------*
*       MODULE PAI INPUT                                              *
*---------------------------------------------------------------------*
module pai input.
  save_ok = ok_code.
  clear ok_code.
  case save_ok.
    when 'EXIT'.
      perform exit_program.
    when 'SWITCH'.
      perform switch_edit_mode.
    when others.
*     do nothing
  endcase.
endmodule.
*---------------------------------------------------------------------*
*       FORM EXIT_PROGRAM                                             *
*---------------------------------------------------------------------*
form exit_program.
  set screen 0.
  leave screen.
endform.
*&---------------------------------------------------------------------*
*&      Form  SELECT_DATA_AND_INIT_STYLE
*&---------------------------------------------------------------------*
*       text
*----------------------------------------------------------------------*
*  -->  p1        text
*  <--  p2        text
*----------------------------------------------------------------------*
form select_data_and_init_style.
  data: lt_sflight type table of sflight with header line,
        lt_celltab type lvc_t_styl,
        l_index type i.

  select * from sflight into table lt_sflight up to g_max rows.
* move corresponding fields from lt_sflight to gt_outtab
  loop at lt_sflight.
    move-corresponding lt_sflight to gt_outtab.
    append gt_outtab.
  endloop.

*§2.After selecting data, set edit status for each row in a loop
*   according to field SEATSMAX.
  loop at gt_outtab.
    l_index = sy-tabix.
    gt_outtab-count = l_index.
    refresh lt_celltab.
    if gt_outtab-seatsmax ge 300.
      perform fill_celltab using 'RW'
                                 l_index
                           changing lt_celltab.
    else.
      perform fill_celltab using 'RO'
                                 l_index
                           changing lt_celltab.
    endif.
*§2c.Copy your celltab to the celltab of the current row of gt_outtab.
    insert lines of lt_celltab into table gt_outtab-celltab.
    modify gt_outtab index l_index.
  endloop.
endform.                               " SELECT_DATA_AND_INIT_STYLE
*&---------------------------------------------------------------------*
*&      Form  FILL_CELLTAB
*&---------------------------------------------------------------------*
*       text
*----------------------------------------------------------------------*
*      <--P_PT_CELLTAB  text
*----------------------------------------------------------------------*
form fill_celltab using value(p_mode) l_index
                  changing pt_celltab type lvc_t_styl.

  data: ls_celltab type lvc_s_styl,
        l_index1 type i,
        l_mode type raw4,
        l_rowstyle(1) type c.
* This forms sets the style of column 'PRICE' editable
* according to 'p_mode' and the rest to read only either way.

  if p_mode eq 'RW'.   ">300
*§2a.Use attribute CL_GUI_ALV_GRID=>MC_STYLE_ENABLED to set a cell
*    to status "editable".
    l_mode = cl_gui_alv_grid=>mc_style_enabled.
  else. "p_mode eq 'RO'   "<300
*§2b.Use attribute CL_GUI_ALV_GRID=>MC_STYLE_DISABLED to set a cell
*    to status "non-editable".
    l_mode = cl_gui_alv_grid=>mc_style_disabled.
  endif.

* is row style selected?
  l_rowstyle = g_rstyle.
  l_index1   = l_index.

* define rowstyle for single rows:
  if l_rowstyle is not initial.
    clear ls_celltab.

    if l_index1 <= '100'.
      ls_celltab-fieldname = ' '.
      ls_celltab-style = cl_gui_alv_grid=>mc_style_no_delete_row. " row not deleted
      insert ls_celltab into table pt_celltab.

* define editablility of single cells:
      ls_celltab-fieldname = 'CARRID'.
      ls_celltab-style = cl_gui_alv_grid=>mc_style_disabled.
      insert ls_celltab into table pt_celltab.
      ls_celltab-fieldname = 'CONNID'.
      ls_celltab-style = cl_gui_alv_grid=>mc_style_disabled.
      insert ls_celltab into table pt_celltab.
      ls_celltab-fieldname = 'FLDATE'.
      ls_celltab-style = cl_gui_alv_grid=>mc_style_disabled.
      insert ls_celltab into table pt_celltab.
      ls_celltab-fieldname = 'PRICE'.
      ls_celltab-style = l_mode.    "depending on value seatmax
      insert ls_celltab into table pt_celltab.
      ls_celltab-fieldname = 'CURRENCY'.
      ls_celltab-style = cl_gui_alv_grid=>mc_style_disabled.
      insert ls_celltab into table pt_celltab.
      ls_celltab-fieldname = 'PLANETYPE'.
      ls_celltab-style = cl_gui_alv_grid=>mc_style_disabled.
      insert ls_celltab into table pt_celltab.
      ls_celltab-fieldname = 'SEATSMAX'.
      ls_celltab-style = l_mode.
      insert ls_celltab into table pt_celltab.
      ls_celltab-fieldname = 'SEATSOCC'.
      ls_celltab-style = cl_gui_alv_grid=>mc_style_disabled.
      insert ls_celltab into table pt_celltab.
      ls_celltab-fieldname = 'PAYMENTSUM'.
      ls_celltab-style = cl_gui_alv_grid=>mc_style_disabled.
      insert ls_celltab into table pt_celltab.
    else.
*  rows can be deleted
      if l_index1 > 100 and l_index1 <= 200.
* do nothing for row style  and cell style
* set cell style:
        ls_celltab-fieldname = 'CARRID'.
        ls_celltab-style = cl_gui_alv_grid=>mc_style_disabled.
        insert ls_celltab into table pt_celltab.
        ls_celltab-fieldname = 'CONNID'.
        ls_celltab-style = cl_gui_alv_grid=>mc_style_disabled.
        insert ls_celltab into table pt_celltab.
        ls_celltab-fieldname = 'FLDATE'.
        ls_celltab-style = cl_gui_alv_grid=>mc_style_disabled.
        insert ls_celltab into table pt_celltab.
        ls_celltab-fieldname = 'PRICE'.
        ls_celltab-style = l_mode.    "depending on value seatmax
        insert ls_celltab into table pt_celltab.
        ls_celltab-fieldname = 'CURRENCY'.
        ls_celltab-style = cl_gui_alv_grid=>mc_style_disabled.
        insert ls_celltab into table pt_celltab.
        ls_celltab-fieldname = 'PLANETYPE'.
        ls_celltab-style = cl_gui_alv_grid=>mc_style_disabled.
        insert ls_celltab into table pt_celltab.
        ls_celltab-fieldname = 'SEATSMAX'.
        ls_celltab-style = l_mode.
        insert ls_celltab into table pt_celltab.
        ls_celltab-fieldname = 'SEATSOCC'.
        ls_celltab-style = cl_gui_alv_grid=>mc_style_disabled.
        insert ls_celltab into table pt_celltab.
        ls_celltab-fieldname = 'PAYMENTSUM'.
        ls_celltab-style = cl_gui_alv_grid=>mc_style_disabled.
        insert ls_celltab into table pt_celltab.
      else.
        if l_index1 > 200 and l_index1 <= 250.
* everything is editable: > 300, rows can not be deleted
           ls_celltab-fieldname = ' '.
           ls_celltab-style = cl_gui_alv_grid=>mc_style_no_delete_row. " row not deleted
           insert ls_celltab into table pt_celltab.

           ls_celltab-fieldname = 'CARRID'.
           ls_celltab-style = cl_gui_alv_grid=>mc_style_enabled.
           insert ls_celltab into table pt_celltab.
           ls_celltab-fieldname = 'CONNID'.
           ls_celltab-style = cl_gui_alv_grid=>mc_style_enabled.
           insert ls_celltab into table pt_celltab.
           ls_celltab-fieldname = 'FLDATE'.
           ls_celltab-style = cl_gui_alv_grid=>mc_style_enabled.
           insert ls_celltab into table pt_celltab.
           ls_celltab-fieldname = 'PRICE'.
           ls_celltab-style = cl_gui_alv_grid=>mc_style_enabled.
           insert ls_celltab into table pt_celltab.
           ls_celltab-fieldname = 'CURRENCY'.
           ls_celltab-style = cl_gui_alv_grid=>mc_style_enabled.
           insert ls_celltab into table pt_celltab.
           ls_celltab-fieldname = 'PLANETYPE'.
           ls_celltab-style = cl_gui_alv_grid=>mc_style_enabled.
           insert ls_celltab into table pt_celltab.
           ls_celltab-fieldname = 'SEATSMAX'.
           ls_celltab-style = cl_gui_alv_grid=>mc_style_enabled.
           insert ls_celltab into table pt_celltab.
           ls_celltab-fieldname = 'SEATSOCC'.
           ls_celltab-style = cl_gui_alv_grid=>mc_style_enabled.
           insert ls_celltab into table pt_celltab.
           ls_celltab-fieldname = 'PAYMENTSUM'.
           ls_celltab-style = cl_gui_alv_grid=>mc_style_enabled.
           insert ls_celltab into table pt_celltab.
         else.  "BT 250 and 600  rows can be deleted.
           ls_celltab-fieldname = 'CARRID'.
           ls_celltab-style = cl_gui_alv_grid=>mc_style_enabled.
           insert ls_celltab into table pt_celltab.
           ls_celltab-fieldname = 'CONNID'.
           ls_celltab-style = cl_gui_alv_grid=>mc_style_enabled.
           insert ls_celltab into table pt_celltab.
           ls_celltab-fieldname = 'FLDATE'.
           ls_celltab-style = cl_gui_alv_grid=>mc_style_enabled.
           insert ls_celltab into table pt_celltab.
           ls_celltab-fieldname = 'PRICE'.
           ls_celltab-style = cl_gui_alv_grid=>mc_style_enabled.
           insert ls_celltab into table pt_celltab.
           ls_celltab-fieldname = 'CURRENCY'.
           ls_celltab-style = cl_gui_alv_grid=>mc_style_enabled.
           insert ls_celltab into table pt_celltab.
           ls_celltab-fieldname = 'PLANETYPE'.
           ls_celltab-style = cl_gui_alv_grid=>mc_style_enabled.
           insert ls_celltab into table pt_celltab.
           ls_celltab-fieldname = 'SEATSMAX'.
           ls_celltab-style = cl_gui_alv_grid=>mc_style_enabled.
           insert ls_celltab into table pt_celltab.
           ls_celltab-fieldname = 'SEATSOCC'.
           ls_celltab-style = cl_gui_alv_grid=>mc_style_enabled.
           insert ls_celltab into table pt_celltab.
           ls_celltab-fieldname = 'PAYMENTSUM'.
           ls_celltab-style = cl_gui_alv_grid=>mc_style_enabled.
           insert ls_celltab into table pt_celltab.
          endif.

      endif.
    endif.
  else.
*without any row style: rows can be deleted
    ls_celltab-fieldname = 'CARRID'.
    ls_celltab-style = cl_gui_alv_grid=>mc_style_enabled.
    insert ls_celltab into table pt_celltab.
    ls_celltab-fieldname = 'CONNID'.
    ls_celltab-style = cl_gui_alv_grid=>mc_style_enabled.
    insert ls_celltab into table pt_celltab.
    ls_celltab-fieldname = 'FLDATE'.
    ls_celltab-style = cl_gui_alv_grid=>mc_style_enabled.
    insert ls_celltab into table pt_celltab.
    ls_celltab-fieldname = 'PRICE'.
    ls_celltab-style = cl_gui_alv_grid=>mc_style_enabled.   "depending on value seatmax
    insert ls_celltab into table pt_celltab.
    ls_celltab-fieldname = 'CURRENCY'.
    ls_celltab-style = cl_gui_alv_grid=>mc_style_enabled.
    insert ls_celltab into table pt_celltab.
    ls_celltab-fieldname = 'PLANETYPE'.
    ls_celltab-style = cl_gui_alv_grid=>mc_style_enabled.
    insert ls_celltab into table pt_celltab.
    ls_celltab-fieldname = 'SEATSMAX'.
    ls_celltab-style = cl_gui_alv_grid=>mc_style_enabled.
    insert ls_celltab into table pt_celltab.
    ls_celltab-fieldname = 'SEATSOCC'.
    ls_celltab-style = cl_gui_alv_grid=>mc_style_enabled.
    insert ls_celltab into table pt_celltab.
    ls_celltab-fieldname = 'PAYMENTSUM'.
    ls_celltab-style = cl_gui_alv_grid=>mc_style_enabled.
    insert ls_celltab into table pt_celltab.
  endif.

endform.                               " FILL_CELLTAB
*&---------------------------------------------------------------------*
*&      Form  SWITCH_EDIT_MODE
*&---------------------------------------------------------------------*
*       text
*----------------------------------------------------------------------*
*  -->  p1        text
*  <--  p2        text
*----------------------------------------------------------------------*
form switch_edit_mode.

  if grid1->is_ready_for_input( ) eq 0.

* set edit enabled cells ready for input
    call method grid1->set_ready_for_input
      exporting
        i_ready_for_input = 1.

  else.
* lock edit enabled cells against input
    call method grid1->set_ready_for_input
      exporting
        i_ready_for_input = 0.

  endif.
endform.                               " SWITCH_EDIT_MODE
*&---------------------------------------------------------------------*
*&      Form  SET_FIELDCAT
*&---------------------------------------------------------------------*
*       text
*----------------------------------------------------------------------*
*      -->P_GT_FIELDCAT  text
*----------------------------------------------------------------------*
form set_fieldcat  using    rt_fieldcat type lvc_t_fcat.

  data: ls_fieldcat type lvc_s_fcat,
        lt_fieldcat type lvc_t_fcat,
        n type i.                                           "#EC NEEDED

  call function 'LVC_FIELDCATALOG_MERGE'
   exporting
     i_structure_name             = 'SFLIGHT'
    changing
      ct_fieldcat                  = gt_fieldcat
*    EXCEPTIONS
*      INCONSISTENT_INTERFACE       = 1
*      PROGRAM_ERROR                = 2
*      OTHERS                       = 3
            .
  if sy-subrc <> 0.    "#EC *
* Implement suitable error handling here
  endif.

  lt_fieldcat = rt_fieldcat.

* add count field
  ls_fieldcat-fieldname = 'COUNT'.
  ls_fieldcat-inttype   = 'I'.
  ls_fieldcat-datatype  = 'INT2'.
  ls_fieldcat-scrtext_s = 'Count'.                          "#EC NOTEXT
  ls_fieldcat-scrtext_m = 'Count'.                          "#EC NOTEXT
  ls_fieldcat-scrtext_l = 'Counter'.                        "#EC NOTEXT
  ls_fieldcat-col_pos = '1'.
  ls_fieldcat-col_opt = 'X'.
  ls_fieldcat-intlen    = 2.
  ls_fieldcat-outputlen = 2.

  append ls_fieldcat to lt_fieldcat.

  rt_fieldcat = lt_fieldcat.

endform.                    " SET_FIELDCAT

Output:

ABAP Code: How to Implement ALV Tree?

2013-05-10T00:25:00.002-07:00

This report program is based on the standard SAP program BCALV_TREE_01. It shows the essential steps to build up a hierarchy using an ALV Tree Control (class CL_GUI_ALV_TREE).

In this program, the hierarchy tree consists of nodes for each month on top level (this level can not be build by a simple ALV Tree because there is no field for months in our output table SFLIGHT. Thus, you can not define this hierarchy by sorting nor initial calculations neither a special layout has been applied. Note also that this example does not build up and change the fieldcatalog of the output table. For this reason, all fields of the output table are shown in the columns although the fields CARRID and FLDATE are already placed in the tree on the left.

Steps:
1.Usual steps when using control technology.

Define reference variables.

Create ALV Tree Control and corresponding container.

2.Create Hierarchy-header
3.Create empty Tree Control
4.Create hierarchy (nodes and leaves)

Select data

Sort output table according to your conceived hierarchy

Add data to tree

5.Send data to frontend.
6.Call dispatch to process toolbar functions

Complete Source Code:

* ｧ1a. Define reference variables
data: g_alv_tree         type ref to cl_gui_alv_tree,
      g_custom_container type ref to cl_gui_custom_container.

data: gt_sflight      type sflight occurs 0,      "Output-Table
      ok_code like sy-ucomm,
      save_ok like sy-ucomm,           "OK-Code
      g_max type i value 255.

end-of-selection.

  call screen 100.

*&---------------------------------------------------------------------*
*&      Module  PBO  OUTPUT
*&---------------------------------------------------------------------*
*       process before output
*----------------------------------------------------------------------*
module pbo output.

  set pf-status 'MAIN100'.
  set titlebar 'MAINTITLE'.

  if g_alv_tree is initial.
    perform init_tree.

    call method cl_gui_cfw=>flush
      exceptions
        cntl_system_error = 1
        cntl_error        = 2.
    if sy-subrc ne 0.
      call function 'POPUP_TO_INFORM'
        exporting
          titel = 'Automation Queue failure'(801)
          txt1  = 'Internal error:'(802)
          txt2  = 'A method in the automation queue'(803)
          txt3  = 'caused a failure.'(804).
    endif.
  endif.

endmodule.                             " PBO  OUTPUT
*&---------------------------------------------------------------------*
*&      Module  PAI  INPUT
*&---------------------------------------------------------------------*
*       process after input
*----------------------------------------------------------------------*
module pai input.
  save_ok = ok_code.
  clear ok_code.

  case save_ok.
    when 'EXIT' or 'BACK' or 'CANC'.
      perform exit_program.

    when others.
* ｧ6. Call dispatch to process toolbar functions
      call method cl_gui_cfw=>dispatch.

  endcase.

  call method cl_gui_cfw=>flush.
endmodule.                             " PAI  INPUT

*&---------------------------------------------------------------------*
*&      Form  init_tree
*&---------------------------------------------------------------------*
*       text
*----------------------------------------------------------------------*
*  -->  p1        text
*  <--  p2        text
*----------------------------------------------------------------------*
form init_tree.
* ｧ1b. Create ALV Tree Control and corresponding Container.

* create container for alv-tree
  data: l_tree_container_name(30) type c.

  l_tree_container_name = 'CCONTAINER1'.

     create object g_custom_container
        exporting
              container_name = l_tree_container_name
        exceptions
              cntl_error                  = 1
              cntl_system_error           = 2
              create_error                = 3
              lifetime_error              = 4
              lifetime_dynpro_dynpro_link = 5.
    if sy-subrc <> 0.
      message x208(00) with 'ERROR'(100).
    endif.

* create tree control
  create object g_alv_tree
    exporting
        parent              = g_custom_container
        node_selection_mode = cl_gui_column_tree=>node_sel_mode_single
        item_selection      = 'X'
        no_html_header      = 'X'
        no_toolbar          = ''
    exceptions
        cntl_error                   = 1
        cntl_system_error            = 2
        create_error                 = 3
        lifetime_error               = 4
        illegal_node_selection_mode  = 5
        failed                       = 6
        illegal_column_name          = 7.
  if sy-subrc <> 0.
    message x208(00) with 'ERROR'.                          "#EC NOTEXT
  endif.

* ｧ2. Create Hierarchy-header
* The simple ALV Tree uses the text of the fields which were used
* for sorting to define this header. When you use
* the 'normal' ALV Tree the hierarchy is build up freely
* by the programmer this is not possible, so he has to define it
* himself.
  data l_hierarchy_header type treev_hhdr.
  perform build_hierarchy_header changing l_hierarchy_header.

* ｧ3. Create empty Tree Control
* IMPORTANT: Table 'gt_sflight' must be empty. Do not change this table
* (even after this method call). You can change data of your table
* by calling methods of CL_GUI_ALV_TREE.
* Furthermore, the output table 'gt_outtab' must be global and can
* only be used for one ALV Tree Control.
  call method g_alv_tree->set_table_for_first_display
    exporting
      i_structure_name    = 'SFLIGHT'
      is_hierarchy_header = l_hierarchy_header
    changing
      it_outtab           = gt_sflight. "table must be empty !

* ｧ4. Create hierarchy (nodes and leaves)
  perform create_hierarchy.

* ｧ5. Send data to frontend.
  call method g_alv_tree->frontend_update.

* wait for automatic flush at end of pbo
endform.                               " init_tree
*&---------------------------------------------------------------------*
*&      Form  build_hierarchy_header
*&---------------------------------------------------------------------*
*       build hierarchy-header-information
*----------------------------------------------------------------------*
*      -->P_L_HIERARCHY_HEADER  strucxture for hierarchy-header
*----------------------------------------------------------------------*
form build_hierarchy_header changing
                               p_hierarchy_header type treev_hhdr.

  p_hierarchy_header-heading = 'Month/Carrier/Date'(300).
  p_hierarchy_header-tooltip = 'Flights in a month'(400).
  p_hierarchy_header-width = 30.
  p_hierarchy_header-width_pix = ' '.

endform.                               " build_hierarchy_header
*&---------------------------------------------------------------------*
*&      Form  exit_program
*&---------------------------------------------------------------------*
*       free object and leave program
*----------------------------------------------------------------------*
form exit_program.

  call method g_custom_container->free.
  leave program.

endform.                               " exit_program
*&---------------------------------------------------------------------*
*&      Form  create_hierarchy
*&---------------------------------------------------------------------*
*       text
*----------------------------------------------------------------------*
*  -->  p1        text
*  <--  p2        text
*----------------------------------------------------------------------*
form create_hierarchy.

  data: ls_sflight type sflight,
        lt_sflight type sflight occurs 0,
        l_yyyymm(6) type c,            "year and month of sflight-fldate
        l_yyyymm_last(6) type c,
        l_carrid like sflight-carrid,
        l_carrid_last like sflight-carrid.

  data: l_month_key type lvc_nkey,
        l_carrid_key type lvc_nkey,
        l_last_key type lvc_nkey.

* ｧ4a. Select data
  select * from sflight into table lt_sflight up to g_max rows.

* ｧ4b. Sort output table according to your conceived hierarchy
* We sort in this order:
*    year and month (top level nodes, yyyymm of DATS)
*      carrier id (next level)
*         day of month (leaves, dd of DATS)
  sort lt_sflight by fldate+0(6) carrid fldate+6(2).
* Note: The top level nodes do not correspond to a field of the
* output table. Instead we use data of the table to invent another
* hierarchy level above the levels that can be build by sorting.

* ｧ4c. Add data to tree

  loop at lt_sflight into ls_sflight.
* Prerequesite: The table is sorted.
* You add a node everytime the values of a sorted field changes.
* Finally, the complete line is added as a leaf below the last
* node.
    l_yyyymm = ls_sflight-fldate+0(6).
    l_carrid = ls_sflight-carrid.

* Top level nodes:
    if l_yyyymm <> l_yyyymm_last.      "on change of l_yyyymm
      l_yyyymm_last = l_yyyymm.

*Providing no key means that the node is added on top level:
      perform add_month using    l_yyyymm
                                      ''
                             changing l_month_key.
* The month changed, thus, there is no predecessor carrier
      clear l_carrid_last.
    endif.

* Carrier nodes:
* (always inserted as child of the last month
*  which is identified by 'l_month_key')
    if l_carrid <> l_carrid_last.      "on change of l_carrid
      l_carrid_last = l_carrid.
      perform add_carrid_line using    ls_sflight
                                       l_month_key
                              changing l_carrid_key.
    endif.

* Leaf:
* (always inserted as child of the last carrier
*  which is identified by 'l_carrid_key')
    perform add_complete_line using  ls_sflight
                                     l_carrid_key
                            changing l_last_key.
  endloop.

endform.                               " create_hierarchy

*&---------------------------------------------------------------------*
*&      Form  add_month
*&---------------------------------------------------------------------*
form add_month  using     p_yyyymm type c
                          p_relat_key type lvc_nkey
                changing  p_node_key type lvc_nkey.

  data: l_node_text type lvc_value,
        ls_sflight type sflight,
        l_month(15) type c.            "output string for month

* get month name for node text
  perform get_month using p_yyyymm
                    changing l_month.
  l_node_text = l_month.

* add node:
* ALV Tree firstly inserts this node as a leaf if you do not provide
* IS_NODE_LAYOUT with field ISFOLDER set. In form 'add_carrid_line'
* the leaf gets a child and thus ALV converts it to a folder
* automatically.
*
  call method g_alv_tree->add_node
    exporting
      i_relat_node_key = p_relat_key
      i_relationship   = cl_gui_column_tree=>relat_last_child
      i_node_text      = l_node_text
      is_outtab_line   = ls_sflight
    importing
      e_new_node_key   = p_node_key.

endform.                               " add_month
*--------------------------------------------------------------------
form add_carrid_line using     ps_sflight type sflight
                               p_relat_key type lvc_nkey
                     changing  p_node_key type lvc_nkey.

  data: l_node_text type lvc_value,
        ls_sflight type sflight.

* add node
* ALV Tree firstly inserts this node as a leaf if you do not provide
* IS_NODE_LAYOUT with field ISFOLDER set. In form 'add_carrid_line'
* the leaf gets a child and thus ALV converts it to a folder
* automatically.
*
  l_node_text =  ps_sflight-carrid.
  call method g_alv_tree->add_node
    exporting
      i_relat_node_key = p_relat_key
      i_relationship   = cl_gui_column_tree=>relat_last_child
      i_node_text      = l_node_text
      is_outtab_line   = ls_sflight
    importing
      e_new_node_key   = p_node_key.

endform.                               " add_carrid_line
*&---------------------------------------------------------------------*
*&      Form  add_complete_line
*&---------------------------------------------------------------------*
form add_complete_line using   ps_sflight type sflight
                               p_relat_key type lvc_nkey
                     changing  p_node_key type lvc_nkey.

  data: l_node_text type lvc_value.

  write ps_sflight-fldate to l_node_text mm/dd/yyyy.

* add leaf:
* ALV Tree firstly inserts this node as a leaf if you do not provide
* IS_NODE_LAYOUT with field ISFOLDER set.
* Since these nodes will never get children they stay leaves
* (as intended).
*
  call method g_alv_tree->add_node
    exporting
      i_relat_node_key = p_relat_key
      i_relationship   = cl_gui_column_tree=>relat_last_child
      is_outtab_line   = ps_sflight
      i_node_text      = l_node_text
    importing
      e_new_node_key   = p_node_key.

endform.                               " add_complete_line
*&---------------------------------------------------------------------*
*&      Form  GET_MONTH
*&---------------------------------------------------------------------*
*       text
*----------------------------------------------------------------------*
*      -->P_P_YYYYMM  text
*      <--P_L_MONTH  text
*----------------------------------------------------------------------*
form get_month using    p_yyyymm
               changing p_month.
* Returns the name of month according to the digits in p_yyyymm

  data: l_monthdigits(2) type c.

  l_monthdigits = p_yyyymm+4(2).
  case l_monthdigits.
    when '01'.
      p_month = 'January'(701).
    when '02'.
      p_month = 'February'(702).
    when '03'.
      p_month = 'March'(703).
    when '04'.
      p_month = 'April'(704).
    when '05'.
      p_month = 'May'(705).
    when '06'.
      p_month = 'June'(706).
    when '07'.
      p_month = 'July'(707).
    when '08'.
      p_month = 'August'(708).
    when '09'.
      p_month = 'September'(709).
    when '10'.
      p_month = 'October'(710).
    when '11'.
      p_month = 'November'(711).
    when '12'.
      p_month = 'December'(712).
  endcase.
  concatenate p_yyyymm+0(4) '->' p_month into p_month.

endform.                               " GET_MONTH
*-----------------------------------------------------------------------

Sample Output:

ABAP Code: Split Screen

2013-05-10T00:11:00.002-07:00

Hi there fellow ABAPers... Do you have any requirement in your development which you need to split the screen? Let say, you need the left part as the menu and the right portion as the result being displayed? Well, thats not a problem now. Here is a code below which you can get the idea how to do it. Enjoy...

Sample Code:

* Classes *****************************************************

class screen_init definition create private.
  public section.
    class-methods init_screen.
    methods constructor.
  private section.
    data: splitter_h type ref to cl_gui_splitter_container,
          splitter_v type ref to cl_gui_splitter_container,
          picture type ref to cl_gui_picture,
          tree type ref to cl_gui_simple_tree.
    methods: fill_tree,
             fill_picture.
endclass.

*

class screen_handler definition.
  public section.
    methods: constructor importing container
               type ref to cl_gui_container,
             handle_node_double_click
               for event node_double_click
               of cl_gui_simple_tree
               importing node_key.
  private section.
    data: html_viewer type ref to cl_gui_html_viewer,
          list_viewer type ref to cl_gui_alv_grid.
    methods: fill_html importing carrid type spfli-carrid,
             fill_list importing carrid type spfli-carrid
                                 connid type spfli-connid.
endclass.

*

class screen_init implementation.

  method init_screen.
    data screen type ref to screen_init.
    create object screen.
  endmethod.

  method constructor.
    data: events type cntl_simple_events,
          event like line of events,
          event_handler type ref to screen_handler,
          container_left type ref to cl_gui_container,
          container_right type ref to cl_gui_container,
          container_top type ref to cl_gui_container,
          container_bottom type ref to cl_gui_container.

    create object splitter_h
           exporting
           parent = cl_gui_container=>screen0
           rows = 1
           columns = 2.

    call method splitter_h->set_border
         exporting border = cl_gui_cfw=>false.

    call method splitter_h->set_column_mode
         exporting mode = splitter_h->mode_absolute.

    call method splitter_h->set_column_width
         exporting id = 1
         width = 107.

    container_left  = splitter_h->get_container( row = 1 column = 1 ).
    container_right = splitter_h->get_container( row = 1 column = 2 ).

    create object splitter_v
           exporting
           parent = container_left
           rows = 2
           columns = 1.

    call method splitter_v->set_border
         exporting border = cl_gui_cfw=>false.

    call method splitter_v->set_row_mode
         exporting mode = splitter_v->mode_absolute.

    call method splitter_v->set_row_height
         exporting id = 1
         height = 160.

    container_top    = splitter_v->get_container( row = 1 column = 1 ).
    container_bottom = splitter_v->get_container( row = 2 column = 1 ).

    create object picture
           exporting parent = container_top.

    create object tree
           exporting parent = container_bottom
                     node_selection_mode =
                            cl_gui_simple_tree=>node_sel_mode_single.
    create object  event_handler
           exporting container = container_right.

    event-eventid = cl_gui_simple_tree=>eventid_node_double_click.
    event-appl_event = ' '.   "system event, does not trigger PAI
    append event to events.
    call method tree->set_registered_events
         exporting events = events.
    set handler event_handler->handle_node_double_click for tree.

    call method: me->fill_picture,
                 me->fill_tree.
  endmethod.

  method fill_picture.
    types pict_line(256) type x.
    data  pict_tab type table of pict_line.
    data  url(255) type c.

    import pict_tab = pict_tab from database abtree(pi) id 'FLIGHTS'.
    call function 'DP_CREATE_URL'
         exporting
              type    = 'IMAGE'
              subtype = 'GIF'
         tables
              data    = pict_tab
         changing
              url     = url.

    call method picture->load_picture_from_url exporting url = url.
    call method picture->set_display_mode
         exporting display_mode = picture->display_mode_fit_center.
  endmethod.

  method fill_tree.
    data: node_table type table of abdemonode,
          node type abdemonode,
          spfli_wa type spfli,
          spfli_tab type sorted table of spfli
                    with unique key carrid connid.

    select carrid connid
      from spfli
      into corresponding fields of table spfli_tab.

    node-hidden = ' '.                 " All nodes are visible,
    node-disabled = ' '.               " selectable,
    node-isfolder = 'X'.                                    " a folder,
    node-expander = ' '.               " have no '+' sign for expansion.
    loop at spfli_tab into spfli_wa.
      at new carrid.
        node-node_key = spfli_wa-carrid.
        clear node-relatkey.
        clear node-relatship.
        node-text = spfli_wa-carrid.
        node-n_image =   ' '.
        node-exp_image = ' '.
        append node to node_table.
      endat.
      at new connid.
        concatenate spfli_wa-carrid spfli_wa-connid into node-node_key.
        node-relatkey = spfli_wa-carrid.
        node-relatship = cl_gui_simple_tree=>relat_last_child.
        node-text = spfli_wa-connid.
        node-n_image =   '@AV@'.       "AV is the internal code
        node-exp_image = '@AV@'.       "for an airplane icon
      endat.
      append node to node_table.
    endloop.

    call method tree->add_nodes
         exporting table_structure_name = 'ABDEMONODE'
                   node_table = node_table.
  endmethod.

endclass.

*

class screen_handler implementation.

  method constructor.
    create object: html_viewer exporting parent = container,
                   list_viewer exporting i_parent = container.
  endmethod.

  method handle_node_double_click.
    data: carrid type spfli-carrid,
          connid type spfli-connid.

    carrid = node_key(2).
    connid = node_key+2(4).
    if connid is initial.
      call method: fill_html exporting carrid = carrid,
                   html_viewer->set_visible exporting visible = 'X',
                   list_viewer->set_visible exporting visible = ' '.
    else.
      call method: fill_list exporting carrid = carrid
                                       connid = connid,
                   list_viewer->set_visible exporting visible = 'X',
                   html_viewer->set_visible exporting visible = ' '.
    endif.

    call method cl_gui_cfw=>flush.
  endmethod.

  method fill_html.
    data url type scarr-url.

    select single url
    from   scarr
    into   url
    where  carrid = carrid.

    call method html_viewer->show_url exporting url = url.
  endmethod.

  method fill_list.
    data: flight_tab type table of demofli,
          begin of flight_title,
            carrname type scarr-carrname,
            cityfrom type spfli-cityfrom,
            cityto   type spfli-cityto,
          end of flight_title,
          list_layout type lvc_s_layo.

    select   single c~carrname p~cityfrom p~cityto
    into     corresponding fields of flight_title
    from     ( scarr as c
               inner join spfli   as p on c~carrid = p~carrid )
    where    p~carrid = carrid and
             p~connid = connid.

    select   fldate seatsmax seatsocc
    into     corresponding fields of table flight_tab
    from     sflight
    where    carrid = carrid and connid = connid
    order by fldate.

    concatenate flight_title-carrname
                connid
                flight_title-cityfrom
                flight_title-cityto
                into list_layout-grid_title separated by space.

    list_layout-smalltitle = 'X'.      "The list title has small fonts,
    list_layout-cwidth_opt = 'X'.      "the column width is adjusted,
    list_layout-no_toolbar = 'X'.      "the toolbar is suppressed.

    call method list_viewer->set_table_for_first_display
         exporting i_structure_name = 'DEMOFLI'
                   is_layout = list_layout
         changing  it_outtab         = flight_tab.
  endmethod.

endclass.

* Program execution ************************************************

load-of-program.
  call screen 100.

* Dialog Modules PBO

module status_0100 output.
  set pf-status 'SCREEN_100'.
  set titlebar 'TIT_100'.
  call method screen_init=>init_screen.
endmodule.

* Dialog Modules PAI

module cancel input.
  leave program.
endmodule.

Output:

How to activate &SAP_EDIT in SE16N?

2013-04-25T00:01:00.001-07:00

SE16N is a powerful transaction code in SAP. What makes it powerful is the use of this command &SAP_EDIT which can modify table records, add entries to tables and the worst, it can delete table records without further notice.

In some ways, this feature is beneficial also as there's no need to create Views to maintain a particular table. However, sometimes it is also crucial to use this feature as data can be modified or deleted without caution. Once this happens, it may bring down the whole system. That's why SAP security team then created an OSS notes (1446530 and 1525586) that disabled this features.

So when you try to type the command &SAP_EDIT into your command bar, it will no longer activate the editing feature. But if you still want to activate it (cause you have a hard head... just kidding), here's the procedure to enable this feature. As I said, please do this with PRE-CAUTIONS.

Steps:
1) Go to tcode SE16N and type the table name you want to modify. In this example, I used the table BSID. It can be seen that the checkbox "Maintain entries" is still uncheck.

2) Now, instead of typing &SAP_EDIT in the command window, type /H to activate the debugger. Then press the enter key.

3) While in debug mode, type the name of the following global variables GD-EDIT. Click the pencil button to change the value of it.

As seen below, enter "X" as the value of the global variable. Then click the eyeglass button.

4) Finally, press F8 key to exit from debugging mode. Now you will see that the option "maintain entries" is now check. This means, you can now edit that table. :)

NOTE: this tutorial needs precautions. This is only for tutorial purposes. Do not do this into your QA or PROD System as it may incur damaged.

Function Module to get file extension name

2013-03-12T14:47:00.001-07:00

In this tutorial, I will discuss with you some standard SAP Function Modules that can be used to get the extension name of a given file such as PDF, DOC, XLS etc.

The first one that I want to show is the FM SCTS_EXE_FILE. It has two input parameters and one output which is the extension name. As seen from this screenshot below. I tested a file having two periods(.) to check if the FM can still recognize the extension name of a given file. As expected, it outputs the correct extension name. So our mark for this FM, PASSED.

The second FM is CRM_IC_WZ_UTILITIES. Just like the first FM above, I tested the same having two periods on the filename. This is to ensure that it takes the correct extension name once processing is done. Voila, as seen below, PDF was taken from the input name filename.file.pdf. So our mark for this FM, PASSED.

In this third FM, PC_SPLIT_COMPLETE_FILENAME, it has two input parameters and five outputs. This time, my test data failed. Using the same file like the one above, nothing was returned as output as seen below. I did not debug anymore this FM to know where it commits the error. But one thing I am sure, it can not be used in this case having two periods in a filename. So our mark for this FM, FAILED.

On this last FM, i used the same data, filename.file.pdf. Amazingly, it returns an output unlike the third FM which returns nothing. But as can be seen below, the extension name that it returns is a part of the filename itself and not the extension name. It takes the first period of a filename whereas it must take the rightmost one. So our mark for this FM, FAILED.

I hope I shared to you some insights which FM can be used if your requirement is to take the extension name of a given filename. Enjoy reading my blog. :)

How to add pushbutton in a Selection screen?

2013-02-10T12:46:00.000-08:00

In this tutorial, I will discuss two methods on how to add push button to a standard report selection screen. A push button is used to trigger an action executed by a user such as altering the selection screen dynamically, calling another program or report. The first way is using the statement FUNCTION KEY which syntax appears below.

SELECTION-SCREEN: FUNCTION KEY 1.
SELECTION-SCREEN: FUNCTION KEY 2..up to..7

Using this method let you add up to seven (7) function keys. The command code for these  function keys corresponds to their number such that for function key 1, it is set to  'FC01'. And for function key 2 it is set to 'FC02' and so on and so forth. These function keys are displayed in the application toolbar just besides the execute button. Add your logic on the event AT SELECTION-SCREEN. The second method is using the statement SELECTION-SCREEN PUSHBUTTON. Its syntax appears below:

SELECTION-SCREEN PUSHBUTTON [/][pos](len)button_text USER-COMMAND fcode [VISIBLE LENGTH vlen][MODIF ID modid]

This statement creates a pushbutton on the current selection screen. The text on the pushbutton is determined by the content of button_text. The rules that apply to text also apply to button_text when creating an output field. In order to position the button on the selection screen, use the parameter /[pos][len]. The syntax and meaning of [/][pos](len) are the same as when creating horizontal lines although in this case, len defines the length of the pushbutton on the selection screen. If a pushbutton extends beyond position 83 or beyond the edge of a block with a frame, it is cut off at the right hand side.


If you specify the USER-COMMAND addition, the pushbutton must be assigned a function code fcode. The function code fcode must be specified directly and can only contain a maximum of 20 characters. If the user selects the pushbutton on the selection screen, the runtime environment triggers the event AT SELECTION-SCREEN and the function code fcode is transferred to the ucomm component in the interface work area sscrfields.

Below are sample codes between the two:
1. Using the FUNCTION KEY statement

TYPE-POOLS icon.
TABLES sscrfields.
DATA functxt TYPE smp_dyntxt.

PARAMETERS: p_carrid TYPE s_carr_id,
p_cityfr TYPE s_from_cit.

SELECTION-SCREEN: FUNCTION KEY 1,
FUNCTION KEY 2.

INITIALIZATION.
functxt-icon_id = icon_ws_plane.
functxt-quickinfo = 'Preselected Carrier'.
functxt-icon_text = 'LH'.
sscrfields-functxt_01 = functxt.
functxt-icon_text = 'UA'.
sscrfields-functxt_02 = functxt.

AT SELECTION-SCREEN.
CASE sscrfields-ucomm.
WHEN 'FC01'.
p_carrid = 'LH'.
p_cityfr = 'Frankfurt'.
WHEN 'FC02'.
p_carrid = 'UA'.
p_cityfr = 'Chicago'.
WHEN OTHERS.

...

ENDCASE.

START-OF-SELECTION.
...

2. Using the PUSHBUTTON statement
TABLES sscrfields.
TYPE-POOLS icon.

SELECTION-SCREEN:
BEGIN OF SCREEN 500 AS WINDOW TITLE title,
PUSHBUTTON 2(10) but1 USER-COMMAND cli1,
PUSHBUTTON 12(30) but2 USER-COMMAND cli2
VISIBLE LENGTH 10,
END OF SCREEN 500.

AT SELECTION-SCREEN.
CASE sscrfields.
WHEN 'CLI1'.
...
WHEN 'CLI2'.
...
ENDCASE.

START-OF-SELECTION.
title = 'Push button'.
but1 = 'Button 1'.

CALL FUNCTION 'ICON_CREATE'
EXPORTING
name = icon_information
text = 'Button 2'
info = 'My Quickinfo'
IMPORTING
RESULT = but2
EXCEPTIONS
OTHERS = 0.

CALL SELECTION-SCREEN '0500' STARTING AT 10 10.

100 ABAP Interview Questions (Part 5)

2013-02-01T20:39:00.001-08:00

Here's the Part 4 of this compiled ABAP questions. Enjoy answering. You can view the first four parts in this link:

ABAP Interview Part 1

ABAP Interview Part 2

ABAP Interview Part 3

ABAP Interview Part 4

81. When creating a transparent table in the ABAP Dictionary, which step automatically creates the table in the underlying database?
A: Adding technical settings to the table
B: Checking the table syntax
C: Saving the table
D: Activating the table

82. Within the ABAP program attributes, Type = 1 represents:
A: INCLUDE program
B: Online program
C: Module pool
D: Function group
E: Subroutine pool

83. If this code results in an error, the remedy is:
SELECT fld1 SUM( fld1 ) FROM tab1 INTO_

A: Remove the spaces from SUM( fld1 ).
B: Move SUM( fld1 ) before fld1.
C: Add GROUP BY f1.
D: Change to SUM( DISTINCT f1 ).

84. Which keyword adds rows to an internal table while accumulating numeric values?
A: INSERT
B: APPEND
C: COLLECT
D: GROUP

85. Assuming itab has a header line, what will be output by the following code?
READ TABLE itab INDEX 3 TRANSPORTING field1.
WRITE: /1 itab-field1, itab-field2.

A: The contents of the third row's itab-field1.
B: The contents of the third row's itab-field1 and itab-field2.
C: The contents of the third row's itab-field2.
D: Nothing.

86. The following code indicates:
SELECTION-SCREEN BEGIN OF BLOCK B1.
PARAMETERS: myparam(10) type C,
Myparam2(10) type N,
SELECTION-SCREEN END OF BLOCK.

A: Draw a box around myparam and myparam2 on the selection screen.
B: Allow myparam and myparam2 to be ready for input during an error dialog.
C: Do not display myparam and myparam2 on the selection screen.
D: Display myparam and myparam2 only if both fields have default values.

87. Which statement will sort the data of an internal table with fields FRUIT, QTY, and PRICE so that it appears as follows? FRUIT QTY PRICE

Apples 12 22.50
Apples 9 18.25
Oranges 15 17.35
Bananas 20 10.20
Bananas 15 6.89
Bananas 5 2.75

A: SORT itab DESCENDING BY QTY PRICE.
B: SORT itab BY PRICE FRUIT.
C: SORT itab.
D: SORT itab BY PRICE DESCENDING.

88. Which keyword adds a line anywhere within an internal table?
A: APPEND
B: MODIFY
C: ADD
D: INSERT

89. To read a single line of an internal table, use the following:
A: LOOP AT itab. _ ENDLOOP.
B: READ itab.
C: SELECT SINGLE * FROM itab.
D: READ TABLE itab.

90. Which Open SQL statement should not be used with cluster databases?
A: UPDATE
B: MODIFY
C: DELETE
D: INSERT

91. To include a field on your screen that is not in the ABAP Dictionary, which include program should contain the data declaration for the field? A: PBO module include program
B: TOP include program
C: PAI module include program
D: Subroutine include program

92. This flow logic statement is used to make multiple fields open for input after an error or warning message.
A: GROUP
B: FIELD-GROUP
C: CHAIN
D: LOOP AT SCREEN

93. Given:
PERFORM subroutine USING var.
The var field is known as what type of parameter?

A: Formal
B: Actual
C: Static
D: Value

94. Are Programs client dependent?
A: Yes
B: No

95. Which interface controls what is shown in the PC?
A: Presentation Interface
B: Application Interface
C: Database Interface
D: Operating system Interface

96. Which work process triggers database changes?
A: Update Work Process
B: Enqueue Process
C: Online Process
D: Database Process

97. How many transport request types are there?
A: 1
B: 2
C: 3
D: 4

98. What are the function modules generated upon creating a lock objects?
A: Enqueue and Dequeue
B: Lock and Unlock
C: None of the above

99. Can you use if-then-else statement in Sapscript?
A: Yes
B: No

100. Can you call subroutine of one program to another program?
A: Yes
B: No

100 ABAP Interview Questions (Part 4)

2013-02-01T20:29:00.004-08:00

Here's the Part 4 of this compiled ABAP questions. Enjoy answering. You can view the first three parts in this link:

ABAP Interview Part 1

ABAP Interview Part 2

ABAP Interview Part 3

61. To allow the user to enter a range of values on a selection screen, use the ABAP keyword:
A: DATA.
B: RANGES.
C: PARAMETERS.
D: SELECT-OPTIONS.

62. If an internal table is declared without a header line, what else must you declare to work with the table's rows?
A: Another internal table with a header line.
B: A work area with the same structure as the internal table.
C: An internal table type using the TYPES statement.
D: A PARAMETER.

63. Assuming an internal table contains 2000 entries, how many entries will it have after the following line of code is executed?
DELETE itab FROM 1500 TO 1700.

A: This is a syntax error.
B: 1801
C: 1800
D: 1799

64. To remove lines from a database table, use ____.
A: UPDATE
B: MODIFY
C: ERASE
D: DELETE

65. All of the following may be performed using SET CURSOR except:
A: Move the cursor to a specific field on a list.
B: Move the cursor to a specific list line.
C: Move the cursor to a specific pushbutton, activating that function.
D: Move the cursor to a specific row and column on a list.

66. When is it optional to pass an actual parameter to a required formal parameter of a function module?
A: The actual parameter is type C.
B: The formal parameter contains a default value.
C: The formal parameter's \"Reference\" attribute is turned on.
D: It is never optional.

67. Coding two INITIALIZATION events will cause a syntax error.
A: True
B: False

68. Adding a COMMIT WORK statement between SELECT_ENDSELECT is a good method for improving performance.
A: True
B: False

69. To save information on a list line for use after the line is selected, use this keyword.
A: APPEND
B: EXPORT
C: WRITE
D: HIDE

70. To bypass automatic field input checks, include this in PAI.
A: AT EXIT-COMMAND
B: ON INPUT
C: ON REQUEST
D: LEAVE TO SCREEN 0.

71. Within a function module's source code, if the MESSAGE_RAISING statement is executed, all of the following system fields are filled automatically except:
A: SY-MSGTY
B: SY-MSGNO
C: SY-MSGV1
D: SY-MSGWA

72. The following code indicates:
REPORT ZLISTTST.
START-OF-SELECTION.
WRITE: text-001.
FORMAT HOTSPOT ON.
WRITE: text-002.
FORMAT HOTSPOT OFF.
AT LINE-SELECTION.
WRITE / text-003.

A: Text-002 may not be selected.
B: The value of text-002 is stored in a special memory area.
C: Text-002 may be clicked once to trigger the output of text-003.
D: None of the above.

73. The ____ type of ABAP Dictionary view consists of one or more transparent tables and may be accessed by an ABAP program using Open SQL.
A: Database view
B: Projection view
C: Help view
D: Entity view

74. A concrete field is associated with a field-symbol via ABAP keyword
A: MOVE
B: WRITE
C: ASSIGN
D: VALUE

75. The output for the following code will be:
report zabaprg.
DATA: char_field type C.

char_field = 'ABAP data'.

WRITE char_field.

A: ABAP data
B: A
C: Nothing, there is a syntax error
D: None of the above

76. Page footers are coded in the event:
A: TOP-OF-PAGE.
B: END-OF-SELECTION.
C: NEW-PAGE.
D: END-OF-PAGE.

77. The event AT SELECTION-SCREEN OUTPUT. occurs before the selection screen is displayed and is the best event for assigning default values to selection criteria.
A: True
B: False

78. The TABLES statement declares a data object.
A: True
B: False

79. Assuming tab1-fld7 is not a key field, how can you prevent reading all the table rows?
SELECT fld1 fld2 fld3 FROM tab1 INTO (fld4, fld5, fld6)
WHERE fld7 = pfld7.
WRITE: /1 fld4, fld5, fld6.
ENDSELECT.

A: Take fld7 out of the WHERE clause.
B: Create an index in the ABAP Dictionary for tab1-fld7.
C: Use INTO TABLE instead of just INTO.
D: Take the WRITE statement out of the SELECT_ENDSELECT.

80. Which of the following is NOT a required attribute when creating an ABAP program?
A: Application
B: Title
C: Status
D: Type

100 ABAP Interview Questions (Part 3)

2013-02-01T20:19:00.002-08:00

Here's the Part 3 of this compiled ABAP questions. Enjoy answering. You can view the first two parts in this link:

ABAP Interview Part 1

ABAP Interview Part 2

41. To allow the user to enter values on the screen for a list field, use:
A: OPEN LINE.
B: SET CURSOR FIELD.
C: WRITE fld AS INPUT FIELD.
D: FORMAT INPUT ON.

42. Before a function module may be tested, it must first be:
A: Linked
B: Authorized
C: Released
D: Active

43. To include a field on your screen that is not in the ABAP Dictionary, which include program should contain the data declaration for the field?
A: PBO module include program
B: TOP include program
C: PAI module include program
D: Subroutine include program

44. If a table contains many duplicate values for a field, minimize the number of records returned by using this SELECT statement addition.
A: MIN
B: ORDER BY
C: DISTINCT
D: DELETE

45. The system internal table used for dynamic screen modification is named:
A: ITAB
B: SCREEN
C: MODTAB
D: SMOD

46. Within the source code of a function module, errors are handled via the keyword:
A: EXCEPTION
B: RAISE
C: STOP
D: ABEND

47. Which system field contains the contents of a selected line?
A: SY-CUCOL
B: SY-LILLI
C: SY-CUROW
D: SY-LISEL

48. The following statement writes what type of data object?
WRITE: /1 'Total Amount:'.

A: Text literal
B: Text variable
C: In-code comment
D: Text integer

49. For the code below, second_field is of what data type?
DATA: first_field type P, second_field like first_field.

A: P
B: C
C: N
D: D

50. Which of the following describes the internal representation of a type D data object?
A: DDMMYYYY
B: YYYYDDMM
C: MMDDYYYY
D: YYYYMMDD

51. A BDC program is used for all of the following except:
A: Downloading data to a local file
B: Data interfaces between SAP and external systems
C: Initial data transfer
D: Entering a large amount of data

52. In regard to PERFORM, which of the following is NOT a true statement?
A: May be used within a subroutine.
B: Requires actual parameters.
C: Recursive calls are allowed in ABAP.
D: Can call a subroutine in another program.

53. What is the transaction code for the ABAP Editor?
A: SE11
B: SE38
C: SE36
D: SE16

54. In regard to HIDE, which of the following is NOT a true statement?
A: Saves the contents of variables in relation to a list line's row number.
B: The hidden variables must be output on a list line.
C: The HIDE area is retrieved when using the READ LINE statement.
D: The HIDE area is retrieved when an interactive event is triggered.

55. Database locks are sufficient in a multi-user environment.
A: True
B: False

56. The complete technical definition of a table field is determined by the field's:
A: Domain
B: Field name
C: Data type
D: Data element

57. In regard to LEAVE, which of the following is NOT a true statement?
A: May be used to return immediately to a calling program.
B: May be used to stop the current loop pass and get the next.
C: May be used to start a new transaction.
D: May be used to go to the next screen.

58. The following code indicates:
SELECT fld6 fld3 fld2 fld1 FROM tab1 INTO CORRESPONDING FIELDS OF TABLE itab
WHERE fld3 = pfld3.

A: The order of the fields in itab does not matter.
B: Fill the header line of itab, but not the body.
C: Table itab can only contain fields also in table tab1.
D: None of the above.

59. The ABAP statement below indicates that the program should continue with the next line of code if the internal table itab:
CHECK NOT itab[] IS INITIAL.

A: Contains no rows
B: Contains at least one row
C: Has a header line
D: Has an empty header line

60. What will be output by the following code?
DATA: BEGIN OF itab OCCURS 0, fval type i, END OF itab.

itab-fval = 1. APPEND itab.
itab-fval = 2. APPEND itab.

FREE itab.
WRITE: /1 itab-fval.

A: 2
B: 0
C: blank
D: 1

100 ABAP Interview Questions (Part 2)

2013-02-01T18:47:00.003-08:00

Here's the Part 2 of this compiled ABAP questions. Enjoy answering. You can view the first part in this link:

ABAP Interview Part 1

21. What must you code in the flow logic to prevent a module from being called unless a field contains a non-initial value (as determined by its data type)?
A: ON INPUT
B: CHAIN
C: FIELD
D: ON REQUEST

22. The AT USER-COMMAND event is triggered by functions defined in the ____.
A: screen painter
B: ABAP report
C: menu painter status
D: ABAP Dictionary

23. In regard to a function group, which of the following is NOT a true statement?
A: Combines similar function modules.
B: Shares global data with all its function modules.
C: Exists within the ABAP workbench as an include program.
D: Shares subroutines with all its function modules.

24. In regard to SET PF-STATUS, you can deactivate unwanted function codes by using ____.
A: EXCLUDING
B: IMMEDIATELY
C: WITHOUT
D: HIDE

25. In regard to data transported in PAI when the FIELD statement is used, which of the following is NOT a true statement?
A: Fields in PBO are transported directly from PAI.
B: Fields with identical names are transported to the ABAP side.
C: Fields not defined in FIELD statements are transported first.
D: Fields that are defined in FIELD statements are transported when their corresponding module is called.

26. The order in which an event appears in the ABAP code determines when the event is processed.
A: True
B: False

27. A field declared as type T has the following internal representation:
A: SSMMHH
B: HHMMSS
C: MMHHSS
D: HHSSMM

28. Which of the following is NOT a component of the default standard ABAP report header?
A: Date and Time
B: List title
C: Page number
D: Underline

29. Assuming a pushbutton with function code 'FUNC' is available in the toolbar of a list report, what event is processed when the button is clicked?
A: AT USER-COMMAND.
B: AT PFn.
C: AT SELECTION-SCREEN.
D: END-OF-SELECTION.

30. In regard to field selection, what option of the SELECT statement is required?
A: FOR ALL ENTRIES
B: WHERE
C: INTO
D: MOVE-CORRESPONDING

31. The following program outputs what?
report zjgtest1
write: /1 'Ready_'.
PARAMETER: test.
INITIALIZATION.
write: /1 'Set_'.
START-OF-SELECTION.
write: /1 'GO!!'.

A: Set_ GO!! (each on its own line)
B: Set_ Ready_ GO!! (all on their own lines)
C: Ready_ GO!! (each on its own line)
D: Ready_ Set_ GO!! (all on their own lines)

32. To declare a selection criterion that does not appear on the selection screen, use:
A: NO-DISPLAY
B: INVISIBLE
C: MODIF ID
D: OBLIGATORY

33. An internal table that is nested within another internal table should not contain a header line.
A: True
B: False

34. What is output by the following code?
DATA: BEGIN OF itab OCCURS 0, letter type c, END OF itab.
itab-letter = 'A'. APPEND itab. itab-letter = 'B'. APPEND itab.
itab-letter = 'C'. APPEND itab. itab-letter = 'D'. APPEND itab.

LOOP AT itab.
SY-TABIX = 2.
WRITE itab-letter.
EXIT.
ENDLOOP.

A: A
B: A B C D
C: B
D: B C D

35. To select all database entries for a certain WHERE clause into an internal table in one step, use
A: SELECT_INTO TABLE itab_
B: SELECT_INTO itab_
C: SELECT_APPENDING itab
D: SELECT_itab_

36. After a successful SELECT statement, what does SY-SUBRC equal?
A: 0
B: 4
C: 8
D: Null

37. This selection screen syntax forces the user to input a value:
A: REQUIRED-ENTRY
B: OBLIGATORY
C: DEFAULT
D: SELECTION-SCREEN EXCLUDE

38. If the following code results in a syntax error, the remedy is:
DATA: itab TYPE SORTED TABLE OF rec_type WITH UNIQUE KEY field1
WITH HEADER LINE.

itab-field1 = 'Company'. itab-field2 = '1234'. INSERT TABLE itab.
itab-field1 = 'Bank'. itab-field2 = 'ABC'. INSERT TABLE itab.

SORT itab.

LOOP AT itab.
write: /1 itab-field1, itab-field2.
ENDLOOP.

A: There is no syntax error here
B: Remove the SORT statement
C: Change INSERT to APPEND
D: Add a WHERE clause to the loop

39. If this code results in an error, the remedy is:
SELECT fld1 fld2 FROM tab1 WHERE fld3 = pfld3.
WRITE: /1 tab1-fld1, tab1-fld2.
ENDSELECT.

A: Add a SY-SUBRC check.
B: Change the WHERE clause to use fld1 or fld2.
C: Remove the /1 from the WRITE statement.
D: Add INTO (tab1-fld1, tab1-fld2).

40. When modifying an internal table within LOOP AT itab. _ ENDLOOP. you must include an index number.
A: True
B: False

100 ABAP Interview Questions (Part 1)

2013-02-01T18:31:00.002-08:00

Are you planning to take up an ABAP Certification or having hard up looking for a new job due to interviews? So this is the right place for you.Here are some of the ABAP Interview/Certifications questions compiled. It tackles many aspect of ABAP programming like data dictionary, dialog programming etc. Enjoy reading and answer as many possible you can.

1. If a table does not have MANDT as part of the primary key, it is ____.
A: A structure
B: Invalid
C: Client-independent
D: Not mandatory

2. In regard to CALL, which of the following is NOT a valid statement?
A: CALL FUNCTION
B: CALL SCREEN
C: CALL TRANSACTION
D: CALL PROGRAM

3. Name the type of ABAP Dictionary table that has these characteristics:
Same number of fields as the database table
Same name as database table
Maps 1:1 to database table

A: Pooled
B: Cluster
C: Transparent
D: View

4. An event starts with an event keyword and ends with:
A: Program execution.
B: END-OF-EVENT.
C: Another event keyword.
D: END-EVENT.

5. What is the system field for the current date?
A: SY-DATUM
B: SY-DATE
C: SY-DATID
D: SY-SDATE
6. The following code indicates:
SELECT fld1 fld2 FROM tab1 APPENDING TABLE itab
WHERE fld1 IN sfld1.

A: Add rows to the existing rows of itab.
B: Add rows to itab after first deleting any existing rows of itab.
C: Select rows from tab1 for matching itab entries.
D: Nothing, this is a syntax error.

7. You may change the following data object as shown below so that it equals 3.14.
CONSTANTS: PI type P decimals 2 value '3.1'.
PI = '3.14'.

A: True
B: False

8. The SAP service that ensures data integrity by handling locking is called:
A: Update
B: Dialog
C: Enqueue/Dequeue
D: Spool

9. Which of these sentences most accurately describes the GET VBAK LATE. event?
A: This event is processed before the second time the GET VBAK event is processed.
B: This event is processed after all occurrences of the GET VBAK event are completed.
C: This event will only be processed after the user has selected a basic list row.
D: This event is only processed if no records are selected from table VBAK.

10. Which of the following is not a true statement in regard to a hashed internal table type?
A: Its key must always be UNIQUE.
B: May only be accessed by its key.
C: Response time for accessing a row depends on the number of entries in the table.
D: Declared using internal table type HASHED TABLE.

11. TO include database-specific SQL statements within an ABAP program, code them between:
A: NATIVE SQL_ENDNATIVE.
B: DB SQL_ENDDB.
C: SELECT_ENDSELECT.
D: EXEC SQL_ENDEXEC.

12. To measure how long a block of code runs, use the ABAP statement:
A: GET TIME .
B: SET TIME FIELD .
C: GET RUN TIME FIELD .
D: SET CURSOR FIELD .

13. When a secondary list is being processed, the data of the basic list is available by default.
A: True
B: False

14. Given:
DATA: BEGIN OF itab OCCURS 10,
qty type I,
END OF itab.

DO 25 TIMES. itab-qty = sy-index. APPEND itab.
ENDDO.

LOOP AT itab WHERE qty > 10.
WRITE: /1 itab-qty.
ENDLOOP.

This will result in:
A: Output of only those itab rows with a qty field less than 10
B: Output of the first 10 itab rows with a qty field greater than 10
C: A syntax error
D: None of the above

15. After a DESCRIBE TABLE statement SY-TFILL will contain
A: The number of rows in the internal table.
B: The current OCCURS value.
C: Zero, if the table contains one or more rows.
D: The length of the internal table row structure.

16. You may declare your own internal table type using the TYPES keyword.
A: True
B: False

17. After adding rows to an internal table with COLLECT, you should avoid adding more rows with APPEND.
A: True
B: False

18. Which of the following is not a component of control break processing when looping at an internal table?
A: AT START OF
B: AT FIRST
C: AT LAST
D: AT NEW

19. A dictionary table is made available for use within an ABAP program via the TABLES statement.
A: True
B: False

20. Which of the following would be best for hiding further selection criteria until a function is chosen?
A: AT NEW SELECTION-SCREEN
B: SELECTION-SCREEN AT LINE-SELECTION
C: SUBMIT SELECTION-SCREEN
D: CALL SELECTION-SCREEN

How to implement "Parallel Cursor"?

2012-12-09T14:18:00.002-08:00

Sometimes we need to loop within a loop as other calls it as a nested loop. We cannot deny the fact that there are tables in the data dictionary wherein we loop a header internal table and carry out some processing for each of the lines in the corresponding Item level internal table. To perform the same, we end up using nested loops which have a great impact on the performance and result in long execution times.

In order to overcome this situation, we need to implement PARALLEL CURSOR technique/approach wherein we maintain a cursor which holds the value of the index from where the subsequent search should start. This will result in vastly optimized ABAP components which would further facilitate faster data loading.

Illustration:
Suppose we have two internal tables IT_EKKO (header) and IT_EKPO (item) containing purchase order header and item level data and we need to extract some item level details on the basis of PO number which is common key in both the tables. We will have to put a nested loop here. Suppose there are 1000 records in table IT_EKPO and for PO 123 there are three records available in IT_EKPO table.

Example of a Nested Loop

DATA : 
   it_ekko  TYPE STANDARD TABLE OF ekko,
   wa_ekko  TYPE ekko,
   it_ekpo  TYPE STANDARD TABLE OF ekpo,
   wa_ekpo  TYPE ekpo.

DATA : 
   lv_tabix TYPE sy-tabix.

SELECT * FROM ekko INTO TABLE it_ekko.
SELECT * FROM ekpo INTO TABLE it_ekpo.

LOOP AT it_ekko INTO wa_ekko.
   LOOP AT it_ekpo INTO wa_ekpo WHERE ebeln = wa_ekko-ebeln.
       "Logial ABAP statements 
   ENDLOOP.
ENDLOOP.

Here when WA_EKKO-EBELN =123 the inner loop will execute 1000 times and statement inside the loop will execute 3 times. This will result in higher data load runs and poor performance. We can optimize the above using parallel cursor technique as elaborated below:

Parallel cursor is the technique to increase the performance of the program, when there are nested loops. The approach uses a variable using which we can maintain a cursor which will avoid the search to start all over again, from the first record. Instead it will control the loop to start the search from a specified index. This as a result makes the search faster and thus the high end performance improvement is scene in data loading processes. A mandatory prerequisite before using the approach is that the internal tables are both sorted by the respective key fields.

Nested Loop Using Parallel Cursor:

DATA : 
it_ekko TYPE STANDARD TABLE OF ekko,
wa_ekko TYPE ekko,
it_ekpo TYPE STANDARD TABLE OF ekpo,
wa_ekpo TYPE ekpo.
DATA : lv_tabix TYPE sy-tabix.

SELECT * FROM ekko INTO TABLE it_ekko.
SELECT * FROM ekpo INTO TABLE it_ekpo.
SORT it_ekko BY ebeln.
SORT it_ekpo BY ebeln.

LOOP AT it_ekko INTO wa_ekko.
   READ TABLE it_ekpo TRANSPORTING NO FIELDS 
   WITH KEY ebeln = wa_ekko-ebeln binary search.
   IF sy-subrc EQ 0.
      lv_tabix = sy-tabix.
      LOOP AT it_ekpo INTO wa_ekpo FROM lv_tabix.
         IF wa_ekpo-ebeln NE wa_ekko-ebeln.
            EXIT.
         ENDIF.
         Logial ABAP statements ………..
      ENDLOOP.
   ENDIF.
ENDLOOP.

Here when WA_EKKO-EBELN =123 the inner loop will execute 4 times and statement inside the loop will execute 3 times. This will result in a major performance improvement over the nested loop code elaborated earlier in the document.

How to access a TCODE without authorization?

2012-05-08T01:32:00.000-07:00

Its weekend again and time to share all knowledge I learned over the week. I know this topic that I will discuss today would be beneficial to my fellow ABAP developers specially when they dont have the SAP_ALL authorizations. For the sake of everyone, SAP_ALL authorizations is an authorization provided to a user in which he can access all standard tcodes of SAP system. So whether this is a functional or technical tcode, it is possible to access.

However, in an environment of a multinational company, this authorization is NOT permitted. As a developer, you are only given the access of all tcodes related to development like, SE38 (ABAP Editor), SE24 (Class Editor), SE37 (Function Module Editor) and other tcode related to development.

Now the issue is, how about if I want to access a particular tcode which is not related to ABAP Development? Let say, SU01, User Maintenance? But when I access it, I got this message "You are not authorized to access"? So in case you encounter it, what will you do?
Do you have any idea to by-pass the authorization set to your user account? Or will you ask your Basis people to grant you an access to this transaction code? How about if they denied your request?

Dont worry now as the pain is over. Well, in this tutorial, I will discuss with you on how to access any SAP Tcodes even you don't have any authorizations.Yes, you are right. We will by-pass the that authorization limiting you to access a particular tcode. The only requirement here is you must have an access to SE38 and you have the role S_DEVELOP. Since you will be creating a new program which we will call, ZTCODE. :)

First thing, create an ABAP program. Then copy this program below. It is just a 12 liner program. A simple one.

DATA: l_tcode TYPE sytcode.
PARAMETERS: p_tcode TYPE sy-tcode.
START-OF-SELECTION.

  SELECT SINGLE tcode FROM tstc
    INTO l_tcode
    WHERE tcode = p_tcode.
  IF sy-subrc = 0.
    CALL TRANSACTION p_tcode.
  ELSE.
    MESSAGE 'TCODE not found.' TYPE 'I'.
  ENDIF.

Once you are done, save and activate your program. The secret here is be sure to create a customized transaction code for this program. Let say, ZTCODE. Otherwise, you can't access that particular tcode you want to view. Clear?

Result:
Initially, I can't access SU01.

But after I created this program, I activated and ran it.

And voila, I can now access SU01 without the BASIS people. :)

How to convert a local class into a global class?

2012-04-05T17:45:00.000-07:00

Hello everyone... Its been quite sometime that I have not added some posts here. I just arrive from a vacation and I dont have any access on the net so its only now again I will add some tutorials. Anyway, what I will discuss today is all about converting your local class into a global class. What I mean is, a class declared directly into your program (SE38) and convert it into a global class found in SE24. Any class declared in SE24 are considered global class.

So this technique is simple to process just follow the steps below. By the way, I will not discussing here how to create a class. It will be discuss in another post.

Steps:
1. Make it sure that you have a local class defined (in SE38) just like this one below. If none, please create a simple one to proceed with this tutorial. So in my sample below, I created a class which I called "Computer". Then I added a method which I named it as "get_brand". This method, once our tutorial is finished, must appear on the global class.

2. Once you created your local class, go to tcode SE24. On its main screen, click on the main menu, Object Type-->Import-->Local classes in program.

3. This screen below appears. Enter the name of your class. It can be different to the name of your local class. No worries on it. Just follow the naming conventions that you have.

Afterwhich, click this Import button below the screen.

4. Lastly, open now your new global class. The method I mentioned above, "get_brand" is now copied into this new global class. This class is now visible then to other programs that you will do in the future.

Enjoy. Keep on visiting my blog. :)

How to display two ALV grid in one screen?

2012-03-27T22:31:00.000-07:00

Hello everyone. Its another topic I want to discuss with you today. Pause for a moment and take a look with this simple ALV grid below. Do you see it? Its two ALV Grid in just one screen. Have you been asked to do to display such? If not yet, then its time for you to take this sample codes I provided below.

REPORT  YYZZYY_TWO_ALV.

DATA: ok_code LIKE sy-ucomm,
      gt_sflight TYPE TABLE OF sflight,
      grid1  TYPE REF TO cl_gui_alv_grid,
      grid2  TYPE REF TO cl_gui_alv_grid.

* splitter control
DATA splitter TYPE REF TO cl_gui_easy_splitter_container.
* container for the splitter control
DATA container TYPE REF TO cl_gui_custom_container.

* containers created by the splitter control
DATA container_1 TYPE REF TO cl_gui_container.
DATA container_2 TYPE REF TO cl_gui_container.
* load control framework definition
TYPE-POOLS cndp.
*---------------------------------------------------------------------*
*       MAIN                                                          *
*---------------------------------------------------------------------*

SELECT * FROM sflight INTO TABLE gt_sflight.

CALL SCREEN 100.

*&---------------------------------------------------------------------*
*&      Module  STATUS_0100  OUTPUT
*&---------------------------------------------------------------------*
*       text
*----------------------------------------------------------------------*
MODULE status_0100 OUTPUT.
SET PF-STATUS 'MAIN100'.
  set TITLEBAR '100'.
  IF  container_1 IS INITIAL.

* create a container for the splitter control
    CREATE OBJECT container
                  EXPORTING container_name = 'CUSTOM'.
* create the splitter control
    CREATE OBJECT splitter
                  EXPORTING parent = container
                            orientation    = 1. "0-horizontal; 1-vertical
* get the containers of the splitter control
    container_1 = splitter->top_left_container.
    container_2 = splitter->bottom_right_container.
* create the picture controls inside the containers of the splitter

    CREATE OBJECT GRID1
           EXPORTING I_PARENT =  container_1.
    CALL METHOD GRID1->SET_TABLE_FOR_FIRST_DISPLAY
         EXPORTING I_STRUCTURE_NAME = 'SFLIGHT'
         CHANGING  IT_OUTTAB        = GT_SFLIGHT.

    CREATE OBJECT GRID2
           EXPORTING I_PARENT =  container_2.
    CALL METHOD GRID2->SET_TABLE_FOR_FIRST_DISPLAY
         EXPORTING I_STRUCTURE_NAME = 'SFLIGHT'
         CHANGING  IT_OUTTAB        = GT_SFLIGHT.
endif.
ENDMODULE.                 " STATUS_0100  OUTPUT
*&---------------------------------------------------------------------*
*&      Module  USER_COMMAND_0100  INPUT
*&---------------------------------------------------------------------*
*       text
*----------------------------------------------------------------------*
MODULE user_command_0100 INPUT.
  CALL METHOD container->free.
  LEAVE PROGRAM.
ENDMODULE.                 " USER_COMMAND_0100  INPUT

How to add Select options in Dialog screens?

2012-03-27T15:54:00.000-07:00

SELECT-OPTIONS is a complex selection which has a structure of lower and higher limit. Users can input multiple values as range or individual value filling up the lower limit only. This screen parameter is usually used and declared in SELECTION-SCREEN and not in Dialog Screens.

So in this tutorial, I will discuss and show to you, how can we implement SELECT-OPTIONS in dialog screens. As I always says, follow these steps I detailed below:

Steps:
1. The first step is create a screen in SE80. Then on that screen, add a susbcreen just like below. I named my subscreen as SUB1. So you can name your subscreen anything you want.

2. The next procedure is to create the SELECT-OPTION using selection-screen but declared as subscreen. As you can see below, Screen 200 is declared as a subscreen. This subscreen will be called into the container we created in Step 1. Then after declaring the subscreen 200, use the event START-OF-SELECTION then call your main screen 100. Take note also, to create this as a separate INCLUDE program.

3. After creating the subscreen, you need to call this subscreen into your main screen. So what to do is, click your main screen, let say Screen 100. In the Flow Logic tab, enter the following or refer to the screenshot below:

On the part of Process Before Output:
CALL SUBSCREEN <name_of_your_subscreen> INCLUDING sy-repid '200'.

Please note that 200 is the subscreen no declared in Step 2.

On the part of Process After Input:
CALL SUBSCREEN <name_of_your_subscreen>.

4. Lastly, save and activate your program. Try to run and you will that SELECT-OPTION is now implemented in to your dialog screen.

I hope you enjoy again reading this post. If you have any query or question, please drop a message to me. I am so much willing to answer you and give feedback as soon as I read your message to me. Cheers.. Enjoy reading... :)

How to implement different PF-STATUS types?

2012-03-26T15:41:00.027-07:00

PF-STATUS is used to allow the user to communicate with the system where the defined function codes direct the user actions to the ABAP program. In dialog programming, there are three types of pf-status available for the developer, namely normal screen, dialog box and context menu (see screenshot below)

In this tutorial, I will discuss the last two statuses on how to create and implement into your ABAP applications.

A. Dialog Box Status – this status works when your screen type is defined as modal dialog box. Normally, this type of status is used with a popup screen where it is called upon using the keywords CALL SCREEN xxx STARTING AT x1 y1. Take note the keywords STARTING AT as this is the keywords to make it as a popup screen.

In order to use and implement this status, follow the steps detailed below.

STEPS:1. First, set your screen type as modal dialog box.

2. Once set, create a PF-STATUS with a type of Dialog Box as seen below.

In this next screen, there are two default commands: Ok and exit. So for demo purposes, I use the exit function. I just type any command name for this function. So it depends again on you, what you want to call each commands.

3. Then on the PBO of your screen, set the PF-STATUS you declared above.

4. Save and activate your program. Try to run and display the popup screen. Click the small “x” button at the upper right of the popup screen and it will close the screen. This is one of the applications of a dialog box status.

B. Context Menu Status – this status is triggered when the user pressed the right mouse key or SHIFT F10, a list of command is shown on the screen. It allows user to select list of functions dynamically defined. It can be assigned to the following screen elements namely: Input/output fields, Text fields, Table controls, Group boxes, subscreens pushbuttons, checkboxes, or radio buttons.

Please note that in my sample, I added a textbox in my screen. In this textbox, I will add here the context menu status. So in your implementations, it could be other screen elements. To implement, follow these steps.

STEPS:
1. Open your screen where you will add your context menu. In my case, it is Screen 200. As can be seen below, the added textbox.

2. Double click this screen element to display the screen painter attributes. On the field ON_CTMENU_, enter a name for your context menu. In my sample, I entered “Context”. So it depends on you what you want to call.

3. Go back to your program and create the GUI status. From the status type, select context menu.

4. In the screen menu, add your function codes. In my sample below, I added the following function codes: ADD, EDIT, DEL and EXIT. So it depends on your requirement, what function codes to be added here. By the way, the part in blue is not shown initially. In order to display it, just pressed the ENTER key or double click the parameter in black.

5. After setting the GUI status, create a subroutine. Take note the name of the routine as it must be the same as the one you defined in the screen painter attribute. Then instantiate a class with reference to CL_CTMENU. Call the method LOAD_GUI_STATUS exporting the program name, status name and the class.

6. Save and activate your program. Try to run. Press right click on the textbox and the context menu you defined then be displayed.

Enjoy Reading... Keep on visiting. :)

How to debug smartform in production system?

2012-03-25T04:29:00.000-07:00

Have you encountered now a logical bug in your smartform which only appears when transported in the production system? Then we cannot replicate the same issue in our development box. So in this case, we have no option but to debug the form directly in production system, right? But we all know that setting a debugging point in the smartform is prohibited in this system. So do you have any idea to debug it?

In this tutorial, I will discuss a simple technique on how to debug the form even on the production system without any interference on the actual code. Just follow the following steps detailed below.

Steps:
1.Run tcode Smartform and open your form. If you are not authorized in your production system to open your form, go back into your development system.

2. Once your form is open, go to main menu, click on Environment-->Function Module Name.

3. In this screenshot, you will see the function name of this form. Take note that every smartform you created, a function name is generated unlike in sapscript that no FM is created.

4. So in the previous steps, we get the name of the function module generated for this form. Our next goal is to determine which part of the form will it going to stop. So in my sample as you see, I need to debug the program lines under %CODE1. Please take note the name of the program lines since we will use this later.

5. After getting the function module name of the form and determining the part where we will going to debug, we are ready to set the breakpoint now. Go to SE37 and input the FM name generated above. Then click display the button. Perform this procedure in your production system. If you dont have any access in SE37, then ask your Basis people to provide you.

6. Then on the toolbar, select the find button with plus sign.

7. Then on this screen, input the name of the program lines you want to debug. Then select the option "In main program". Then click ok.

8. In this screen, it will show what lines contains your search word. Just double click it so you will be directed in the actual code.

9. Finally, you will see now your code and you can put a breakpoint just like below. Run your program again and debugging mode will then be prompted.

Enjoy reading... Keep on visiting my blogs. :)