2010 Aug 04 3:48 AM
Hi All,
I am forcefully scheduling a report to run in background mode even though the users run it online.
While doing so I have handled all the parameters and the select options in the selection screen in the following way.
SELECT OPTIONS
wa_rspar-selname = 'BUDAT'.
wa_rspar-kind = 'S'.
if BUDAT[] is not initial.
loop at BUDAT.
wa_rspar-sign = BUDAT-sign.
wa_rspar-option = BUDAT-option.
wa_rspar-low = BUDAT-low.
wa_rspar-high = BUDAT-high.
append wa_rspar to rspar.
endloop.
else.
wa_rspar-low = BUDAT.
append wa_rspar to rspar.
endif.
clear: wa_rspar.
PARAMETERS.
wa_rspar-selname = 'SORTART'.
wa_rspar-kind = 'P'.
wa_rspar-low = SORTART.
append wa_rspar to rspar.
clear: wa_rspar.
While doing so since the report uses logical database-the dynamic selection portion has to be handled otherwise the dynamic selection is ignored and the report is displayed wrong.
How can we handle the dynamic selection portion for the forceful conversion of the program to background mode even if it is run online.
Has anyone faced this kind of issue.If so how was it resolved.
Thanks in advance.
Hi All,
I am forcefully scheduling a report to run in background mode even though the users run it online.
While doing so I have handled all the parameters and the select options in the selection screen in the following way.
SELECT OPTIONS
wa_rspar-selname = 'BUDAT'.
wa_rspar-kind = 'S'.
if BUDAT[] is not initial.
loop at BUDAT.
wa_rspar-sign = BUDAT-sign.
wa_rspar-option = BUDAT-option.
wa_rspar-low = BUDAT-low.
wa_rspar-high = BUDAT-high.
append wa_rspar to rspar.
endloop.
else.
wa_rspar-low = BUDAT.
append wa_rspar to rspar.
endif.
clear: wa_rspar.
PARAMETERS.
wa_rspar-selname = 'SORTART'.
wa_rspar-kind = 'P'.
wa_rspar-low = SORTART.
append wa_rspar to rspar.
clear: wa_rspar.
While doing so since the report uses logical database-the dynamic selection portion has to be handled otherwise the dynamic selection is ignored and the report is displayed wrong.
How can we handle the dynamic selection portion for the forceful conversion of the program to background mode even if it is run online.
Has anyone faced this kind of issue.If so how was it resolved.
Thanks in advance.
2014 Dec 10 4:05 PM
Dear all,
I have exactly the same issue but can't find any suggestions how to resolve this.
Was anyone able to fill the dynamic selections of a logical database in a Report?
The following doesn't work:
INITIALIZATION.
sd_budat-low = sy-datum.
sd_budat-sign = 'I'.
sd_budat-option = 'EQ'.
APPEND sd_budat.
Thanks!
2014 Dec 12 1:51 PM
Finally it seems not to be possible to fill the dynamic selection of a logical database during INITIALIZATION in a report which is using the respective logical database (under report properties).
My solution was to create a new select option within the customer program which refers to the respective database column (... FOR bsis-gjahr). If this column is supported by the dynamic selections of the logical database, then the values entered on the selection screen are automatically transferred and used by the logical database selection. It is just important to refer to the correct table, as BSIS-gjahr is working while BSEG-gjahr and BKPF-gjahr are not working in my example.
See the following link:
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |