SAP UJE_API_DELETE_PROFILE Function Module for BPC: Delete Profile

Search SAP Function Modules

UJE_API_DELETE_PROFILE is a standard uje api delete profile 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: Delete 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 delete profile FM, simply by entering the name UJE_API_DELETE_PROFILE 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_DELETE_PROFILE 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_DELETE_PROFILE'"BPC: Delete Profile
  EXPORTING
   I_APPSET_ID =  "BPC: AppSet ID
   IS_USER =  "BPC: User Login Info
   I_PROFILE_ID =  "BPC: Profile ID
   I_PROFILE_CLASS =  "BPC security profile class

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

.

IMPORTING Parameters details for UJE_API_DELETE_PROFILE

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)

I_PROFILE_CLASS - BPC security profile class

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

EXPORTING Parameters details for UJE_API_DELETE_PROFILE

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_DELETE_PROFILE 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_DELETE_PROFILE

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