Screen fields without parameter id's in IW26 pseudo-selection screen

Question

The initial screen of IW26 looks like a selection screen but isn't.  It uses a number of screens as follows:
1) For notification/status/order: IQS0 1050 (IQSO is the function group)
2) For Notification Reference Object: IWO1 0100
3) For Notification Responsibilities: IQSO 7326
4) For Notification Start/End Dates: IQS0 7330
5) For Notification Item: IQS0 7324
6) For Notification Malfunction Data: IQS0 7328
If you look at IQS0 7330, you'll see that the only the "Priority" screen field has a parameter id.
If you look at IQS0:7324, you'll see that none of the Item-Related screen-fields have parameter ID's.
Same for IQS0:7328 - none of the Malfunction-related fields have parameter id's.
So - if we do a call transaction/skip first screen, we can't preset any of the Item-related screen fields in 7324, nor any of the Malfunction-related screen fields in 7330, nor any of the Date-related fields in 7328 except Priority.
If we were dealing with a "regular" selection-screen here, I know how to get around this problem - do a "submit program" with the selection-screen parameters and select-options "preset" in the with-clause of the submit.
But here we don't have a regular selection-screen.  We have the screens 7330, 7324, and 7328 in IQS0.  So I can't do a "submit program".
So how do I preset screen-fields on these screens when SAP has provided no parameter ids for them?
(I assume here that I can's use "submit program" because I'm not trying to present real selection screen fields.)
Sorry if this is a dumb question, but I've only dealt with this problem before when the transaction has a real selection screen and I can use "submit program" with a with clause in which the parameters and select-options are preset.
Thanks for any help anyone can provide.
I

Answer 1

Hi Rich -
I've done the ten because you confirmed my suspicion that nothing "clean" can be done here.  I thought maybe some kind of customer screen exit would allow parameter id's to be assigned on the fly rather than in Dictionary, or something like that, but if you've never heard of this then I'm sure it can't be done.
Anyway, the issue regarding the BDC is not the usual one of maintainability over time - it's a political one.
The functional analysts want to use a 3rd party product to create a simpler front-end screen for IW26 - the guys on the shop floor don't want to chase the trees.
We told them that this third party product has recently been known to cause headaches (in fact, by pure coincidence there was a post tonight 12/26 about this product.)
They said - well what else are you going to do, write a BDC?
I hadn't looked at IW26 so I assumed it had a regular selection screen and said to them that a BDC wouldn't be necessary - a call transaction or submit program would suffice.
But of course I spoke too soon, unless I can get an OSSN with the parameter IDs.
Anyway - that's the history here.
BTW, I am going to blog on this topic of "missing" parameter ID's for two reasons:
a) it ticks me off;
b) if IW26 is to be efficiently called as a service, these missing ID's have got to be there;
c) there's no reason to go to a 3rd party product just to avoid using a BDC when parameter IDs are missing.
I know, I know - I'll blog about anything ...
Regards
djh