SAP UJE_API_BATCH_MANAGE_USER Function Module for BPC: Add/Update Users and their profile and team assignment









UJE_API_BATCH_MANAGE_USER is a standard uje api batch manage user 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: Add/Update Users and their profile and team assignment 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 batch manage user FM, simply by entering the name UJE_API_BATCH_MANAGE_USER 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_BATCH_MANAGE_USER 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_BATCH_MANAGE_USER'"BPC: Add/Update Users and their profile and team assignment
  EXPORTING
   I_APPSET_ID =  "BPC: AppSet ID
   IS_USER =  "BPC: User Login Info
   IT_USER_INFO =  "BPC: User
   I_ACTION =  "BPC: Action Flag to indicate the action taken on the record
   IT_TEAM_ASIN =  "BPC: Internal Table of User Team
   IT_TPROFILE_ID =  "Task Profile Assignment List
   IT_MPROFILE_ID =  "Member Access Profile Assignment List

 IMPORTING
   E_SUCCESS =  "BPC: Bool
   ET_MESSAGE_LINES =  "BPC: Error Log
.



IMPORTING Parameters details for UJE_API_BATCH_MANAGE_USER

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)

IT_USER_INFO - BPC: User

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

I_ACTION - BPC: Action Flag to indicate the action taken on the record

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

IT_TEAM_ASIN - BPC: Internal Table of User Team

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

IT_TPROFILE_ID - Task Profile Assignment List

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

IT_MPROFILE_ID - Member Access Profile Assignment List

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

EXPORTING Parameters details for UJE_API_BATCH_MANAGE_USER

E_SUCCESS - BPC: Bool

Data type: UJ_BOOL
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)

Copy and paste ABAP code example for UJE_API_BATCH_MANAGE_USER 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_e_success  TYPE UJ_BOOL, "   
lv_i_appset_id  TYPE UJ_APPSET_ID, "   
lv_is_user  TYPE UJ0_S_USER, "   
lv_et_message_lines  TYPE UJ0_T_MESSAGE, "   
lv_it_user_info  TYPE UJE_T_USER_INFO_ACT, "   
lv_i_action  TYPE UJ_ACTION, "   
lv_it_team_asin  TYPE UJE_T_USER_TEAM, "   
lv_it_tprofile_id  TYPE UJE_T_PROFILE_ASIN, "   
lv_it_mprofile_id  TYPE UJE_T_PROFILE_ASIN. "   

  CALL FUNCTION 'UJE_API_BATCH_MANAGE_USER'  "BPC: Add/Update Users and their profile and team assignment
    EXPORTING
         I_APPSET_ID = lv_i_appset_id
         IS_USER = lv_is_user
         IT_USER_INFO = lv_it_user_info
         I_ACTION = lv_i_action
         IT_TEAM_ASIN = lv_it_team_asin
         IT_TPROFILE_ID = lv_it_tprofile_id
         IT_MPROFILE_ID = lv_it_mprofile_id
    IMPORTING
         E_SUCCESS = lv_e_success
         ET_MESSAGE_LINES = lv_et_message_lines
. " UJE_API_BATCH_MANAGE_USER




ABAP code using 7.40 inline data declarations to call FM UJE_API_BATCH_MANAGE_USER

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!