topic update screen 0 in Application Development and Automation Discussions

update screen 0

Former Member — Thu, 25 Jan 2007 11:48:58 GMT

Hi everyone!

I am newby to ABAP, so hopefully I count on your help

In my report, I start from reading a database and outputing the content to a list (this is my screen 0). I have a nice header on this list.

Then I perform some data manipulation (adding/deleting/modifing records) via screen 100.

In PAI, I make changes to the database and commit. Afterwards I return to screen 0.

Now I would like the output on screen 0 updated (i.e. new entries should appear on the list).

Please, give me a hint how to manage that.

Kind regards

Rafal

Re: update screen 0

Former Member — Thu, 25 Jan 2007 11:52:38 GMT

before u go back to screen 0 , write this statement and chekout if it works

SUBMIT <REPORT NAME>

Re: update screen 0

Former Member — Fri, 26 Jan 2007 08:02:17 GMT

Thank Chandrasekhar!

Your idea is called "recurency", I guess. I wasn't sure if it is possible in ABAP, but fortunately it is. First I was affraid that SUBMIT opens another session and can not be efficient. Then I found the issue in an ABAP guide (<i>Sap Bc Abap Programming - 1540 Pages</i>). Below I put the information for those who may ask the same question in the future.

<b>Memory Organization in Program Calls</b>

The first ABAP program in a session on the application server opens its own internal session (roll area) within the main session. All externally-called procedures [Page 451] run in the same internal session as the calling program, that is, the main program and working data of the procedure are loaded into the same memory area in the internal session. When you call an executable program or a transaction, the system opens a new internal session for each program. Here, there are two possible cases: If the second program does not return

control to the calling program when it has finished running, the called program replaces the calling program in the internal session. The contents of the memory of the calling program are deleted. If the second program does return control to the calling program when it has finished running, the session of the called program is not deleted. Instead, it becomes inactive, and its memory contents are placed on a stack. The system can open up to 9 further internal sessions in external program calls. See also Memory Structures of an ABAP Program [Page 66].

Thanks once more and regards

Re: update screen 0

Former Member — Fri, 26 Jan 2007 08:05:19 GMT

If ur problem is solved with my answer then the 10 points should be mine )))