SAP UJE_API_GET_MPROFILEDATA Function Module for BPC: Get all the details of the member access profile









UJE_API_GET_MPROFILEDATA is a standard uje api get mprofiledata SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for BPC: Get all the details of the member access profile 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 uje api get mprofiledata FM, simply by entering the name UJE_API_GET_MPROFILEDATA into the relevant SAP transaction such as SE37 or SE38.

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



Function UJE_API_GET_MPROFILEDATA 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 'UJE_API_GET_MPROFILEDATA'"BPC: Get all the details of the member access profile
  EXPORTING
   I_APPSET_ID =  "BPC: AppSet ID
   IS_USER =  "BPC: User Login Info
   I_PROFILE_ID =  "BPC: Profile ID

 IMPORTING
   ES_PROFILE =  "BPC: Profile
   ET_MEMACCESS =  "BPC: Internal Table of Member Access
   ET_APP_DIM =  "Available secured dimensions per application
   ET_USER_ID =  "BPC: internal table of user id
   ET_TEAM_ID =  "BPC: Internal Table of Team ID
   ET_MESSAGE_LINES =  "BPC: Error Log
   E_SUCCESS =  "BPC: Bool
.



IMPORTING Parameters details for UJE_API_GET_MPROFILEDATA

I_APPSET_ID - BPC: AppSet ID

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

IS_USER - BPC: User Login Info

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

I_PROFILE_ID - BPC: Profile ID

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

EXPORTING Parameters details for UJE_API_GET_MPROFILEDATA

ES_PROFILE - BPC: Profile

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

ET_MEMACCESS - BPC: Internal Table of Member Access

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

ET_APP_DIM - Available secured dimensions per application

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

ET_USER_ID - BPC: internal table of user id

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

ET_TEAM_ID - BPC: Internal Table of Team ID

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

ET_MESSAGE_LINES - BPC: Error Log

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

E_SUCCESS - BPC: Bool

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

Copy and paste ABAP code example for UJE_API_GET_MPROFILEDATA 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_es_profile  TYPE UJE_S_PROFILE, "   
lv_i_appset_id  TYPE UJ_APPSET_ID, "   
lv_is_user  TYPE UJ0_S_USER, "   
lv_et_memaccess  TYPE UJE_T_MEMACCESS, "   
lv_et_app_dim  TYPE UJE_TS_APP_DIM, "   
lv_i_profile_id  TYPE UJ_PROFILE_ID, "   
lv_et_user_id  TYPE UJE_T_API_USER_ID, "   
lv_et_team_id  TYPE UJE_T_API_TEAM_ID, "   
lv_et_message_lines  TYPE UJ0_T_MESSAGE, "   
lv_e_success  TYPE UJ_BOOL. "   

  CALL FUNCTION 'UJE_API_GET_MPROFILEDATA'  "BPC: Get all the details of the member access profile
    EXPORTING
         I_APPSET_ID = lv_i_appset_id
         IS_USER = lv_is_user
         I_PROFILE_ID = lv_i_profile_id
    IMPORTING
         ES_PROFILE = lv_es_profile
         ET_MEMACCESS = lv_et_memaccess
         ET_APP_DIM = lv_et_app_dim
         ET_USER_ID = lv_et_user_id
         ET_TEAM_ID = lv_et_team_id
         ET_MESSAGE_LINES = lv_et_message_lines
         E_SUCCESS = lv_e_success
. " UJE_API_GET_MPROFILEDATA




ABAP code using 7.40 inline data declarations to call FM UJE_API_GET_MPROFILEDATA

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!