SAP ME_LOG_READ_BUILD_OBJ Function Module for NOTRANSL: Interface Anwendungs-Log: gelesenen Log in Objektform ueberfuehr









ME_LOG_READ_BUILD_OBJ is a standard me log read build obj 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: gelesenen Log in Objektform ueberfuehr 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 read build obj FM, simply by entering the name ME_LOG_READ_BUILD_OBJ 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_READ_BUILD_OBJ 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_READ_BUILD_OBJ'"NOTRANSL: Interface Anwendungs-Log: gelesenen Log in Objektform ueberfuehr
  EXPORTING
   IM_OBJECT =  "Message object
   IM_DESCRIPTION =  "Purchasing Documents: Object Description

 IMPORTING
   EX_OBJECT_WITH_ERROR =  "Boolean Variable (X=True, -=False, Space=Unknown)
   EX_ENQ_ERR_MAT =  "Boolean Variable (X=True, -=False, Space=Unknown)
   EX_ENQ_ERR_CON =  "Boolean Variable (X=True, -=False, Space=Unknown)
   EX_BITMASK =  "Generic Type

EXCEPTIONS
   ILLEGAL_CALL = 1    ILLEGAL_PARAMETERS = 2    NOTHING_FOUND = 3
.



IMPORTING Parameters details for ME_LOG_READ_BUILD_OBJ

IM_OBJECT - Message object

Data type: MMPUR_MESSAGE_OBJ
Optional: No
Call by Reference: Yes

IM_DESCRIPTION - Purchasing Documents: Object Description

Data type: MEPO_OBJDESC
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for ME_LOG_READ_BUILD_OBJ

EX_OBJECT_WITH_ERROR - Boolean Variable (X=True, -=False, Space=Unknown)

Data type: BOOLEAN
Optional: No
Call by Reference: Yes

EX_ENQ_ERR_MAT - Boolean Variable (X=True, -=False, Space=Unknown)

Data type: BOOLEAN
Optional: No
Call by Reference: Yes

EX_ENQ_ERR_CON - Boolean Variable (X=True, -=False, Space=Unknown)

Data type: BOOLEAN
Optional: No
Call by Reference: Yes

EX_BITMASK - Generic Type

Data type: ANY
Optional: No
Call by Reference: Yes

EXCEPTIONS details

ILLEGAL_CALL -

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

ILLEGAL_PARAMETERS -

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

NOTHING_FOUND -

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

Copy and paste ABAP code example for ME_LOG_READ_BUILD_OBJ 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_im_object  TYPE MMPUR_MESSAGE_OBJ, "   
lv_illegal_call  TYPE MMPUR_MESSAGE_OBJ, "   
lv_ex_object_with_error  TYPE BOOLEAN, "   
lv_ex_enq_err_mat  TYPE BOOLEAN, "   
lv_im_description  TYPE MEPO_OBJDESC, "   
lv_illegal_parameters  TYPE MEPO_OBJDESC, "   
lv_nothing_found  TYPE MEPO_OBJDESC, "   
lv_ex_enq_err_con  TYPE BOOLEAN, "   
lv_ex_bitmask  TYPE ANY. "   

  CALL FUNCTION 'ME_LOG_READ_BUILD_OBJ'  "NOTRANSL: Interface Anwendungs-Log: gelesenen Log in Objektform ueberfuehr
    EXPORTING
         IM_OBJECT = lv_im_object
         IM_DESCRIPTION = lv_im_description
    IMPORTING
         EX_OBJECT_WITH_ERROR = lv_ex_object_with_error
         EX_ENQ_ERR_MAT = lv_ex_enq_err_mat
         EX_ENQ_ERR_CON = lv_ex_enq_err_con
         EX_BITMASK = lv_ex_bitmask
    EXCEPTIONS
        ILLEGAL_CALL = 1
        ILLEGAL_PARAMETERS = 2
        NOTHING_FOUND = 3
. " ME_LOG_READ_BUILD_OBJ




ABAP code using 7.40 inline data declarations to call FM ME_LOG_READ_BUILD_OBJ

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



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!