SAP FEHLERPROTOKOLL_FUELLEN Function Module for Fill Error Table for Deadline Monitoring









FEHLERPROTOKOLL_FUELLEN is a standard fehlerprotokoll fuellen SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Fill Error Table for Deadline Monitoring 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 fehlerprotokoll fuellen FM, simply by entering the name FEHLERPROTOKOLL_FUELLEN into the relevant SAP transaction such as SE37 or SE38.

Function Group: FVWT
Program Name: SAPLFVWT
Main Program:
Appliation area: F
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function FEHLERPROTOKOLL_FUELLEN 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 'FEHLERPROTOKOLL_FUELLEN'"Fill Error Table for Deadline Monitoring
  EXPORTING
   I_ARBG =  "Arbeitsgebiet Terminüberwachung
*  I_MSGV4 = ' ' "Variable 4 der Message
*  I_XTEXT1 = ' ' "Informationstext1
*  I_XTEXT2 = ' ' "Informationstext2
*  I_XTEXT3 = ' ' "Informationstext3
   I_BUKRS =  "Company Code
   I_LANGU =  "Language
   I_MSGID =  "Message ID
   I_MSGNO =  "Message Number
   I_MSGTY =  "Nachrichtentyp (W,I,E,A)
*  I_MSGV1 = ' ' "Variable 1 der Message
*  I_MSGV2 = ' ' "Variable 2 der Message
*  I_MSGV3 = ' ' "Variable 3 der Message

TABLES
   FEHLER =  "Error Message Table
.



IMPORTING Parameters details for FEHLERPROTOKOLL_FUELLEN

I_ARBG - Arbeitsgebiet Terminüberwachung

Data type: TZW01-SARBG
Optional: No
Call by Reference: No ( called with pass by value option)

I_MSGV4 - Variable 4 der Message

Data type: SY-MSGV4
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_XTEXT1 - Informationstext1

Data type: SPROT_VW-XTEXT1
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_XTEXT2 - Informationstext2

Data type: SPROT_VW-XTEXT2
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_XTEXT3 - Informationstext3

Data type: SPROT_VW-XTEXT3
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_BUKRS - Company Code

Data type: VWBEVI-BUKRS
Optional: No
Call by Reference: No ( called with pass by value option)

I_LANGU - Language

Data type: SY-LANGU
Optional: No
Call by Reference: No ( called with pass by value option)

I_MSGID - Message ID

Data type: SY-MSGID
Optional: No
Call by Reference: No ( called with pass by value option)

I_MSGNO - Message Number

Data type: SY-MSGNO
Optional: No
Call by Reference: No ( called with pass by value option)

I_MSGTY - Nachrichtentyp (W,I,E,A)

Data type: SY-MSGTY
Optional: No
Call by Reference: No ( called with pass by value option)

I_MSGV1 - Variable 1 der Message

Data type: SY-MSGV1
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_MSGV2 - Variable 2 der Message

Data type: SY-MSGV2
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

I_MSGV3 - Variable 3 der Message

Data type: SY-MSGV3
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for FEHLERPROTOKOLL_FUELLEN

FEHLER - Error Message Table

Data type: SPROT_VW
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for FEHLERPROTOKOLL_FUELLEN 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_fehler  TYPE STANDARD TABLE OF SPROT_VW, "   
lv_i_arbg  TYPE TZW01-SARBG, "   
lv_i_msgv4  TYPE SY-MSGV4, "   SPACE
lv_i_xtext1  TYPE SPROT_VW-XTEXT1, "   SPACE
lv_i_xtext2  TYPE SPROT_VW-XTEXT2, "   SPACE
lv_i_xtext3  TYPE SPROT_VW-XTEXT3, "   SPACE
lv_i_bukrs  TYPE VWBEVI-BUKRS, "   
lv_i_langu  TYPE SY-LANGU, "   
lv_i_msgid  TYPE SY-MSGID, "   
lv_i_msgno  TYPE SY-MSGNO, "   
lv_i_msgty  TYPE SY-MSGTY, "   
lv_i_msgv1  TYPE SY-MSGV1, "   SPACE
lv_i_msgv2  TYPE SY-MSGV2, "   SPACE
lv_i_msgv3  TYPE SY-MSGV3. "   SPACE

  CALL FUNCTION 'FEHLERPROTOKOLL_FUELLEN'  "Fill Error Table for Deadline Monitoring
    EXPORTING
         I_ARBG = lv_i_arbg
         I_MSGV4 = lv_i_msgv4
         I_XTEXT1 = lv_i_xtext1
         I_XTEXT2 = lv_i_xtext2
         I_XTEXT3 = lv_i_xtext3
         I_BUKRS = lv_i_bukrs
         I_LANGU = lv_i_langu
         I_MSGID = lv_i_msgid
         I_MSGNO = lv_i_msgno
         I_MSGTY = lv_i_msgty
         I_MSGV1 = lv_i_msgv1
         I_MSGV2 = lv_i_msgv2
         I_MSGV3 = lv_i_msgv3
    TABLES
         FEHLER = lt_fehler
. " FEHLERPROTOKOLL_FUELLEN




ABAP code using 7.40 inline data declarations to call FM FEHLERPROTOKOLL_FUELLEN

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 SARBG FROM TZW01 INTO @DATA(ld_i_arbg).
 
"SELECT single MSGV4 FROM SY INTO @DATA(ld_i_msgv4).
DATA(ld_i_msgv4) = ' '.
 
"SELECT single XTEXT1 FROM SPROT_VW INTO @DATA(ld_i_xtext1).
DATA(ld_i_xtext1) = ' '.
 
"SELECT single XTEXT2 FROM SPROT_VW INTO @DATA(ld_i_xtext2).
DATA(ld_i_xtext2) = ' '.
 
"SELECT single XTEXT3 FROM SPROT_VW INTO @DATA(ld_i_xtext3).
DATA(ld_i_xtext3) = ' '.
 
"SELECT single BUKRS FROM VWBEVI INTO @DATA(ld_i_bukrs).
 
"SELECT single LANGU FROM SY INTO @DATA(ld_i_langu).
 
"SELECT single MSGID FROM SY INTO @DATA(ld_i_msgid).
 
"SELECT single MSGNO FROM SY INTO @DATA(ld_i_msgno).
 
"SELECT single MSGTY FROM SY INTO @DATA(ld_i_msgty).
 
"SELECT single MSGV1 FROM SY INTO @DATA(ld_i_msgv1).
DATA(ld_i_msgv1) = ' '.
 
"SELECT single MSGV2 FROM SY INTO @DATA(ld_i_msgv2).
DATA(ld_i_msgv2) = ' '.
 
"SELECT single MSGV3 FROM SY INTO @DATA(ld_i_msgv3).
DATA(ld_i_msgv3) = ' '.
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!