SAP SD_WRITE_LOG_VZLOG Function Module for NOTRANSL: Protokoll schreiben in VZLOG









SD_WRITE_LOG_VZLOG is a standard sd write log vzlog 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: Protokoll schreiben in VZLOG 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 sd write log vzlog FM, simply by entering the name SD_WRITE_LOG_VZLOG into the relevant SAP transaction such as SE37 or SE38.

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



Function SD_WRITE_LOG_VZLOG 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 'SD_WRITE_LOG_VZLOG'"NOTRANSL: Protokoll schreiben in VZLOG
  EXPORTING
*  I_PARKEY =  "Table Key Field (Abbreviated)
*  I_TCODE =  "Current Transaction Code
*  I_TABNAME =  "Table Name
*  I_TEXT_STRING =  "DE-EN-LANG-SWITCH-NO-TRANSLATION
*  I_PARNAME1 =  "Parameter Name 1
*  I_PARNAME2 =  "Parameter Name 2
*  I_PARNAME3 =  "Parameter Name 3
*  I_UNAME =  "User Name
*  I_DATUM =  "Current Date of Application Server
*  I_UZEIT =  "Current Time of Application Server
*  I_VBELN =  "Sales and Distribution Document Number
*  I_VBTYP =  "Sales Document Category
.



IMPORTING Parameters details for SD_WRITE_LOG_VZLOG

I_PARKEY - Table Key Field (Abbreviated)

Data type: PARKEY
Optional: Yes
Call by Reference: Yes

I_TCODE - Current Transaction Code

Data type: SYTCODE
Optional: Yes
Call by Reference: Yes

I_TABNAME - Table Name

Data type: TABNAME
Optional: Yes
Call by Reference: Yes

I_TEXT_STRING - DE-EN-LANG-SWITCH-NO-TRANSLATION

Data type: STRING
Optional: Yes
Call by Reference: Yes

I_PARNAME1 - Parameter Name 1

Data type: PARNAME1
Optional: Yes
Call by Reference: Yes

I_PARNAME2 - Parameter Name 2

Data type: PARNAME2
Optional: Yes
Call by Reference: Yes

I_PARNAME3 - Parameter Name 3

Data type: PARNAME3
Optional: Yes
Call by Reference: Yes

I_UNAME - User Name

Data type: USERNAME
Optional: Yes
Call by Reference: Yes

I_DATUM - Current Date of Application Server

Data type: SYDATUM
Optional: Yes
Call by Reference: Yes

I_UZEIT - Current Time of Application Server

Data type: SYUZEIT
Optional: Yes
Call by Reference: Yes

I_VBELN - Sales and Distribution Document Number

Data type: VBELN
Optional: Yes
Call by Reference: Yes

I_VBTYP - Sales Document Category

Data type: VBTYP
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for SD_WRITE_LOG_VZLOG 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_parkey  TYPE PARKEY, "   
lv_i_tcode  TYPE SYTCODE, "   
lv_i_tabname  TYPE TABNAME, "   
lv_i_text_string  TYPE STRING, "   
lv_i_parname1  TYPE PARNAME1, "   
lv_i_parname2  TYPE PARNAME2, "   
lv_i_parname3  TYPE PARNAME3, "   
lv_i_uname  TYPE USERNAME, "   
lv_i_datum  TYPE SYDATUM, "   
lv_i_uzeit  TYPE SYUZEIT, "   
lv_i_vbeln  TYPE VBELN, "   
lv_i_vbtyp  TYPE VBTYP. "   

  CALL FUNCTION 'SD_WRITE_LOG_VZLOG'  "NOTRANSL: Protokoll schreiben in VZLOG
    EXPORTING
         I_PARKEY = lv_i_parkey
         I_TCODE = lv_i_tcode
         I_TABNAME = lv_i_tabname
         I_TEXT_STRING = lv_i_text_string
         I_PARNAME1 = lv_i_parname1
         I_PARNAME2 = lv_i_parname2
         I_PARNAME3 = lv_i_parname3
         I_UNAME = lv_i_uname
         I_DATUM = lv_i_datum
         I_UZEIT = lv_i_uzeit
         I_VBELN = lv_i_vbeln
         I_VBTYP = lv_i_vbtyp
. " SD_WRITE_LOG_VZLOG




ABAP code using 7.40 inline data declarations to call FM SD_WRITE_LOG_VZLOG

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.

 
 
 
 
 
 
 
 
 
 
 
 


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!