BUP_S_EEWA_CORE_DATA_API SAP (BP-API: Data Employee Addresses) Structure details
Description: BP-API: Data Employee Addresses
Related tables to BUP_S_EEWA_CORE_DATA_API
Access table BUP_S_EEWA_CORE_DATA_API
Structure field list including key, data, relationships and ABAP select examples
BUP_S_EEWA_CORE_DATA_API 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 "BP-API: Data Employee Addresses" 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_BUP_S_EEWA_CORE_DATA_API TYPE BUP_S_EEWA_CORE_DATA_API.
The BUP_S_EEWA_CORE_DATA_API table consists of various fields, each holding specific information or linking keys about BP-API: Data Employee Addresses data available in SAP. These include PARTNER_UUID (GUID of a Business Partner in CHAR 32 Format for BAPIs), PARTNER_GUID (Business Partner GUID), ADDRESS_GUID (GUID of a Business Partner Address), ORG_ADDR_NUMBER (Address number).. 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 (Deep)
SAP BUP_S_EEWA_CORE_DATA_API 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 | Business Partner Number | BU_PARTNER | CHAR | 10 | Assigned to domain | ALPHA | BU_PARTNER | BPA | BUPA |
PARTNER_UUID | GUID of a Business Partner in CHAR 32 Format for BAPIs | BU_PARTNER_GUID_BAPI | CHAR | 32 | SYSUUID_C | ||||
PARTNER_GUID | Business Partner GUID | BU_PARTNER_GUID | RAW | 16 | SYSUUID | ||||
ADDRESS_GUID | GUID of a Business Partner Address | BU_ADDRESS_GUID | RAW | 16 | SYSUUID | ||||
ORG_ADDR_NUMBER | Address number | AD_ADDRNUM | CHAR | 10 | Assigned to domain | ALPHA | AD_ADDRNUM | ADR | |
ORG_ADDR_ORIGIN | Origin of the Organization Part of a Workplace Address | BU_ORG_ADDR_ORIGIN | CHAR | 1 | BU_ORG_ADDR_ORIGIN | ||||
FROM_DATE | Date | DATUM | DATS | 8 | DATUM | ||||
TO_DATE | Date | DATUM | DATS | 8 | DATUM | ||||
ORG_ADDRESS_ID | Node Id as in the ESA-model | ADDR_NODE_ID | CHAR | 70 | ADDR_NODE_ID | ||||
WP_ADDRESS_ID | Node Id as in the ESA-model | ADDR_NODE_ID | CHAR | 70 | ADDR_NODE_ID | ||||
WORKPLACE | 0 | ||||||||
DEPARTMENT | Department | AD_DPRTMNT | CHAR | 40 | TEXT40 | ||||
FUNCTION | Function | AD_FNCTN | 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 | ||||
ID_CODE | Short name for correspondence | AD_ID_CODE | CHAR | 10 | TEXT10 | ||||
IH_MAIL | Int. mail postal code | AD_IH_MAIL | CHAR | 10 | TEXT10 | ||||
COMMDATA_WP | 0 | ||||||||
TELEPHONE | 0 | ||||||||
FACSIMILE | 0 | ||||||||
0 | |||||||||
WEB | 0 | ||||||||
TELEX | 0 | ||||||||
TELETEX | 0 | ||||||||
RML | 0 | ||||||||
X400 | 0 | ||||||||
PRINTER | 0 | ||||||||
SSF | 0 | ||||||||
PAGER | 0 | ||||||||
COMMUNICATION_PREFERENCE_WP | 0 | ||||||||
LANGU | Language Key | SPRAS | LANG | 1 | ISOLA | SPRAS | SPR | H_T002 | |
DEFLT_COMM | Communication Method (Key) (Business Address Services) | AD_COMM | CHAR | 3 | Assigned to domain | AD_COMM | |||
TITLE | Form-of-Address Key | AD_TITLE | CHAR | 4 | Assigned to domain | AD_TITLE | |||
NAME1 | Name 1 | AD_NAME1 | CHAR | 40 | TEXT40 | ||||
NAME2 | Name 2 | AD_NAME2 | CHAR | 40 | TEXT40 | ||||
NAME3 | Name 3 | AD_NAME3 | CHAR | 40 | TEXT40 | ||||
NAME4 | Name 4 | AD_NAME4 | CHAR | 40 | TEXT40 | ||||
SORT1 | Search Term 1 | AD_SORT1 | CHAR | 20 | CHAR20 | ||||
SORT2 | Search Term 2 | AD_SORT2 | CHAR | 20 | CHAR20 | ||||
LOCATION | 0 | ||||||||
NAME_CO | c/o name | AD_NAME_CO | CHAR | 40 | TEXT40 | ||||
CITY1 | City | AD_CITY1 | CHAR | 40 | TEXT40 | CLCITYNAME | |||
CITY2 | District | AD_CITY2 | CHAR | 40 | TEXT40 | CITY_PART | |||
CITY_CODE | City code for city/street file | AD_CITYNUM | CHAR | 12 | ALPHA | CITY_CODE | |||
CITYP_CODE | District code for City and Street file | AD_CITYPNM | CHAR | 8 | ALPHA | CITYP_CODE | |||
HOME_CITY | City (different from postal city) | AD_CITY3 | CHAR | 40 | TEXT40 | ||||
CITYH_CODE | Different city for city/street file | AD_CITYHNM | CHAR | 12 | ALPHA | CITY_CODE | |||
CHCKSTATUS | City file test status | AD_CHECKST | CHAR | 1 | AD_CHECKST | ||||
REGIOGROUP | Regional structure grouping | REGIOGROUP | CHAR | 8 | REGIOGROUP | ||||
POST_CODE1 | City postal code | AD_PSTCD1 | CHAR | 10 | CHAR10 | ||||
POST_CODE2 | PO Box Postal Code | AD_PSTCD2 | CHAR | 10 | CHAR10 | ||||
POST_CODE3 | Company Postal Code (for Large Customers) | AD_PSTCD3 | CHAR | 10 | CHAR10 | ||||
PO_BOX | PO Box | AD_POBX | CHAR | 10 | CHAR10 | ||||
DONT_USE_P | PO Box Address Undeliverable Flag | AD_NO_USEP | CHAR | 4 | AD_NO_USE | ||||
PO_BOX_NUM | Flag: PO Box Without Number | AD_POBXNUM | CHAR | 1 | XFELD | ||||
PO_BOX_LOC | PO Box city | AD_POBXLOC | CHAR | 40 | TEXT40 | CITY_NAME | |||
CITY_CODE2 | City PO box code (City file) | AD_CIT2NUM | CHAR | 12 | ALPHA | CITY_CODE | |||
PO_BOX_REG | Region for PO Box (Country, State, Province, ...) | AD_POBXREG | CHAR | 3 | REGIO | ||||
PO_BOX_CTY | PO box country | AD_POBXCTY | CHAR | 3 | LAND1 | ||||
TRANSPZONE | Transportation zone to or from which the goods are delivered | LZONE | CHAR | 10 | ZONE | ||||
STREET | Street | AD_STREET | CHAR | 60 | TEXT60 | CLSTRTNAME | |||
DONT_USE_S | Street Address Undeliverable Flag | AD_NO_USES | CHAR | 4 | AD_NO_USE | ||||
STREETCODE | Street Number for City/Street File | AD_STRNUM | CHAR | 12 | ALPHA | STRT_CODE | |||
HOUSE_NUM1 | House Number | AD_HSNM1 | CHAR | 10 | TEXT10 | ||||
HOUSE_NUM2 | House number supplement | AD_HSNM2 | CHAR | 10 | TEXT10 | ||||
STR_SUPPL1 | Street 2 | AD_STRSPP1 | CHAR | 40 | TEXT40 | ||||
STR_SUPPL2 | Street 3 | AD_STRSPP2 | CHAR | 40 | TEXT40 | ||||
STR_SUPPL3 | Street 4 | AD_STRSPP3 | CHAR | 40 | TEXT40 | ||||
LOCATION | Street 5 | AD_LCTN | CHAR | 40 | TEXT40 | ||||
BUILDING | Building (Number or Code) | AD_BLDNG | CHAR | 20 | TEXT20 | ||||
FLOOR | Floor in building | AD_FLOOR | CHAR | 10 | TEXT10 | ||||
ROOMNUMBER | Room or Appartment Number | AD_ROOMNUM | CHAR | 10 | TEXT10 | ||||
COUNTRY | Country Key | LAND1 | CHAR | 3 | LAND1 | LND | |||
REGION | STATE (State, Province, County) | REGIO | CHAR | 3 | REGIO | ||||
TIME_ZONE | Address time zone | AD_TZONE | CHAR | 6 | TZNZONE | ||||
TAXJURCODE | Tax Jurisdiction | AD_TXJCD | CHAR | 15 | AD_TXJCD | TXJ | |||
PO_BOX_LOBBY | PO Box Lobby | AD_PO_BOX_LBY | CHAR | 40 | TEXT40 | ||||
DELI_SERV_TYPE | Type of Delivery Service | AD_DELIVERY_SERVICE_TYPE | CHAR | 4 | AD_DELIVERY_SERVICE_TYPE | ||||
DELI_SERV_NUMBER | Number of Delivery Service | AD_DELIVERY_SERVICE_NUMBER | CHAR | 10 | CHAR10 | ||||
COUNTY | County | AD_COUNTY | CHAR | 40 | TEXT40 | CLTCNTYNAME | |||
TOWNSHIP | Township | AD_TOWNSHIP | CHAR | 40 | TEXT40 | CLTWSHPNAME | |||
NOTES | 0 | ||||||||
COMMDATA_ORG | 0 | ||||||||
TELEPHONE | 0 | ||||||||
FACSIMILE | 0 | ||||||||
0 | |||||||||
WEB | 0 | ||||||||
TELEX | 0 | ||||||||
TELETEX | 0 | ||||||||
RML | 0 | ||||||||
X400 | 0 | ||||||||
PRINTER | 0 | ||||||||
SSF | 0 | ||||||||
PAGER | 0 | ||||||||
COMMUNICATION_PREFERENCE_ORG | 0 | ||||||||
LANGU | Language Key | SPRAS | LANG | 1 | ISOLA | SPRAS | SPR | H_T002 | |
DEFLT_COMM | Communication Method (Key) (Business Address Services) | AD_COMM | CHAR | 3 | AD_COMM |
Key field | Non-key field |
How do I retrieve data from SAP structure BUP_S_EEWA_CORE_DATA_API using ABAP code?
As BUP_S_EEWA_CORE_DATA_API 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 BUP_S_EEWA_CORE_DATA_API as there is no data to select.How to access SAP table BUP_S_EEWA_CORE_DATA_API
Within an ECC or HANA version of SAP you can also view further information about BUP_S_EEWA_CORE_DATA_API 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