E2UPLD1 SAP (Configuration of data upload from subsystem) Structure details
Description: Configuration of data upload from subsystem
Structure field list including key, data, relationships and ABAP select examples
E2UPLD1 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 "Configuration of data upload from subsystem" 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_E2UPLD1 TYPE E2UPLD1.
The E2UPLD1 table consists of various fields, each holding specific information or linking keys about Configuration of data upload from subsystem data available in SAP. These include LDEST (Logical destination of subsystem), KKANA (Name of the directory for the communications channel), UPLDA (Upload file name), EUSER (User name).. 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 E2UPLD1 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 |
| MANDT | Client | MANDT | CLNT | 3 | Assigned to domain | MANDT | |||
| LDEST | Logical destination of subsystem | DEST32 | CHAR | 32 | CHAR32 | ||||
| KKANA | Name of the directory for the communications channel | KKANAL | CHAR | 10 | Assigned to domain | KKANAL | |||
| UPLDA | Upload file name | UPLDAT | CHAR | 8 | Assigned to domain | DUPLDAT | |||
| EUSER | User name | USERNAME | CHAR | 12 | USERNAME | ||||
| PASSW | Password for RFC user | PASS10 | CHAR | 10 | CHAR10 | ||||
| LANGU | Logon Language | AUSWSPR | CHAR | 1 | CHAR1 | ||||
| SAPSY | SAP System Name | PFESYSNAME | CHAR | 3 | CHAR3 | ||||
| APSER | Name of application server for communication | APSERV | CHAR | 30 | TEXT30 | ||||
| SAPSE | SAP service: Communication with external systems | SAPSE | CHAR | 2 | CHAR2 | ||||
| FUNCT | Name of function module | FUNIT | CHAR | 30 | CHAR30 | ||||
| SEGANZ | Max. number of segments in IDoc for ALE communication | SEGANZ | NUMC | 5 | SEGANZ | ||||
| LOGSYS | Logical system | LOGSYS | CHAR | 10 | Assigned to domain | ALPHA | LOGSYS |
| Key field | Non-key field |
How do I retrieve data from SAP structure E2UPLD1 using ABAP code?
As E2UPLD1 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 E2UPLD1 as there is no data to select.How to access SAP table E2UPLD1
Within an ECC or HANA version of SAP you can also view further information about E2UPLD1 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