SAP BM_STRUCTURE_ACCESS_PERMISSION Function Module for









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

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



Function BM_STRUCTURE_ACCESS_PERMISSION 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_STRUCTURE_ACCESS_PERMISSION'"
  EXPORTING
   STRUCTURE_ID =  "
*  STRUCTURE_TYPE = ' ' "Structure type
   MODE =  "Check-in mode: Insert / change
*  DEVCLASS =  "
*  LANGUAGE = SY-LANGU "Current Language
*  SUPPRESS_LANGUAGE_CHECK = ' ' "
*  OBJECT_TYPE =  "
*  OBJECT_ID =  "

 IMPORTING
   ENQUEUED =  "
   E_DEVCLASS =  "

TABLES
*  MESSAGES =  "Messages
.



IMPORTING Parameters details for BM_STRUCTURE_ACCESS_PERMISSION

STRUCTURE_ID -

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

STRUCTURE_TYPE - Structure type

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

MODE - Check-in mode: Insert / change

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

DEVCLASS -

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

LANGUAGE - Current Language

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

SUPPRESS_LANGUAGE_CHECK -

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

OBJECT_TYPE -

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

OBJECT_ID -

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

EXPORTING Parameters details for BM_STRUCTURE_ACCESS_PERMISSION

ENQUEUED -

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

E_DEVCLASS -

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

TABLES Parameters details for BM_STRUCTURE_ACCESS_PERMISSION

MESSAGES - Messages

Data type: BMMSGTAB
Optional: Yes
Call by Reference: Yes

Copy and paste ABAP code example for BM_STRUCTURE_ACCESS_PERMISSION 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_enqueued  TYPE UFFLAG, "   
lt_messages  TYPE STANDARD TABLE OF BMMSGTAB, "   
lv_structure_id  TYPE TTREE-ID, "   
lv_e_devclass  TYPE DEVCLASS, "   
lv_structure_type  TYPE TTREE-TYPE, "   SPACE
lv_mode  TYPE RPYGSGF-MODE, "   
lv_devclass  TYPE DEVCLASS, "   
lv_language  TYPE SY-LANGU, "   SY-LANGU
lv_suppress_language_check  TYPE BMT_FLAG, "   SPACE
lv_object_type  TYPE BMOBJECT-TYPE, "   
lv_object_id  TYPE ANY. "   

  CALL FUNCTION 'BM_STRUCTURE_ACCESS_PERMISSION'  "
    EXPORTING
         STRUCTURE_ID = lv_structure_id
         STRUCTURE_TYPE = lv_structure_type
         MODE = lv_mode
         DEVCLASS = lv_devclass
         LANGUAGE = lv_language
         SUPPRESS_LANGUAGE_CHECK = lv_suppress_language_check
         OBJECT_TYPE = lv_object_type
         OBJECT_ID = lv_object_id
    IMPORTING
         ENQUEUED = lv_enqueued
         E_DEVCLASS = lv_e_devclass
    TABLES
         MESSAGES = lt_messages
. " BM_STRUCTURE_ACCESS_PERMISSION




ABAP code using 7.40 inline data declarations to call FM BM_STRUCTURE_ACCESS_PERMISSION

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 ID FROM TTREE INTO @DATA(ld_structure_id).
 
 
"SELECT single TYPE FROM TTREE INTO @DATA(ld_structure_type).
DATA(ld_structure_type) = ' '.
 
"SELECT single MODE FROM RPYGSGF INTO @DATA(ld_mode).
 
 
"SELECT single LANGU FROM SY INTO @DATA(ld_language).
DATA(ld_language) = SY-LANGU.
 
DATA(ld_suppress_language_check) = ' '.
 
"SELECT single TYPE FROM BMOBJECT INTO @DATA(ld_object_type).
 
 


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!