WHY WE USE IMPORT EXPORT PARAMETERS ?

[Former Member]

hI,

WHY WE USE IMPORT EXPORT PARAMETERS ?

Can any one give me example of that ?

Regards,

Gurprit

[Former Member]

hi,

example first use

export fieldname to memory id 'PRN'.

memory id should be 3 charecter

and then use import

import fieldname to memory id 'PRN'.

memory id should be same and the fieldname should be of same data type.

regards,

Santosh Thorat

[Former Member]

Hi Gurprit,

If you want to pass some data.. internal table or a global variable with some value from one program to another program/User Exit/Badi/FM within the same session then you need to use IMPORT/EXPORT parameters.

Program 1

Has itab1 data... with 100 records

It will export itab1 to program2

Program 2 ..is based on the 100 records from program 1..

so program 2 will import those 100 records from itab1

Best regards,

Prashant

[Former Member]

Hi

It is used for Exporting and Importing data from 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

SAP global memory retains field value through out session.

set parameter id 'MAT' field v_matnr.

get parameter id 'MAT' field v_matnr.

They are stored in table TPARA.

ABAP memory is a memory area that all ABAP programs within the same internal session can access using the EXPORT and IMPORT statements. Data within this area remains intact during a whole sequence of program calls. To pass data

to a program which you are calling, the data needs to be placed in ABAP memory before the call is made. The internal session of the called program then replaces that of the calling program. The program called can then read from the ABAP memory. If control is then returned to the program which made the initial call, the same process operates in reverse.

ABAP memory is temporary and values are retained in same LUW.

export itab to memory id 'TEST'.

import itab from memory Id 'TEST'.

Here itab should be declared of same type and length.

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

ABAP Memmory & SAP Memmory

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

http://www.sap-img.com/abap/type-and-uses-of-lock-objects-in-sap.htm

Regards

Anji

[Former Member]

Hi,

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.

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.

Thanks,

Reward If Helpful.

[Former Member]

are guru....

import and export parameters are for print settings in smartforms...

points man...