Knowledge Management

Question:
Is it possible to determine the selection screen values of a background job (when no variant was used) after the job is completed?
When a report was run in background after specifying values in the selection screen, the job's step will show something like &000001 under the Parameters column. Is there a way to find out what values were used on the selection screen?
I am wondering if the values are stored in some tables pertaining to the job scheduling.
Thanks for your time.
_________________
Sudhi Karkada
Answer:
Here's how you'd do it in release 4.0:
1. In SM37, cut the '&' variant from the screen using ctrl+y.
2. Then go to SE38 and enter the program name
3. Choose menu Goto --> Variants and paste the '&' variant here
4. Click display and you should see the values the user ran the program with.
Hope this helps!
Amanda
Answer:
I usually just do it from SM37.
Go into the Step List overview. Highlight the step in question. From menu choose Goto - Variant and it should show you what values were used.
This works well with & variants.
I recall an issue we had in an older release with formal variants.
If you run a job on Tuesday with a named variant. Then on Wednesday the variant is changed. When you look at the variant for the job run on Tuesday through SM37, it will show the updated values, and NOT the values that it held at runtime.
Answer:
Amanda, your suggestion worked and thanks for your help.
Aussie FB, your suggestion doesn't work for & variant. At least it didn't work for the job I was looking at.
Thank you,
_________________
Sudhi Karkada
Answer:
I tried both methods and Both work well.
KRK
Answer:
I tried both methods and Both work well.
KRK
Both methods work well, except for the problem mentioned by aussie fatboy.
If you want to know for sure which values have been used at the time the program has been running, you'll have to print the select options / Parameters on a cover page ...
Answer:
I really don't mean to start an argument, but just for future reference, I want to clarify certain things.
If the method suggested by Aussie did work in _all_ the situations, I would not have posted the original question at all. Apparently it doesn't work in certain situations.
The situation where it did not work for me is when the job was started remotely by a BW process under the user ID ALEREMOTE. (I can not say with confidence that THAT is the reason it didn't work.) If I ran a plain background job without using a variant, the values of & variant do show up via Goto -> Variant menu option.
Amanda's solution works even in the situation where Goto -> Variant menu option didn't work.
_________________
Sudhi Karkada