SRM_WRITE_APPLICATION_LOG 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 SRM_WRITE_APPLICATION_LOG into the relevant SAP transaction such as SE37 or SE80.
Associated Function Group:
SRM01
Released Date:
Not Released
Processing type: Normal fucntion module
CALL FUNCTION 'SRM_WRITE_APPLICATION_LOG' "
EXPORTING
msgid = " sy-msgid Messages, Message Class
msgty = " sy-msgty Messages, Message Type
msgno = " sy-msgno Messages, Message Number
* msgv1 = " sy-msgv1 Messages, Message Variable
* msgv2 = " sy-msgv2 Messages, Message Variable
* msgv3 = " sy-msgv3 Messages, Message Variable
* msgv4 = " sy-msgv4 Messages, Message Variable
* text = " balmi-altext Application log: Standard text
* probclass = " balmi-probclass Application log: Message problem class
* object = 'SRM' " balhdr-object Application log: Object name (Application code)
subobject = " balhdr-subobject Application Log: Subobject
* no_update_task = 'X' " boolean Boolean Variable (X=true, -=false, space=unknown)
* do_commit = '-' " boolean
. " SRM_WRITE_APPLICATION_LOG
The ABAP code below is a full code listing to execute function module SRM_WRITE_APPLICATION_LOG 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_msgid) = 'some text here'.
DATA(ld_msgty) = 'some text here'.
DATA(ld_msgno) = 'Check type of data required'.
DATA(ld_msgv1) = 'some text here'.
DATA(ld_msgv2) = 'some text here'.
DATA(ld_msgv3) = 'some text here'.
DATA(ld_msgv4) = 'some text here'.
DATA(ld_text) = some text here
DATA(ld_probclass) = some text here
SELECT single OBJECT
FROM BALHDR
INTO @DATA(ld_object).
SELECT single SUBOBJECT
FROM BALHDR
INTO @DATA(ld_subobject).
DATA(ld_no_update_task) = 'some text here'.
DATA(ld_do_commit) = 'some text here'. . CALL FUNCTION 'SRM_WRITE_APPLICATION_LOG' EXPORTING msgid = ld_msgid msgty = ld_msgty msgno = ld_msgno * msgv1 = ld_msgv1 * msgv2 = ld_msgv2 * msgv3 = ld_msgv3 * msgv4 = ld_msgv4 * text = ld_text * probclass = ld_probclass * object = ld_object subobject = ld_subobject * no_update_task = ld_no_update_task * do_commit = ld_do_commit . " SRM_WRITE_APPLICATION_LOG
IF SY-SUBRC EQ 0. "All OK ENDIF.
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_msgid | TYPE SY-MSGID , |
| ld_msgty | TYPE SY-MSGTY , |
| ld_msgno | TYPE SY-MSGNO , |
| ld_msgv1 | TYPE SY-MSGV1 , |
| ld_msgv2 | TYPE SY-MSGV2 , |
| ld_msgv3 | TYPE SY-MSGV3 , |
| ld_msgv4 | TYPE SY-MSGV4 , |
| ld_text | TYPE BALMI-ALTEXT , |
| ld_probclass | TYPE BALMI-PROBCLASS , |
| ld_object | TYPE BALHDR-OBJECT , |
| ld_subobject | TYPE BALHDR-SUBOBJECT , |
| ld_no_update_task | TYPE BOOLEAN , |
| ld_do_commit | TYPE BOOLEAN . |
Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name SRM_WRITE_APPLICATION_LOG or its description.