SAP BM_OBJECT_GET_DATA Function Module for









BM_OBJECT_GET_DATA is a standard bm object get data 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 bm object get data FM, simply by entering the name BM_OBJECT_GET_DATA into the relevant SAP transaction such as SE37 or SE38.

Function Group: SFTO
Program Name: SAPLSFTO
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function BM_OBJECT_GET_DATA 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 'BM_OBJECT_GET_DATA'"
EXPORTING
OBJECT_TYPE = "
OBJECT_ID = "
* LANGUAGE = SY-LANGU "
* CHECK_OBJECT_TYPE = 'X' "
* DELETE_DELIMITERS = 'X' "
* READ_DEVCLASS = ' ' "

IMPORTING
IS_DELETED = "

CHANGING
* GENERAL_DATA = "
* SPECIFIC_DATA = "

EXCEPTIONS
NOT_FOUND = 1 WRONG_OBJECT_TYPE = 2
.



IMPORTING Parameters details for BM_OBJECT_GET_DATA

OBJECT_TYPE -

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

OBJECT_ID -

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

LANGUAGE -

Data type: SY-LANGU
Default: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)

CHECK_OBJECT_TYPE -

Data type: BMT_FLAG
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

DELETE_DELIMITERS -

Data type: BMT_FLAG
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

READ_DEVCLASS -

Data type: BMT_FLAG
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for BM_OBJECT_GET_DATA

IS_DELETED -

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

CHANGING Parameters details for BM_OBJECT_GET_DATA

GENERAL_DATA -

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

SPECIFIC_DATA -

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

EXCEPTIONS details

NOT_FOUND -

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

WRONG_OBJECT_TYPE -

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

Copy and paste ABAP code example for BM_OBJECT_GET_DATA 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_not_found  TYPE STRING, "   
lv_is_deleted  TYPE BMT_FLAG, "   
lv_object_type  TYPE BMOBJECT-TYPE, "   
lv_general_data  TYPE BMOBJECT, "   
lv_object_id  TYPE BMOBJECT-ID, "   
lv_specific_data  TYPE ANY, "   
lv_wrong_object_type  TYPE ANY, "   
lv_language  TYPE SY-LANGU, "   SY-LANGU
lv_check_object_type  TYPE BMT_FLAG, "   'X'
lv_delete_delimiters  TYPE BMT_FLAG, "   'X'
lv_read_devclass  TYPE BMT_FLAG. "   SPACE

  CALL FUNCTION 'BM_OBJECT_GET_DATA'  "
    EXPORTING
         OBJECT_TYPE = lv_object_type
         OBJECT_ID = lv_object_id
         LANGUAGE = lv_language
         CHECK_OBJECT_TYPE = lv_check_object_type
         DELETE_DELIMITERS = lv_delete_delimiters
         READ_DEVCLASS = lv_read_devclass
    IMPORTING
         IS_DELETED = lv_is_deleted
    CHANGING
         GENERAL_DATA = lv_general_data
         SPECIFIC_DATA = lv_specific_data
    EXCEPTIONS
        NOT_FOUND = 1
        WRONG_OBJECT_TYPE = 2
. " BM_OBJECT_GET_DATA




ABAP code using 7.40 inline data declarations to call FM BM_OBJECT_GET_DATA

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 TYPE FROM BMOBJECT INTO @DATA(ld_object_type).
 
 
"SELECT single ID FROM BMOBJECT INTO @DATA(ld_object_id).
 
 
 
"SELECT single LANGU FROM SY INTO @DATA(ld_language).
DATA(ld_language) = SY-LANGU.
 
DATA(ld_check_object_type) = 'X'.
 
DATA(ld_delete_delimiters) = 'X'.
 
DATA(ld_read_devclass) = ' '.
 


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!