How to generate the return code automatically through EP

Question

Hello all,
           I have created a transaction Iview and i am calling transaction SE16 to which i am passing application parameter as the table name which i want to see.Now i am getting the SE16 screen with the table name successfully passed on to the input field. But i want the Iview to process this screen also so that i dont have to press enter to see the next screen. i want this iview to process the SE16 screen directly and show me the next screen. I dont know how can i pass the return code parameter which will directly execute the table name entered in SE16 screen.suppose my table name is "ABC" and i have set the application parameter as DATABROWSE-TABLENAME=ABC&~okcode=ANZE where ANZE is the sy-ucomm value.Plz reply at the earliest.
Thanks and regards,
Alpa Desai.

Answer 1

Madden wrote:
I do think OOP can only complement procedural programming,Wrong. They don't have to have anything to do with each other.
but I just wish for my app to exit the same way whether I return or not an exit code.
I mean we are talking about the implementation, or the system, here.
Simply let it end and the "return code" will be 0.
But ... is there a way for a Java application to execute another Java application ? The analog for CreateProcess, but in the Java world ?Start a thread and call the main method of the class that kicks it off with the necessary arguements is one way.
When an Java app executes another Java app will a new VM be created ?Runtime.getRuntime().exec() and call java ...... Which will, obviously, start a new VM.
Is ther an internal way, for this that will work inside the same VM ?See the thread situation above.
How will the parent get the exit code from the child ?If called with Runtime simply call System.exit and then (from the original program) evaluate the return code (see the Runtime and Process classes).
If called in a thread, without using Runtime.exec any where, then you use a return at the end of the main method, but, if you are looking for a "return code" from an entire application, you're probably looking at Runtime.exec anyway. Otherwise, you are better of writing it so that it can be used in a real OOP manner (i.e. you don't have to call the main method of another application at all, you simply start instantiating and using the classes involved), in which case, a "return code" from the "application" is meaningless.
>
Timothy Madden,
RomaniaEdited by: masijade. on Nov 19, 2007 10:18 AM