SPA/GPA PARAMETERS

hi all,
i am using set parameter id to call my module pool program from another report.now i wants to clear the value in the parameter id which is displayed when i start the transacion indivually,please let me know how can i do it.thanks alot

thanks solved by my self
when i press back button i write
set parameter id 'NAME' field space.

Similar Messages

Clearing user parameters (SPA/GPA)

Hi all,
I have a program which calls SAP transactions in interactive mode (CALL TRANSACTION with mode 'A').
When the user works with the called transactions, I want input fields not to be filled according to the user parameters (SPA/GPA parameters).
Anybody knows how to disable GPA in a called transaction or simply clear all the user specific parameters for this session?
Thanks,
Dror

May be the solution by Marcin will interest you: how to empty current user sap memory

Issue regarding SAP/GPA parameters

Issue : When Sales Order, Delivary, Transfer Order, Billing is created by one user , and if the same user creates Sales Return Order(VA01) it is working fine. But if any other user creates this Sales Return then it is not showing Sales Return AMOUNT value which has to be copied from the Billing Dcoument.
This Sales Return transaction calling Form Routine which contains code to get Sales Return value . when same user who created Sales Order, Delivary, Transfer Order, Billing creates Sales Return then SPA/GPA PARAMETERs used in Form Routine program to get Reference Billing Document no.,etc , are getting populated by values , but if different user creates Sales Return this SAP/GPA PARAMETERS is not getting populated. i.e
DATA V_VBELN TYPE VBELN.
GET PARAMETER ID 'VF' FIELD V_VBELN .
why it is not getting populated plz help

Hi M Kumar,
Please note SPA / GPA are user specific, hence if same user creates Sales Return Order values will be copied from previously created document, while it will not be copied for other user.
Set Parameter : "Writes the contents of the field f to the global user-specific SAP memory and the local transaction-specific SAP memory under the ID pid. "
Regards,
Mohaiyuddin

What is SPA/GPA?

Hi All,
Can any body tell what is GPA and SPA?
Thanks,
Sriram.

Hi Sriram,
Every time a usr is logged in, SAp reserves a specific memory area which is user-specific area which can be accessed by user sessions.
SPA/GPA are special memory parameters that an ABAp program can access and are stored in the SAP memory. They are also called SET/GET parameters. These parameters can have names up to 20 characters. In SU01, under parameters tab, you can see the user specific parameter values.
All SPA/GPA parameters are stored in table TPARA which can be maintained.
You can use them in transactions by setting the 'Parameter ID' attribute of a screen field.
Read documentation for SET or GET parameter.
Regards,
Srinivas

DB SPA/Gpa

what is the difference bet SAP mry/ ABAP mry?
what is views?
interactive / classical reproting?
synchronous/ asynchronous?
Pts will be awarded

Hi
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
ABAP/4 Memory =>
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.
View=>
view is, in essence, a virtual table. It does not physically exist. Rather, it is created by a query joining one or more tables.
Creating a VIEW
The syntax for creating a VIEW is:
CREATE VIEW view_name AS
SELECT columns
FROM table
WHERE predicates;
Interactive Report=>
An interactive report generally works in the following fashion:
1. Basic list is displayed.
2. User double clicks on any valid line
    or
    User selects a line and presses as button on the tool bar.
3. The corresponding event is triggered
4. Then in the code, the line on which action was done, is read.
5. Depending on the values in that selected line, a secondary list is displayed.
6. Steps from 2-5 are repeated till the end.
Classical Report=>
THE LIST PRODUCED BY CLASSICAL REPORT DOESN'T allow user to interact with the system
    the list produced by interactive report allows the user to interact with the system.
