SAP FTBU_CONVERT_PROTOKOLL_FILL Function Module for NOTRANSL: Umsetzung: Protokollzeile füllen
FTBU_CONVERT_PROTOKOLL_FILL is a standard ftbu convert protokoll fill SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Umsetzung: Protokollzeile füllen 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 ftbu convert protokoll fill FM, simply by entering the name FTBU_CONVERT_PROTOKOLL_FILL into the relevant SAP transaction such as SE37 or SE38.
Function Group: FTBU_CONV
Program Name: SAPLFTBU_CONV
Main Program: SAPLFTBU_CONV
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function FTBU_CONVERT_PROTOKOLL_FILL 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 'FTBU_CONVERT_PROTOKOLL_FILL'"NOTRANSL: Umsetzung: Protokollzeile füllen.
EXPORTING
I_IDX = "ABAP System Field: Row Index of Internal Tables
I_VAR4 = "Message Variable 2
I_NEWOBJEKT = "New Section
I_AG = "Message Class
I_MSGNR = "Message Number
I_SEVERITY = "Error severity(' ',W(arning),E(rror),A(bnormal termination))
I_LEVEL = "Log Level
I_VAR1 = "Message Variable 1
I_VAR2 = "Message Variable 2
I_VAR3 = "Message Variable 2
IMPORTING
E_PROTOKOLL_DETAIL = "Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
IMPORTING Parameters details for FTBU_CONVERT_PROTOKOLL_FILL
I_IDX - ABAP System Field: Row Index of Internal Tables
Data type: SY-TABIXOptional: No
Call by Reference: Yes
I_VAR4 - Message Variable 2
Data type: SPROT_U-VAR4Optional: No
Call by Reference: Yes
I_NEWOBJEKT - New Section
Data type: SPROT_U-NEWOBJOptional: No
Call by Reference: Yes
I_AG - Message Class
Data type: SPROT_U-AGOptional: No
Call by Reference: Yes
I_MSGNR - Message Number
Data type: SPROT_U-MSGNROptional: No
Call by Reference: Yes
I_SEVERITY - Error severity(' ',W(arning),E(rror),A(bnormal termination))
Data type: SPROT_U-SEVERITYOptional: No
Call by Reference: Yes
I_LEVEL - Log Level
Data type: SPROT_U-LEVELOptional: No
Call by Reference: Yes
I_VAR1 - Message Variable 1
Data type: SPROT_U-VAR1Optional: No
Call by Reference: Yes
I_VAR2 - Message Variable 2
Data type: SPROT_U-VAR2Optional: No
Call by Reference: Yes
I_VAR3 - Message Variable 2
Data type: SPROT_U-VAR3Optional: No
Call by Reference: Yes
EXPORTING Parameters details for FTBU_CONVERT_PROTOKOLL_FILL
E_PROTOKOLL_DETAIL - Data element for domain BOOLE: TRUE (='X') and FALSE (=' ')
Data type: BOOLE-BOOLEOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for FTBU_CONVERT_PROTOKOLL_FILL 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_idx | TYPE SY-TABIX, " | |||
| lv_e_protokoll_detail | TYPE BOOLE-BOOLE, " | |||
| lv_i_var4 | TYPE SPROT_U-VAR4, " | |||
| lv_i_newobjekt | TYPE SPROT_U-NEWOBJ, " | |||
| lv_i_ag | TYPE SPROT_U-AG, " | |||
| lv_i_msgnr | TYPE SPROT_U-MSGNR, " | |||
| lv_i_severity | TYPE SPROT_U-SEVERITY, " | |||
| lv_i_level | TYPE SPROT_U-LEVEL, " | |||
| lv_i_var1 | TYPE SPROT_U-VAR1, " | |||
| lv_i_var2 | TYPE SPROT_U-VAR2, " | |||
| lv_i_var3 | TYPE SPROT_U-VAR3. " |
|   CALL FUNCTION 'FTBU_CONVERT_PROTOKOLL_FILL' "NOTRANSL: Umsetzung: Protokollzeile füllen |
| EXPORTING | ||
| I_IDX | = lv_i_idx | |
| I_VAR4 | = lv_i_var4 | |
| I_NEWOBJEKT | = lv_i_newobjekt | |
| I_AG | = lv_i_ag | |
| I_MSGNR | = lv_i_msgnr | |
| I_SEVERITY | = lv_i_severity | |
| I_LEVEL | = lv_i_level | |
| I_VAR1 | = lv_i_var1 | |
| I_VAR2 | = lv_i_var2 | |
| I_VAR3 | = lv_i_var3 | |
| IMPORTING | ||
| E_PROTOKOLL_DETAIL | = lv_e_protokoll_detail | |
| . " FTBU_CONVERT_PROTOKOLL_FILL | ||
ABAP code using 7.40 inline data declarations to call FM FTBU_CONVERT_PROTOKOLL_FILL
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 TABIX FROM SY INTO @DATA(ld_i_idx). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_e_protokoll_detail). | ||||
| "SELECT single VAR4 FROM SPROT_U INTO @DATA(ld_i_var4). | ||||
| "SELECT single NEWOBJ FROM SPROT_U INTO @DATA(ld_i_newobjekt). | ||||
| "SELECT single AG FROM SPROT_U INTO @DATA(ld_i_ag). | ||||
| "SELECT single MSGNR FROM SPROT_U INTO @DATA(ld_i_msgnr). | ||||
| "SELECT single SEVERITY FROM SPROT_U INTO @DATA(ld_i_severity). | ||||
| "SELECT single LEVEL FROM SPROT_U INTO @DATA(ld_i_level). | ||||
| "SELECT single VAR1 FROM SPROT_U INTO @DATA(ld_i_var1). | ||||
| "SELECT single VAR2 FROM SPROT_U INTO @DATA(ld_i_var2). | ||||
| "SELECT single VAR3 FROM SPROT_U INTO @DATA(ld_i_var3). | ||||
Search for further information about these or an SAP related objects