‎2008 Apr 30 8:21 PM
I am calling Report1 from Report 2.
I am using SUBMIT REPORT1 AND RETURN.
Call transaction method is used in report 1 to make some changes on a screen . have code for saving it.
This part is processed well. When the control gets back to report2(i have to do something else on the same screen) and when I see the screen... the changes made with report1 are not seen. It reflects the old data itself.
Do I need to use Commit stmt after submit? to retain the changes.
Plz help.
thanks
‎2008 Apr 30 8:23 PM
You need to refresh your report data in report2 and rewrite the list again.
Regards,
Naimesh Patel
‎2008 Apr 30 8:27 PM
hi alchemi,
Here you do not need to specify a destination. ... If the update is triggered locally because of the COMMIT WORK statemen
pls see the below links they may help yout
https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=doIneedtouseCommitstatementaftersubmit+++&adv=false&sortby=cm_rnd_rankvalue
www.geocities.com/sapcircle/questions2.
www.geocities.com/sapcircle/questions2.
thanks
sagar
<REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Apr 30, 2008 3:42 PM
‎2008 Apr 30 8:39 PM
Which screen are u talking about?
Is that a database change?
When you come back from called report to calling report, the internal session of the called report gets deleted(and hence the program context gets deleted). Therefore, all the temperory changes will wipe out.
If you started a transaction using CALL TRANSACTION T_CODE and that transaction uses update techniques, you can use the UPDATE ... addition to specify the update technique asynchronous (default), synchronous, or local that the program should use.
G@urav.