Execute Transactions using Docking Container Tree Controls

[Former Member]

Hello

Can somone please provide a sample ABAP code to execute Transactions using Docking Container Tree Controls, the requirement can be described as below :-

1. Opening Screem will have 2 windows split vertically.. smaller left hand window and wider right hand window

2. Left Hand Window should contain Transaction Codes classified in a tree like structure

3. When user double clicks on any transaction code, the report/module pool should run in the right hand window with normal flow logic within the right hand window. During this time the left hand window with transaction codes should continue to be visible

4. User may abort executing the right hand window at any stage and double click on new transaction code on left hand window for new process to continue

5. It would be great if this program can run as a trasactional iview on portal too

Thanx

Jibu

[Former Member]

Hi,

To me Transaction SE80 and ABAPDOCU looks similar to your requirement...may be you could just get a hint if you analyse the programs running SE80 and ABAPDOCU...

[Former Member]

Yes ... ABAPDOCU provides the Split Windows and Tree

however it does not execute the program on the right hand window keeping left hand window intact

[lijisusan_mathews]

what you do is :

Create a screen and place one custom container( on left) and 1 sub-screen( on right).

In the custom container, add your tree ( make sure you add double_click event for it) . Now add your transaction list in this.

Now in the sub-screen part, in the flow logic, make sure you do not specify the sub-screen number directly. Instead you pass variables , say W_DYNNR.

Now for each transaction you have to create separate screens( actually sub-screen, it has to come in the sub-screen to the right) .

When you do this, create it in such a way that you add a selection screen sub-screen ( for selection on top ) and a custom container below ( for output ). So when you execute, values will come down.

Now to display the report when you double click on the tree nodes, in the double)click event, just set the W_DYNNR value for that transaction.. this method should solve your issue. Sorry I could not write a code for you at this time

Suzie.

[Former Member]

Thanx Suzie ... your idea about having tree and subscreen will definitely work ... but how do we submit a report by passing the relevant parameters dynamically without over-writing current session ... we can use "submit (<report>) exporting list to memory and return" and later used FM LIST_FROM_MEMORY to read the list ... then the challenge is to show this as ALV list in the output container below subscreen .. cheers