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

Function RSBBS_REPORT_SAVE 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 'RSBBS_REPORT_SAVE'"BW: Save Assignments.
EXPORTING
I_APPL = "Application
I_S_ONAM = "Structure of the Sending/Receiving Report RRI
* I_FROM_CONTENT = RS_C_FALSE "Content Copy
* I_CONTREL = "Content release
* I_CONTTIMESTMP = "Content Time Stamp: Last Modification to the Object by SAP
IMPORTING
E_T_MSG = "BW: Table with Messages (Application Log)
CHANGING
C_T_DEF = "
C_T_TEXT = "
C_T_MAPPING = "
EXCEPTIONS
INSERT_NOT_POSSIBLE = 1 TRSTI_INSERT_NOT_POSSIBLE = 2 CANCEL = 3
IMPORTING Parameters details for RSBBS_REPORT_SAVE
I_APPL - Application
Data type: RSTI_APPLOptional: No
Call by Reference: Yes
I_S_ONAM - Structure of the Sending/Receiving Report RRI
Data type: RSBBSBWONAMOptional: No
Call by Reference: Yes
I_FROM_CONTENT - Content Copy
Data type: RS_BOOLDefault: RS_C_FALSE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_CONTREL - Content release
Data type: RSCONTRELOptional: Yes
Call by Reference: Yes
I_CONTTIMESTMP - Content Time Stamp: Last Modification to the Object by SAP
Data type: RSCONTTIMESTMPOptional: Yes
Call by Reference: Yes
EXPORTING Parameters details for RSBBS_REPORT_SAVE
E_T_MSG - BW: Table with Messages (Application Log)
Data type: RS_T_MSGOptional: No
Call by Reference: Yes
CHANGING Parameters details for RSBBS_REPORT_SAVE
C_T_DEF -
Data type: RSBBS_T_DEFOptional: No
Call by Reference: Yes
C_T_TEXT -
Data type: RSBBS_T_TEXTOptional: No
Call by Reference: Yes
C_T_MAPPING -
Data type: RSBBS_T_MAPPINGOptional: No
Call by Reference: Yes
EXCEPTIONS details
INSERT_NOT_POSSIBLE - Error when adding
Data type:Optional: No
Call by Reference: Yes
TRSTI_INSERT_NOT_POSSIBLE - Non-fatal error while inserting into TRSTI
Data type:Optional: No
Call by Reference: Yes
CANCEL -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for RSBBS_REPORT_SAVE 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_appl | TYPE RSTI_APPL, " | |||
| lv_c_t_def | TYPE RSBBS_T_DEF, " | |||
| lv_e_t_msg | TYPE RS_T_MSG, " | |||
| lv_insert_not_possible | TYPE RS_T_MSG, " | |||
| lv_c_t_text | TYPE RSBBS_T_TEXT, " | |||
| lv_i_s_onam | TYPE RSBBSBWONAM, " | |||
| lv_trsti_insert_not_possible | TYPE RSBBSBWONAM, " | |||
| lv_cancel | TYPE RSBBSBWONAM, " | |||
| lv_c_t_mapping | TYPE RSBBS_T_MAPPING, " | |||
| lv_i_from_content | TYPE RS_BOOL, " RS_C_FALSE | |||
| lv_i_contrel | TYPE RSCONTREL, " | |||
| lv_i_conttimestmp | TYPE RSCONTTIMESTMP. " |
|   CALL FUNCTION 'RSBBS_REPORT_SAVE' "BW: Save Assignments |
| EXPORTING | ||
| I_APPL | = lv_i_appl | |
| I_S_ONAM | = lv_i_s_onam | |
| I_FROM_CONTENT | = lv_i_from_content | |
| I_CONTREL | = lv_i_contrel | |
| I_CONTTIMESTMP | = lv_i_conttimestmp | |
| IMPORTING | ||
| E_T_MSG | = lv_e_t_msg | |
| CHANGING | ||
| C_T_DEF | = lv_c_t_def | |
| C_T_TEXT | = lv_c_t_text | |
| C_T_MAPPING | = lv_c_t_mapping | |
| EXCEPTIONS | ||
| INSERT_NOT_POSSIBLE = 1 | ||
| TRSTI_INSERT_NOT_POSSIBLE = 2 | ||
| CANCEL = 3 | ||
| . " RSBBS_REPORT_SAVE | ||
ABAP code using 7.40 inline data declarations to call FM RSBBS_REPORT_SAVE
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_from_content) | = RS_C_FALSE. | |||
Search for further information about these or an SAP related objects