‎2011 Mar 30 7:50 AM
Folks,
I have this piece of coding in my program:
SET PARAMETER ID 'XXX' FIELD YYY-12345.
CALL TRANSACTION 'ABCD'
AND SKIP FIRST SCREEN.
SM30 for the transaction XXX has the following default values:
Transaction Code = ABCD
Skip initial screen
Transaction SM30
Default Values UPDATE = x
-
Now I wish to avoid the parameter id because if the user goes to tr SU3 (own data via session manager) and there sets the value
of the parameter ID to another table or view which they should not be able to access directly from this program.
Any help is appreciated.
‎2011 Mar 30 8:46 AM
Hi ,
You can assign Authorization Group to maintenance tables and restrict users.
SE11->TM Generator(From menu)->Authorization Group
‎2011 Mar 30 9:06 AM
Hi,
you can create a parameter transaction in SE93.
Fill it with those values:
Transaction: SM30
Skip initial screen: marked
Name of screen field: VIEWNAME
Value: *** here your table name ***
Name of screen field: UPDATE
Value: X
This transaction you can call in your report!
Regards
Klaus
‎2011 Mar 30 9:38 AM
Hello Klaus,
Many thanks for this good hint.
I have the following question:
1) Can I still continue my original coding " SET PARAMETER ...." before calling the transaction ? because the whole purpose was to solve the issue of user going to Tr SU3.
‎2011 Mar 30 10:36 AM
Hi,
you can continue to set the parameter, because it has no effect for the new parameter transaction, but I can't see the issue with SU3.
If a user changes the parameter value then he has'nt the needed authority automatically.
SET/GET parameters are set by standard transaction too. You can't avoid this, why to avoid this in your program?
Regards,
Klaus
‎2011 Mar 30 10:28 AM
Instead of using get and set parameter to pass a value to transaction ABCD you could use something like
call transaction 'ABCD' using bdcdata mode 'E' update 'S'with bdcdata holding the screen field you want to transfer to trancaction ABCD and a process code to skip the first screen.
Regards Jack
‎2011 Mar 30 12:16 PM
Hello Jack,
Thanks a lot for your valuable inputs.
can you let me how to avoid the initial screen ?
‎2011 Mar 30 12:25 PM
Hi, to avoid initial screen you need to add a process code in batch input table. the coding depends on the screen you are processing in transaction ABCD. Best is to create a batch input recording for your transaction, then analyse it and add the screen field(s) an processes code to your ABAP.
Here is an example for another tracaction code:
insert initial line into table bdcdata assigning <bdcdata>.
<bdcdata>-fnam = 'BDC_OKCODE'.
<bdcdata>-fval = '=ONLI'.Regards Jack