APPL_LOG_WRITE_SINGLE_MESSAGE SAP Function module - Application log: Enter single message without parameters

APPL_LOG_WRITE_SINGLE_MESSAGE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name APPL_LOG_WRITE_SINGLE_MESSAGE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: SLG0
Released Date: 22.12.1994
Processing type: Normal fucntion module

Pattern for FM APPL_LOG_WRITE_SINGLE_MESSAGE - APPL LOG WRITE SINGLE MESSAGE

CALL FUNCTION 'APPL_LOG_WRITE_SINGLE_MESSAGE' "Application log: Enter single message without parameters
  EXPORTING
*   object = SPACE              " balhdr-object  Object name
*   subobject = SPACE           " balhdr-subobject  Sub-object name
*   log_handle = SPACE          " balhdr-log_handle  Log handle
    message =                   " balmi         Message
*   update_or_insert = 'U'      "               Change (U) or insert (I) message flag
  IMPORTING
    e_msg_handle =              " balmsghndl    Message handle
  EXCEPTIONS
    OBJECT_NOT_FOUND = 1        "               Object not found
    SUBOBJECT_NOT_FOUND = 2     "               Subobject not found
    .  "  APPL_LOG_WRITE_SINGLE_MESSAGE

ABAP code example for Function Module APPL_LOG_WRITE_SINGLE_MESSAGE

The ABAP code below is a full code listing to execute function module APPL_LOG_WRITE_SINGLE_MESSAGE including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_e_msg_handle  
 
 TYPE BALMSGHNDL
.

 

SELECT single OBJECT 
  FROM BALHDR 
  INTO @DATA(ld_object).

 

SELECT single SUBOBJECT 
  FROM BALHDR 
  INTO @DATA(ld_subobject).

 

SELECT single LOG_HANDLE 
  FROM BALHDR 
  INTO @DATA(ld_log_handle).


DATA(ld_message) = 'Check type of data required'.

DATA(ld_update_or_insert) = 'some text here'.
.

CALL FUNCTION 'APPL_LOG_WRITE_SINGLE_MESSAGE'
  EXPORTING
*   object =                     ld_object
*   subobject =                  ld_subobject
*   log_handle =                 ld_log_handle
    message =                    ld_message
*   update_or_insert =           ld_update_or_insert
  IMPORTING
    e_msg_handle =               ld_e_msg_handle
  EXCEPTIONS
    OBJECT_NOT_FOUND =           1
    SUBOBJECT_NOT_FOUND =        2
    .  "  APPL_LOG_WRITE_SINGLE_MESSAGE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_e_msg_handle
 
 TYPE BALMSGHNDL ,
ld_object
 
 TYPE BALHDR-OBJECT ,
ld_subobject
 
 TYPE BALHDR-SUBOBJECT ,
ld_log_handle
 
 TYPE BALHDR-LOG_HANDLE ,
ld_message
 
 TYPE BALMI ,
ld_update_or_insert
 
 TYPE STRING .



SELECT single OBJECT 
  FROM BALHDR 
  INTO ld_object.


SELECT single SUBOBJECT 
  FROM BALHDR 
  INTO ld_subobject.


SELECT single LOG_HANDLE 
  FROM BALHDR 
  INTO ld_log_handle.

ld_message = 'Check type of data required'.
ld_update_or_insert = 'some text here'.