date-low

[Former Member]

if not date-low is initial and not source-datab is initial.

if date-low <= sy-datum.

clear ws_date.

ws_year = date-low+0(4).

ws_month = date-low+4(2).

ws_day = date-low+6(2).

concatenate ws_day ws_month ws_year into ws_date.

-

---

if not source-datbi is initial and not date-high is initial.

if date-high > sy-datum.

clear ws_date.

ws_year = date-high+0(4).

ws_month = date-high+4(2).

ws_day = date-high+6(2).

Is date-low and date-high a syatme variable here?

How does date-low and date-high derive its value?

This is used in LSMW

[Former Member]

Its not a system variable.

It would be uploaded from a file in LSMW.

[kathryn_mcgallicher]

Hello,

In your example code, date appears to be a field that allows a range, meaning a lower limit and upper limit can be specified.

I'm not familiar with the transaction you mention, but in a standard report with a selection screen, the field date could be either a parameter or a selection option. If you allow the range option, then date-low would be the low end of the range and date-high would be the upper end of the range. You don't specifically define date-low and date-high, they are part of the attributes of date. When viewing a field like this on a selection screen, there would be two entry fields side-by-side with the text word "to" inbetween them. You could then enter a date range such as 01/01/2007 and 07/11/2007 so that your code considers all dates between those two (and including those two). If you want to reference either the low end or the upper end individually, you add the -low and/or -high.

Hope this helps...

K

[Former Member]

Look into the mapping data declarations section. There may be a select-option that is defined there. From that it is filling up variables for later use.