b) ONCE A CLASSICAL REPORT EXECUTED USER LOOSES CONTROL.IR USER HAS CONTROL.
c) IN CLASSICAL REPORT DRILLING IS NOT POSSIBLE.IN INTERACTIVE DRILLING IS POSSIBLE
Synchronous=>
In synchronous update, you do not submit an update request using CALL FUNCTION... IN UPDATE TASK. Instead, you use the ABAP statement COMMIT WORK AND WAIT. When the update is finished, control passes back to the program. Synchronous update works in the same way as bundling update requests in a subroutine (PERFORM ON COMMIT). This kind of update is useful when you want to use both asynchronous and synchronous processing without having to program the bundles in two separate ways.
Asynchronous =>
Asynchronous calls are the default if the UPDATE parameter is not specified. Asynchronous calls do not effect the return code (sy-subrc).
Note - This is opposite of how synchronous/asynchronous workflow tasks behave, in the sense that control is returned to the workflow in a synchronous step even if there is no commit or rollback encountered!
I hope this will give you some idea to solve your problem.
Thanks
Mrutyunjaya Tripathy

How to create a SPA/GPA parameter ?

Dear Experts,
Please help me in creating a new SPA/GPA parameter. Please let me know the procedure to this creation.
Thanks in advance.

Hi S R,
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.
Regards,
Tanveer.
Please mark helpful answers.

SPA/GPA parameter

hello,i want to insert SPA/GPA parameter to the standard datasheet of sap,how can i do,thank you.
otherwise,i want to insert search help to the standard datasheet of sap,that how can i do,thank you.

Go to SM30 enter the table name TPARA and click on MAINTAIN where u can give the Parameter names
OR
You can do that by going to SE80. Display the development class, right-click on the Development Class name and choose the option Create - >More - > SET / GET Parameter ID.
Regards
- Gopi

Spa gpa parameter values are not getting in badi

Dear all,
i am filling the material value in MIGO transaction tabstrip . and i written the code in MB_MIGO_BADI . i am not getting the values in migo badi i written the stmt
GET parameter id 'MAT' FIELD V_MATNR. it is giving the sy-subrc 4 . while dubuging i check the ABAP MEMORY but it is not showing the P-ID MAT in it.
kindly help.

Have you checked Organization Access to ensure that no one restricted that org?
Or shipping grants and roles?
I think there are quite a few places that you can restrict access.

Job scheduling(passing the values to the child program)

when i'm trying to schedule a background job(using job_open job_submit and job_close) i'm passing the values of the selection screen(parent program) to my child program using set parameter id. And trying to get the values using get parameter id in the cild program.
But the values of the parent program are not being passed to the child program what may be the cause for it?

