SAP BBP_OM_USR_CREATE_POS_AT_ORG Function Module for
BBP_OM_USR_CREATE_POS_AT_ORG is a standard bbp om usr create pos at org 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 create pos at org FM, simply by entering the name BBP_OM_USR_CREATE_POS_AT_ORG 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_CREATE_POS_AT_ORG 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_CREATE_POS_AT_ORG'".
EXPORTING
* ACT_HOLDER = SY-UNAME "
ACT_ORGUNIT = "
* ACT_STEXT = "
* ACT_SHORT = "
* IS_MANAGER = "
* POSITION_ID = '00000000' "
* IV_COMMIT_FLAG = 'X' "
IMPORTING
ACT_POSITION = "
EXCEPTIONS
ORGUNIT_NOT_VALID = 1 POSITION_NOT_VALID = 2 NO_ACTIVE_PLVAR = 3 ERROR_TO_GET_NEW_NUMBER = 4 ERROR_DURING_INSERT = 5 ENQUEUE_ERROR = 6 DEQUEUE_ERROR = 7 USER_NOT_VALID = 8 ERROR_ON_DATE = 9
IMPORTING Parameters details for BBP_OM_USR_CREATE_POS_AT_ORG
ACT_HOLDER -
Data type:Default: SY-UNAME
Optional: Yes
Call by Reference: No ( called with pass by value option)
ACT_ORGUNIT -
Data type: HROBJECT-OBJIDOptional: No
Call by Reference: No ( called with pass by value option)
ACT_STEXT -
Data type: OBJEC-STEXTOptional: Yes
Call by Reference: No ( called with pass by value option)
ACT_SHORT -
Data type: OBJEC-SHORTOptional: Yes
Call by Reference: No ( called with pass by value option)
IS_MANAGER -
Data type: FLAGOptional: Yes
Call by Reference: No ( called with pass by value option)
POSITION_ID -
Data type: OBJEC-OBJIDDefault: '00000000'
Optional: Yes
Call by Reference: No ( called with pass by value option)
IV_COMMIT_FLAG -
Data type: COMMIT_FLGDefault: 'X'
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for BBP_OM_USR_CREATE_POS_AT_ORG
ACT_POSITION -
Data type: HROBJECT-OBJIDOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ORGUNIT_NOT_VALID -
Data type:Optional: No
Call by Reference: Yes
POSITION_NOT_VALID -
Data type:Optional: No
Call by Reference: Yes
NO_ACTIVE_PLVAR -
Data type:Optional: No
Call by Reference: Yes
ERROR_TO_GET_NEW_NUMBER -
Data type:Optional: No
Call by Reference: Yes
ERROR_DURING_INSERT -
Data type:Optional: No
Call by Reference: Yes
ENQUEUE_ERROR -
Data type:Optional: No
Call by Reference: Yes
DEQUEUE_ERROR -
Data type:Optional: No
Call by Reference: Yes
USER_NOT_VALID -
Data type:Optional: No
Call by Reference: Yes
ERROR_ON_DATE -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BBP_OM_USR_CREATE_POS_AT_ORG 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_act_holder | TYPE STRING, " SY-UNAME | |||
| lv_act_position | TYPE HROBJECT-OBJID, " | |||
| lv_orgunit_not_valid | TYPE HROBJECT, " | |||
| lv_act_orgunit | TYPE HROBJECT-OBJID, " | |||
| lv_position_not_valid | TYPE HROBJECT, " | |||
| lv_act_stext | TYPE OBJEC-STEXT, " | |||
| lv_no_active_plvar | TYPE OBJEC, " | |||
| lv_act_short | TYPE OBJEC-SHORT, " | |||
| lv_error_to_get_new_number | TYPE OBJEC, " | |||
| lv_is_manager | TYPE FLAG, " | |||
| lv_error_during_insert | TYPE FLAG, " | |||
| lv_position_id | TYPE OBJEC-OBJID, " '00000000' | |||
| lv_enqueue_error | TYPE OBJEC, " | |||
| lv_dequeue_error | TYPE OBJEC, " | |||
| lv_iv_commit_flag | TYPE COMMIT_FLG, " 'X' | |||
| lv_user_not_valid | TYPE COMMIT_FLG, " | |||
| lv_error_on_date | TYPE COMMIT_FLG. " |
|   CALL FUNCTION 'BBP_OM_USR_CREATE_POS_AT_ORG' " |
| EXPORTING | ||
| ACT_HOLDER | = lv_act_holder | |
| ACT_ORGUNIT | = lv_act_orgunit | |
| ACT_STEXT | = lv_act_stext | |
| ACT_SHORT | = lv_act_short | |
| IS_MANAGER | = lv_is_manager | |
| POSITION_ID | = lv_position_id | |
| IV_COMMIT_FLAG | = lv_iv_commit_flag | |
| IMPORTING | ||
| ACT_POSITION | = lv_act_position | |
| EXCEPTIONS | ||
| ORGUNIT_NOT_VALID = 1 | ||
| POSITION_NOT_VALID = 2 | ||
| NO_ACTIVE_PLVAR = 3 | ||
| ERROR_TO_GET_NEW_NUMBER = 4 | ||
| ERROR_DURING_INSERT = 5 | ||
| ENQUEUE_ERROR = 6 | ||
| DEQUEUE_ERROR = 7 | ||
| USER_NOT_VALID = 8 | ||
| ERROR_ON_DATE = 9 | ||
| . " BBP_OM_USR_CREATE_POS_AT_ORG | ||
ABAP code using 7.40 inline data declarations to call FM BBP_OM_USR_CREATE_POS_AT_ORG
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_act_holder) | = SY-UNAME. | |||
| "SELECT single OBJID FROM HROBJECT INTO @DATA(ld_act_position). | ||||
| "SELECT single OBJID FROM HROBJECT INTO @DATA(ld_act_orgunit). | ||||
| "SELECT single STEXT FROM OBJEC INTO @DATA(ld_act_stext). | ||||
| "SELECT single SHORT FROM OBJEC INTO @DATA(ld_act_short). | ||||
| "SELECT single OBJID FROM OBJEC INTO @DATA(ld_position_id). | ||||
| DATA(ld_position_id) | = '00000000'. | |||
| DATA(ld_iv_commit_flag) | = 'X'. | |||
Search for further information about these or an SAP related objects