RNBUP_SEARCH SAP (Search Fields for Additional HC-Specific BP) Structure details
Description: Search Fields for Additional HC-Specific BP
Structure field list including key, data, relationships and ABAP select examples
RNBUP_SEARCH 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 "Search Fields for Additional HC-Specific BP" 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_RNBUP_SEARCH TYPE RNBUP_SEARCH.
The RNBUP_SEARCH table consists of various fields, each holding specific information or linking keys about Search Fields for Additional HC-Specific BP data available in SAP. These include PARTNER_NUMBER (Business Partner Number), SEARCH1 (Search term 1 for business partner), SEARCH2 (Search term 2 for business partner), EXTERNAL_NUMBER (Business Partner Number in External System).. 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: Not classified
SAP RNBUP_SEARCH 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 |
PARTNER_NUMBER | Business Partner Number | BU_PARTNER | CHAR | 10 | Assigned to domain | ALPHA | BU_PARTNER | BPA | BUPA |
SEARCH1 | Search term 1 for business partner | BU_SORT1 | CHAR | 20 | BU_SORT1 | ||||
SEARCH2 | Search term 2 for business partner | BU_SORT2 | CHAR | 20 | BU_SORT1 | ||||
EXTERNAL_NUMBER | Business Partner Number in External System | BU_BPEXT | CHAR | 20 | CHAR20 | ||||
CITY | City name in upper case for search help | AD_MC_CITY | CHAR | 25 | CHAR25 | ||||
STREET | Street name in upper case for search help | AD_MC_STRT | CHAR | 25 | CHAR25 | ||||
HOUSE_NUMBER | House Number | AD_HSNM1 | CHAR | 10 | TEXT10 | ||||
PARTNER_ROLE | BP role | BU_ROLE | CHAR | 6 | Assigned to domain | BU_RLTYP | BUPA_ROLE | ||
POST_CODE1 | City postal code | AD_PSTCD1 | CHAR | 10 | CHAR10 | ||||
COUNTRY | Country Key | LAND1 | CHAR | 3 | T005 | LAND1 | LND | ||
NATION | Version ID for International Addresses | AD_NATION | CHAR | 1 | Assigned to domain | AD_NATION | ADDRESS_NATION | ||
CITY_MC | City | AD_CITY1 | CHAR | 40 | TEXT40 | CLCITYNAME | |||
STREET_MC | Street | AD_STREET | CHAR | 60 | TEXT60 | CLSTRTNAME | |||
COUNTY | County name in upper case for search help | AD_MC_COUNTY | CHAR | 25 | CHAR25 | ||||
TOWNSHIP | Township name in upper case for search help | AD_MC_TWSHP | CHAR | 25 | CHAR25 | ||||
COUNTY_MC | County | AD_COUNTY | CHAR | 40 | TEXT40 | CLTCNTYNAME | |||
TOWNSHIP_MC | Township | AD_TOWNSHIP | CHAR | 40 | TEXT40 | CLTWSHPNAME | |||
IDTYPE | Identification Type | BU_IDENT_TYPE | CHAR | 6 | Assigned to domain | BU_ID_TYPE | BUPA_ALL_IDENTIFICATION_NUMBER | ||
IDNUMBER | Identification Number | BU_ID_NUMBER | CHAR | 60 | CHAR60 | ||||
FIRST_NAME | First name of business partner (person) | BU_NAMEP_F | CHAR | 40 | BU_NAME | ||||
LAST_NAME | Last name of business partner (person) | BU_NAMEP_L | CHAR | 40 | BU_NAME | ||||
BIRTH_DATE | Date of Birth of Business Partner | BU_BIRTHDT | DATS | 8 | DATUM | ||||
BIRTH_PLACE | Birthplace of business partner | BU_BIRTHPL | CHAR | 40 | TEXT40 | ||||
ORG_NAME1 | Name 1 of organization | BU_NAMEOR1 | CHAR | 40 | BU_NAME | ||||
ORG_NAME2 | Name 2 of organization | BU_NAMEOR2 | CHAR | 40 | BU_NAME | ||||
ORG_NAME3 | Name 3 of organization | BU_NAMEOR3 | CHAR | 40 | BU_NAME | ||||
ORG_NAME4 | Name 4 of organization | BU_NAMEOR4 | CHAR | 40 | BU_NAME | ||||
LOCATION1 | Business partner: International location number part 1 (DI) | BU_LOCATION1STR | CHAR | 7 | CHAR7 | ||||
LOCATION2 | Business partner: International location number part 2 (DI) | BU_LOCATION2STR | CHAR | 5 | CHAR5 | ||||
LOCATION3 | Business partner: International location number part 3 (DI) | BU_LOCATION3STR | CHAR | 1 | CHAR1 | ||||
NAME_GRP1 | Name 1 (group) | BU_NAMEGR1 | CHAR | 40 | BU_NAME | ||||
NAME_GRP2 | Name 2 (group) | BU_NAMEGR2 | CHAR | 40 | BU_NAME | ||||
NAME1 | Partner name1 | PARTNER_NAME1 | CHAR | 40 | BU_NAME | ||||
NAME2 | Partner Name2 | PARTNER_NAME2 | CHAR | 40 | BU_NAME | ||||
GPARTNER | IS-H: Business Partner | GPARTNER | CHAR | 10 | Assigned to domain | ALPHA | RI_KUNNR | NGP | |
SHORT_NAME | IS-H: Short Name of Business Partner | KZNAME | CHAR | 12 | ISH_C12 | ||||
SEX | IS-H: Sex Indicator - Internal | GSCHL | CHAR | 1 | GSCHL | ||||
SEX_M | Selection: Business partner is male | BU_XSEXM | CHAR | 1 | XFELD | ||||
SEX_F | Selection: Business partner is female | BU_XSEXF | CHAR | 1 | XFELD | ||||
SEX_U | Selection: Sex of business partner is not known | BU_XSEXU | CHAR | 1 | XFELD |
Key field | Non-key field |
How do I retrieve data from SAP structure RNBUP_SEARCH using ABAP code?
As RNBUP_SEARCH 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 RNBUP_SEARCH as there is no data to select.How to access SAP table RNBUP_SEARCH
Within an ECC or HANA version of SAP you can also view further information about RNBUP_SEARCH 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