As HR ABAPers know, using the Logical Database approach (I'm using PNPCE) gives you a system-generated Selection Screen. Part of the specs I have for this report involves making sure that the begin and end dates for the period selected are for a two-week period. If not, I should display an error message until the user enters a period such that the period (pn-begda and pn-endda) reflect a two-week period.
The code for the validation is easy enough, and I put it in the AT SELECTION-SCREEN event. But here's the problem -- the code fires every time the user clicks the "Reporting Period" drop-down box, never giving the user a chance to specify a two-week period. It fires because pn-begda and pn-endda are still all zeroes. Even if I select "Other Period" from the drop-down list, the text boxes to allow me to specify the begin and end dates don't appear.
I've been working on this for quite a while, trying all kinds of things, but I'm spinning my wheels now. I just want that check to happen when the user clicks the Execute button on the Selection Screen, not when he/she is still trying to enter criteria. I'm thinking screen field validation for a system-generated Selection Screen has to be a pretty common thing, and there must be a good solution out there.
Any ideas?
Bluesky
