LXE_SXMAN_TRANSPORT_TASK SAP (SXMan Transport Task) Structure details
Description: SXMan Transport Task
Related tables to LXE_SXMAN_TRANSPORT_TASK
Access table LXE_SXMAN_TRANSPORT_TASK
Structure field list including key, data, relationships and ABAP select examples
LXE_SXMAN_TRANSPORT_TASK 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 "SXMan Transport Task" 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_LXE_SXMAN_TRANSPORT_TASK TYPE LXE_SXMAN_TRANSPORT_TASK.
The LXE_SXMAN_TRANSPORT_TASK table consists of various fields, each holding specific information or linking keys about SXMan Transport Task data available in SAP. These include REPOSITORY (System Name in CMS), ACTIVITYID (Activity ID in Java Environment), VENDOR (Provider in Java Transport Environment), SCNAME (Name of Software Component).. 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: Cannot Be Enhanced
SAP LXE_SXMAN_TRANSPORT_TASK 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 |
| ID | Transport Request ID for Java Environment | LXETRNSPRTID | NUMC | 10 | LXETRNSPRTID | ||||
| REPOSITORY | System Name in CMS | LXECMSRPSTRY | CHAR | 15 | LXECMSRPSTRY | ||||
| ACTIVITYID | Activity ID in Java Environment | LXEACTIVITYID | CHAR | 32 | LXEACTIVITYID | ||||
| VENDOR | Provider in Java Transport Environment | LXEVENDOR | CHAR | 20 | LXEVENDOR | ||||
| SCNAME | Name of Software Component | LXESCNAME | CHAR | 30 | LXESCNAME | ||||
| WORKSPACE | Workspace Name in Java Transport Environment | LXEWORKSPACE | CHAR | 255 | LXEWORKSPACE | ||||
| STATUS | SXMan Tranport Request Status | LXETRNSPRTSTT | NUMC | 3 | LXETRNSPRTSTT | ||||
| CHNGUSER | Last Changed by | AS4USER | CHAR | 12 | AS4USER | ||||
| CHNGDATE | System Date | SYDATUM | DATS | 8 | SYDATS | ||||
| CHNGTIME | System Time | SYUZEIT | TIMS | 6 | SYTIME | ||||
| CRTDATE | System Date | SYDATUM | DATS | 8 | SYDATS | ||||
| CRTTIME | System Time | SYUZEIT | TIMS | 6 | SYTIME | ||||
| OBJECTSTOTAL | 0 | ||||||||
| OBJECTSERROR | 0 |
| Key field | Non-key field |
How do I retrieve data from SAP structure LXE_SXMAN_TRANSPORT_TASK using ABAP code?
As LXE_SXMAN_TRANSPORT_TASK 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 LXE_SXMAN_TRANSPORT_TASK as there is no data to select.How to access SAP table LXE_SXMAN_TRANSPORT_TASK
Within an ECC or HANA version of SAP you can also view further information about LXE_SXMAN_TRANSPORT_TASK 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