SAP BM_CUSTOMIZE Function Module for









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

Function Group: SF09
Program Name: SAPLSF09
Main Program: SAPLSF09
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function BM_CUSTOMIZE 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_CUSTOMIZE'"
EXPORTING
OBJECT_TYPE = "Object type
OBJECT_KEY = "Object key
* VARIANT = ' ' "

EXCEPTIONS
INVALID_OBJECT_TYPE = 1
.



IMPORTING Parameters details for BM_CUSTOMIZE

OBJECT_TYPE - Object type

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

OBJECT_KEY - Object key

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

VARIANT -

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

EXCEPTIONS details

INVALID_OBJECT_TYPE -

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

Copy and paste ABAP code example for BM_CUSTOMIZE 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_object_type  TYPE DF41S-PARENT_TYP, "   
lv_invalid_object_type  TYPE DF41S, "   
lv_object_key  TYPE DF41S-PARENT_OBJ, "   
lv_variant  TYPE DF50L-VARIANT_ID. "   SPACE

  CALL FUNCTION 'BM_CUSTOMIZE'  "
    EXPORTING
         OBJECT_TYPE = lv_object_type
         OBJECT_KEY = lv_object_key
         VARIANT = lv_variant
    EXCEPTIONS
        INVALID_OBJECT_TYPE = 1
. " BM_CUSTOMIZE




ABAP code using 7.40 inline data declarations to call FM BM_CUSTOMIZE

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 PARENT_TYP FROM DF41S INTO @DATA(ld_object_type).
 
 
"SELECT single PARENT_OBJ FROM DF41S INTO @DATA(ld_object_key).
 
"SELECT single VARIANT_ID FROM DF50L INTO @DATA(ld_variant).
DATA(ld_variant) = ' '.
 


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!