SAP BICS_CONS_SAVE_VIEW Function Module for Save State
BICS_CONS_SAVE_VIEW is a standard bics cons save view SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Save State 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 bics cons save view FM, simply by entering the name BICS_CONS_SAVE_VIEW into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSBOLAP_BICS_CONSUMER
Program Name: SAPLRSBOLAP_BICS_CONSUMER
Main Program: SAPLRSBOLAP_BICS_CONSUMER
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function BICS_CONS_SAVE_VIEW 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 'BICS_CONS_SAVE_VIEW'"Save State.
EXPORTING
I_NAME = "Name of View
I_TEXT = "Description of View
I_DEFINITION = "Navigational State from Consumer's Viewpoint
* I_OVERWRITE = RS_C_FALSE "Overwrite Existing State
* I_VIEW_TYPE = 'SELECTOR' "View Type
* I_VIEW_VISIBILITY = ' ' "Visibility of a View
IMPORTING
E_MAX_MESSAGE_TYPE = "Message Type
E_NAME = "Name of View
E_SUCCESSFULL = "Successful
TABLES
* E_T_MESSAGE = "Message
* I_T_STATISTIC_INFO = "OLAP Statistics: Mass Insert of Event Data
* I_T_SERVICE_DESC_PROPERTIES = "Properties
IMPORTING Parameters details for BICS_CONS_SAVE_VIEW
I_NAME - Name of View
Data type: RSBOLAP_VIEW_NAMEOptional: No
Call by Reference: No ( called with pass by value option)
I_TEXT - Description of View
Data type: RSBOLAP_OBJECT_TEXTOptional: No
Call by Reference: No ( called with pass by value option)
I_DEFINITION - Navigational State from Consumer's Viewpoint
Data type: XSTRINGOptional: No
Call by Reference: No ( called with pass by value option)
I_OVERWRITE - Overwrite Existing State
Data type: RS_BOOLDefault: RS_C_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_VIEW_TYPE - View Type
Data type: RSBOLAP_DATA_PROVIDER_TYPEDefault: 'SELECTOR'
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_VIEW_VISIBILITY - Visibility of a View
Data type: RSBOLAP_VIEW_VISIBILITYDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BICS_CONS_SAVE_VIEW
E_MAX_MESSAGE_TYPE - Message Type
Data type: SYMSGTYOptional: No
Call by Reference: No ( called with pass by value option)
E_NAME - Name of View
Data type: RSBOLAP_VIEW_NAMEOptional: No
Call by Reference: No ( called with pass by value option)
E_SUCCESSFULL - Successful
Data type: RS_BOOLOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BICS_CONS_SAVE_VIEW
E_T_MESSAGE - Message
Data type: BICS_PROV_MESSAGEOptional: Yes
Call by Reference: Yes
I_T_STATISTIC_INFO - OLAP Statistics: Mass Insert of Event Data
Data type: RSSTA_S_EVENTINPUTOptional: Yes
Call by Reference: Yes
I_T_SERVICE_DESC_PROPERTIES - Properties
Data type: RSBOLAP_S_NAME_VALUEOptional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BICS_CONS_SAVE_VIEW 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_name | TYPE RSBOLAP_VIEW_NAME, " | |||
| lt_e_t_message | TYPE STANDARD TABLE OF BICS_PROV_MESSAGE, " | |||
| lv_e_max_message_type | TYPE SYMSGTY, " | |||
| lv_e_name | TYPE RSBOLAP_VIEW_NAME, " | |||
| lv_i_text | TYPE RSBOLAP_OBJECT_TEXT, " | |||
| lt_i_t_statistic_info | TYPE STANDARD TABLE OF RSSTA_S_EVENTINPUT, " | |||
| lv_i_definition | TYPE XSTRING, " | |||
| lv_e_successfull | TYPE RS_BOOL, " | |||
| lt_i_t_service_desc_properties | TYPE STANDARD TABLE OF RSBOLAP_S_NAME_VALUE, " | |||
| lv_i_overwrite | TYPE RS_BOOL, " RS_C_FALSE | |||
| lv_i_view_type | TYPE RSBOLAP_DATA_PROVIDER_TYPE, " 'SELECTOR' | |||
| lv_i_view_visibility | TYPE RSBOLAP_VIEW_VISIBILITY. " SPACE |
|   CALL FUNCTION 'BICS_CONS_SAVE_VIEW' "Save State |
| EXPORTING | ||
| I_NAME | = lv_i_name | |
| I_TEXT | = lv_i_text | |
| I_DEFINITION | = lv_i_definition | |
| I_OVERWRITE | = lv_i_overwrite | |
| I_VIEW_TYPE | = lv_i_view_type | |
| I_VIEW_VISIBILITY | = lv_i_view_visibility | |
| IMPORTING | ||
| E_MAX_MESSAGE_TYPE | = lv_e_max_message_type | |
| E_NAME | = lv_e_name | |
| E_SUCCESSFULL | = lv_e_successfull | |
| TABLES | ||
| E_T_MESSAGE | = lt_e_t_message | |
| I_T_STATISTIC_INFO | = lt_i_t_statistic_info | |
| I_T_SERVICE_DESC_PROPERTIES | = lt_i_t_service_desc_properties | |
| . " BICS_CONS_SAVE_VIEW | ||
ABAP code using 7.40 inline data declarations to call FM BICS_CONS_SAVE_VIEW
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.| DATA(ld_i_overwrite) | = RS_C_FALSE. | |||
| DATA(ld_i_view_type) | = 'SELECTOR'. | |||
| DATA(ld_i_view_visibility) | = ' '. | |||
Search for further information about these or an SAP related objects