SAP ME_LOG_GET_OBJECT_TYPE Function Module for NOTRANSL: Interface Anwendungs-Log: Objekttyp ermitteln
ME_LOG_GET_OBJECT_TYPE is a standard me log get object type SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Interface Anwendungs-Log: Objekttyp ermitteln processing and below is the pattern details for this FM, 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 me log get object type FM, simply by entering the name ME_LOG_GET_OBJECT_TYPE into the relevant SAP transaction such as SE37 or SE38.
Function Group: MELOG
Program Name: SAPLMELOG
Main Program: SAPLMELOG
Appliation area: D
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ME_LOG_GET_OBJECT_TYPE 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 'ME_LOG_GET_OBJECT_TYPE'"NOTRANSL: Interface Anwendungs-Log: Objekttyp ermitteln.
EXPORTING
IM_BSTYP = "Purchasing Document Category
IMPORTING
EX_OBJECT_TYPE = "Object Type
EXCEPTIONS
FAILURE = 1
IMPORTING Parameters details for ME_LOG_GET_OBJECT_TYPE
IM_BSTYP - Purchasing Document Category
Data type: EBSTYPOptional: No
Call by Reference: Yes
EXPORTING Parameters details for ME_LOG_GET_OBJECT_TYPE
EX_OBJECT_TYPE - Object Type
Data type: SWO_OBJTYPOptional: No
Call by Reference: Yes
EXCEPTIONS details
FAILURE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for ME_LOG_GET_OBJECT_TYPE 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_failure | TYPE STRING, " | |||
| lv_im_bstyp | TYPE EBSTYP, " | |||
| lv_ex_object_type | TYPE SWO_OBJTYP. " |
|   CALL FUNCTION 'ME_LOG_GET_OBJECT_TYPE' "NOTRANSL: Interface Anwendungs-Log: Objekttyp ermitteln |
| EXPORTING | ||
| IM_BSTYP | = lv_im_bstyp | |
| IMPORTING | ||
| EX_OBJECT_TYPE | = lv_ex_object_type | |
| EXCEPTIONS | ||
| FAILURE = 1 | ||
| . " ME_LOG_GET_OBJECT_TYPE | ||
ABAP code using 7.40 inline data declarations to call FM ME_LOG_GET_OBJECT_TYPE
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.Search for further information about these or an SAP related objects