BBP_USER_BOBUSER_KEYS SAP (User-Specific: Requester (Buying on Behalf of), Texts) Structure details
Description: User-Specific: Requester (Buying on Behalf of), Texts
Related tables to BBP_USER_BOBUSER_KEYS
Access table BBP_USER_BOBUSER_KEYS
Structure field list including key, data, relationships and ABAP select examples
BBP_USER_BOBUSER_KEYS is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "User-Specific: Requester (Buying on Behalf of), Texts" Information within sap ABAP programs.
This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.
i.e. DATA: wa_BBP_USER_BOBUSER_KEYS TYPE BBP_USER_BOBUSER_KEYS.
The BBP_USER_BOBUSER_KEYS table consists of various fields, each holding specific information or linking keys about User-Specific: Requester (Buying on Behalf of), Texts data available in SAP. These include PARTNER (Business Partner Number), PARTNER_GUID (Business Partner GUID), USERNAME (User Name), NAME_FIRST (First name).. See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .
Delivery Class:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Can be enhanced (character-type or numeric)
SAP BBP_USER_BOBUSER_KEYS structure fields - Full list of fields found in SAP data dictionary
Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
OWNER | User Name | SYUNAME | CHAR | 12 | SYCHAR12 | ||||
PARTNER | Business Partner Number | BU_PARTNER | CHAR | 10 | Assigned to domain | ALPHA | BU_PARTNER | BPA | BUPA |
PARTNER_GUID | Business Partner GUID | BU_PARTNER_GUID | RAW | 16 | SYSUUID | ||||
USERNAME | User Name | SYUNAME | CHAR | 12 | SYCHAR12 | ||||
NAME_FIRST | First name | AD_NAMEFIR | CHAR | 40 | TEXT40 | ||||
NAME_LAST | Last name | AD_NAMELAS | CHAR | 40 | TEXT40 | ||||
BUILDING | Building (number or code) | AD_BLDNG_P | CHAR | 10 | TEXT10 | ||||
FLOOR | Floor in building | AD_FLOOR | CHAR | 10 | TEXT10 | ||||
ROOMNUMBER | Room or Appartment Number | AD_ROOMNUM | CHAR | 10 | TEXT10 | ||||
INHOUSE_MAIL | Int. mail postal code | AD_IH_MAIL | CHAR | 10 | TEXT10 | ||||
TEL_NUMBER | First telephone no.: dialling code+number | AD_TLNMBR1 | CHAR | 30 | CHAR30 | ||||
TEL_EXTENS | First Telephone No.: Extension | AD_TLXTNS1 | CHAR | 10 | CHAR10 | ||||
TITLE_ACA1 | Academic Title: Key | AD_TITLE1 | CHAR | 4 | Assigned to domain | AD_TITLE1 | AD_TITLE1 | ||
TITLE_TEXT | Academic Title: Written Form | AD_TITLE1T | CHAR | 20 | TEXT20 |
Key field | Non-key field |
How do I retrieve data from SAP structure BBP_USER_BOBUSER_KEYS using ABAP code?
As BBP_USER_BOBUSER_KEYS is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on BBP_USER_BOBUSER_KEYS as there is no data to select.How to access SAP table BBP_USER_BOBUSER_KEYS
Within an ECC or HANA version of SAP you can also view further information about BBP_USER_BOBUSER_KEYS and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects