SAP BBP_CM_APP_USERS_GET Function Module for Get responsible Users for specified categories
BBP_CM_APP_USERS_GET is a standard bbp cm app users get 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 responsible Users for specified categories 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 cm app users get FM, simply by entering the name BBP_CM_APP_USERS_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: BBP_CM_COM_INF_MASTDATA
Program Name: SAPLBBP_CM_COM_INF_MASTDATA
Main Program: SAPLBBP_CM_APP_PROGRAM
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BBP_CM_APP_USERS_GET 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_CM_APP_USERS_GET'"Get responsible Users for specified categories.
EXPORTING
IV_CAT_GUID = "GUID in character format
TABLES
ET_USERS = "List of Bidders
IMPORTING Parameters details for BBP_CM_APP_USERS_GET
IV_CAT_GUID - GUID in character format
Data type: BBP_CM_GUID_DOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for BBP_CM_APP_USERS_GET
ET_USERS - List of Bidders
Data type: BBPS_CM_BIDDERLIST_F4Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for BBP_CM_APP_USERS_GET 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_et_users | TYPE STANDARD TABLE OF BBPS_CM_BIDDERLIST_F4, " | |||
| lv_iv_cat_guid | TYPE BBP_CM_GUID_D. " |
|   CALL FUNCTION 'BBP_CM_APP_USERS_GET' "Get responsible Users for specified categories |
| EXPORTING | ||
| IV_CAT_GUID | = lv_iv_cat_guid | |
| TABLES | ||
| ET_USERS | = lt_et_users | |
| . " BBP_CM_APP_USERS_GET | ||
ABAP code using 7.40 inline data declarations to call FM BBP_CM_APP_USERS_GET
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.Search for further information about these or an SAP related objects