topic Re: how to store selection parameter value in memory in Application Development and Automation Discussions

how to store selection parameter value in memory

laxman_sankhla3 — Tue, 16 Oct 2007 07:11:59 GMT

i want to store selection parameter value in memory and than i want to use that value.

how i can do it.

please help.

thanks.

Re: how to store selection parameter value in memory

Former Member — Tue, 16 Oct 2007 07:16:12 GMT

Hi,

Try like below:

Using Default Values from SAP Memory

The MEMORY-ID option of the PARAMETERS statement allows you to use a default value from the global SAP memory (SPA/GPA parameters). The syntax is as follows:

Syntax

PARAMETERS ...... MEMORY ID <pid>......

When you use this option, the value stored at that point under the name <pid> in the global user-related SAP memory appears as the default value for on the selection screen.

<pid> can be up to 3 characters long and must not be enclosed in quotation marks.

You use the global SAP memory to pass values retained beyond transaction limits between programs. This memory is available to a user for the entire duration of a terminal session and any parallel sessions use the same memory. The SAP memory is thus more comprehensive than the transaction-bound ABAP/4 memory (see Data Clusters in ABAP/4 Memory).

Parameters can be set user specific in the user's master records with the name <pid>. For further information about the SAP memory, refer to the keyword documentation for SET/GET PARAMETER and to Passing Data Between Programs.

The following report stores a value under the name "HK" in the global SAP memory:

REPORT SAPMZTS1.

SET PARAMETER ID 'HK' FIELD 'Test Parameter'.

This value is used in the following report as a default value for the parameter TEST:

PROGRAM SAPMZTS2.

PARAMETERS TEST(16) MEMORY ID HK.

The selection screen of SAPMZTS2 looks as follows:

regards

Shiva

Re: how to store selection parameter value in memory

Former Member — Tue, 16 Oct 2007 07:19:09 GMT

selection screen parameters values can be stored in variants

enter the vlues in the selection screen

and click n the save button then it will ask you to enter variant name

after saving this variant

in application tool bar one more button adds like variants if you click there you will find variants created for that selection screen

you can create anynumber of variants

in feture you can select that variant that values will come automatically

Reward if usefull

Re: how to store selection parameter value in memory

Former Member — Tue, 16 Oct 2007 07:26:53 GMT

hi laxman,

if you want to store the value in ABAP memory then

use EXPORT <Parameter> TO MEMORY ID id.

to retreive the value form ABAP memory.

use IMPORT <parameter> from MEMORY ID id.

if you want to store the value in SAP memory

OR

if u want to store the values as variants.

give the values in sel screen.

and save them as variants by providing a name to that variant.

use SET PARAMETER ID pid FIELD dobj.

to retreive the value from SAP memory

use GET PARAMETER ID pid FIELD dobj.

Reward points if useful

Chandra

Message was edited by:

Chandrasekhar Velpula

Re: how to store selection parameter value in memory

Former Member — Tue, 16 Oct 2007 07:33:21 GMT

hi,

use abap memory statements [IMPORT ...... FROM ........] and [EXPORT ........ TO ......] and sap gloabal memory statements [SET PARAMETER] and [GET PARAMETER] u can do it.

for ex:

f you want to store the value in ABAP memory then

use EXPORT <Parameter> TO MEMORY ID id.

to retreive the value form ABAP memory.

use IMPORT <parameter> from MEMORY ID id.

if you want to store the value in SAP memory

use SET PARAMETER ID pid FIELD dobj.

to retreive the value from SAP memory

use GET PARAMETER ID pid FIELD dobj.

if helpful reward some points.

with regards,

Suresh Aluri.

Re: how to store selection parameter value in memory

laxman_sankhla3 — Tue, 16 Oct 2007 07:34:02 GMT

hi i want to store movement type value in memory and than i want to use that movement type,

TCODE - MB1A.

thanks.

Re: how to store selection parameter value in memory

Former Member — Tue, 16 Oct 2007 07:34:38 GMT

good

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:

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.

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:

REPORT BOOKINGS NO STANDARD PAGE HEADING.

TABLES SBOOK.

START-OF-SELECTION.

WRITE: 'Select a booking',

/ '----

SKIP.

GET SBOOK.

WRITE: SBOOK-CARRID, SBOOK-CONNID,

SBOOK-FLDATE, SBOOK-BOOKID.

HIDE: SBOOK-CARRID, SBOOK-CONNID,

SBOOK-FLDATE, SBOOK-BOOKID.

AT LINE-SELECTION.

SET PARAMETER ID: 'CAR' FIELD SBOOK-CARRID,

'CON' FIELD SBOOK-CONNID,

'DAY' FIELD SBOOK-FLDATE,

'BOK' FIELD SBOOK-BOOKID.

CALL TRANSACTION 'BOOK'.

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.

reward point if helpful.

thanks

mrutyun^