topic Re: Set & Get in Application Development and Automation Discussions

Set & Get

Former Member — Mon, 04 Feb 2008 11:42:26 GMT

i'm new to this ABAP

could u plz tell me about

set & get parameters

set & get cursor

and the difference between these two??

Thanks & Regards

Sateesh

Re: Set & Get

Former Member — Mon, 04 Feb 2008 11:43:26 GMT

Hello Sateesh

plz go through this

If u want to pass values from 1 screen to othet screen we use memory id to

pass values from one screen to another screen using set & get parameters.

SET PARAMETER command's function is to create a storage location in memory &

retrieve its contents.The set parameter statement is issued in PAI ,the

value must be input into the fields first before it can be placed in the

buffer.

Syntax : SET PARAMETER ID <pid> FIELD <f>.

This statement saves the content of field <f> under the ID <pid> in tha sap memory.

GET PARAMETER command's function is to pass data from the screen fields to

the abap program.

Syntax : GET PARAMETER ID <pid> FIELD <f>.

This statement fills the value stored under the ID <pid> into the variable

<f>.

SET CURSOR : -

SET CURSOR FIELD <f> .

This statement keeps the name of the screen element on which the cursor is

positioned .

GET CURSOR : -

GET CURSOR FIELD <f> .

This statement transfers the name of the screen element on which the cursor

is positioned during a user action into the variable <f>.

Re: Set & Get

Former Member — Mon, 04 Feb 2008 11:47:14 GMT

Thank You

Re: Set & Get

Former Member — Mon, 04 Feb 2008 11:48:51 GMT

Set Parameter ID is used to set values to the fields of the screens through the program.

Get Parameter ID is used to get the values into the program that are entered in the fields of the screens.

To fill the input fields of a called transaction with data from the calling program, you can use the SPA/GPA technique. 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:

SET PARAMETER ID <pid> FIELD <f>.

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:

GET PARAMETER ID <pid> FIELD <f>.

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.

http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9e0435c111d1829f0000e829fbfe/content.htm

A parameter id allows you to store and retrieve values for a specific user, see below for syntax on how to perform these operations.

The program displays a report containing what the value of the parameter id is before you run the SAP program and what it is after wards. Before will contain blank or what ever you entered last time the program was executed, and the after value will be the value you entered onto the ABAP selection screen this time.

Example program,:

REPORT PARAMID .

data: gd_valuein(10) type c,

gd_valueout(10) type c.

PARAMETERS: p_value(10) type c.

********************

*start-of-selection.

start-of-selection.

get parameter ID 'ZMESS' field gd_valuein.

set parameter ID 'ZMESS' field p_value.

get parameter ID 'ZMESS' field gd_valueout.

******************

*end-of-selection.

end-of-selection.

write:/ 'value at start of program:', gd_valuein,

/ 'value at end of program:', gd_valueout.

plz reward if useful

vivek

Re: Set & Get

Former Member — Mon, 04 Feb 2008 11:50:49 GMT

go through this link which ll give you detail idea about the set cursor.

http://www.sts.tu-harburg.de/teaching/sap_r3/ABAP4/set_curs.htm

plz reward if helpful

vivek

Re: Set & Get

Former Member — Mon, 04 Feb 2008 11:56:37 GMT

hi sateesh,

set cursor:

1. SET CURSOR FIELD f.

Places the cursor dynamically at the start of the field g which is specified in the field f. You must specify the name of the field in uppercase letters.

2. SET CURSOR LINE line

Places the cursor dynamically in the loop line line with step loops or in the absolute list line line (SY-LILLI) in list processing. This variant is only possible with step loops and in list processing.

3. SET CURSOR col line

This variant of the statement SET CURSOR does not operate on the cells of a table control or the fields of a tabstrip control, since different elements may exist at the absolute position col line.

get cursor

1. GET CURSOR FIELD f.

Transfers the name of the field at the cursor position to the field f.

The Return Code is set as follows:

SY-SUBRC = 0:

Cursor was positioned on a field.

SY-SUBRC = 4:

Cursor was not positioned on a field.

2. GET CURSOR LINE line

As for variant 1 with addition LINE, except that there are differences with the return code and the effect of the additions.

The Return Code is set as follows:

SY-SUBRC = 0:

The cursor is on one of the list lines (list processing) or on a loop line (step loop).

SY-SUBRC = 4:

The cursor is not on one of the list or loop lines.

set parameter

SET PARAMETER ID pid FIELD f.

Writes the contents of the field f to the global user-specific SAP memory and the local transaction-specific SAP memory under the ID pid. Any existing values under the same ID are overwritten.

Parameter IDs can be up to 20 characters long. They cannot consist entirely of spaces. The SAP system description contains an overview of parameter IDs. You can also produce a list using the ABAP Workbench.

get parameter

GET PARAMETER ID pid FIELD f

First, the value stored under the key pid is transferred from the local SAP memory into the field f. If this key is not available in the local SAP memory, the value stored under the same key pid is transferred from the global user-related SAP memory to the field f.

A parameter ID can have up to 20 characters. You can find an overview of the keys (parameters) used in the SAP system description or the appropriate function in the ABAP Workbench.

The Return Code is set as follows:

SY-SUBRC = 0: A value was read from SAP memory. SY-SUBRC = 4: No value was found in SAP memory under the specified key.

hope this can help you.