Skip to Content
Former Member
Sep 26, 2007 at 05:07 PM

Encapsulated transaction call from a (sub) screen


Hi all,

i want to built a customer transaction what calls an amodal window movable over the calling session and i want to display a standard transaction in the underlying original session, e.g. FB03.

My problem is, that when i have opened the amodal window and i call FB03 afterwards, the amodal window is closed. If i leave FB03 i run trough the PBO of my calling screen and i reopen the amodal window again.

So: Is there any chance, to encapsulate the called transaction, so that it is displayed in my calling window without terminating the transaction what has called it? From a subscreen? From a container?

I remember that similar standard functionality may exist in workflows, but i am not sure.

Thanks in advance for any hints.