‎2006 Feb 23 12:33 PM
Hej together,
I'm stuck on the following:
I do have to rewrite an old inconsistency report to use new UI techniques instead of old lists.
At first a selection-screen is created. The criteria of this screen is checked using the event AT SELECTION-SCREEN wherein some database queries are done either.
Some of the results will be used later on in the event START-OF-SELECTION.
Inside START-OF-SELECTION I put the CALL on dynpro 100 (where my tree and grid etc. is placed for display). PBO100 does some additional queries based on the results of AT-SELECTION-SCREEEN-queries.
NOW:
If I do go back to the Selectionscreen via CALL SELECTION-SCREEN 1000, it'll jump to START-OF-SELECTION instead of executing the needed AT-SELECTION-SCREEN.
In result on dynpro 100 the hierarchy is built incorrectly.
Hope it's comprehensible
Thanks in advance for any suggestions.
hejda
BS
‎2006 Feb 23 12:55 PM
hi
Call selection-screen 1000 will can the start-of-selection.
instead use LEAVE to Screen 1000 which will goto the screen 1000 but it will not trigger at selection-screen.
it will trigger at selection-screen output.
hope it solves your problem
regards
kishore
‎2006 Feb 23 12:49 PM
Hi Boris,
try the at selection-screen output.
and don't call the dynpro 1000, try instead the leave to screen 1000.
Rgd
Frédéric
‎2006 Feb 23 12:49 PM
Hi,
I think if you directly make a call to the selection screen then system will execute from start-of-selection only. Can you try re-submitting the report program with the parameters you want for calculation at selection screen event?
Hope it will solve your issue.
Regards,
Jignesh
‎2006 Feb 23 12:55 PM
hi
Call selection-screen 1000 will can the start-of-selection.
instead use LEAVE to Screen 1000 which will goto the screen 1000 but it will not trigger at selection-screen.
it will trigger at selection-screen output.
hope it solves your problem
regards
kishore
‎2006 Feb 23 1:08 PM
Hello Boris...
I have following code and it works perfect
select-options s_matnr for mara-matnr.
at selection-screen output.
select single * from mara where matnr in s_matnr.
start-of-selection.
write : /'error'.
CALL SCREEN 100.
MODULE user_command_0100 INPUT.
save_code = ok_code.
CLEAR ok_code.
CASE save_code .
WHEN 'DISPLAY'.
IF radio1 EQ 'X'.
output = 'red'.
ELSEIF radio2 EQ 'X'.
output = 'green'.
ELSEIF radio3 EQ 'X'.
output = 'blue'.
ENDIF.
<b></b>
WHEN 'EXIT'.
call selection-screen 1000.
<b></b>
ENDCASE.
ENDMODULE. " USER_COMMAND_0100 INPUT
‎2006 Feb 24 10:02 AM
Hej,
thanks a lot for your responses. They were thought-provoking impulses.
After a certain period of time I found the error somewhere else. I used an old ABAP statement where it is not allowed in Objects.
I wanted to remark that LEAVE TO SCREEN or a SET SCREEN/LEAVE combination will not work with SELECTION SCREENS. They will abort dumping with something like 'could not process SEL.SCREEN via LEAVE' (at least I can prove that for calls Dynpro PBOs).
Have a nice day,
BS