Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

get,set & import,export

Former Member
0 Likes
492

could u plz explain in detail about GPA,SPA and import,export parameters.

thank u in advance

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
445

hai

In Short

- Using SPA/GPA parameters (SAP memory)

- Using EXPORT/IMPORT data (ABAP/4 memory)

In Long

We can pass data to a called program using SPA/GPA parameters. SPA/GPA parameters are field values saved globally in memory. Each parameter is identified by a three-character code: you can define these parameters in the object browser by selecting other objects on the first screen. The SPA/GPA storage is user-specific and valid throughout all the user's sessions. By using the SET PARAMETER or GET PARAMETER statements these statements let you store and retrieve SPA/GPA values from an ABAP/4 program. If the selection screens for the two transactions do not share the same required fields, use these statements to store screen fields explicitly by name. Before calling the new transaction from a PAI module, store the caller transaction's fields under one name:

SET PARAMETER ID 'RID' FIELD <FIELD NAME1>.

The system stores the value in <field name1> in the

SPA parameter 'RID'. The three-character identifier 'RID' must be defined in the SAP table TPARA. If the SPA parameter 'RID' already contains a value, the SET PARAMETER statement overwrites it (with the contents of <FIELD NAME1>).

In the PBO module for the called transaction, retrieve the fields under the other name:

GET PARAMTER ID 'RID' FIELD <FIELD NAME2>.

**Please reward suitable points***

With Regards

Navin Khedikar

2 REPLIES 2
Read only

Former Member
0 Likes
446

hai

In Short

- Using SPA/GPA parameters (SAP memory)

- Using EXPORT/IMPORT data (ABAP/4 memory)

In Long

We can pass data to a called program using SPA/GPA parameters. SPA/GPA parameters are field values saved globally in memory. Each parameter is identified by a three-character code: you can define these parameters in the object browser by selecting other objects on the first screen. The SPA/GPA storage is user-specific and valid throughout all the user's sessions. By using the SET PARAMETER or GET PARAMETER statements these statements let you store and retrieve SPA/GPA values from an ABAP/4 program. If the selection screens for the two transactions do not share the same required fields, use these statements to store screen fields explicitly by name. Before calling the new transaction from a PAI module, store the caller transaction's fields under one name:

SET PARAMETER ID 'RID' FIELD <FIELD NAME1>.

The system stores the value in <field name1> in the

SPA parameter 'RID'. The three-character identifier 'RID' must be defined in the SAP table TPARA. If the SPA parameter 'RID' already contains a value, the SET PARAMETER statement overwrites it (with the contents of <FIELD NAME1>).

In the PBO module for the called transaction, retrieve the fields under the other name:

GET PARAMTER ID 'RID' FIELD <FIELD NAME2>.

**Please reward suitable points***

With Regards

Navin Khedikar

Read only

Former Member
0 Likes
445