SAP RSVAREXIT_0CCMAW_IP Function Module for InfoProvider from time interval
RSVAREXIT_0CCMAW_IP is a standard rsvarexit 0ccmaw ip SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for InfoProvider from time interval processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for rsvarexit 0ccmaw ip FM, simply by entering the name RSVAREXIT_0CCMAW_IP into the relevant SAP transaction such as SE37 or SE38.
Function Group: CCMSBI_TOOLS
Program Name: SAPLCCMSBI_TOOLS
Main Program: SAPLCCMSBI_TOOLS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function RSVAREXIT_0CCMAW_IP pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'RSVAREXIT_0CCMAW_IP'"InfoProvider from time interval.
EXPORTING
I_VNAM = "Name (ID) of a Report Variable
I_VARTYP = "Type of a Report Variable
I_IOBJNM = "InfoObject
I_S_COB_PRO = "InfoObject Properties (in Context of InfoCube / ODS Object)
I_S_RKB1D = "Control Bar OLAP Processor
I_S_RKB1F = "
I_THX_VAR = "Table of All Variables
* I_STEP = "
IMPORTING
E_T_RANGE = "
EXCEPTIONS
UNKNOWN_VARIABLE = 1 UNEXPECTED_VARTYPE = 2 INVALID_PERIV = 3 VARIABLE_INITIAL = 4 NO_PROCESSING = 5
IMPORTING Parameters details for RSVAREXIT_0CCMAW_IP
I_VNAM - Name (ID) of a Report Variable
Data type: RSZVNAMOptional: No
Call by Reference: No ( called with pass by value option)
I_VARTYP - Type of a Report Variable
Data type: RSZVARTYPOptional: No
Call by Reference: No ( called with pass by value option)
I_IOBJNM - InfoObject
Data type: RSIOBJNMOptional: No
Call by Reference: No ( called with pass by value option)
I_S_COB_PRO - InfoObject Properties (in Context of InfoCube / ODS Object)
Data type: RSD_S_COB_PROOptional: No
Call by Reference: No ( called with pass by value option)
I_S_RKB1D - Control Bar OLAP Processor
Data type: RSR_S_RKB1DOptional: No
Call by Reference: No ( called with pass by value option)
I_S_RKB1F -
Data type: RRO01_S_RKB1FOptional: No
Call by Reference: No ( called with pass by value option)
I_THX_VAR - Table of All Variables
Data type: RRO01_THX_VAROptional: No
Call by Reference: No ( called with pass by value option)
I_STEP -
Data type: IOptional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for RSVAREXIT_0CCMAW_IP
E_T_RANGE -
Data type: RSR_T_RANGESIDOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
UNKNOWN_VARIABLE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
UNEXPECTED_VARTYPE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_PERIV -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
VARIABLE_INITIAL -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_PROCESSING -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for RSVAREXIT_0CCMAW_IP Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_i_vnam | TYPE RSZVNAM, " | |||
| lv_e_t_range | TYPE RSR_T_RANGESID, " | |||
| lv_unknown_variable | TYPE RSR_T_RANGESID, " | |||
| lv_i_vartyp | TYPE RSZVARTYP, " | |||
| lv_unexpected_vartype | TYPE RSZVARTYP, " | |||
| lv_i_iobjnm | TYPE RSIOBJNM, " | |||
| lv_invalid_periv | TYPE RSIOBJNM, " | |||
| lv_i_s_cob_pro | TYPE RSD_S_COB_PRO, " | |||
| lv_variable_initial | TYPE RSD_S_COB_PRO, " | |||
| lv_i_s_rkb1d | TYPE RSR_S_RKB1D, " | |||
| lv_no_processing | TYPE RSR_S_RKB1D, " | |||
| lv_i_s_rkb1f | TYPE RRO01_S_RKB1F, " | |||
| lv_i_thx_var | TYPE RRO01_THX_VAR, " | |||
| lv_i_step | TYPE I. " |
|   CALL FUNCTION 'RSVAREXIT_0CCMAW_IP' "InfoProvider from time interval |
| EXPORTING | ||
| I_VNAM | = lv_i_vnam | |
| I_VARTYP | = lv_i_vartyp | |
| I_IOBJNM | = lv_i_iobjnm | |
| I_S_COB_PRO | = lv_i_s_cob_pro | |
| I_S_RKB1D | = lv_i_s_rkb1d | |
| I_S_RKB1F | = lv_i_s_rkb1f | |
| I_THX_VAR | = lv_i_thx_var | |
| I_STEP | = lv_i_step | |
| IMPORTING | ||
| E_T_RANGE | = lv_e_t_range | |
| EXCEPTIONS | ||
| UNKNOWN_VARIABLE = 1 | ||
| UNEXPECTED_VARTYPE = 2 | ||
| INVALID_PERIV = 3 | ||
| VARIABLE_INITIAL = 4 | ||
| NO_PROCESSING = 5 | ||
| . " RSVAREXIT_0CCMAW_IP | ||
ABAP code using 7.40 inline data declarations to call FM RSVAREXIT_0CCMAW_IP
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.Search for further information about these or an SAP related objects