dock a container on a standard program

[Former Member]

Hello,

i want to create a docking container and dock it on standard programs. I use "call transaction" or "submit" to call a standard program. But the problem is i can't use my container duaring the standard program is runing. I suppose it is because of switching between different modes (internal and head mode or smth. like that). Do you have any idea to make my container active in both of the modes?

thank you very much for your help,

Anton

[Former Member]

Hello Anton,

It is not about the internal and head mode but it is about switching between screen and list processors. If you look at the

working of application server then you will find that every dialog step consist of set of instruction executed by screen as well as list processors so they execute in sequence that means once you start processing list then controlled is passed to list processor and to return to screen processor you need to switch back programmatically.

Thanks,

Augustin.

[Former Member]

Hi Augustin, thank you for your reply.

I just don't understand why can i see the docking container on dynpros of my z_report and there is no container more on dynpros of std.program?

If i do "call transaction xy." the program switches to screen processor, and i can't do anything until the user leaves the transaction xy.

[Former Member]

Hello Anton,

One possibility you can try is write docking container code in PBO of the screen from called transaction. Ofcouse this is only possible if transaction called is custom one or else you may check with some screen exit from where you can load docking container.

Enjoy SAP!

Thanks,

Augustin.

[RichHeilman]

The way the docking container works is, that you attach the docking container to the specific screen, so in order for you to get it to be visible in standard programs, you would have to change the code in the standard programs. You can't just attach it it externally. it doesn't work that way.

Regards,

Rich Heilman

[Former Member]

Hello Mr. Heilman,

but if i code:

CREATE OBJECT cl_docker

EXPORTING

no_autodef_progid_dynnr = 'X'

EXCEPTIONS

OTHERS = 6.

i do not attach it to the specific screen, but i have it on each dynpro i call (except the dynpros of std.program). That's why i thought there must be an opportunity to dock it on the dynpros of other Programs as well.

Regards,

Anton

[RichHeilman]

I was not aware of that parameter, so not sure. But if that does allow to attach to any screen in the sessions, i would bet that it is limited to the internal session, and not extend to other sessions like when you CALL TRANSACTION or SUBMIT.

Regards,

Rich Heilman

[Former Member]

Hello Anton,

I think you should try parameter lifetime.

lifetime

Lifetime management parameter specifying the lifetime of the control

cntl_lifetime_dynpro : The control remains alive for the lifetime of the screen (that is, while it remains in the screen stack). It is not destroyed, for example, by a call screen or call transaction statement.

For more information you can follow the link:

http://help.sap.com/saphelp_nw04/helpdata/EN/f5/4f6e0a9f2511d295cc00a0c930660b/frameset.htm

Thanks,

Augustin.