rathan,
Why con't you use
SUBMIT... [VIA SELECTION-SCREEN]
[USING SELECTION-SET <var>]
[WITH <sel> <criterion>]
[WITH FREE SELECTIONS <freesel>]
[WITH SELECTION-TABLE <rspar>].
When you start an executable program, the standard selection screen normally appears, containing the selection criteria and parameters of both the logical database connected to the program and of the program itself (see Direct Execution - Reports). When you start an executable program using SUBMIT, there are various additions that you can use to fill the input fields on the selection screen:
SUBMIT... [VIA SELECTION-SCREEN]
[USING SELECTION-SET <var>]
[WITH <sel> <criterion>]
[WITH FREE SELECTIONS <freesel>]
[WITH SELECTION-TABLE <rspar>].
These options have the following effects:
VIA SELECTION-SCREEN
The selection screen of the called executable program (report) appears. If you transfer values to the program using one or more of the other options, the corresponding input fields in the selections screen are filled. The user can change these values. By default, the system does not display a selection screen after SUBMIT.
USING SELECTION-SET <var>
This option tells the system to start the called program with the variant <var>.
WITH <sel> <criterion>
Use this option to fill individual elements <sel> of the selection screen (selection tables and parameters). Use one of the elements <criterion>:
<op> <f> [SIGN <s>], for single value selection
If <sel> is a selection criterion, use <op> to fill the OPTION field, <f> to fill the LOW field, and <s> to fill the SIGN field of the selection table <sel> in the called program.
If <sel> is a parameter, you can use any operator for <op>. The parameter <sel> is always filled with <f>.
[NOT] BETWEEN <f1> AND <f2> [SIGN <s>], for interval selection
<f1> is transferred into the LOW field, <f2> into the HIGH field, and <s> into the SIGN field of the selection table <sel> in the called program. If you omit the NOT option, the system places the value BT into the OPTION field; if you use NOT, the system fills OPTION with NB.
IN <seltab>, transferring a selection table
This addition fills the selection table <sel> in the called program with the values of the table <seltab> in the calling program. Table <seltab> must have the structure of a selection table. Use the RANGES statement to create selection tables.
WITH FREE SELECTION <freesel>, user dialog for dynamic selections
To use this option, the called program must be connected to a logical database that supports dynamic selections. In the calling program, use the function modules FREE_SELECTIONS_INIT and FREE_SELECTIONS_DIALOG. They allow the user to enter dynamic selections on a selection screen. One export parameter of these function modules has structure RSDS_TEXPR from the RSDS type group. Transfer the values of this export parameter by means of the internal table <freesel> of the same structure to the called report.
WITH SELECTION-TABLE <rspar>, dynamic transfer of values
You need an internal table <rspar> with the Dictionary structure RSPARAMS. The table then consists of the following six fields:
SELNAME (type C, length 8) for the name of the selection criterion or parameter
KIND (type C, length 1) for the selection type (S for selection criterion, P for parameter)
SIGN, OPTION, LOW, HIGH as in a normal selection table, except that LOW and HIGH both have type C and length 45.
This table can be filled dynamically in the calling program with all of the required values for the selection screen of the called program. If the name of a selection criterion appears more than once, the system creates a multiple-line selection table for that criterion in the called program. If the name of a parameter appears more than once, the system uses the last value. Note that LOW and HIGH have type C, so that the system executes type conversions to the criteria of the called program. This is important for date fields, for example. Before your program is used in a live context, you should check it using the VIA SELECTION-SCREEN addition.
Except for WITH SELECTION-TABLE, you can use any of the above options several times and in any combination within a SUBMIT statement. In particular, you can use the WITH <sel> option several times for one single criterion <sel>. In the called program, the system appends the corresponding lines to the selection tables used. For parameters, it uses the last value specified. The only combination possible for the WITH SELECTION-TABLE option is USING SELECTION-SET.
If the input fields on the selection screen are linked to SPA/GPA parameters, you can also use this technique to pass values to the selection screen (see Passing Data Between Programs).
The following executable program (report) creates a selection screen containing the parameter PARAMET and the selection criterion SELECTO:
REPORT demo_program_submit_rep1.
DATA number TYPE i.
PARAMETERS      paramet(14) TYPE c.
SELECT-OPTIONS selecto FOR number.
The program DEMO_PROGRAM_SUBMIT_REP1 is called by the following program using various parameters:
REPORT demo_program_submit_sel_screen NO STANDARD PAGE HEADING.
DATA: int TYPE i,
      rspar TYPE TABLE OF rsparams,
      wa_rspar LIKE LINE OF rspar.
RANGES seltab FOR int.
WRITE: 'Select a Selection!',
SKIP.
FORMAT HOTSPOT COLOR 5 INVERSE ON.
WRITE: 'Selection 1',
     / 'Selection 2'.
AT LINE-SELECTION.
CASE sy-lilli.
    WHEN 4.
      seltab-sign = 'I'. seltab-option = 'BT'.
      seltab-low = 1.   seltab-high   = 5.
      APPEND seltab.
      SUBMIT demo_program_submit_rep1 VIA SELECTION-SCREEN
                      WITH paramet eq 'Selection 1'
                      WITH selecto IN seltab
                      WITH selecto ne 3
                      AND RETURN.
    WHEN 5.
      wa_rspar-selname = 'SELECTO'. wa_rspar-kind = 'S'.
      wa_rspar-sign = 'E'. wa_rspar-option = 'BT'.
      wa_rspar-low = 14. wa_rspar-high = 17.
      APPEND wa_rspar TO rspar.
      wa_rspar-selname = 'PARAMET'. wa_rspar-kind = 'P'.
      wa_rspar-low = 'Selection 2'.
      APPEND wa_rspar TO rspar.
      wa_rspar-selname = 'SELECTO'. wa_rspar-kind = 'S'.
      wa_rspar-sign = 'I'. wa_rspar-option = 'GT'.
      wa_rspar-low = 10.
      APPEND wa_rspar TO rspar.
      SUBMIT demo_program_submit_rep1 VIA SELECTION-SCREEN
                      WITH SELECTION-TABLE rspar
                      AND RETURN.
