Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Reg Dynamic Selections in Logical DataBases

Former Member
0 Likes
508

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.

2 REPLIES 2
Read only

felixklingel
Explorer
0 Likes
479

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!

Read only

0 Likes
479

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:

http://help.sap.com/saphelp_470/helpdata/en/9f/dba73935c111d1829f0000e829fbfe/content.htm?frameset=/...