When use SET/GET statement for loading from memory

[Former Member]

Ho experts,

I would like to ask you when is it necessary to use the SET/GET statements to transport values between a screen and an ABAP code? I thought it always works automatically.

Thanks in advance,

Radek

[Former Member]

Hi,

If you want to pass data between two external sessions use SET/GET Parameterts, otherwise to pass among the internal sessions use IMPORT/EXPORT key word.

Go through the following link

or Take F1 help on the Above Key words

You can search the inter net like Google.com by providing the above keywords, and you can get full information.

Check the below Thread for more info

Cheerz

Ram

[Former Member]

It do works automatically...

But look at following scenarios -

1. You do not have any screen field defined for Plant (Parameter ID - WRK) and you want to check what is the value maintained by user for this parameter. (Or is there any value at all set for this user for WRK). you may use GET PARAMETER.....

(Of course, this is just an example, there is alternate way to define screen field and make it invisible).

2. Consider a scenario wherein you want to call some transaction by skipping first screen...First screen contains Plant and has WRK parameter ID assigned to it...You can use SET PARAMETER to set value of plant and skip first screen...First screen will automatically filled with the value passed by SET PARAMETER and user will be directly taken to second screen.

These are just few examples to understand the concept.

Thanks,

Regards,

Mohaiyuddin

[Former Member]

To answer your question"I thought it always works automatically" more fully, when you look at a field's attributes within the dynpro you will see both a "SET Paramater" and a "GET Parameter" option - this allows you to determine the behaviour. However with report programs, the selection screen(s) generated by SAP will tick both these options automatically should you have a parameter defined with "memory id xxx."... this may lead to the impression that there will always be a "set" and a "get" for a screen field but this behaviour is adjustable for custom dynpros.

Jonathan