Archive

Posts Tagged ‘dialog programming’

Getting a field value of a screen field

January 29th, 2009

In dialog programming, the value of a screen field will be moved to the variable in your program after the Process After Input (PAI) is executed. What if you need the value before PAI is executed? For example, you have two fields in your screen: functional location (VIQMEL-TPLNR) and equipment (VIQMEL-EQUNR). You need to implement a search help for equipment number, but you only what to get equipments that is installed in the functional location specified.

When you debug your search help module, you can’t get the value of functional location the user entered. Why? Because your search help module will be placed in Process on value-request (POV), and the POV will be executed before PAI.

How to obtain your screen field value then? Simple. Just execute Function Module ‘GET_DYNP_VALUE’ and you will get what you want. Read more…

vera ABAP , ,

Multiple lines text element

January 27th, 2009

Did you ever need a multiple lines input for your user interface in dialog programming using screen painter? Well, I did. And I spent the whole day searching for a way to implement what I wanted.

Guess what! A few minutes ago I thought why didn’t I use an internal table with one element and put it in my screen? Why didn’t I think of that? Bummer! I had to waste a whole day searching for a “multiple lines text element” :P .

Here’s the code you will need to get what you want:

  1. First, you will need to declare an internal table containing 1 field only. For example:
    data: BEGIN OF T_LINES OCCURS 0,
    lines(100),
    END OF T_LINES.
  2. Read more…

vera ABAP , ,