SAP BBP_GET_USER_PIDS Function Module for Get Internet user's parameters









BBP_GET_USER_PIDS is a standard bbp get user pids SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get Internet user's parameters processing and below is the pattern details for this FM, 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 get user pids FM, simply by entering the name BBP_GET_USER_PIDS into the relevant SAP transaction such as SE37 or SE38.

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



Function BBP_GET_USER_PIDS 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_GET_USER_PIDS'"Get Internet user's parameters
EXPORTING
USER_ID = "user ID
* PARAMETER_ID = "
* DEFAULT_VALUE_ONLY = 'X' "General flag

TABLES
PIDLIST = "internal table that holds all PID entries

EXCEPTIONS
ERROR_GET_PIDS = 1
.



IMPORTING Parameters details for BBP_GET_USER_PIDS

USER_ID - user ID

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

PARAMETER_ID -

Data type: BBP_PIDDAT-PID
Optional: Yes
Call by Reference: No ( called with pass by value option)

DEFAULT_VALUE_ONLY - General flag

Data type: FLAG
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BBP_GET_USER_PIDS

PIDLIST - internal table that holds all PID entries

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

EXCEPTIONS details

ERROR_GET_PIDS - No PId entries for the user

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

Copy and paste ABAP code example for BBP_GET_USER_PIDS 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:
lt_pidlist  TYPE STANDARD TABLE OF PIDS, "   
lv_user_id  TYPE BBP_PIDDAT-NODE_NO, "   
lv_error_get_pids  TYPE BBP_PIDDAT, "   
lv_parameter_id  TYPE BBP_PIDDAT-PID, "   
lv_default_value_only  TYPE FLAG. "   'X'

  CALL FUNCTION 'BBP_GET_USER_PIDS'  "Get Internet user's parameters
    EXPORTING
         USER_ID = lv_user_id
         PARAMETER_ID = lv_parameter_id
         DEFAULT_VALUE_ONLY = lv_default_value_only
    TABLES
         PIDLIST = lt_pidlist
    EXCEPTIONS
        ERROR_GET_PIDS = 1
. " BBP_GET_USER_PIDS




ABAP code using 7.40 inline data declarations to call FM BBP_GET_USER_PIDS

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.

 
"SELECT single NODE_NO FROM BBP_PIDDAT INTO @DATA(ld_user_id).
 
 
"SELECT single PID FROM BBP_PIDDAT INTO @DATA(ld_parameter_id).
 
DATA(ld_default_value_only) = '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!