SAP ALINK_WRITE_LOG Function Module for









ALINK_WRITE_LOG is a standard alink 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 alink write log FM, simply by entering the name ALINK_WRITE_LOG into the relevant SAP transaction such as SE37 or SE38.

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



Function ALINK_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 'ALINK_WRITE_LOG'"
EXPORTING
LOGAREA = "Subobject for ArchiveLink Logging
* LFUNCTION = 'R' "
* LUSER = SY-UNAME "SAP System, User Logon Name
* LDATE = SY-DATUM "Date Data Element for SYST
* LTIME = SY-UZEIT "Date and Time, Current Application Server Time
* TOAV0 = "SAP ArchiveLink: Link Table
* TOADL = "SAP ArchiveLink print lists
* LBARCODE = "Character Field of Length 40

IMPORTING
WRITTEN = "Single-Character Flag

EXCEPTIONS
ERROR_PARAMETER = 1 ERROR_DDIC = 2
.



IMPORTING Parameters details for ALINK_WRITE_LOG

LOGAREA - Subobject for ArchiveLink Logging

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

LFUNCTION -

Data type: C
Default: 'R'
Optional: No
Call by Reference: No ( called with pass by value option)

LUSER - SAP System, User Logon Name

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

LDATE - Date Data Element for SYST

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

LTIME - Date and Time, Current Application Server Time

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

TOAV0 - SAP ArchiveLink: Link Table

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

TOADL - SAP ArchiveLink print lists

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

LBARCODE - Character Field of Length 40

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

EXPORTING Parameters details for ALINK_WRITE_LOG

WRITTEN - Single-Character Flag

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

EXCEPTIONS details

ERROR_PARAMETER - Data invalid

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

ERROR_DDIC - Error in database operation

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

Copy and paste ABAP code example for ALINK_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_logarea  TYPE SAESOBJ, "   
lv_written  TYPE BOOL, "   
lv_error_parameter  TYPE BOOL, "   
lv_lfunction  TYPE C, "   'R'
lv_error_ddic  TYPE C, "   
lv_luser  TYPE SYUNAME, "   SY-UNAME
lv_ldate  TYPE SYDATUM, "   SY-DATUM
lv_ltime  TYPE SYUZEIT, "   SY-UZEIT
lv_toav0  TYPE TOAV0, "   
lv_toadl  TYPE TOADL, "   
lv_lbarcode  TYPE CHAR40. "   

  CALL FUNCTION 'ALINK_WRITE_LOG'  "
    EXPORTING
         LOGAREA = lv_logarea
         LFUNCTION = lv_lfunction
         LUSER = lv_luser
         LDATE = lv_ldate
         LTIME = lv_ltime
         TOAV0 = lv_toav0
         TOADL = lv_toadl
         LBARCODE = lv_lbarcode
    IMPORTING
         WRITTEN = lv_written
    EXCEPTIONS
        ERROR_PARAMETER = 1
        ERROR_DDIC = 2
. " ALINK_WRITE_LOG




ABAP code using 7.40 inline data declarations to call FM ALINK_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.

 
 
 
DATA(ld_lfunction) = 'R'.
 
 
DATA(ld_luser) = SY-UNAME.
 
DATA(ld_ldate) = SY-DATUM.
 
DATA(ld_ltime) = SY-UZEIT.
 
 
 
 


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!