A variable processing type defines how a variable receives its values. The following processing types are available:
- Manual Input / Default Value
If you select the processing type Manual Input for an input-ready variable, you can manually enter the required value when executing the query.
You can specify a default value when you create the variable. The default value is displayed for input-enabled variables in the input field of the variable screen. The default value can also be used as the variable value for fields that are not input-enabled.
- Replacement Path
You use the Replacement Path processing type to specify the value that automatically replaces the variable when you execute the query.
The Replacement Path processing type can be used with characteristic value variables, text variables, and formula variables.
For example, when you enter a Characteristic value for a a characteristic value variable, you do not need to enter manually the text for the text variable straight away. Instead, it can be retrieved dynamically from the characteristic value or even from the characteristic value variable.
Replacement from Characteristic Value:
Text and formula variables with the processing type Replacement Path can be replaced with a corresponding characteristic value. The value of a formula variable has to be a number. The value of a text variable has to be a text.
Replacement from CURRENT MEMBER:
CURRENT MEMBER variables (variables with the replacement path CURRENT MEMBER) can only be defined for characteristics, which relate to a calendar. These include 0CALDAY, 0CALMONTH, 0FISCPER, and other similar characteristics, as well as characteristics that reference these. This function is not possible for other characteristics, especially pseudo time characteristics such as 0CALMONTH2 or 0FISCPER3.
The CURRENT MEMBER variable can be used in restricted key figures as a single value, or as either the lower limit or the upper limit in combination with an offset. However, only one restriction with a CURRENT MEMBER variable – with a maximum of one interval – is allowed per restricted key figure.
For example, define the value from the previous month by defining a restricted key figure, and restricting the 0CALMONTH characteristic with the Current Member variable with an offset of -1.
Replacement from Query:
Characteristic value variables with the Replacement Path processing type can be replaced with the results of a query. The variable is replaced from the data result of the selected query.
Replacement from Variable:
Characteristic value variables, text variables, and formula variables with processing type Replacement Path can be replaced by the value from a different variable, the source variable. The value is determined either from the key, the external attribute of the key, the description, or the attribute value. You can also define an offset start and offset length. The variable is replaced in the Variables screen with each data release.
- Authorization
With the Authorization processing type you can specify that a variable is automatically filled with the values from the user authorization. When the user opens a query, the system automatically selects the data according to his or her authorizations.
The Authorization processing type can be used with characteristic value variables and hierarchy node variables. As a precondition, you must have maintained the authorizations.
- Customer Exit
The processing type, Customer Exit, allows you to set up a processing type for variables that is specially tailored for your requirements. A customer exit is designed as an enhancement that you can configure with customer-specific logic. The customer exit enables you to generate default values for variables, or create variable values from specified variables automatically. You can also check all the variables after they have been entered.
The prerequisite here is that you need to create the enhancement implementation for the RSROA_VARIABLES_EXIT_BADI enhancement spot (located in package RSROA_VAR) in the ABAP Development Tools. The BADl implementation includes the IF_BADI_INTERFACE interface.
Note
The Customer Exit processing type cannot be used with external SAP HANA views. Processing type SAP HANA Exit is provided for this purpose.
- SAP HANA Exit
Processing type SAP HANA Exit is a specific form of processing type Customer Exit. It allows you to use an AMDP class implementation to determine default values for variables. We particularly recommend using the SAP HANA Exit in queries that you want to generate an external SAP HANA view for, and for which special requirements apply for in terms of determining the variable values and processing performance.
In the ABAP Development Tools, you create the enhancement implementation for the RSROA_VARIABLES_HANA_EXIT enhancement spot. This is contained in package RSROA_VAR. The BADI implementation class requires an AMDP class containing the following interfaces: IF_BADI_INTERFACE,IF_AMDP_MARKER_HDB, and IF_RSROA_VAR_HANA_EXIT.
- SAP Exit
The SAP exit processing type is contained in variables that are delivered with SAP BW/4HANA Content Add-On.
Note that you can use the variables provided by SAP only once they exist as an active version. You may have to activate these delivered variables before you can use them.
- BRFplus Exit
Variables of processing type BRFplus Exit make it possible to access the functions of the SAP rule engine Business Rules Framework plus (BRFplus) in SAP BW/4HANA.
Variables of processing type BRFplus Exit have a BRFplus Function tab page. On this tab page, you can assign a BRFplus function to the variable. This BRFplus function is then executed when the variable is processed
These BRFplus functions must have a corresponding BRFplus context (signature) and a corresponding result data object (result object).
You can set the required logic for this kind of BRFplus function in the Business Rules Framework plus (transaction BRFPLUS).
Variable Types and available Processing Types
Characteristic Value | Text | Formula | Hierarchy | Hierarchy Node | |
Manual Input / Default Value | Yes | Yes | Yes | Yes | Yes |
Replacement Path | Replacement from query, variable, or CURRENT MEMBER | Replacement from InfoObject or variable | Replacement from InfoObject or variable | ||
Customer Exit, SAP Exit | Yes | Yes | Yes | Yes | Yes |
SAP HANA Exit | Yes | Yes | |||
BRF plus Exit | Yes | Yes | Yes | ||
Authorization | Yes | Yes |