SAP BM_OBJECT_TYPE_IS_EXTENDABLE Function Module for
BM_OBJECT_TYPE_IS_EXTENDABLE is a standard bm object type is extendable 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 type is extendable FM, simply by entering the name BM_OBJECT_TYPE_IS_EXTENDABLE into the relevant SAP transaction such as SE37 or SE38.
Function Group: SBM_EXTENSION
Program Name: SAPLSBM_EXTENSION
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BM_OBJECT_TYPE_IS_EXTENDABLE 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_TYPE_IS_EXTENDABLE'".
EXPORTING
OBJECT_TYPE = "Object Type
* STRUCTURE_TYPE = "Structure type
EXCEPTIONS
NOT_POSSIBLE = 1
IMPORTING Parameters details for BM_OBJECT_TYPE_IS_EXTENDABLE
OBJECT_TYPE - Object Type
Data type: BMOBJECT-TYPEOptional: No
Call by Reference: No ( called with pass by value option)
STRUCTURE_TYPE - Structure type
Data type: TTREE-TYPEOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NOT_POSSIBLE -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BM_OBJECT_TYPE_IS_EXTENDABLE 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 BMOBJECT-TYPE, " | |||
| lv_not_possible | TYPE BMOBJECT, " | |||
| lv_structure_type | TYPE TTREE-TYPE. " |
|   CALL FUNCTION 'BM_OBJECT_TYPE_IS_EXTENDABLE' " |
| EXPORTING | ||
| OBJECT_TYPE | = lv_object_type | |
| STRUCTURE_TYPE | = lv_structure_type | |
| EXCEPTIONS | ||
| NOT_POSSIBLE = 1 | ||
| . " BM_OBJECT_TYPE_IS_EXTENDABLE | ||
ABAP code using 7.40 inline data declarations to call FM BM_OBJECT_TYPE_IS_EXTENDABLE
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 TYPE FROM TTREE INTO @DATA(ld_structure_type). | ||||
Search for further information about these or an SAP related objects