‎2009 Jul 16 10:20 AM
Hi all,
I have the following problem.
We have written an own transaction 'XYZ'. This transaction calls different other transactions.
We use the statement "call transaction <xyz> and skip first screen" with set/get parameters.
But when the users are in the transaction 'XYZ' with two or more modus the set/get parameter are wrong and the called transactions were showing wrong values.
How can I avoid this?
regards
‎2009 Jul 16 10:23 AM
Hi,
try like this.
set parameter id 'ANR' for <field>.
call transaction <xyz> and skip first screen.
Regards,
Vijay
‎2009 Jul 16 10:26 AM
Hi,
first in your transaction 'xyz' you need to lock your table entry with primary keys.So that other user cant open with same record.
second when you set the id set it with that primary key combination, so that it will be unique when user gets the same.
sample code
concatenate vbeln bukrs into p_string.
set parameter id p_string field v_pgmname
other program
get parameter id p_string field v_pgmname .regards
Sajid
Edited by: shaik sajid on Jul 16, 2009 11:26 AM
‎2009 Jul 16 10:28 AM
Try using SUBMIT satement as follows
for eg
SUBMIT rm07mlbd "prog name
WITH SELECTION-TABLE it_rspar EXPORTING LIST TO MEMORY
AND RETURN.
Fill it_rspar depending on the selection screen of called program
x_rspar-selname = 'WERKS'.
x_rspar-kind = 'S'.
x_rspar-sign = 'I'.
x_rspar-option = 'EQ'.
x_rspar-low = "VALUE to be passed"
CONDENSE x_rspar-low.
APPEND x_rspar TO it_rspar.
CLEAR x_rspar.