SAP BBP_USER_GET_DETAIL_FIELDS_INT Function Module for









BBP_USER_GET_DETAIL_FIELDS_INT is a standard bbp user get detail fields int 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 user get detail fields int FM, simply by entering the name BBP_USER_GET_DETAIL_FIELDS_INT into the relevant SAP transaction such as SE37 or SE38.

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



Function BBP_USER_GET_DETAIL_FIELDS_INT 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_USER_GET_DETAIL_FIELDS_INT'"
EXPORTING
USERNAME = "
* GET_MANAGER_AND_ORGUNIT = 'X' "
* GET_DEFAULT_COUNTRY = 'X' "

IMPORTING
LASTNAME = "
ROOM_NUMBER = "
INHOUSE_MAIL = "
TELEPHONE_NUMBER = "
TELEPHONE_EXTENSION = "
FAX_NUMBER = "
FAX_EXTENSION = "
DATE_FORMAT = "
DECIMAL_FORMAT = "
IS_MANAGER_X_FLAG = "
IS_MANAGER_ON_FLAG = "
FIRSTNAME = "
ORGUNIT = "
COUNTRY = "
USER_TYPE = "
REGION = "
COMM_TYPE = "
LOGONDATA = "
E_MAIL = "
ACADEMIC_TITLE_KEY = "
ACADEMIC_TITLE_TEXT = "
FORM_OF_ADDRESS_KEY = "
FORM_OF_ADDRESS_TEXT = "
BUILDING = "
FLOOR = "

TABLES
* PROFILES = "
* ACTGROUPS = "
* RETURN = "
.



IMPORTING Parameters details for BBP_USER_GET_DETAIL_FIELDS_INT

USERNAME -

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

GET_MANAGER_AND_ORGUNIT -

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

GET_DEFAULT_COUNTRY -

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

EXPORTING Parameters details for BBP_USER_GET_DETAIL_FIELDS_INT

LASTNAME -

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

ROOM_NUMBER -

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

INHOUSE_MAIL -

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

TELEPHONE_NUMBER -

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

TELEPHONE_EXTENSION -

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

FAX_NUMBER -

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

FAX_EXTENSION -

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

DATE_FORMAT -

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

DECIMAL_FORMAT -

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

IS_MANAGER_X_FLAG -

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

IS_MANAGER_ON_FLAG -

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

FIRSTNAME -

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

ORGUNIT -

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

COUNTRY -

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

USER_TYPE -

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

REGION -

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

COMM_TYPE -

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

LOGONDATA -

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

E_MAIL -

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

ACADEMIC_TITLE_KEY -

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

ACADEMIC_TITLE_TEXT -

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

FORM_OF_ADDRESS_KEY -

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

FORM_OF_ADDRESS_TEXT -

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

BUILDING -

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

FLOOR -

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

TABLES Parameters details for BBP_USER_GET_DETAIL_FIELDS_INT

PROFILES -

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

ACTGROUPS -

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

RETURN -

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

Copy and paste ABAP code example for BBP_USER_GET_DETAIL_FIELDS_INT 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_lastname  TYPE BAPIBUS1006_CENTRAL_PERSON-LASTNAME, "   
lt_profiles  TYPE STANDARD TABLE OF BAPIPROF, "   
lv_username  TYPE SY-UNAME, "   
lv_room_number  TYPE BAPIBUS1006002_ADDRESS-ROOM_NO, "   
lv_inhouse_mail  TYPE BAPIBUS1006002_ADDRESS-INHOUSE_ML, "   
lv_telephone_number  TYPE BAPIADTEL-TELEPHONE, "   
lv_telephone_extension  TYPE BAPIADTEL-EXTENSION, "   
lv_fax_number  TYPE BAPIADFAX-FAX, "   
lv_fax_extension  TYPE BAPIADFAX-EXTENSION, "   
lv_date_format  TYPE BAPIDEFAUL-DATFM, "   
lv_decimal_format  TYPE BAPIDEFAUL-DCPFM, "   
lv_is_manager_x_flag  TYPE BBPSAPNEW-CUSTOMIZED, "   
lv_is_manager_on_flag  TYPE CHAR2, "   
lt_actgroups  TYPE STANDARD TABLE OF BAPIAGR, "   
lv_firstname  TYPE BAPIBUS1006_CENTRAL_PERSON-FIRSTNAME, "   
lv_get_manager_and_orgunit  TYPE BBPSAPNEW-CUSTOMIZED, "   'X'
lv_orgunit  TYPE OBJEC-OBJID, "   
lv_country  TYPE BAPIBUS1006_ADDRESS-COUNTRY, "   
lv_user_type  TYPE BBUWAPLIST-SELECTION, "   
lv_region  TYPE BAPIBUS1006_ADDRESS-REGION, "   
lv_comm_type  TYPE BAPIBUS1006_ADDRESS-COMM_TYPE, "   
lv_logondata  TYPE BAPILOGOND, "   
lv_e_mail  TYPE BAPIADSMTP-E_MAIL, "   
lt_return  TYPE STANDARD TABLE OF BAPIRET2, "   
lv_get_default_country  TYPE BBPSAPNEW-CUSTOMIZED, "   'X'
lv_academic_title_key  TYPE BAPIBUS1006_CENTRAL_PERSON-TITLE_ACA1, "   
lv_academic_title_text  TYPE BBP_USR01-TITLE, "   
lv_form_of_address_key  TYPE BAPIBUS1006_CENTRAL-TITLE_KEY, "   
lv_form_of_address_text  TYPE BBP_USR01-FORMOFADDR, "   
lv_building  TYPE BAPIBUS1006002_ADDRESS-BUILDING_P, "   
lv_floor  TYPE BAPIBUS1006002_ADDRESS-FLOOR. "   

  CALL FUNCTION 'BBP_USER_GET_DETAIL_FIELDS_INT'  "
    EXPORTING
         USERNAME = lv_username
         GET_MANAGER_AND_ORGUNIT = lv_get_manager_and_orgunit
         GET_DEFAULT_COUNTRY = lv_get_default_country
    IMPORTING
         LASTNAME = lv_lastname
         ROOM_NUMBER = lv_room_number
         INHOUSE_MAIL = lv_inhouse_mail
         TELEPHONE_NUMBER = lv_telephone_number
         TELEPHONE_EXTENSION = lv_telephone_extension
         FAX_NUMBER = lv_fax_number
         FAX_EXTENSION = lv_fax_extension
         DATE_FORMAT = lv_date_format
         DECIMAL_FORMAT = lv_decimal_format
         IS_MANAGER_X_FLAG = lv_is_manager_x_flag
         IS_MANAGER_ON_FLAG = lv_is_manager_on_flag
         FIRSTNAME = lv_firstname
         ORGUNIT = lv_orgunit
         COUNTRY = lv_country
         USER_TYPE = lv_user_type
         REGION = lv_region
         COMM_TYPE = lv_comm_type
         LOGONDATA = lv_logondata
         E_MAIL = lv_e_mail
         ACADEMIC_TITLE_KEY = lv_academic_title_key
         ACADEMIC_TITLE_TEXT = lv_academic_title_text
         FORM_OF_ADDRESS_KEY = lv_form_of_address_key
         FORM_OF_ADDRESS_TEXT = lv_form_of_address_text
         BUILDING = lv_building
         FLOOR = lv_floor
    TABLES
         PROFILES = lt_profiles
         ACTGROUPS = lt_actgroups
         RETURN = lt_return
