SAP BBP_OM_USR_ASSIGN_USER Function Module for
BBP_OM_USR_ASSIGN_USER is a standard bbp om usr assign user 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 bbp om usr assign user FM, simply by entering the name BBP_OM_USR_ASSIGN_USER into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_OM_USER
Program Name: SAPLBBP_OM_USER
Main Program: SAPLBBP_OM_USER
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function BBP_OM_USR_ASSIGN_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 'BBP_OM_USR_ASSIGN_USER'".
EXPORTING
IS_EMPLOYEE_ID = "
* IV_USERNAME = "
* IV_CHECK_USER_EXISTENCE = 'X' "
* IV_CUT_ASSIGNMENTS = 'X' "
* IV_COMMIT_FLAG = 'X' "
EXCEPTIONS
CX_BBP_OM_INTERNAL_ERROR = 1 CX_BBP_OM_NOT_FOUND = 2 CX_BBP_OM_CONFLICT = 3 CX_BBP_OM_NO_AUTHORIZATION = 4
IMPORTING Parameters details for BBP_OM_USR_ASSIGN_USER
IS_EMPLOYEE_ID -
Data type: BBPS_ES_PERSON_IDOptional: No
Call by Reference: Yes
IV_USERNAME -
Data type: XUBNAMEOptional: Yes
Call by Reference: Yes
IV_CHECK_USER_EXISTENCE -
Data type: XFLAGDefault: 'X'
Optional: Yes
Call by Reference: Yes
IV_CUT_ASSIGNMENTS -
Data type: XFLAGDefault: 'X'
Optional: Yes
Call by Reference: Yes
IV_COMMIT_FLAG -
Data type: COMMIT_FLGDefault: 'X'
Optional: Yes
Call by Reference: Yes
EXCEPTIONS details
CX_BBP_OM_INTERNAL_ERROR -
Data type:Optional: No
Call by Reference: Yes
CX_BBP_OM_NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
CX_BBP_OM_CONFLICT -
Data type:Optional: No
Call by Reference: Yes
CX_BBP_OM_NO_AUTHORIZATION -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BBP_OM_USR_ASSIGN_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_is_employee_id | TYPE BBPS_ES_PERSON_ID, " | |||
lv_cx_bbp_om_internal_error | TYPE BBPS_ES_PERSON_ID, " | |||
lv_iv_username | TYPE XUBNAME, " | |||
lv_cx_bbp_om_not_found | TYPE XUBNAME, " | |||
lv_cx_bbp_om_conflict | TYPE XUBNAME, " | |||
lv_iv_check_user_existence | TYPE XFLAG, " 'X' | |||
lv_iv_cut_assignments | TYPE XFLAG, " 'X' | |||
lv_cx_bbp_om_no_authorization | TYPE XFLAG, " | |||
lv_iv_commit_flag | TYPE COMMIT_FLG. " 'X' |
  CALL FUNCTION 'BBP_OM_USR_ASSIGN_USER' " |
EXPORTING | ||
IS_EMPLOYEE_ID | = lv_is_employee_id | |
IV_USERNAME | = lv_iv_username | |
IV_CHECK_USER_EXISTENCE | = lv_iv_check_user_existence | |
IV_CUT_ASSIGNMENTS | = lv_iv_cut_assignments | |
IV_COMMIT_FLAG | = lv_iv_commit_flag | |
EXCEPTIONS | ||
CX_BBP_OM_INTERNAL_ERROR = 1 | ||
CX_BBP_OM_NOT_FOUND = 2 | ||
CX_BBP_OM_CONFLICT = 3 | ||
CX_BBP_OM_NO_AUTHORIZATION = 4 | ||
. " BBP_OM_USR_ASSIGN_USER |
ABAP code using 7.40 inline data declarations to call FM BBP_OM_USR_ASSIGN_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.DATA(ld_iv_check_user_existence) | = 'X'. | |||
DATA(ld_iv_cut_assignments) | = 'X'. | |||
DATA(ld_iv_commit_flag) | = 'X'. | |||
Search for further information about these or an SAP related objects