ISUWA_ROUTE_AUTO SAP (Route Automation Data) Structure details
Description: Route Automation Data
Related tables to ISUWA_ROUTE_AUTO
Access table ISUWA_ROUTE_AUTO
Structure field list including key, data, relationships and ABAP select examples
ISUWA_ROUTE_AUTO 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 "Route Automation Data" 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_ISUWA_ROUTE_AUTO TYPE ISUWA_ROUTE_AUTO.
The ISUWA_ROUTE_AUTO table consists of various fields, each holding specific information or linking keys about Route Automation Data data available in SAP. These include MANDT (Client), ROUTE (Planned Waste Disposal Order Route), ROUTE_TXT (Text for route), STICHTAG (Date from which the route is valid).. 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 ISUWA_ROUTE_AUTO 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 |
EWAROUTE | 0 | ||||||||
MANDT | Client | MANDT | CLNT | 3 | MANDT | ||||
ROUTE | Planned Waste Disposal Order Route | EROUTE | CHAR | 10 | ALPHA | EROUTE | EROUTE | EROUTE_MAIN | |
ROUTE_TXT | Text for route | EROUTE_TXT | CHAR | 30 | CHAR30 | ||||
STICHTAG | Date from which the route is valid | EGUELTIGVON | DATS | 8 | DATUM | ||||
WASTE_TYPE1 | Waste | WASTE_TYPE | CHAR | 18 | MATN1 | MATNR | MAT | MAT1 | |
PRODUCT_AREA1 | Service Area | PRODUCT_AREA | CHAR | 2 | PRODUCT_ID | ||||
RESULTYP | Confirmation category | ERESULT | CHAR | 2 | ERESULT_ID | ||||
PRODUCT_AREA2 | Secondary service area | PRODUCT_AREA2 | CHAR | 2 | PRODUCT_ID | ||||
RESULTYP2 | Confirmation category | ERESULT | CHAR | 2 | ERESULT_ID | ||||
PRODUCT_AREA3 | Tertiary service area | PRODUCT_AREA3 | CHAR | 2 | PRODUCT_ID | ||||
RESULTYP3 | Confirmation category | ERESULT | CHAR | 2 | ERESULT_ID | ||||
FLEET_CAT | Vehicle Type | FLEET_CAT | CHAR | 10 | EQART | FLEET_CAT | |||
CAL_ID | Factory Calendar | WFCID | CHAR | 2 | WFCID | FCI | |||
CORR_OPT | Correct non-workday | CALCORR | CHAR | 1 | CALCORR | ||||
WASTE_CAL | Waste Management Calendar as Template for Route | WASTE_CAL | CHAR | 8 | CHAR8 | ECAL | |||
KOLONNE | Resource master | KOLONNE | NUMC | 8 | ORGEH | ||||
KOLONNE_TXT | Resource master text | KOLONNE_TXT | CHAR | 25 | TEXT25 | ||||
STANDARDDRIVER | Standard driver of route | STANDARDDRIVER | NUMC | 8 | CR_OBJID | ||||
EVOL_ROUTE_TARGE | Planned volume of route | EVOL_ROUTE_TARGET | QUAN | 13(3) | MENG13 | ||||
VOL_UNIT | Volume unit | VOL_UNIT | UNIT | 3 | CUNIT | MEINS | |||
EPREM_ROUTE_TARG | Target Number of Premises | EPREMISE_TARGET | NUMC | 5 | NUMC5 | ||||
ECONT_ROUTE_TARG | Planned number of containers for route | ECONT_ROUTE_TARGET | DEC | 5 | DEC5 | ||||
ETIME_ROUTE_TARG | Planned duration of route | ETIME_ROUTE_TARGET | TIMS | 6 | TIME | ||||
MEIZT | Unit of measure for travelling times | MEIZT | UNIT | 3 | CUNIT | MEINS | |||
EDIST_ROUTE_TARG | Planned distance of route | EDIST_ROUTE_TARGET | QUAN | 13(3) | MENG13 | ||||
MEDST | Unit of measure for distance | MEDST | UNIT | 3 | CUNIT | MEINS | |||
EWGHT_ROUTE_TARG | Planned weight of route | EWGHT_ROUTE_TARGET | QUAN | 13(3) | MENG13 | ||||
WEIGHT_UNIT | Unit of weight | WEIGHT_UNIT | UNIT | 3 | CUNIT | MEINS | |||
WASTE_DISP_PLANT | Waste Disposal Facility | WASTE_DISP_PLANT | CHAR | 10 | ALPHA | KUNNR | KUN | DEBI | |
REGIOGROUP | Political regional structure element | REGPOLIT | CHAR | 8 | REGPOLIT | TE227 | |||
FORM_ALLORD | Application Form 'Waste Disposal Orders in Full' | FORM_ALLORD | CHAR | 30 | FORMKEY | ||||
FORM_POSORD | Application Form 'Waste Disposal Order Items' | FORM_POSORD | CHAR | 30 | FORMKEY | ||||
FORM_HEADORD | Application Form 'Waste Disposal Orders Cover Sheet' | FORM_HEADORD | CHAR | 30 | FORMKEY | ||||
ESHIFT | Shift | ESHIFT | CHAR | 4 | CHAR4 | ||||
SHIFT_VON | Start time | TIMEFROM | TIMS | 6 | |||||
SHIFT_BIS | End time | TIMETO | TIMS | 6 | |||||
EPNT_ROUTE_TARG | Target Service Points for Route | EPOINT_ROUTE_TARG | CHAR | 4 | CHAR4 | ||||
FLEET_EQUNR1 | Vehicle Number (Equipment Number) | E_VEHICLE | CHAR | 18 | ALPHA | EQUNR | EQN | EQUI | |
ARBID1 | Object ID of the resource | CR_OBJID | NUMC | 8 | CR_OBJID | ||||
ARBPL1 | Work center | ARBPL | CHAR | 8 | ARBPL | AGR | |||
WERKS1 | Plant | WERKS_D | CHAR | 4 | WERKS | WRK | H_T001W_C | ||
FLEET_EQUNR2 | Vehicle Number (Equipment Number) | E_VEHICLE | CHAR | 18 | ALPHA | EQUNR | EQN | EQUI | |
ARBID2 | Object ID of the resource | CR_OBJID | NUMC | 8 | CR_OBJID | ||||
ARBPL2 | Work center | ARBPL | CHAR | 8 | ARBPL | AGR | |||
WERKS2 | Plant | WERKS_D | CHAR | 4 | WERKS | WRK | H_T001W_C | ||
FLEET_EQUNR3 | Vehicle Number (Equipment Number) | E_VEHICLE | CHAR | 18 | ALPHA | EQUNR | EQN | EQUI | |
ARBID3 | Object ID of the resource | CR_OBJID | NUMC | 8 | CR_OBJID | ||||
ARBPL3 | Work center | ARBPL | CHAR | 8 | ARBPL | AGR | |||
WERKS3 | Plant | WERKS_D | CHAR | 4 | WERKS | WRK | H_T001W_C | ||
INACTIVE | Indicator to Show Whether Route Has Been Deactivated | ROUTE_INACTIVE | CHAR | 1 | KENNZX | ||||
INACTIVE_DATE | Date, From Which Route Is Inactive | INACTIVE_DATE | DATS | 8 | DATUM | ||||
OBJNR | Object number | J_OBJNR | CHAR | 22 | J_OBJNR | ONR | |||
SWERK | Maintenance plant | SWERK | CHAR | 4 | WERKS | SWK | |||
STORT | Location of maintenance object | PMLOC | CHAR | 10 | AP_STAND | ||||
BEBER | Plant section | BEBER | CHAR | 3 | BEBER | BBE | |||
GSBER | Business Area | GSBER | CHAR | 4 | GSBER | GSB | |||
KOKRS | Controlling Area | KOKRS | CHAR | 4 | CACCD | CAC | |||
KOSTL | Cost Center | KOSTL | CHAR | 10 | ALPHA | KOSTL | KOS | ||
BUKRS | Company Code | BUKRS | CHAR | 4 | BUKRS | BUK | C_T001 | ||
DAUFN | Standing order number | DAUFN | CHAR | 12 | ALPHA | AUFNR | ORDP | ||
AUFNR | Settlement order | ILOM_ORDST | CHAR | 12 | ALPHA | AUFNR | ORDE | ||
DWERK | Delivering Plant | DWERK | CHAR | 4 | WERKS | ||||
BEH_LGORT | Location: Storage location in plant | L_LGORT | CHAR | 4 | LGORT | LAG | |||
COSTCOL | Cost Collector for Waste Disposal Order | ECOSTCOL | CHAR | 2 | ECOSTCOL | ||||
INITIAL_STATUS | Initial Status When Creating Waste Disposal Order | INITIAL_STATUS | CHAR | 4 | INITIAL_STATUS | ||||
FRAKTION | Waste Fraction | WASTETYPE | CHAR | 9 | MATKL | ||||
KOPFVERWIEGUNG | Header Weighing | EEWA_VERWKOPF | CHAR | 1 | EEWA_VERWIEGUNGOK | ||||
POSVERWIEGUNG | Item Weighing | EEWA_VERWPOS | CHAR | 1 | EEWA_VERWIEGUNGOK | ||||
ERDAT | Date on Which Record Was Created | ERDAT | DATS | 8 | DATUM | ||||
ERNAM | Name of Person who Created the Object | ERNAM | CHAR | 12 | USNAM | ||||
AEDAT | Changed On | AEDAT | DATS | 8 | DATUM | ||||
AENAM | Name of Person Who Changed Object | AENAM | CHAR | 12 | USNAM | ||||
BEGRU | Authorization Group | BEGRU | CHAR | 4 | BEGRU | ||||
LOEVM | Deletion Indicator | LOEVM | CHAR | 1 | XFELD | ||||
ROUTE_USE | Indicators | KENNZX | CHAR | 1 | KENNZX | ||||
ROUTE_WMODE | Processing mode (1 = display, 2 = change, 3 = create...) | E_MODE | CHAR | 1 | E_MODE | ||||
ROUTE_OKCODE | Function Code | CUA_CODE | CHAR | 20 | CUA_CODE |
Key field | Non-key field |
How do I retrieve data from SAP structure ISUWA_ROUTE_AUTO using ABAP code?
As ISUWA_ROUTE_AUTO 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 ISUWA_ROUTE_AUTO as there is no data to select.How to access SAP table ISUWA_ROUTE_AUTO
Within an ECC or HANA version of SAP you can also view further information about ISUWA_ROUTE_AUTO 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