. " BBP_USER_GET_DETAIL_FIELDS_INT




ABAP code using 7.40 inline data declarations to call FM BBP_USER_GET_DETAIL_FIELDS_INT

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 LASTNAME FROM BAPIBUS1006_CENTRAL_PERSON INTO @DATA(ld_lastname).
 
 
"SELECT single UNAME FROM SY INTO @DATA(ld_username).
 
"SELECT single ROOM_NO FROM BAPIBUS1006002_ADDRESS INTO @DATA(ld_room_number).
 
"SELECT single INHOUSE_ML FROM BAPIBUS1006002_ADDRESS INTO @DATA(ld_inhouse_mail).
 
"SELECT single TELEPHONE FROM BAPIADTEL INTO @DATA(ld_telephone_number).
 
"SELECT single EXTENSION FROM BAPIADTEL INTO @DATA(ld_telephone_extension).
 
"SELECT single FAX FROM BAPIADFAX INTO @DATA(ld_fax_number).
 
"SELECT single EXTENSION FROM BAPIADFAX INTO @DATA(ld_fax_extension).
 
"SELECT single DATFM FROM BAPIDEFAUL INTO @DATA(ld_date_format).
 
"SELECT single DCPFM FROM BAPIDEFAUL INTO @DATA(ld_decimal_format).
 
"SELECT single CUSTOMIZED FROM BBPSAPNEW INTO @DATA(ld_is_manager_x_flag).
 
 
 
"SELECT single FIRSTNAME FROM BAPIBUS1006_CENTRAL_PERSON INTO @DATA(ld_firstname).
 
"SELECT single CUSTOMIZED FROM BBPSAPNEW INTO @DATA(ld_get_manager_and_orgunit).
DATA(ld_get_manager_and_orgunit) = 'X'.
 
"SELECT single OBJID FROM OBJEC INTO @DATA(ld_orgunit).
 
"SELECT single COUNTRY FROM BAPIBUS1006_ADDRESS INTO @DATA(ld_country).
 
"SELECT single SELECTION FROM BBUWAPLIST INTO @DATA(ld_user_type).
 
"SELECT single REGION FROM BAPIBUS1006_ADDRESS INTO @DATA(ld_region).
 
"SELECT single COMM_TYPE FROM BAPIBUS1006_ADDRESS INTO @DATA(ld_comm_type).
 
 
"SELECT single E_MAIL FROM BAPIADSMTP INTO @DATA(ld_e_mail).
 
 
"SELECT single CUSTOMIZED FROM BBPSAPNEW INTO @DATA(ld_get_default_country).
DATA(ld_get_default_country) = 'X'.
 
"SELECT single TITLE_ACA1 FROM BAPIBUS1006_CENTRAL_PERSON INTO @DATA(ld_academic_title_key).
 
"SELECT single TITLE FROM BBP_USR01 INTO @DATA(ld_academic_title_text).
 
"SELECT single TITLE_KEY FROM BAPIBUS1006_CENTRAL INTO @DATA(ld_form_of_address_key).
 
"SELECT single FORMOFADDR FROM BBP_USR01 INTO @DATA(ld_form_of_address_text).
 
"SELECT single BUILDING_P FROM BAPIBUS1006002_ADDRESS INTO @DATA(ld_building).
 
"SELECT single FLOOR FROM BAPIBUS1006002_ADDRESS INTO @DATA(ld_floor).
 


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!