SAP BBP_OM_STRUC_GET_POS_FROM_USER Function Module for









BBP_OM_STRUC_GET_POS_FROM_USER is a standard bbp om struc get pos from 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 struc get pos from user FM, simply by entering the name BBP_OM_STRUC_GET_POS_FROM_USER into the relevant SAP transaction such as SE37 or SE38.

Function Group: BBP_OM_STRUCTURE
Program Name: SAPLBBP_OM_STRUCTURE
Main Program: SAPLBBP_OM_STRUCTURE
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function BBP_OM_STRUC_GET_POS_FROM_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_STRUC_GET_POS_FROM_USER'"
  EXPORTING
   USER =  "
*  SEL_DATE = SY-DATUM "
*  PPOMA_CALL = ' ' "
*  AUTHORITY_CHECK = 'X' "

 IMPORTING
   POSITION =  "

EXCEPTIONS
   PATH_NOT_FOUND = 1    ERROR_READING_STRUCTURE = 2    NO_ROOTS = 3    INVALID_ROOTS = 4    INTERNAL_ERROR = 5    POSITION_IS_AMBIGUOUS = 6    POSITION_IS_UNOCCUPIED = 7
.



IMPORTING Parameters details for BBP_OM_STRUC_GET_POS_FROM_USER

USER -

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

SEL_DATE -

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

PPOMA_CALL -

Data type: FLAG
Default: SPACE
Optional: Yes
Call by Reference: Yes

AUTHORITY_CHECK -

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

EXPORTING Parameters details for BBP_OM_STRUC_GET_POS_FROM_USER

POSITION -

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

EXCEPTIONS details

PATH_NOT_FOUND -

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

ERROR_READING_STRUCTURE -

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

NO_ROOTS -

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

INVALID_ROOTS -

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)

POSITION_IS_AMBIGUOUS -

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

POSITION_IS_UNOCCUPIED -

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

Copy and paste ABAP code example for BBP_OM_STRUC_GET_POS_FROM_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_user  TYPE UNAME, "   
lv_position  TYPE HROBJID, "   
lv_path_not_found  TYPE HROBJID, "   
lv_sel_date  TYPE OMSELDATE, "   SY-DATUM
lv_error_reading_structure  TYPE OMSELDATE, "   
lv_no_roots  TYPE OMSELDATE, "   
lv_ppoma_call  TYPE FLAG, "   SPACE
lv_invalid_roots  TYPE FLAG, "   
lv_authority_check  TYPE FLAG, "   'X'
lv_internal_error  TYPE FLAG, "   
lv_position_is_ambiguous  TYPE FLAG, "   
lv_position_is_unoccupied  TYPE FLAG. "   

  CALL FUNCTION 'BBP_OM_STRUC_GET_POS_FROM_USER'  "
    EXPORTING
         USER = lv_user
         SEL_DATE = lv_sel_date
         PPOMA_CALL = lv_ppoma_call
         AUTHORITY_CHECK = lv_authority_check
    IMPORTING
         POSITION = lv_position
    EXCEPTIONS
        PATH_NOT_FOUND = 1
        ERROR_READING_STRUCTURE = 2
        NO_ROOTS = 3
        INVALID_ROOTS = 4
        INTERNAL_ERROR = 5
        POSITION_IS_AMBIGUOUS = 6
        POSITION_IS_UNOCCUPIED = 7
. " BBP_OM_STRUC_GET_POS_FROM_USER




ABAP code using 7.40 inline data declarations to call FM BBP_OM_STRUC_GET_POS_FROM_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_sel_date) = SY-DATUM.
 
 
 
DATA(ld_ppoma_call) = ' '.
 
 
DATA(ld_authority_check) = '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!