SAP ARCHIV_WRITE_LOG Function Module for









ARCHIV_WRITE_LOG is a standard archiv write log SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 archiv write log FM, simply by entering the name ARCHIV_WRITE_LOG into the relevant SAP transaction such as SE37 or SE38.

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



Function ARCHIV_WRITE_LOG 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 'ARCHIV_WRITE_LOG'"
  EXPORTING
*  COMMAND = 'INFO' "Command
*  STRING1 = ' ' "Problem description 1
*  STRING2 = ' ' "Problem description 2
*  LOGGING = ' ' "Calling point
*  MESSAGE_ID = SY-MSGID "Message ID
*  MESSAGE_TYPE = SY-MSGTY "
*  MESSAGE_NUMBER = SY-MSGNO "Message number
*  MSGV1 = SY-MSGV1 "
*  MSGV2 = SY-MSGV2 "
*  MSGV3 = SY-MSGV3 "
*  MSGV4 = SY-MSGV4 "
.



IMPORTING Parameters details for ARCHIV_WRITE_LOG

COMMAND - Command

Data type: TOA_L03-COMMAND
Default: 'INFO'
Optional: Yes
Call by Reference: No ( called with pass by value option)

STRING1 - Problem description 1

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

STRING2 - Problem description 2

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

LOGGING - Calling point

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

MESSAGE_ID - Message ID

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

MESSAGE_TYPE -

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

MESSAGE_NUMBER - Message number

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

MSGV1 -

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

MSGV2 -

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

MSGV3 -

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

MSGV4 -

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

Copy and paste ABAP code example for ARCHIV_WRITE_LOG 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_command  TYPE TOA_L03-COMMAND, "   'INFO'
lv_string1  TYPE TOA_L03-STRING, "   SPACE
lv_string2  TYPE TOA_L03-STRING2, "   SPACE
lv_logging  TYPE TOA_L03-LOGGING, "   SPACE
lv_message_id  TYPE SY-MSGID, "   SY-MSGID
lv_message_type  TYPE SY-MSGTY, "   SY-MSGTY
lv_message_number  TYPE SY-MSGNO, "   SY-MSGNO
lv_msgv1  TYPE SY, "   SY-MSGV1
lv_msgv2  TYPE SY, "   SY-MSGV2
lv_msgv3  TYPE SY, "   SY-MSGV3
lv_msgv4  TYPE SY. "   SY-MSGV4

  CALL FUNCTION 'ARCHIV_WRITE_LOG'  "
    EXPORTING
         COMMAND = lv_command
         STRING1 = lv_string1
         STRING2 = lv_string2
         LOGGING = lv_logging
         MESSAGE_ID = lv_message_id
         MESSAGE_TYPE = lv_message_type
         MESSAGE_NUMBER = lv_message_number
         MSGV1 = lv_msgv1
         MSGV2 = lv_msgv2
         MSGV3 = lv_msgv3
         MSGV4 = lv_msgv4
. " ARCHIV_WRITE_LOG




ABAP code using 7.40 inline data declarations to call FM ARCHIV_WRITE_LOG

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 COMMAND FROM TOA_L03 INTO @DATA(ld_command).
DATA(ld_command) = 'INFO'.
 
"SELECT single STRING FROM TOA_L03 INTO @DATA(ld_string1).
DATA(ld_string1) = ' '.
 
"SELECT single STRING2 FROM TOA_L03 INTO @DATA(ld_string2).
DATA(ld_string2) = ' '.
 
"SELECT single LOGGING FROM TOA_L03 INTO @DATA(ld_logging).
DATA(ld_logging) = ' '.
 
"SELECT single MSGID FROM SY INTO @DATA(ld_message_id).
DATA(ld_message_id) = SY-MSGID.
 
"SELECT single MSGTY FROM SY INTO @DATA(ld_message_type).
DATA(ld_message_type) = SY-MSGTY.
 
"SELECT single MSGNO FROM SY INTO @DATA(ld_message_number).
DATA(ld_message_number) = SY-MSGNO.
 
DATA(ld_msgv1) = SY-MSGV1.
 
DATA(ld_msgv2) = SY-MSGV2.
 
DATA(ld_msgv3) = SY-MSGV3.
 
DATA(ld_msgv4) = SY-MSGV4.
 


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!