Skip to Content
avatar image
Former Member

How to use SET and GET parameter commands ?

Explain these two giving an example?As which is used for what?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • avatar image
    Former Member
    Jun 22, 2005 at 05:41 AM

    Hi Albert,

    The SET PARAMETER statement is generally used in the PAI event for a screen. The user will have entered some value for a field on the screen and once you determine the correctness of that value, you can use the SET PARAMETER ID statement in the PAI.

    The GET PARAMETER ID statement is generally used in the PBO event. During the PBO, you are preparing the screen for display to the user. Some of the fields on the screen may need to be filled with some default values. This default value is the last correct value that has been entered for that field during the current logon to the SAP system.

    Hope that helps. Also there are other posts in this forum which address this question. Please search for them to get more information.


    Anand Mandalika.

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jun 22, 2005 at 05:37 AM

    Hi Albert,


    data: var(10) type c.

    var = 'test'

    set parameter id 'XYZ' value var.

    you set the parameter XYZ to the value test in the global memory.

    You can then access this value in another program by getting it out of the memory using

    data: var(10) type c.

    get parameter id 'XYZ' value var.

    So with this you can pass parameters from program to program. Check also the F1 help for the set/get parameter statement.

    Hope this helps



    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jun 22, 2005 at 08:35 AM

    Hi Albert,

    SAP allows you to make use of SPA/GPA technique to fill the input fields of a called transaction with data from the calling program.SPA/GPA parameters are values that the system stores in the global, user-specific SAP memory. SAP memory allows you to pass values between programs. A user can access the values stored in the SAP memory during one terminal session for all parallel sessions. Each SPA/GPA parameter is identified by a 20-character code. You can maintain them in the Repository Browser in the ABAP Workbench. The values in SPA/GPA parameters are user-specific.

    ABAP programs can access the parameters using the SET PARAMETER and GET PARAMETER statements.

    To fill one, use:


    This statement saves the contents of field <f> under the ID <pid> in the SAP memory. The code <pid> can be up to 20 characters long. If there was already a value stored under <pid>, this statement overwrites it. If the ID <pid> does not exist, double-click <pid> in the ABAP Editor to create a new parameter object.

    To read an SPA/GPA parameter, use:


    This statement fills the value stored under the ID <pid> into the variable <f>. If the system does not find a value for <pid> in the SAP memory, it sets SY-SUBRC to 4, otherwise to 0.

    To fill the initial screen of a program using SPA/GPA parameters, you normally only need the SET PARAMETER statement.

    The relevant fields must each be linked to an SPA/GPA parameter.

    On a selection screen, you link fields to parameters using the MEMORY ID addition in the PARAMETERS or SELECT-OPTIONS statement. If you specify an SPA/GPA parameter ID when you declare a parameter or selection option, the corresponding input field is linked to that input field.

    On a screen, you link fields to parameters in the Screen Painter. When you define the field attributes of an input field, you can enter the name of an SPA/GPA parameter in the Parameter ID field in the screen attributes. The SET parameter and GET parameter checkboxes allow you to specify whether the field should be filled from the corresponding SPA/GPA parameter in the PBO event, and whether the SPA/GPA parameter should be filled with the value from the screen in the PAI event.

    When an input field is linked to an SPA/GPA parameter, it is initialized with the current value of the parameter each time the screen is displayed. This is the reason why fields on screens in the R/3 System often already contain values when you call them more than once.

    When you call programs, you can use SPA/GPA parameters with no additional programming overhead if, for example, you need to fill obligatory fields on the initial screen of the called program. The system simply transfers the values from the parameters into the input fields of the called program.

    However, you can control the contents of the parameters from your program by using the SET PARAMETER statement before the actual program call. This technique is particularly useful if you want to skip the initial screen of the called program and that screen contains obligatory fields.

    If you want to set SPA/GPA parameters before a program call, you need to know which parameters are linked to which fields on the initial screen. A simple way of doing this is to start the program that you want to call, place the cursor on the input fields, and choose F1 followed by Technical info. The Parameter ID field contains the name of the corresponding SPA/GPA parameter. Alternatively, you can look at the screen definition in the Screen Painter.

    The SPA/GPA parameter for the input field Company has the ID CAR. Use this method to find the IDs CON, DAY, and BOK for the other input fields.

    The following executable program is connected to the logical database F1S and calls an update transaction:




    WRITE: 'Select a booking',

    / '----














    The basic list of the program shows fields from the database table SBOOK according to the user entries on the selection screen. These data are also stored in the HIDE areas of each line.



    Add comment
    10|10000 characters needed characters exceeded