SAP UJE_API_GET_USERDATA Function Module for BPC: Retrieve all of the details of a user

Search SAP Function Modules

UJE_API_GET_USERDATA is a standard uje api get userdata 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: Retrieve all of the details of a user 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 userdata FM, simply by entering the name UJE_API_GET_USERDATA 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_USERDATA 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_USERDATA'"BPC: Retrieve all of the details of a user
  EXPORTING
   I_APPSET_ID =  "BPC: AppSet ID
   IS_USER =  "BPC: User Login Info
*  I_USER_ID =  "BPC: User ID

 IMPORTING
   ET_USER =  "BPC: Internal Table of User Details
   E_SUCCESS =  "BPC: Error Log
   ET_MESSAGE_LINES =  "BPC: Messages

.

IMPORTING Parameters details for UJE_API_GET_USERDATA

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_USER_ID - BPC: User ID

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

EXPORTING Parameters details for UJE_API_GET_USERDATA

ET_USER - BPC: Internal Table of User Details

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

E_SUCCESS - BPC: Error Log

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

ET_MESSAGE_LINES - BPC: Messages

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_GET_USERDATA 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.

ABAP code using 7.40 inline data declarations to call FM UJE_API_GET_USERDATA

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