topic Re: set and get parameter in Application Development and Automation Discussions

set and get parameter

Former Member — Mon, 10 Apr 2006 07:52:44 GMT

Can anybody clarify this doubt.

Why sometimes set and get parameter statement.

at the same time inport export will work.

where import export don't work set get will work

Plz clarify.

Prashanth

Re: set and get parameter

Former Member — Mon, 10 Apr 2006 07:56:03 GMT

example........

data: cac_kokrs like coas-kokrs,

get parameter id 'CAC' field cac_kokrs.WRITE CAC_KOKRS.

parameter ID 'CAC' is checked in SAP MEMORY and if it is there, it is assigned to cac_kokrs.

The parameter id will be unique for a particular field in

SAP MEMORY.

U CAN ALSO USE

SET parameter id 'CAC' field cac_kokrs. ABOVE.

BUT THE DIFFERENCE BETWEEN THE TWO IS AS FOLLOWS:

get parameter id

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.

1.in the above syntax para is a variable for which parameter id is assigned.

2. get parameter id returns sy-subrc.

set parametr id

SET PARAMETER ID: 'CAR' FIELD carrier,

'CON' FIELD connection.

1. the parameter id 'CAR' is static , u cant use variables.

Re: set and get parameter

Former Member — Mon, 10 Apr 2006 07:57:13 GMT

Prashanth,

IMPORT and EXPORT are program specific (ABAP Memory) and it depends on what memory id the developer is giving.

Where SET / GET PARAMETER, there is a memory id associated with a field all the time.

You cannot use IMPORT / EXPORT when you want to pass something to Standard programs, like for example CALL TRANSACTION tcode AND SKIP FIRST SCREEN. Here you will have to use the SET/GET.

regards,

Ravi

Note : Please mark the helpful answers

Re: set and get parameter

Former Member — Mon, 10 Apr 2006 07:59:23 GMT

You should have particular problem with that stataments, only GET PARAMETER should fail if SET PARAMETER is not done before.

You can see the actived PARAMETER in debug.

Anyeway the PARAMETER has to be defined by SE80.

Max

Re: set and get parameter

hymavathi_oruganti — Mon, 10 Apr 2006 07:59:42 GMT

U CAN SEE THAT ABAP MEMORY IS SUBSET OF SAP MEMORY.

SO WHAT EVE WORKS IN SUBEST WILL WORK IN SUPERSET BUT NOT VICEVERSA.

There are three types of memories.

1. ABAP MEMORY

2. SAP MEMORY

3. EXTERNAL MEMORY.

1.we will use EXPORT/ IMPORT TO/ FROM MEMORY-ID when we want to transfer between ABAP memory

2. we will use GET PARAMETER ID/ SET PARAMETER ID to transfer between SAP MEMORY

3. we will use EXPORT/IMPORT TO/FROM SHARED BUFFER to transfer between external memory.

ABAP MEMORY : we can say that two reports in the same session will be in ABAP MEMORY

SAP MEMORY: TWO DIFFERENT SESSIONS WILL BE IN SAP MEMORY.

for ex: IF WE CALL TWO DIFFERENT TRANSACTIONS SE38, SE11

then they both are in SAP MEMORY.

EXTERNAL MEMORY: TWO different logons will be in EXTERNAL MEMORY.

Message was edited by: Hymavathi Oruganti

Re: set and get parameter

Former Member — Mon, 10 Apr 2006 08:57:35 GMT

Hi,

Chk this link for some infor on set & get params:

Regards,

Anjali

Re: set and get parameter

vinod_gunaware2 — Mon, 10 Apr 2006 09:18:26 GMT

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.

<b>Reading Data Objects from Memory</b>

To read data objects from ABAP memory into an ABAP program, use the following statement:

Syntax

IMPORT <f1> [TO <g 1>] <f 2> [TO <g 2>] ... FROM MEMORY ID <key>.

This statement reads the data objects specified in the list from a cluster in memory. If you do not use the TO <g i > option, the data object <f i > in memory is assigned to the data object in the program with the same name. If you do use the option, the data object <f i > is read from memory into the field <g i >. The name <key> identifies the cluster in memory. It may be up to 32 characters long.

You do not have to read all of the objects stored under a particular name <key>. You can restrict the number of objects by specifying their names. If the memory does not contain any objects under the name <key>, SY-SUBRC is set to 4. If, on the other hand, there is a data cluster in memory with the name <key>, SY-SUBRC is always 0, regardless of whether it contained the data object <f i >. If the cluster does not contain the data object <f i >, the target field remains unchanged.

<b>Saving Data Objects in Memory</b>

To read data objects from an ABAP program into ABAP memory, use the following statement:

Syntax

EXPORT <f1> [FROM <g 1>] <f 2> [FROM <g 2>] ... TO MEMORY ID <key>.

This statement stores the data objects specified in the list as a cluster in memory. If you do not use the option FROM <f i >, the data object <f i > is saved under its own name. If you use the FROM <g i > option, the data objet <g i > is saved under the name <f i >. The name <key> identifies the cluster in memory. It may be up to 32 characters long.

regards

vinod