/SCTM/TMMD_UI
204 messages in this application area
Each row lists the SAP message number and the English message text as provided in the source extract. Use anchors (e.g. #msg-123) to deep-link to a specific message on this page.
| Message | Message text |
|---|---|
| 1 | Enter the name of the route |
| 2 | Route &1 exists already |
| 3 | Route &1 does not exist |
| 4 | Location &1 does not exist |
| 5 | Means of transport &1 does not exist |
| 6 | Leg &1 exists already |
| 7 | Saving successful |
| 8 | Location is not compatible with previous leg |
| 9 | Zone &1 does not exist |
| 10 | First stop and last stop must agree with the leg |
| 11 | Error while saving the route: &1 |
| 12 | Number of selected entries: &1 |
| 13 | Error while saving the stops |
| 14 | Internal error |
| 15 | Validity [&1,&2] is not permitted as a period of time |
| 16 | Enter a valid weight group |
| 17 | Maximum weight group must be greater than minimum weight group |
| 18 | Transportation service provider/carrier &1 does not exist |
| 19 | Transportation Zone &1 invalid as Transshipment Location |
| 20 | Route &1 is marked for deletion |
| 21 | Route &1 is not marked for deletion |
| 22 | You do not have the necessary authorization for this function |
| 23 | Route &1 is already being processed by user &2 |
| 24 | Route &1 was distributed successfully |
| 25 | Error while distributing route &1 |
| 26 | No target system was found |
| 27 | Error while saving the routes |
| 28 | Routes with deletion flag were deleted |
| 29 | Enter a valid carrier |
| 30 | Validity [&1,&2] lies in the past |
| 31 | Data cannot be distributed |
| 32 | Error while distributing zone &1 |
| 33 | Route &1 was saved successfully |
| 34 | Routes were not deleted |
| 35 | Supply-Chain-Unit &1: no authority for this activity |
| 36 | Means of transport &2: Neither the same nor higher-level than MTr &1 |
| 37 | Maximum weight must be greater than minimum weight |
| 38 | Enter a weight unit |
| 39 | Maximum volume must be greater than minimum volume |
| 40 | Enter a volume unit |
| 41 | Enter a unit for the length/width/height |
| 42 | Function is not allowed |
| 43 | You cannot change the cross-docking location |
| 44 | Restrictions for weight/volume/dimensions would be lost |
| 45 | Choose one route to copy |
| 46 | Request type & does not exist |
| 47 | Shipping condition & does not exist |
| 48 | Time unit & is invalid |
| 49 | Locking error |
| 50 | Lead times for request types were deleted |
| 51 | Request types for stops were deleted |
| 52 | Route &1 is used in CD route &2 and cannot be deleted |
| 53 | Route &1 either does not begin or end at location of CD route &2 |
| 54 | No route meets selection criteria |
| 55 | Schedules with deletion flag were deleted |
| 56 | Zones with deletion flag were deleted |
| 57 | Schedules were not deleted |
| 58 | Zones were not deleted |
| 59 | Leg location &1 is the cross-docking location for CD Route &2 |
| 60 | Supply chain unit &1 already exists |
| 61 | Schedule &1: sequence number of stop &2 not in [&3,&4] |
| 62 | Schedule &1: inconsistent stop sequence |
| 63 | Means of transport &1 cannot be used for schedule &2 |
| 64 | Schedule &1 defined for means of transport &2 already dep. calendar &3 |
| 65 | Schedule &1 defined for means of transport &2 already TSP / carrier &3 |
| 66 | Vehicle &1 is defined as means of transport &2 |
| 67 | Stop &1 is not contained in zone &2 of the schedule |
| 68 | No location meets the selection criteria |
| 69 | Transportation zone &1 must be an optional stop |
| 70 | Aspect &1 is unknown or cannot be processed |
| 71 | Check transportation lane (&1,&2,&3): transportation duration 0 |
| 72 | Departure calendar &1 for MTr &2 deleted; sched. not superord. to MTr &3 |
| 73 | TSP/carrier &1 for MTr &2 was deleted; schedule not superord. to MTr &3 |
| 74 | Departure calendar &1: change means of transport from &2 to &3 |
| 75 | TSP / carrier &1: change means of transport from &2 to &3 |
| 76 | Schedule &1 already exists |
| 77 | No authority to distribute Routing Guide master data |
| 78 | No authority to create Routing Guide master data |
| 79 | No authority to change Routing Guide master data |
| 80 | No schedule found for search variant |
| 81 | No transportation zone found for search variant |
| 82 | No route found for search variant |
| 83 | No TSP / carrier profile found for search variant |
| 84 | Search pattern for stop sequence incomplete |
| 85 | No authority to display Routing Guide master data |
| 86 | No authority to delete Routing Guide master data |
| 87 | No authority to create Cross-Docking Routes |
| 88 | No authority to change Cross-Docking Routes |
| 89 | No authority to delete Cross-Docking Routes |
| 90 | Calendar &2 exists already for request type &1 |
| 91 | Transportation service provider &1 was already defined for MTr &2 |
| 92 | No means of transport maintained; MTr &1 of leg was entered by default |
| 93 | No authority to create Supply-Chain-Unit &1 |
| 94 | No authority to change Supply-Chain-Unit &1 |
| 95 | No authority to display Supply-Chain-Unit &1 |
| 96 | No authority to assign Supply-Chain-Unit &1 |
| 97 | No authority to save Supply-Chain-Unit &1 |
| 98 | No authority to read Supply-Chain-Unit &1 |
| 99 | Calendar &1: invalid vehicle |
| 100 | *************Messages for Zone Maintenance******************** |
| 101 | Enter the name of the zone |
| 102 | Zone &1 exists already |
| 103 | Zone &1 does not exist |
| 104 | Zone &1: error when saving |
| 105 | Zone &1 is marked for deletion |
| 106 | Zone &1 is already being edited by user &2 |
| 107 | Zone &1: fill all mandatory fields |
| 108 | Zone &1: country/region key does not exist |
| 109 | Postal code zone limit &2 is not in format of country/region &1 |
| 110 | Postal code zone: upper limit &2 must be greater than lower limit &1 |
| 111 | No zone is marked for deletion |
| 112 | Zone &1: postal code zone limit does not exist |
| 113 | Region &2 is not in the format of country/region &1 |
| 114 | Zone &1: region does not exist |
| 115 | Country/Region &1 does not exist |
| 116 | Maintain zones of type Leg in route maintenance |
| 117 | Zone &1: data is inconsistent |
| 118 | Zone &1: data was saved successfully |
| 119 | Save Zones first before executing this function |
| 120 | Selected zones with deletion flag were deleted |
| 121 | Zone type &1 does not exist |
| 122 | Type of zone &1 set to "mixed zone" |
| 123 | You are not allowed to change leg zone &1 |
| 124 | Choose a region |
| 125 | Country/Region &1: region &2 is already assigned |
| 126 | Country/Region &1 is already assigned |
| 127 | Country/Region &1 was assigned |
| 128 | All regions in country/region &1 were added |
| 129 | Country/Region &1 does not have any regions |
| 130 | Region &1 of country/region &2 is already covered by &3 zone(s) |
| 131 | Postal Codes &1 - &2 of Ctry/Reg. &3 are already covered by &4 zone(s) |
| 132 | Location &1 is already directly included in &2 zone(s) |
| 133 | Select a valid zone type |
| 134 | Cannot change zone type to a leg zone |
| 135 | Zone &1; coordinates determined successfully |
| 136 | Zone &1; cannot determine coordinates (no locations assigned) |
| 137 | Zone &1; cannot determine coordinates (check assigned locations) |
| 138 | Zone type must be mixed due to existing definitions |
| 139 | Zone type corrected to &1 |
| 140 | Zone &1 is still used in area &2 |
| 141 | Route &1 is still used in area &2 |
| 142 | Carrier &1 is still used in area &2 |
| 143 | You cannot change the zone type for a leg zone |
| 144 | Selected Zone(s) do not include any locations |
| 145 | Do you want to save &1 new zones? |
| 146 | Location &1 already exists |
| 147 | Number of displayed Locations restricted to &1 |
| 150 | *************Messages for Schedule Maintenance******************** |
| 151 | Select a schedule to copy |
| 152 | Cannot copy schedule; schedule not found |
| 153 | Schedule &1 already exists |
| 154 | Selected schedule not in edit mode |
| 155 | No departures selected |
| 156 | Schedule &1: same stop appears twice in the stop sequence |
| 157 | Stop &1: Minimum Wait Time greater Maximum Wait Time |
| 158 | Stop &1: Wait times can't be saved |
| 159 | Schedule &1: Departure &2 &3 not inserted |
| 160 | Schedule &1: Departure &2 &3 already exists |
| 161 | No departures available |
| 162 | &1 calendar departures have been restored |
| 163 | Schedule &1: Departure &2 &3 is outside of the schedule validity |
| 164 | Departures are assigned without calendar |
| 165 | All departures have been fixed |
| 166 | All departures have been unfixed |
| 167 | Schedule &1: multiple departure calendars are assigned |
| 168 | Schedule &1: transportation duration between two stops is initial |
| 169 | Schedule &1 is inconsistent and can not be used in TM planning |
| 170 | Carrier profile created for carrier &1 |
| 200 | **********Messages for Location Dependencies********* |
| 201 | Transportation zone &2 still exists for location &1 |
| 202 | Location is still assigned to zone &1 |
| 203 | Location is still assigned to route &1 |
| 204 | Location was included in route &1; regenerate stops |
| 205 | Location is still assigned to carrier/transportation service provider &1 |
| 206 | Location &1 is marked for deletion |
| 300 | ****Messages for RG Master Data Distribution***** |
| 301 | Select at least one criterium in the master data selection |
| 302 | Enter routes for distribution |
| 303 | Enter zones for distribution |
| 304 | Enter transportation service providers for distribution |
| 305 | Only direct, region, and postal code zones are distributed |
| 306 | No recipient was found for business object &1 |
| 307 | No route was found |
| 308 | Business object &1: system error while generating an IDoc |
| 309 | Not all locations in zone &1 are known externally |
| 310 | Business partner &1 does not exist in target system |
| 311 | Transportation group &1 does not exist in target system |
| 312 | Product freight group &1 does not exist in target system |
| 313 | Means of transport &1 does not exist in target system |
| 314 | Freight code set &1 does not exist in target system |
| 315 | Location &1 does not exist in target system |
| 316 | Distribution was completed successfully |
| 317 | Zone &1 not in target system; TSP / carrier assignment not distributed |
| 318 | Location &1 not in target system; TSP/carrier assignment not distributed |
| 319 | |
| 320 | |
| 400 | ******Calendar Assignment****** |
| 401 | Supply chain unit &1 does not exist |
| 402 | Enter the name of the calendar |
| 403 | Calendar &1 exists already |
| 404 | Calendar &1 is already assigned to a different supply chain unit |
| 405 | Departure pattern for calendar &1 is invalid |
| 406 | Departure calendar &1 does not exist |
| 407 | Calendar &1 is not defined in /SAPAPO/CALENDAR |
Message texts are shown for technical reference in consulting and education contexts. SAP, SAP TM, SAP EWM, SAP GTS, SAP S/4HANA and other SAP product and service names are trademarks or registered trademarks of SAP SE in Germany and other countries.