ENDCASE.
Pls. reward if useful...

Set and get parameter id

Hi,
I need to store one variable value and I need to retrieve the same variable value in same program. For this I have written set and get parameter ids in the same program. It is working fine but if I log off the system and if I logon the system it is not working I mean before log off the variable is showing some value if I log on again that variable is showing empty. But I want to capture the field values after log off and log on also. Is there any other option can I use table?
Please help me I will give points.
Thanks.

Hi
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 <b>TPARA</b>.
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

How to use SET and GET parameter commands ?

Explain these two giving an example?As which is used for what?

Hi Albert,
         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.
Cheers
Nishanth

How to call a dialog program with return value in another dialog program

Dear All,
How can I call a dialog program with return value from another dialog program?
Regards,
Alok.

Hi Alok,
You can you SET/GET parameters to do this.
This is some information about this.
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 PARAMETERstatements.
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 ID pid can be up to 20 characters long. If there was already a value stored under pid, this statement overwrites it. If you double-click pid in the ABAP Editor, parameters that do not exist can be created as a Repository object.
To read an SPA/GPA parameter, use:
GET PARAMETER ID pid FIELD f.
This statement places the value stored under the pid ID into the variable f. If the system does not find any value for pid in the SAP memory, sy-subrc is set to 4. Otherwise, it sets the value to 0.
Thanks,
SriRatna

How to restrict running of report in foreground

My requirement is that, the user should not be allowed to run the report in foreground. Since there is a high possibility for the report to go to time-out.. I want to force the user to run it in background only.. How can we do that ? IS it Basis related or .. can it be done in abap ?
Thanking you..
Shankar

Hi Shankara,
Here is what is happening with your logic.
1. User is running the program and got to the selection screen.
2. User enters the selection values and then presses execute.
3. User gets the diaolog box asking him whether the program should be run in the background.
4. User says yes and you are doing the submit of your program.
The problem lies in the step 4 where you are submitting your program.
Remember, when you submit a program, you are supposed to have passed the selection screen data in one of the standard ways of passing the data which is either creating a variant and passing the variant to the job, or use SPA/GPA parameters if relevant or any other method.
Since you are calling your program again within the same program, but without passing the selection screen values, your program is failing. Here is a sample program to achieve what you are trying to achieve.
REPORT ztest.
PARAMETERS: p_vbeln LIKE vbak-vbeln,
            p_bkrun NO-DISPLAY.
DATA: ls_vbak LIKE vbak.
DATA: v_answer,
      v_jobcount LIKE tbtcjob-jobcount.
IF p_bkrun IS INITIAL.
*-- not background processing
    CALL FUNCTION 'POPUP_TO_CONFIRM_STEP'
         EXPORTING
              textline1      = 'This may time out.'
              textline2      = 'Do you want to run in background?'
              titel          = 'Warning!!!'
              cancel_display = space
         IMPORTING
              answer         = v_answer.
    IF v_answer = 'J'.
*-- run in the background
      CALL FUNCTION 'JOB_OPEN'
           EXPORTING
                jobname          = 'ZTEST'
           IMPORTING
                jobcount         = v_jobcount
           EXCEPTIONS
                cant_create_job = 1
                invalid_job_data = 2
                jobname_missing = 3
                OTHERS           = 4.
      IF sy-subrc <> 0.
        MESSAGE ID sy-msgid TYPE 'E' NUMBER sy-msgno
                WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
        EXIT.
      ENDIF.
