topic Re: parameteres in Application Development and Automation Discussions

parameteres

Former Member — Mon, 17 Sep 2007 05:26:40 GMT

hi all,

what is Getparameter ID & setparameter ID, where these will be useful for us.

Re: parameteres

former_member283648 — Mon, 17 Sep 2007 05:29:13 GMT

These are usefull when u want to transfer data across sessions. These set values in SAP memory area and the values are set using SET Parameter ID. The values are read using GET Parameter ID.

Re: parameteres

Former Member — Mon, 17 Sep 2007 05:29:36 GMT

CALL TRANSACTION 'ZFI001D'.

ELSEIF WA_SELFIELD-FIELDNAME = 'BELNR'.

READ TABLE IT_FINAL INDEX WA_SELFIELD-TABINDEX.

IF SY-SUBRC = 0 .

SET PARAMETER ID 'BLN' FIELD IT_FINAL-BELNR.

SET PARAMETER ID 'BUK' FIELD IT_FINAL-BUKRS.

SET PARAMETER ID 'GJR' FIELD IT_FINAL-GJAHR.

CALL TRANSACTION 'FB03' AND SKIP FIRST SCREEN.

ENDIF.

have alook at this.

to capture the the value , we have to to find the parameter id , and it to subsequent screen. i e to secondatry list

Re: parameteres

Former Member — Mon, 17 Sep 2007 05:30:03 GMT

HI,

this is for using sap memory

SAP memory is a memory area to which all main sessions within a SAPgui have access. You can use SAP memory either to pass data from one program to another within a session, or to pass data from one session to another. Application programs that use SAP memory must do so using SPA/GPA parameters (also known as SET/GET parameters). These parameters can be set either for a particular user or for a particular program using the SET PARAMETER statement. Other ABAP programs can then retrieve the set parameters using the GET PARAMETER statement. The most frequent use of SPA/GPA parameters is to fill input fields on screens

calling program

PARAMETER:INPUT(30).

SET PARAMETER ID 'EXAMPLE' FIELD input.

submit ZEXAMPLE1 VIA SELECTION-SCREEN AND RETURN.

zexample1

DATA:VAR TYPE SY-UCOMM.

PARAMETERS:EXAMPLE1(30).

AT SELECTION-SCREEN OUTPUT.

GET PARAMETER ID 'EXAMPLE' FIELD VAR.

example1 = var.

rgds,

bharat.

Re: parameteres

Former Member — Mon, 17 Sep 2007 05:30:35 GMT

Hi,

The SAP Memory is a user-specific memory area of the application server, which is accessed by all main sessions of a user session at once. ABAP programs have access to SPA/GPA parameters stored in the SAP Memory (also called SET/GET parameters).

e.g.

Using Set parameter

you can give value of variable (dobj) to parameter ID 'pid'. This will store value in SAP memory

SET PARAMETER ID pid FIELD dobj.

When you want to use that value stored in SAP memory

you can use GET parameter.

GET PARAMETER ID pid FIELD dobj.

The above cannot be used for internal table. Supported data types are (data type C, N, D or T).

Memory-ID is used to save and retrieve the last entered data in the field.

Eg: PARAMETERS p_vbeln for vbak-vbeln memory-id pid

Shared memory is the area that can be used to share data between different processes.

Here itab should be declared of same type and length.

http://www.sap-img.com/abap/difference-between-sap-and-abap-memory.htm

Regards,

Priyanka.

Re: parameteres

Former Member — Mon, 17 Sep 2007 05:31:00 GMT

SET PARAMETER

Syntax

SET PARAMETER ID pid FIELD dobj.

Effect:

This statement sets the content of the SPA/GPA parameter specified in pid to the content of the data object dobj. For pid, a flat character-type field is expected that can contain a maximum of 20 characters, which cannot be exclusively blank characters. pid is case-sensitive. For dobj, a flat, (as of release 6.10 character-type) field is expected, whose binary content is transferred in an unconverted format.

If the SPA/GPA parameter specified for the current user in pid does not yet exist in the SAP memory, it is created. If the SPA/GPA parameter has already been created for the current user, its value is overwritten.

In a program, SPA/GPA parameters can only be created or assigned values if a name exists for them in the table TPARA. The extended program check reports an error if it can statically determine that a name specified in pid is not contained in the database table TPARA. ist.

Note:

For a SPA/GPA parameter specified in pid to match a name in the database table TPARA, it must be entered in upper case.

Example:

If the user selects a flight displayed in the basic list, when the event ATLINE-SELECTION takes place, the SPA/GPA parameters CAR and CON are set to the ID of the airline and the connection number. The names of both parameters are defined in the table TPARA for this purpose. In the initial screen of the transaction DEMO_TRANSACTION, two input fields are linked with SPA/GPA these parameters and are displayed with the selected values as start values.

DATA: carrier TYPE spfli-carrid,

connection TYPE spfli-connid.

START-OF-SELECTION.

SELECT carrid connid

FROM spfli

INTO (carrier, connection).

WRITE: / carrier HOTSPOT, connection HOTSPOT.

HIDE: carrier, connection.

ENDSELECT.

AT LINE-SELECTION.

SET PARAMETER ID: 'CAR' FIELD carrier,

'CON' FIELD connection.

CALL TRANSACTION 'DEMO_TRANSACTION'.

GET PARAMETER

Syntax

GET PARAMETER ID pid FIELD dobj.

Effect

This statement sets the content of the data object dobj to the content of the SPA/GPA parameter specified in pid. pid must be a flat character-type field that contains no more than 20 characters and does not consist solely of blanks; it is also case-sensitive. dobj must be a flat and (as of Release 6.10) character-type field into which the binary content of the SPA/GPA parameter is transferred unconverted.

If the SPA/GPA parameter specified in pid was not yet created in the SAP Memory for the current user, the data object dobj is initialized and sy-subrc is set to 4.

In a program, only those SPA/GPA parameters can be read for which there is a name in the table TPARA. The extended program check reports an error, if it can be statically determined that an ID specified in pid is not in the table TPARA.

System fields

sy-subrc Meaning

0 The SPA/GPA parameter specified in pid exists for the current user in the SAP Memory and its value was transferred to the target field.

4 The SPA/GPA parameter specified in pid does not exist for the current user in the SAP Memory.

Notes

An SPA/GPA parameter that is readable with GET PARAMETER can previously have been created in the SAP Memory using the SET PARAMETER statement or automatically during the event PAI of a screen or selection screen.

For an SPA/GPA parameter specified in pid to match a name in the database table TPARA, it must be specified in uppercase.

Example

In this example, the current value of the SPA/GPA parameter RID is read from the SAP Memory to the data object prog. In the screens of the ABAP Workbench, this parameter is linked with the input fields for a program name. When an ABAP Workbench tool, in which an ABAP program is processed, is first called, the parameter is created at the event PAI and assigned the name of the program specified there. If in the same user session, no screen is processed that set the parameter RID and no corresponding SET PARAMETER statement was executed beforehand, RID is not found in the SAP Memory.

DATA: para TYPE tpara-paramid VALUE 'RID',

prog TYPE sy-repid.

GET PARAMETER ID para FIELD prog.

IF sy-subrc <> 0.

MESSAGE 'Parameter not found' TYPE 'I'.

ENDIF.

Cheers

Ravish

Reward if useful

Re: parameteres

Former Member — Mon, 17 Sep 2007 05:33:23 GMT

hi,

when you want to move to some standard transaction after double clicking a particular field in the list display then set patameter id is used.