SAP Note 26573 - PARAMETER/SELECT-OPTIONS with SPA/GPA

Symptom:

Up to and including 3.0A:
If a parameter or a select option was assigned an SPA/GPA ID by adding ... MEMORY ID abc, then this was active during background processing and for a selection screen processed in the background. As a consequence, the value from the SPA/GPA memory is taken (even for initial values transferred explicitly during the SUBMIT) without the user being able to see this. The effect is particularly unpleasant in the case of background processing: if the report was scheduled here twice within the same job (and a value not equal to the initial value was transferred the first time, but the initial value was transferred the second time), the value from the first step was taken for both the first AND the second step.
As of 3.0B:
SPA/GPA handling is deactivated on the selection screens in the case of a selection screen processed in the background and in background processing. The above problems no longer occur. However, all of the programs which transferred parameters using SPA/GPA (instead of transferring them explicitly during the SUBMIT) run into difficulties.

As of Release 4.0:
In the variant maintenance, SPA/GPA handling can be deactivated for a parameter or a select option.

From 4.0 to 4.5 (and after implementing the advance correction specified in Note 74501 also in 3.1H/I):
The following occurs:
You get a variant on the selection screen. You overwrite a field supplied with a memory ID (parameter or LOW field of a select option) with an initial value. After pressing enter, the old value from the SPA-/GPA memory is there again.

4.6A to 4.6C: You overwrite a field, which has a memory ID (parameter
field or LOW field of a selection option) by using the initial value.
After ENTER, the system displays the old value from the SPA-/GPA memory.
This makes it necessary to delete all these values twice. The problem
only occurs, if you start the program using a variant.

Cause and prerequisites

The cause and prerequisites are known.

Solution
There is a correction for Release 3.0B for the problem described at
the beginning.

The problem described under 4.0 to 4.5 is corrected by a kernel
patch.
Text: "Correct handling of flag NOGPA".

Resulting problems are eliminated by an additional kernel patch (text: "SPA handling on selection screens").
For Release 3.1H/I: If the preliminary correction given in Note 74501 was implemented, you must check whether this implementation was complete, because the preliminary correction has been extended in the meantime.

Make a correction to solve the 4.6 problem. You can make an advance
correction.

Additional key words

ABAPNOTE ABAPRESERR SELECT-OPTIONS SUBMIT