*-- submit the program in the background
      SUBMIT ztest
        WITH p_bkrun = 'X'
        WITH p_vbeln = p_vbeln
        USER sy-uname
        VIA JOB 'ZTEST' NUMBER v_jobcount AND RETURN.
*-- close the job
      CALL FUNCTION 'JOB_CLOSE'
           EXPORTING
                jobcount             = v_jobcount
                jobname              = 'ZTEST'
                strtimmed            = 'X'
           EXCEPTIONS
                cant_start_immediate = 1
                invalid_startdate    = 2
                jobname_missing      = 3
                job_close_failed     = 4
                job_nosteps          = 5
                job_notex            = 6
                lock_failed          = 7
                OTHERS               = 8.
      IF sy-subrc <> 0.
        MESSAGE ID sy-msgid TYPE 'W' NUMBER sy-msgno
                WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
      ENDIF.
      EXIT.
    ELSE.
      CLEAR v_answer.
    ENDIF.
ENDIF.
CHECK v_answer IS INITIAL.
SELECT SINGLE * FROM vbak
                  INTO ls_vbak
                 WHERE vbeln = p_vbeln.
IF sy-subrc <> 0.
    WRITE:/ 'Invalid Order Id.'.
ENDIF.
END-OF-SELECTION.
CHECK v_answer IS INITIAL.
IF p_bkrun IS INITIAL.
    WRITE:/ 'Here is the result running the program in foreground.'.
ELSE.
    WRITE:/ 'Here is the result running the program in background.'.
ENDIF.
WRITE:/ ls_vbak-vbeln,
          ls_vbak-vkorg.
Let me know if you have any questions.
Srinivas

How to preset fields in TA BP with default values

Hi!
I want to fill few fields in transaction BP with default values.
This should be if there`s a new business partner to insert.
If i can do this depending on the selected role it was the best
First i thought on SPA/GPA-parameters ... but then i can`t do it in depence on the selected role.
In customizing i can tell only if a field should be displayed or not, for input or not, ... but no values to insert.
Is here anybody with a good idea for me?
Thanks a lot in advance.
Best regards,
Ingo
Edited by: Ingo Schmökel on Jul 1, 2008 7:20 PM

Hi,
There is one possibility which requires an enhancement of the
BDT event ISDAT and a call to the function module
BUP_BUPA_FIELDVALUES_SET. This means that an ISDAT function module needs to be written (transaction BUS7) which calls the function module BUP_BUPA_FIELDVALUES_SET with the needed values that are to be defaulted. You can read the role value using BUS_PARAMETERS_ISSTA_GET (T_RLTYP).The fields which are possible can be found in the DDIC structure BUSDEFAULT. However this is limited only to the fields inside this structure.
Thanks and warm regards,
Smita.

How to preset fields in a transaction BP with default values

Hi!
I want to fill few fields in transaction BP with default values.
This should be if there`s a new business partner to insert.
If i can do this depending on the selected role it was the best
First i thought on SPA/GPA-parameters ... but then i can`t do it in depence on the selected role.
In customizing i can tell only if a field should be displayed or not, for input or not, ... but no values to insert.
Is here anybody with a good idea for me?
I`ve posted my question first in crm-section but i think here it`s better
Thanks a lot in advance.
Best regards,
Ingo

Hi,
There is one possibility which requires an enhancement of the
BDT event ISDAT and a call to the function module
BUP_BUPA_FIELDVALUES_SET. This means that an ISDAT function module needs to be written (transaction BUS7) which calls the function module BUP_BUPA_FIELDVALUES_SET with the needed values that are to be defaulted. You can read the role value using BUS_PARAMETERS_ISSTA_GET (T_RLTYP).The fields which are possible can be found in the DDIC structure BUSDEFAULT. However this is limited only to the fields inside this structure.
Thanks and warm regards,
Smita.

SPA/GPA PARAMETERS

Similar Messages

Maybe you are looking for