SAP SUBST_APPEND_DEFAULT_PROTOCOL Function Module for Aufbereitung einer Nachricht in interne Tabelle









SUBST_APPEND_DEFAULT_PROTOCOL is a standard subst append default protocol SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Aufbereitung einer Nachricht in interne Tabelle 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 subst append default protocol FM, simply by entering the name SUBST_APPEND_DEFAULT_PROTOCOL into the relevant SAP transaction such as SE37 or SE38.

Function Group: SUGI
Program Name: SAPLSUGI
Main Program: SAPLSUGI
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function SUBST_APPEND_DEFAULT_PROTOCOL 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 'SUBST_APPEND_DEFAULT_PROTOCOL'"Aufbereitung einer Nachricht in interne Tabelle
  EXPORTING
*  IV_LEVEL = '3' "
*  IV_V4 = ' ' "
*  IV_SEVERITY = ' ' "
*  IV_LANGU = ' ' "
*  IV_MSAG = ' ' "
*  IV_MSGNR = ' ' "
*  IV_NEWOBJ = ' ' "
*  IV_V1 = ' ' "
*  IV_V2 = ' ' "
*  IV_V3 = ' ' "
.



IMPORTING Parameters details for SUBST_APPEND_DEFAULT_PROTOCOL

IV_LEVEL -

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

IV_V4 -

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

IV_SEVERITY -

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

IV_LANGU -

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

IV_MSAG -

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

IV_MSGNR -

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

IV_NEWOBJ -

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

IV_V1 -

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

IV_V2 -

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

IV_V3 -

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

Copy and paste ABAP code example for SUBST_APPEND_DEFAULT_PROTOCOL 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_iv_level  TYPE SPROT-LEVEL, "   '3'
lv_iv_v4  TYPE SY-MSGV4, "   SPACE
lv_iv_severity  TYPE SPROT-SEVERITY, "   SPACE
lv_iv_langu  TYPE SPROT-LANGU, "   SPACE
lv_iv_msag  TYPE SPROT-AG, "   SPACE
lv_iv_msgnr  TYPE SY-MSGNO, "   SPACE
lv_iv_newobj  TYPE SPROT-NEWOBJ, "   SPACE
lv_iv_v1  TYPE SY-MSGV1, "   SPACE
lv_iv_v2  TYPE SY-MSGV2, "   SPACE
lv_iv_v3  TYPE SY-MSGV3. "   SPACE

  CALL FUNCTION 'SUBST_APPEND_DEFAULT_PROTOCOL'  "Aufbereitung einer Nachricht in interne Tabelle
    EXPORTING
         IV_LEVEL = lv_iv_level
         IV_V4 = lv_iv_v4
         IV_SEVERITY = lv_iv_severity
         IV_LANGU = lv_iv_langu
         IV_MSAG = lv_iv_msag
         IV_MSGNR = lv_iv_msgnr
         IV_NEWOBJ = lv_iv_newobj
         IV_V1 = lv_iv_v1
         IV_V2 = lv_iv_v2
         IV_V3 = lv_iv_v3
. " SUBST_APPEND_DEFAULT_PROTOCOL




ABAP code using 7.40 inline data declarations to call FM SUBST_APPEND_DEFAULT_PROTOCOL

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_iv_level).
DATA(ld_iv_level) = '3'.
 
"SELECT single MSGV4 FROM SY INTO @DATA(ld_iv_v4).
DATA(ld_iv_v4) = ' '.
 
"SELECT single SEVERITY FROM SPROT INTO @DATA(ld_iv_severity).
DATA(ld_iv_severity) = ' '.
 
"SELECT single LANGU FROM SPROT INTO @DATA(ld_iv_langu).
DATA(ld_iv_langu) = ' '.
 
"SELECT single AG FROM SPROT INTO @DATA(ld_iv_msag).
DATA(ld_iv_msag) = ' '.
 
"SELECT single MSGNO FROM SY INTO @DATA(ld_iv_msgnr).
DATA(ld_iv_msgnr) = ' '.
 
"SELECT single NEWOBJ FROM SPROT INTO @DATA(ld_iv_newobj).
DATA(ld_iv_newobj) = ' '.
 
"SELECT single MSGV1 FROM SY INTO @DATA(ld_iv_v1).
DATA(ld_iv_v1) = ' '.
 
"SELECT single MSGV2 FROM SY INTO @DATA(ld_iv_v2).
DATA(ld_iv_v2) = ' '.
 
"SELECT single MSGV3 FROM SY INTO @DATA(ld_iv_v3).
DATA(ld_iv_v3) = ' '.
 


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!