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

Function BRIEFINGBOOK_INSERT 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 'BRIEFINGBOOK_INSERT'"Import reports to report portfolio.
EXPORTING
APPLCLASS = "
SOURCE = "Program, which created the report
VARIANT = "Variant with which the report was created
* BI_SMODE = '2' "
IMPORTING
REPORT_NAME = "Name, under which the report is stored
TABLES
I_T242E = "Report portfolio parameters
TEXT_TAB = "Report format in SAPscript
EXCEPTIONS
D_NUMBRES_EXPIRED = 1 H_NUMBRES_EXPIRED = 2 NO_REPORT_INSERT = 3
IMPORTING Parameters details for BRIEFINGBOOK_INSERT
APPLCLASS -
Data type: TKEB1-APPLCLASSOptional: No
Call by Reference: No ( called with pass by value option)
SOURCE - Program, which created the report
Data type: T242E-HERKUOptional: No
Call by Reference: No ( called with pass by value option)
VARIANT - Variant with which the report was created
Data type: T242E-SELSETOptional: No
Call by Reference: No ( called with pass by value option)
BI_SMODE -
Data type: RKB1D-SMODEDefault: '2'
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BRIEFINGBOOK_INSERT
REPORT_NAME - Name, under which the report is stored
Data type: T242E-BRCHTOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BRIEFINGBOOK_INSERT
I_T242E - Report portfolio parameters
Data type: CFT2412EOptional: No
Call by Reference: No ( called with pass by value option)
TEXT_TAB - Report format in SAPscript
Data type: TLINEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
D_NUMBRES_EXPIRED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
H_NUMBRES_EXPIRED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
NO_REPORT_INSERT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BRIEFINGBOOK_INSERT 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: | ||||
| lt_i_t242e | TYPE STANDARD TABLE OF CFT2412E, " | |||
| lv_applclass | TYPE TKEB1-APPLCLASS, " | |||
| lv_report_name | TYPE T242E-BRCHT, " | |||
| lv_d_numbres_expired | TYPE T242E, " | |||
| lv_source | TYPE T242E-HERKU, " | |||
| lt_text_tab | TYPE STANDARD TABLE OF TLINE, " | |||
| lv_h_numbres_expired | TYPE TLINE, " | |||
| lv_variant | TYPE T242E-SELSET, " | |||
| lv_no_report_insert | TYPE T242E, " | |||
| lv_bi_smode | TYPE RKB1D-SMODE. " '2' |
|   CALL FUNCTION 'BRIEFINGBOOK_INSERT' "Import reports to report portfolio |
| EXPORTING | ||
| APPLCLASS | = lv_applclass | |
| SOURCE | = lv_source | |
| VARIANT | = lv_variant | |
| BI_SMODE | = lv_bi_smode | |
| IMPORTING | ||
| REPORT_NAME | = lv_report_name | |
| TABLES | ||
| I_T242E | = lt_i_t242e | |
| TEXT_TAB | = lt_text_tab | |
| EXCEPTIONS | ||
| D_NUMBRES_EXPIRED = 1 | ||
| H_NUMBRES_EXPIRED = 2 | ||
| NO_REPORT_INSERT = 3 | ||
| . " BRIEFINGBOOK_INSERT | ||
ABAP code using 7.40 inline data declarations to call FM BRIEFINGBOOK_INSERT
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.| "SELECT single APPLCLASS FROM TKEB1 INTO @DATA(ld_applclass). | ||||
| "SELECT single BRCHT FROM T242E INTO @DATA(ld_report_name). | ||||
| "SELECT single HERKU FROM T242E INTO @DATA(ld_source). | ||||
| "SELECT single SELSET FROM T242E INTO @DATA(ld_variant). | ||||
| "SELECT single SMODE FROM RKB1D INTO @DATA(ld_bi_smode). | ||||
| DATA(ld_bi_smode) | = '2'. | |||
Search for further information about these or an SAP related objects