BBPS_NONR3_INPUT_PARTNER SAP (Transfer Structure for Master Data Upload Business Partner) Structure details
Dictionary Type: Structure
Description: Transfer Structure for Master Data Upload Business Partner
Description: Transfer Structure for Master Data Upload Business Partner
ABAP Code to SELECT data from BBPS_NONR3_INPUT_PARTNER
Related tables to BBPS_NONR3_INPUT_PARTNER
Access table BBPS_NONR3_INPUT_PARTNER
Related tables to BBPS_NONR3_INPUT_PARTNER
Access table BBPS_NONR3_INPUT_PARTNER
Structure field list including key, data, relationships and ABAP select examples
BBPS_NONR3_INPUT_PARTNER 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 "Transfer Structure for Master Data Upload Business Partner" 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_BBPS_NONR3_INPUT_PARTNER TYPE BBPS_NONR3_INPUT_PARTNER.
The BBPS_NONR3_INPUT_PARTNER table consists of various fields, each holding specific information or linking keys about Transfer Structure for Master Data Upload Business Partner data available in SAP. These include PARTNER_TYPE (Business Partner Type with Master Data Upload), DUNS_NUMBER (Dun & Bradstreet Number), EXT_PARTNER_NO (Number of Partner in Non-R/3 System), BACKEND_SYSTEM (Logical 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: Can be enhanced (character-type)
SAP BBPS_NONR3_INPUT_PARTNER 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 |
| ACTIVITY | Requested Processing Mode with Master Data Upload | BBP_NONR3_ACTIVITY | CHAR | 4 | BBP_NONR3_ACTIVITY | ||||
| PARTNER_TYPE | Business Partner Type with Master Data Upload | BBP_NONR3_PARTNER_TYPE | CHAR | 6 | BBP_NONR3_PARTNER_TYPE | ||||
| DUNS_NUMBER | Dun & Bradstreet Number | BBP_CT_DUNS | CHAR | 9 | CHAR9 | ||||
| EXT_PARTNER_NO | Number of Partner in Non-R/3 System | BBP_NONR3_EXTERNAL_ID | CHAR | 10 | ALPHA | BBP_NONR3_EXTERNAL_ID | |||
| BACKEND_SYSTEM | Logical system | LOGSYS | CHAR | 10 | Assigned to domain | ALPHA | LOGSYS | ||
| PARTNER_NAME1 | Name field 1 (name1/last name) | BU_NAME1 | CHAR | 40 | BU_NAME | ||||
| PARTNER_NAME2 | Name field 2 (name2/first name) | BU_NAME2 | CHAR | 40 | BU_NAME | ||||
| SEARCHTERM1 | Search term 1 for business partner | BU_SORT1 | CHAR | 20 | BU_SORT1 | ||||
| SEARCHTERM2 | Search term 2 for business partner | BU_SORT2 | CHAR | 20 | BU_SORT1 | ||||
| INDUSTRY_SECTOR | Industry sector | BU_INDSECT | CHAR | 10 | Assigned to domain | BU_INDSECT | H_TB023 | ||
| PARTNER_BLOCKED | Central Block for Business Partner | BU_XBLCK | CHAR | 1 | XFELD | ||||
| C_O_NAME | c/o name | AD_NAME_CO | CHAR | 40 | TEXT40 | ||||
| CITY | City | AD_CITY1 | CHAR | 40 | TEXT40 | CLCITYNAME | |||
| DISTRICT | District | AD_CITY2 | CHAR | 40 | TEXT40 | CITY_PART | |||
| POSTAL_CODE | City postal code | AD_PSTCD1 | CHAR | 10 | CHAR10 | ||||
| PO_BOX | PO Box | AD_POBX | CHAR | 10 | CHAR10 | ||||
| PO_BOX_CODE | PO Box Postal Code | AD_PSTCD2 | CHAR | 10 | CHAR10 | ||||
| PO_BOX_CITY | PO Box city | AD_POBXLOC | CHAR | 40 | TEXT40 | CITY_NAME | |||
| PO_BOX_CTRY_ISO | Country ISO code | INTCA | CHAR | 2 | INTCA | F4_INTCA | |||
| PO_BOX_WO_NUMBER | Flag: PO Box Without Number | AD_POBXNUM | CHAR | 1 | XFELD | ||||
| COMP_POST_CODE | Company Postal Code (for Large Customers) | AD_PSTCD3 | CHAR | 10 | CHAR10 | ||||
| STREET_PREFIX | Street 2 | AD_STRSPP1 | CHAR | 40 | TEXT40 | ||||
| STREET | Street | AD_STREET | CHAR | 60 | TEXT60 | CLSTRTNAME | |||
| STREET_SUFFIX | Street 4 | AD_STRSPP3 | CHAR | 40 | TEXT40 | ||||
| HOUSE_NUMBER | House Number | AD_HSNM1 | CHAR | 10 | TEXT10 | ||||
| BUILDING | Building (Number or Code) | AD_BLDNG | CHAR | 20 | TEXT20 | ||||
| FLOOR | Floor in building | AD_FLOOR | CHAR | 10 | TEXT10 | ||||
| ROOM_NUMBER | Room or Appartment Number | AD_ROOMNUM | CHAR | 10 | TEXT10 | ||||
| COUNTRY_ISO | Country ISO code | INTCA | CHAR | 2 | INTCA | F4_INTCA | |||
| REGION | STATE (State, Province, County) | REGIO | CHAR | 3 | Assigned to domain | REGIO | |||
| TAXJUR_CODE | Tax Jurisdiction | AD_TXJCD | CHAR | 15 | AD_TXJCD | TXJ | |||
| LANGUAGE_ISO | 2-Character SAP Language Code | LAISO | CHAR | 2 | LAISO | ||||
| TEL_NUMBER | First telephone no.: dialling code+number | AD_TLNMBR1 | CHAR | 30 | CHAR30 | ||||
| TEL_EXTENSION | First Telephone No.: Extension | AD_TLXTNS1 | CHAR | 10 | CHAR10 | ||||
| TEL_COUNTRY_ISO | Country ISO code | INTCA | CHAR | 2 | INTCA | F4_INTCA | |||
| FAX_NUMBER | First fax no.: dialling code+number | AD_FXNMBR1 | CHAR | 30 | CHAR30 | ||||
| FAX_EXTENSION | First fax no.: extension | AD_FXXTNS1 | CHAR | 10 | CHAR10 | ||||
| FAX_COUNTRY_ISO | Country ISO code | INTCA | CHAR | 2 | INTCA | F4_INTCA | |||
| EMAIL_ADDRESS | E-Mail Address | AD_SMTPADR | CHAR | 241 | SXIDN | AD_SMTPADR | |||
| FTP_ADDR_PART1 | Part of an FTP or HTTP Address | BBP_NONR3_URI_PART | CHAR | 250 | CHAR250 | ||||
| FTP_ADDR_PART2 | Part of an FTP or HTTP Address | BBP_NONR3_URI_PART | CHAR | 250 | CHAR250 | ||||
| HTTP_ADDR_PART1 | Part of an FTP or HTTP Address | BBP_NONR3_URI_PART | CHAR | 250 | CHAR250 | ||||
| HTTP_ADDR_PART2 | Part of an FTP or HTTP Address | BBP_NONR3_URI_PART | CHAR | 250 | CHAR250 | ||||
| EXT_ADDRESS_NO | Address number | AD_ADDRNUM | CHAR | 10 | Assigned to domain | ALPHA | AD_ADDRNUM | ADR | |
| STD_COMM | Communication: FTP, HTTP, and so on | BBP_SERVICE | CHAR | 10 | BBP_SERVICE | ||||
| PURCHASING_ORG | Object ID | OBJEKTID | NUMC | 8 | NUM08 | PON | |||
| PO_CURRENCY_ISO | ISO currency code | ISOCD | CHAR | 3 | ISOCD | ||||
| SEND_MEDIUM | Transmission Medium (Printer, Fax, EDI, XML, and so on) | BBP_METYPE | CHAR | 3 | BBP_METYPE | ||||
| PAYMENT_TERM | Terms of Payment (CRM Style) | BBP_CRMT_PMNTTRMS | CHAR | 4 | CHAR4 | ||||
| BUYERS_ACCOUNT | Our Account Number at the Vendor | BBP_OWN_ACC_NO | CHAR | 40 | CHAR40 | ||||
| ERS | Evaluated Receipt Settlement (ERS) | BBP_XERSY | CHAR | 1 | XFELD | ||||
| GR_CONF_EXP | Indicator: Goods Receipt Confirmation Expected | BBPT_BU_GOODSREC_CONFEX | CHAR | 1 | BBP_BOOLEAN | ||||
| IV_CONF_EXP | Indicator: Invoice Receipt Expected | BBPT_BU_INVOICE_CONFEX | CHAR | 1 | BBP_BOOLEAN | ||||
| OR_RESP_EXP | Indicator: Order Confirmation Expected | BBP_BU_ORDER_RESP_EXPECTED | CHAR | 1 | BBP_BOOLEAN | ||||
| ASN_EXP | Indicator: Shipping Notification Expected | BBP_BU_ASN_EXPECTED | CHAR | 1 | BBP_BOOLEAN | ||||
| PURCHASE_BLOCK | Purchasing Block | BBP_BU_PUR_BLOCK | CHAR | 1 | XFELD | ||||
| INCOME_TAX_NO | Business Partner Tax Number | BPTAXNUM | CHAR | 20 | BPTAXNUM | ||||
| SALES_TAX_NO | Business Partner Tax Number | BPTAXNUM | CHAR | 20 | BPTAXNUM |
| Key field | Non-key field |
How do I retrieve data from SAP structure BBPS_NONR3_INPUT_PARTNER using ABAP code?
As BBPS_NONR3_INPUT_PARTNER 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 BBPS_NONR3_INPUT_PARTNER as there is no data to select.How to access SAP table BBPS_NONR3_INPUT_PARTNER
Within an ECC or HANA version of SAP you can also view further information about BBPS_NONR3_INPUT_PARTNER 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