7.12.10

SAP Note 12044 - Regenerating coding after variable maintenance.

Symptom

Changes to a variable in variable maintenance to not cause automatic regeneration of applications that use that variable.
Changes to the following properties of a variable could be relevant for Report Writer reports:

* SPA/GPA Parameters Internal variable <-> External variable
Value variable <-> Formula variable

* Description (short text of variable)

Changes to the following properties of a variable could be relevant for validation, substitution, and control (VSR):

* Default set of a set variable

Additional key words

Variable maintenance GS11, GS12, SAPMGSGM ----- SUPPORTGUIDE 20010208103353 -----
REPORTWRITER, SGRW_SET, SGRW_DOCU_CONS_NOTE
SGRW_OM SGRW_PS SGRW_PC SGRW_SL SGRW_PCA SGRW_EC SGRW_LIS
Cause and prerequisites

Regeneration of programs in the affected areas is not automatically triggered after variable maintenance.
Solution

For Report Writer reports: regenerate the affected report groups.
As of release 4.5A, this is done automatically when changing the
variables, i.e. manual generation is not required.
For validation, substitution and control (VSR): Do not use any set
variables.
In VSR, set variables can be used indirectly via multi-sets only; these should not be used, however. Construct "IN " can be replaced by "IN AND IN ", where and are the single or basic sets contained in the multi-set. This way, it is clearer in the boolean formula which characteristics are actually checked. If you use multi-sets nevertheless, they should not contain any set variables since set variables in VSR are always replaced by their default sets - therefore, you can directly enter the default set into the multi-set. If you use a multi-set with a set variable in VSR nevertheless, you need to generate the ABAP coding for controlling again by executing ABAP/4 program RGUGBR00 after changing the set variables. (Select option 'Generate sets'.)

No comments:

Post a Comment