SAP EWU_PROTOCOL_APPEND Function Module for NOTRANSL: Anhängen einer Zeile an das Protokoll









EWU_PROTOCOL_APPEND is a standard ewu protocol append 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: Anhängen einer Zeile an das Protokoll 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 ewu protocol append FM, simply by entering the name EWU_PROTOCOL_APPEND into the relevant SAP transaction such as SE37 or SE38.

Function Group: EWU4
Program Name: SAPLEWU4
Main Program:
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function EWU_PROTOCOL_APPEND 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 'EWU_PROTOCOL_APPEND'"NOTRANSL: Anhängen einer Zeile an das Protokoll
EXPORTING
* LEVEL = '1' "Level
* MSGV4 = ' ' "Text Variable
* MSGTY = ' ' "Defect type
* LANGU = SY-LANGU "Language
MSGID = "Application area
MSGNO = "Error Number
* NEWOBJ = ' ' "New Object
* MSGV1 = ' ' "Text Variable
* MSGV2 = ' ' "Text Variable
* MSGV3 = ' ' "Text Variable

EXCEPTIONS
PROTOCOL_ERROR = 1
.



IMPORTING Parameters details for EWU_PROTOCOL_APPEND

LEVEL - Level

Data type: SPROT-LEVEL
Default: '1'
Optional: Yes
Call by Reference: No ( called with pass by value option)

MSGV4 - Text Variable

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

MSGTY - Defect type

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

LANGU - Language

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

MSGID - Application area

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

MSGNO - Error Number

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

NEWOBJ - New Object

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

MSGV1 - Text Variable

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

MSGV2 - Text Variable

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

MSGV3 - Text Variable

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

EXCEPTIONS details

PROTOCOL_ERROR -

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

Copy and paste ABAP code example for EWU_PROTOCOL_APPEND 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_level  TYPE SPROT-LEVEL, "   '1'
lv_protocol_error  TYPE SPROT, "   
lv_msgv4  TYPE SPROT, "   SPACE
lv_msgty  TYPE SY-MSGTY, "   SPACE
lv_langu  TYPE SY-LANGU, "   SY-LANGU
lv_msgid  TYPE SY-MSGID, "   
lv_msgno  TYPE SY-MSGNO, "   
lv_newobj  TYPE SPROT-NEWOBJ, "   SPACE
lv_msgv1  TYPE SPROT, "   SPACE
lv_msgv2  TYPE SPROT, "   SPACE
lv_msgv3  TYPE SPROT. "   SPACE

  CALL FUNCTION 'EWU_PROTOCOL_APPEND'  "NOTRANSL: Anhängen einer Zeile an das Protokoll
    EXPORTING
         LEVEL = lv_level
         MSGV4 = lv_msgv4
         MSGTY = lv_msgty
         LANGU = lv_langu
         MSGID = lv_msgid
         MSGNO = lv_msgno
         NEWOBJ = lv_newobj
         MSGV1 = lv_msgv1
         MSGV2 = lv_msgv2
         MSGV3 = lv_msgv3
    EXCEPTIONS
        PROTOCOL_ERROR = 1
. " EWU_PROTOCOL_APPEND




ABAP code using 7.40 inline data declarations to call FM EWU_PROTOCOL_APPEND

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 LEVEL FROM SPROT INTO @DATA(ld_level).
DATA(ld_level) = '1'.
 
 
DATA(ld_msgv4) = ' '.
 
"SELECT single MSGTY FROM SY INTO @DATA(ld_msgty).
DATA(ld_msgty) = ' '.
 
"SELECT single LANGU FROM SY INTO @DATA(ld_langu).
DATA(ld_langu) = SY-LANGU.
 
"SELECT single MSGID FROM SY INTO @DATA(ld_msgid).
 
"SELECT single MSGNO FROM SY INTO @DATA(ld_msgno).
 
"SELECT single NEWOBJ FROM SPROT INTO @DATA(ld_newobj).
DATA(ld_newobj) = ' '.
 
DATA(ld_msgv1) = ' '.
 
DATA(ld_msgv2) = ' '.
 
DATA(ld_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!