SAP ISU_DEVCHECK_APPLLOG_ONE_MSG Function Module for
ISU_DEVCHECK_APPLLOG_ONE_MSG is a standard isu devcheck appllog one msg 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 isu devcheck appllog one msg FM, simply by entering the name ISU_DEVCHECK_APPLLOG_ONE_MSG into the relevant SAP transaction such as SE37 or SE38.
Function Group: EDEC
Program Name: SAPLEDEC
Main Program: SAPLEDEC
Appliation area: E
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ISU_DEVCHECK_APPLLOG_ONE_MSG 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 'ISU_DEVCHECK_APPLLOG_ONE_MSG'".
EXPORTING
X_OBJECT = "
* X_ALTEXT = "
* X_USEREXITP = "
* X_USEREXITF = "
* X_DETLEVEL = "
* X_PROBCLASS = "
* X_ALSORT = "
X_SUBOBJECT = "
X_MSGTY = "
X_MSGID = "
X_MSGNO = "
* X_MSGV1 = "
* X_MSGV2 = "
* X_MSGV3 = "
* X_MSGV4 = "
EXCEPTIONS
OBJECT_NOT_FOUND = 1 SUBOBJECT_NOT_FOUND = 2
IMPORTING Parameters details for ISU_DEVCHECK_APPLLOG_ONE_MSG
X_OBJECT -
Data type: BALHDR-OBJECTOptional: No
Call by Reference: No ( called with pass by value option)
X_ALTEXT -
Data type: BALMI-ALTEXTOptional: Yes
Call by Reference: No ( called with pass by value option)
X_USEREXITP -
Data type: BALMI-USEREXITPOptional: Yes
Call by Reference: No ( called with pass by value option)
X_USEREXITF -
Data type: BALMI-USEREXITFOptional: Yes
Call by Reference: No ( called with pass by value option)
X_DETLEVEL -
Data type: BALMI-DETLEVELOptional: Yes
Call by Reference: No ( called with pass by value option)
X_PROBCLASS -
Data type: BALMI-PROBCLASSOptional: Yes
Call by Reference: No ( called with pass by value option)
X_ALSORT -
Data type: BALMI-ALSORTOptional: Yes
Call by Reference: No ( called with pass by value option)
X_SUBOBJECT -
Data type: BALHDR-SUBOBJECTOptional: No
Call by Reference: No ( called with pass by value option)
X_MSGTY -
Data type: BALMI-MSGTYOptional: No
Call by Reference: No ( called with pass by value option)
X_MSGID -
Data type: BALMI-MSGIDOptional: No
Call by Reference: No ( called with pass by value option)
X_MSGNO -
Data type: BALMI-MSGNOOptional: No
Call by Reference: No ( called with pass by value option)
X_MSGV1 -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
X_MSGV2 -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
X_MSGV3 -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
X_MSGV4 -
Data type:Optional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
OBJECT_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
SUBOBJECT_NOT_FOUND -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ISU_DEVCHECK_APPLLOG_ONE_MSG 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_x_object | TYPE BALHDR-OBJECT, " | |||
| lv_object_not_found | TYPE BALHDR, " | |||
| lv_x_altext | TYPE BALMI-ALTEXT, " | |||
| lv_x_userexitp | TYPE BALMI-USEREXITP, " | |||
| lv_x_userexitf | TYPE BALMI-USEREXITF, " | |||
| lv_x_detlevel | TYPE BALMI-DETLEVEL, " | |||
| lv_x_probclass | TYPE BALMI-PROBCLASS, " | |||
| lv_x_alsort | TYPE BALMI-ALSORT, " | |||
| lv_x_subobject | TYPE BALHDR-SUBOBJECT, " | |||
| lv_subobject_not_found | TYPE BALHDR, " | |||
| lv_x_msgty | TYPE BALMI-MSGTY, " | |||
| lv_x_msgid | TYPE BALMI-MSGID, " | |||
| lv_x_msgno | TYPE BALMI-MSGNO, " | |||
| lv_x_msgv1 | TYPE BALMI, " | |||
| lv_x_msgv2 | TYPE BALMI, " | |||
| lv_x_msgv3 | TYPE BALMI, " | |||
| lv_x_msgv4 | TYPE BALMI. " |
|   CALL FUNCTION 'ISU_DEVCHECK_APPLLOG_ONE_MSG' " |
| EXPORTING | ||
| X_OBJECT | = lv_x_object | |
| X_ALTEXT | = lv_x_altext | |
| X_USEREXITP | = lv_x_userexitp | |
| X_USEREXITF | = lv_x_userexitf | |
| X_DETLEVEL | = lv_x_detlevel | |
| X_PROBCLASS | = lv_x_probclass | |
| X_ALSORT | = lv_x_alsort | |
| X_SUBOBJECT | = lv_x_subobject | |
| X_MSGTY | = lv_x_msgty | |
| X_MSGID | = lv_x_msgid | |
| X_MSGNO | = lv_x_msgno | |
| X_MSGV1 | = lv_x_msgv1 | |
| X_MSGV2 | = lv_x_msgv2 | |
| X_MSGV3 | = lv_x_msgv3 | |
| X_MSGV4 | = lv_x_msgv4 | |
| EXCEPTIONS | ||
| OBJECT_NOT_FOUND = 1 | ||
| SUBOBJECT_NOT_FOUND = 2 | ||
| . " ISU_DEVCHECK_APPLLOG_ONE_MSG | ||
ABAP code using 7.40 inline data declarations to call FM ISU_DEVCHECK_APPLLOG_ONE_MSG
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 OBJECT FROM BALHDR INTO @DATA(ld_x_object). | ||||
| "SELECT single ALTEXT FROM BALMI INTO @DATA(ld_x_altext). | ||||
| "SELECT single USEREXITP FROM BALMI INTO @DATA(ld_x_userexitp). | ||||
| "SELECT single USEREXITF FROM BALMI INTO @DATA(ld_x_userexitf). | ||||
| "SELECT single DETLEVEL FROM BALMI INTO @DATA(ld_x_detlevel). | ||||
| "SELECT single PROBCLASS FROM BALMI INTO @DATA(ld_x_probclass). | ||||
| "SELECT single ALSORT FROM BALMI INTO @DATA(ld_x_alsort). | ||||
| "SELECT single SUBOBJECT FROM BALHDR INTO @DATA(ld_x_subobject). | ||||
| "SELECT single MSGTY FROM BALMI INTO @DATA(ld_x_msgty). | ||||
| "SELECT single MSGID FROM BALMI INTO @DATA(ld_x_msgid). | ||||
| "SELECT single MSGNO FROM BALMI INTO @DATA(ld_x_msgno). | ||||
Search for further information about these or an SAP related objects