SAP BBP_OM_USR_RESTORE_POSITION Function Module for
BBP_OM_USR_RESTORE_POSITION is a standard bbp om usr restore 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 restore position FM, simply by entering the name BBP_OM_USR_RESTORE_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_RESTORE_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_RESTORE_POSITION'".
EXPORTING
HANDLE = "
* RELEASE_HANDLE = 'X' "
ORGUNIT = "
CENTRAL_PERSON = "
USER = "
* COMMIT = 'X' "
IMPORTING
POSITION = "
EXCEPTIONS
INVALID_HANDLE = 1 INTERNAL_ERROR = 2 WRITE_ERROR = 3 DELETE_ERROR = 4 INVALID_ORGUNIT = 5 INVALID_PERSON = 6 INVALID_USER = 7
IMPORTING Parameters details for BBP_OM_USR_RESTORE_POSITION
HANDLE -
Data type: IOptional: No
Call by Reference: Yes
RELEASE_HANDLE -
Data type: FLAGDefault: 'X'
Optional: Yes
Call by Reference: Yes
ORGUNIT -
Data type: HROBJIDOptional: No
Call by Reference: Yes
CENTRAL_PERSON -
Data type: HROBJIDOptional: No
Call by Reference: Yes
USER -
Data type: UNAMEOptional: No
Call by Reference: Yes
COMMIT -
Data type: FLAGDefault: 'X'
Optional: Yes
Call by Reference: Yes
EXPORTING Parameters details for BBP_OM_USR_RESTORE_POSITION
POSITION -
Data type: HROBJIDOptional: No
Call by Reference: Yes
EXCEPTIONS details
INVALID_HANDLE -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INTERNAL_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
WRITE_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DELETE_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_ORGUNIT -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_PERSON -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
INVALID_USER -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BBP_OM_USR_RESTORE_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_handle | TYPE I, " | |||
| lv_position | TYPE HROBJID, " | |||
| lv_invalid_handle | TYPE HROBJID, " | |||
| lv_internal_error | TYPE HROBJID, " | |||
| lv_release_handle | TYPE FLAG, " 'X' | |||
| lv_orgunit | TYPE HROBJID, " | |||
| lv_write_error | TYPE HROBJID, " | |||
| lv_delete_error | TYPE HROBJID, " | |||
| lv_central_person | TYPE HROBJID, " | |||
| lv_user | TYPE UNAME, " | |||
| lv_invalid_orgunit | TYPE UNAME, " | |||
| lv_commit | TYPE FLAG, " 'X' | |||
| lv_invalid_person | TYPE FLAG, " | |||
| lv_invalid_user | TYPE FLAG. " |
|   CALL FUNCTION 'BBP_OM_USR_RESTORE_POSITION' " |
| EXPORTING | ||
| HANDLE | = lv_handle | |
| RELEASE_HANDLE | = lv_release_handle | |
| ORGUNIT | = lv_orgunit | |
| CENTRAL_PERSON | = lv_central_person | |
| USER | = lv_user | |
| COMMIT | = lv_commit | |
| IMPORTING | ||
| POSITION | = lv_position | |
| EXCEPTIONS | ||
| INVALID_HANDLE = 1 | ||
| INTERNAL_ERROR = 2 | ||
| WRITE_ERROR = 3 | ||
| DELETE_ERROR = 4 | ||
| INVALID_ORGUNIT = 5 | ||
| INVALID_PERSON = 6 | ||
| INVALID_USER = 7 | ||
| . " BBP_OM_USR_RESTORE_POSITION | ||
ABAP code using 7.40 inline data declarations to call FM BBP_OM_USR_RESTORE_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_release_handle) | = 'X'. | |||
| DATA(ld_commit) | = 'X'. | |||
Search for further information about these or an SAP related objects