SAP BBP_OM_USR_ASSIGN_POSITION Function Module for









BBP_OM_USR_ASSIGN_POSITION is a standard bbp om usr assign position 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 position FM, simply by entering the name BBP_OM_USR_ASSIGN_POSITION 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_POSITION 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_POSITION'"
EXPORTING
IV_POSITION_ID = "
* IV_ORGUNIT_ID = "
* IV_BEGDA = SY-DATUM "
* IV_ENDDA = '99991231' "
* IV_CUT_ASSIGNMENTS = 'X' "
* IV_COMMIT_FLAG = 'X' "

EXCEPTIONS
CX_BBP_OM_INTERNAL_ERROR = 1 CX_BBP_OM_NOT_FOUND = 2 CX_BBP_OM_NO_AUTHORIZATION = 3
.



IMPORTING Parameters details for BBP_OM_USR_ASSIGN_POSITION

IV_POSITION_ID -

Data type: HROBJID
Optional: No
Call by Reference: Yes

IV_ORGUNIT_ID -

Data type: HROBJID
Optional: Yes
Call by Reference: Yes

IV_BEGDA -

Data type: BEGDA
Default: SY-DATUM
Optional: Yes
Call by Reference: Yes

IV_ENDDA -

Data type: ENDDA
Default: '99991231'
Optional: Yes
Call by Reference: Yes

IV_CUT_ASSIGNMENTS -

Data type: XFLAG
Default: 'X'
Optional: Yes
Call by Reference: Yes

IV_COMMIT_FLAG -

Data type: XFLAG
Default: '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_NO_AUTHORIZATION -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BBP_OM_USR_ASSIGN_POSITION 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_iv_position_id  TYPE HROBJID, "   
lv_cx_bbp_om_internal_error  TYPE HROBJID, "   
lv_iv_orgunit_id  TYPE HROBJID, "   
lv_cx_bbp_om_not_found  TYPE HROBJID, "   
lv_iv_begda  TYPE BEGDA, "   SY-DATUM
lv_cx_bbp_om_no_authorization  TYPE BEGDA, "   
lv_iv_endda  TYPE ENDDA, "   '99991231'
lv_iv_cut_assignments  TYPE XFLAG, "   'X'
lv_iv_commit_flag  TYPE XFLAG. "   'X'

  CALL FUNCTION 'BBP_OM_USR_ASSIGN_POSITION'  "
    EXPORTING
         IV_POSITION_ID = lv_iv_position_id
         IV_ORGUNIT_ID = lv_iv_orgunit_id
         IV_BEGDA = lv_iv_begda
         IV_ENDDA = lv_iv_endda
         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_NO_AUTHORIZATION = 3
. " BBP_OM_USR_ASSIGN_POSITION




ABAP code using 7.40 inline data declarations to call FM BBP_OM_USR_ASSIGN_POSITION

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_begda) = SY-DATUM.
 
 
DATA(ld_iv_endda) = '99991231'.
 
DATA(ld_iv_cut_assignments) = 'X'.
 
DATA(ld_iv_commit_flag) = 'X'.
 


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!