Kontakt

Ansicht
Dokumentation

Sets: New functions for maintaining and processing variables ( RELNFI_GLX_SETS_VAR )

Sets: New functions for maintaining and processing variables ( RELNFI_GLX_SETS_VAR )

rdisp/max_wprun_time - Maximum work process run time   BAL Application Log Documentation  
Diese Dokumentation steht unter dem Copyright der SAP AG.
SAP E-Book

!!!!!!!!!!!!NICHT ÜBERSETZEN - RELEASE-2.1-RELEVANT!!!!!!!!!!!!!!!

Kurztext

Sets: New functions for maintaining and processing variables

Beschreibung

The functionality of variables (in basic sets) has been extended as follows:

  • Check box 'Use parameter ID' instead of entry field 'Memory ID'
Instead of the field 'Memory ID' which has been used so far for defining the SPA/GPA parameter for a variable, the check box 'Use parameter ID' is provided for value variables. When creating new variables, the field only appears on the input screen if a parameter ID/memory ID is defined in the Data Dictionary for the field for which the variable is being created. For variables which have already been defined, the field also appears on the screen if a memory ID has been defined for the variable. If this memory ID differs from the ID defined in the Data Dictionary, the user-defined memory ID is maintained until the variable has been saved, with the 'Use parameter ID' check box deactivated.
  • New variable type 'Formula variable':
A new variable type 'formula variable' has been introduced in addition to the existing variable types 'value variable' and 'set variable'. Formula variables can be used in basic sets as value variables. However, the default value of a formula variable is not predefined. It is determined when used by calculating the defined formula.
There are two different types of formula variable, depending on the field for which the variable is created:
  • Formula variables for a non-numeric (alphanumeric) field (for example, GLT0-RACCT, CCSS-KSTAR)

For formula variables created for alphanumeric fields, the default value of the variable is determined using SAP or user exits. SAP exits are, for example, the current fiscal year, the current period. For more information on exits and the rules used for defining your own exits, refer to the section 'Weitere Hinweise'.
  • Formula variables for a numeric field (for example, GLT0-RYEAR, CCSS-GJAHR)

For formula variables created for numeric fields, the default value of the variable is determined by calculating the specified formula. You can use constants (1993), value variables (&WVAR), formula variables (&FVAR), as well as SAP and user-defined exits (#S001, #U000) in these formulas.
Example: A variable for the 'fiscal year' should always contain the current year. Another variable for the 'fiscal year' should always contain the previous year of the current year.
Using the existing procedure, you define both variables with a corresponding default value, without taking into account the dependency 'current year' <-> 'previous year'.
Variable 'YEAR' --> default value '1993'
Variable 'PYEAR' --> default value '1992'
If you use formula variables to determine the default value, you can establish a relationship between the variables.
Variable 'YEAR' --> SAP exit '#S001'
Variable 'PYEAR' --> formula '&YEAR' - 1
If you use sets with formula variables defined in this way, this means that, in the Report Writer for example, only the variable '&YEAR' is displayed on the selection screen for changing. The variable '&PYEAR' is determined internally and always contains the respective previous year. For '&YEAR', the system takes the current year from the system date using the SAP exit '#S001' (current year). This means that you do not have to make any changes to the default value of the variable '&YEAR' for the fiscal year change.

Detailed information on the operators and functions that can be used in formulas is given in the field documentation for the entry field 'Formula'.
  • New selection field 'Internal variable':
For value and formula variables, you can define a variable as an 'internal variable'. This means that the default values of the variables can no longer be changed in the applications which process basic sets with variables (for example, in the Report Writer).
Formula variables which use other variables in the formula are automatically defined as internal variables when you save the variable definition.

Soft-/Hardwarevoraussetzungen

Besonderheiten bei der Installation

Auswirkungen auf die Systemverwaltung

Auswirkungen auf das Customizing

Auswirkungen auf Batch-Input

Änderungen an der Oberfläche

Änderungen in der Vorgehensweise

Abhängige Funktionen

Planungen

Weitere Hinweise

Exits in formula variable processing are ABAP/4 form routines which return values or character strings to formula processing. The exits are defined in special ABAP/4 FORM pools. Exits can be SAP exits or user exits. It is defined for each exit whether it returns numeric values only or alphanumeric values. When using exits in numeric or alphanumeric formula variables, you should note the following rules:

  • Exits which return numeric values can be used both in numeric and in alphanumeric formula variables.
  • Exits which return alphanumeric values can only be used in alphanumeric formula variables.

Exit names consist of four characters in the form 'Sxxx' for SAP exits or 'Uxxx' for user exits where 'xxx' must be a three-digit number.

The exits are implemented as follows:

  • SAP exits
The standard SAP exits are defined in the ABAP/4 FORM pool 'RGSVS000'. This FORM pool may not be changed since other exits can be added to it, if required. The SAP exits defined up to now are:
  • S001 year (from the system date)
    S002 month (from the system date)
    S003 day of the month (from the system date)
    S004 calendar week (from the system date)
    S005 day of the year (from the system date)

  • User exits
The user exits are defined in an ABAP/4 FORM pool, the name of which has to be defined in the ATAB table 'T80U' for the application area 'Sets: formula variables'. The ABAP/4 FORM pool 'RGSVU000' is defined as a reference in this table. In this FORM pool and in another ABAP/4 FORM pool 'RGSVUSAP', it is described how user exits are created. According to these ABAP/4 FORM pools, a separate FORM pool is to be created for user exits and entered in table 'T80U'. The new exits can then be used as SAP exits.
Important: If exits are changed/deleted in the FORM pool, or another exit FORM pool is entered in the table 'T80U', you must first ensure that the affected exits are not used in any formula variable.





ABAP Short Reference   ABAP Short Reference  
Diese Dokumentation steht unter dem Copyright der SAP AG.

Length: 7510 Date: 20240523 Time: 160709     sap01-206 ( 134 ms )