/ISIDEX/EIDENT_SEARCHDATA SAP (Search Data for Point of Delivery Identification) Structure details
Description: Search Data for Point of Delivery Identification
Related tables to /ISIDEX/EIDENT_SEARCHDATA
Access table /ISIDEX/EIDENT_SEARCHDATA
Structure field list including key, data, relationships and ABAP select examples
/ISIDEX/EIDENT_SEARCHDATA 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 Data for Point of Delivery Identification" 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_/ISIDEX/EIDENT_SEARCHDATA TYPE /ISIDEX/EIDENT_SEARCHDATA.
The /ISIDEX/EIDENT_SEARCHDATA table consists of various fields, each holding specific information or linking keys about Search Data for Point of Delivery Identification data available in SAP. These include EXT_UI (Point of delivery ID), NAME1 (Name field 1 (name1/last name)), NAME2 (Name field 2 (name2/first name)), STREET (Street).. 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 /ISIDEX/EIDENT_SEARCHDATA 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 |
| KEYDATE | Key Date for Identification of Point of Delivery | /ISIDEX/E_IDENTKEYDATE | DATS | 8 | |||||
| EXT_UI | Point of delivery ID | EXT_UI | CHAR | 50 | EXT_UI | EXT_POD | |||
| NAME1 | Name field 1 (name1/last name) | BU_NAME1 | CHAR | 40 | BU_NAME | ||||
| NAME2 | Name field 2 (name2/first name) | BU_NAME2 | CHAR | 40 | BU_NAME | ||||
| STREET | Street | AD_STREET | CHAR | 60 | TEXT60 | CLSTRTNAME | |||
| HOUSENR | House Number | AD_HSNM1 | CHAR | 10 | TEXT10 | ||||
| HOUSENREXT | House number supplement | AD_HSNM2 | CHAR | 10 | TEXT10 | ||||
| POSTCODE | City postal code | AD_PSTCD1 | CHAR | 10 | CHAR10 | ||||
| CITY | City | AD_CITY1 | CHAR | 40 | TEXT40 | CLCITYNAME | |||
| FLOOR | Floor in building | AD_FLOOR | CHAR | 10 | TEXT10 | ||||
| ROOMNUMBER | Room or Appartment Number | AD_ROOMNUM | CHAR | 10 | TEXT10 | ||||
| .INCLU-BU_ | 0 | ||||||||
| STREETBU_ | Street | AD_STREET | CHAR | 60 | TEXT60 | CLSTRTNAME | |||
| HOUSENRBU_ | House Number | AD_HSNM1 | CHAR | 10 | TEXT10 | ||||
| HOUSENREXTBU_ | House number supplement | AD_HSNM2 | CHAR | 10 | TEXT10 | ||||
| POSTCODEBU_ | City postal code | AD_PSTCD1 | CHAR | 10 | CHAR10 | ||||
| CITYBU_ | City | AD_CITY1 | CHAR | 40 | TEXT40 | CLCITYNAME | |||
| FLOORBU_ | Floor in building | AD_FLOOR | CHAR | 10 | TEXT10 | ||||
| ROOMNUMBERBU_ | Room or Appartment Number | AD_ROOMNUM | CHAR | 10 | TEXT10 | ||||
| METERNR | Serial Number | GERNR | CHAR | 18 | GERNR | GERNR | SER | ||
| BU_PARTNER | Business Partner Number | BU_PARTNER | CHAR | 10 | Assigned to domain | ALPHA | BU_PARTNER | BPA | BUPA |
| IDREFNR | ID/Reference Number | EIDESWTMDIDREFNR | CHAR | 35 | TEXT35 | ||||
| TRANSREASON | Transaction Reason | EIDESWTMDTRAN | CHAR | 3 | Assigned to domain | EIDESWTMDTRAN | |||
| SERVICEID | Service Provider | SERVICE_PROV | CHAR | 10 | Assigned to domain | SERVICE_PROV | EESERVPROVID | SERVICEPROVIDER | |
| SWTMDCAT | Message Category | EIDESWTMDCAT | CHAR | 3 | Assigned to domain | EIDESWTMDCAT | EIDESWTMDCAT | ||
| SPARTYP | Division category | SPARTYP | NUMC | 2 | SPARTYP | SPT |
| Key field | Non-key field |
How do I retrieve data from SAP structure /ISIDEX/EIDENT_SEARCHDATA using ABAP code?
As /ISIDEX/EIDENT_SEARCHDATA 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 /ISIDEX/EIDENT_SEARCHDATA as there is no data to select.How to access SAP table /ISIDEX/EIDENT_SEARCHDATA
Within an ECC or HANA version of SAP you can also view further information about /ISIDEX/EIDENT_SEARCHDATA 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