2016 Feb 22 10:49 AM
Hello Experts,
When Changing Report A it is nesecceary to use
SUBMIT Report B
WITH s_batch IN rt_charg
EXPORTING LIST TO MEMORY AND RETURN.
But in our case Report B is a Replica of Report A and we would not want to keep two identical programs to prevent the accumulation amount of information that we do not need making it difficult to categorize.
Is it possible to Submit the Same Report A but avoiding the endless loop. eg the first time it will submit Report A. When inside Report A there should be a condition that will prevent Sumbmision again Report A and continue the rest of the code.
Searching the web I have come across with inner session. I was thinking something like:
If inner session = 1 then:
SUBMIT Report A
WITH s_batch IN rt_charg
EXPORTING LIST TO MEMORY AND RETURN.
else.
exit.
Thanks in advance
2016 Feb 22 10:58 AM
Set a memory ID in the first report, read it in the second and if it's set then don't call it, or even better use the same enqueue function that SE38 uses to lock a program for change. Then in the second report try to lock the same record and if it fails don't do the submit.
With the memory ID you need to remember to clear it when you have finished.
Rich
2016 Feb 22 10:58 AM
Set a memory ID in the first report, read it in the second and if it's set then don't call it, or even better use the same enqueue function that SE38 uses to lock a program for change. Then in the second report try to lock the same record and if it fails don't do the submit.
With the memory ID you need to remember to clear it when you have finished.
Rich
2016 Feb 22 11:24 AM
Is it possible to provide some sample code because I am new to this. Thanks in advance!!
2016 Feb 22 12:20 PM