E1IST_ADDRESS SAP (IS-T Business Partner: Address Data) IDoc segment structure details
Dictionary Type: IDoc segment structure
Description: IS-T Business Partner: Address Data
Description: IS-T Business Partner: Address Data
ABAP Code to SELECT data from E1IST_ADDRESS
Related tables to E1IST_ADDRESS
Access table E1IST_ADDRESS
Related tables to E1IST_ADDRESS
Access table E1IST_ADDRESS
IDoc segment structure field list including key, data, relationships and ABAP select examples
E1IST_ADDRESS is a standard SAP Structure which is used to define the field attributes of IDoc segment E1IST_ADDRESS. The segment is used within the below IDoc to send IS-T Business Partner: Address Data information via the IDoc send process
IST_EBS_BUPART_DOCBelow is the standard documentation available and a few details of the fields which make up this IDoc segment structure. To view further details checkout the IDoc links above or use relevant transactions such as WE30(IDoc development), WE31 (segment development)...Also check here for more IDoc related development help, or you can obviously also use standard dictionary object dev tcodes such as SE11, SE80 etc...
Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Cannot Be Enhanced
SAP E1IST_ADDRESS idoc segment 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 |
| NAME_CO | 0 | ||||||||
| CITY1 | 0 | ||||||||
| CITY2 | 0 | ||||||||
| CITY_CODE | 0 | ||||||||
| CITYP_CODE | 0 | ||||||||
| HOME_CITY | 0 | ||||||||
| CITYH_CODE | 0 | ||||||||
| CHCKSTATUS | 0 | ||||||||
| REGIOGROUP | 0 | ||||||||
| POST_CODE1 | 0 | ||||||||
| POST_CODE2 | 0 | ||||||||
| POST_CODE3 | 0 | ||||||||
| PCODE1_EXT | 0 | ||||||||
| PCODE2_EXT | 0 | ||||||||
| PCODE3_EXT | 0 | ||||||||
| PO_BOX | 0 | ||||||||
| PO_BOX_NUM | 0 | ||||||||
| PO_BOX_LOC | 0 | ||||||||
| CITY_CODE2 | 0 | ||||||||
| PO_BOX_REG | 0 | ||||||||
| PO_BOX_CTY_ISO | 0 | ||||||||
| POSTALAREA | 0 | ||||||||
| TRANSPZONE | 0 | ||||||||
| STREET | 0 | ||||||||
| STREETCODE | 0 | ||||||||
| STREETABBR | 0 | ||||||||
| HOUSE_NUM1 | 0 | ||||||||
| HOUSE_NUM2 | 0 | ||||||||
| HOUSE_NUM3 | 0 | ||||||||
| STR_SUPPL1 | 0 | ||||||||
| STR_SUPPL2 | 0 | ||||||||
| STR_SUPPL3 | 0 | ||||||||
| LOCATION | 0 | ||||||||
| BUILDING | 0 | ||||||||
| FLOOR | 0 | ||||||||
| ROOMNUMBER | 0 | ||||||||
| COUNTRY_ISO | 0 | ||||||||
| LANGU_ISO | 0 | ||||||||
| REGION | 0 | ||||||||
| SORT1 | 0 | ||||||||
| SORT2 | 0 | ||||||||
| SORT_PHN | 0 | ||||||||
| ADDRORIGIN | 0 | ||||||||
| EXTENSION1 | 0 | ||||||||
| EXTENSION2 | 0 | ||||||||
| TIME_ZONE | 0 | ||||||||
| TAXJURCODE | 0 | ||||||||
| ADDRESS_ID | 0 | ||||||||
| REMARK | 0 | ||||||||
| LANGU_CREA_ISO | 0 | ||||||||
| DEFLT_COMM | 0 | ||||||||
| TEL_NUMBER | 0 | ||||||||
| TEL_EXTENS | 0 | ||||||||
| FAX_NUMBER | 0 | ||||||||
| FAX_EXTENS | 0 |
| Key field | Non-key field |
How do I retrieve data from SAP structure E1IST_ADDRESS using ABAP code?
As E1IST_ADDRESS 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 E1IST_ADDRESS as there is no data to select.How to access SAP table E1IST_ADDRESS
Within an ECC or HANA version of SAP you can also view further information about E1IST_ADDRESS 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