/SCWM/MFS - Material Flow Control
The following messages are stored in message class /SCWM/MFS: Material Flow Control.
It is part of development package /SCWM/MFS in software component SCM-EWM. This development package consists of objects that can be grouped under "Material Flow Systems".
It is part of development package /SCWM/MFS in software component SCM-EWM. This development package consists of objects that can be grouped under "Material Flow Systems".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Action '00' is reserved for function module: '/SCWM/MFS_RECEIVE' |
| 001 | Conveyor segment &1 is inactive with exception code &2 |
| 002 | Maximum capacity of conveyor segment &1 reached |
| 003 | No entry determined in storage control, WT remains inactive |
| 004 | No storage bin is maintained in communication point &1 &2 |
| 005 | Communication point and clarification bin must not be identical |
| 006 | At least one clar. communication point or SP/EP/NIO indicator must be set |
| 007 | You must specify the associated PLC for the clar. communication point |
| 008 | Conveyor segment for clarific. communication point &1 &2 is not active |
| 009 | No storage bin or communication point was transferred |
| 010 | Unable to determine a communication point |
| 011 | MFS action &1 is not defined |
| 012 | Unable to determine an MFS action |
| 013 | Communication point type &1 is not maintained |
| 014 | Unable to determine a communication point for storage bin &1 |
| 015 | Conveyor segment &1 is not assigned to a conveyor segment group |
| 016 | Conveyor segment group &1 is not maintained |
| 017 | Conveyor segment &1 is not maintained |
| 018 | PLC &1 is not maintained |
| 019 | Unable to determine a telegram structure for telegram type &1 |
| 020 | No communication point has been entered as a starting point |
| 021 | No communication point has been entered as an end point |
| 022 | No communication point has been entered as a clarification comm. point |
| 023 | No data maintained in table &2 for warehouse number &1 |
| 024 | No storage bin defined for storage group &1 |
| 025 | Details of where storage section &1 is called from are not specified |
| 026 | No follow-on storage group found for &1, looking for intermed. location |
| 027 | No storage group found for storage bin &1 |
| 028 | Unable to determine data for warehouse number &1 |
| 029 | Unable to find conveyor segment for storage group &1 |
| 030 | Storage bins in the item table overlap with each other. Table deleted. |
| 031 | No value found on node &1, unable to determine line |
| 032 | You do not have authorization for warehouse number &1 and PLC &2 |
| 033 | Specify the capacity and exception code |
| 034 | Communication point &1 &2 is inactive with exception code &3 |
| 035 | Maximum capacity of communication point &1 reached |
| 036 | Error occurred while changing inbound telegram queue |
| 037 | Error occurred while deleting inbound telegram queue |
| 038 | Error occurred while reading inbound telegram queue |
| 039 | No inactive warehouse task exists for HU &1 |
| 040 | Communication channel for object &1, object type &2 not found (&3 &4) |
| 041 | Customizing data for communic. channel &1 of PLC &2 (whse &3) not defined |
| 042 | Application data for communic. channel &1 of PLC &2 (whse &3) not defined |
| 043 | Communication channel &1 of PLC &2 is blocked by exception &3 |
| 044 | Communication channel &1 of PLC &2 is not synchronized |
| 045 | Ranking sequence of communication channel objects for PLC &1 not found |
| 046 | Unable to determine a suitable communication channel |
| 047 | Mapping structure for telegram category &1 of PLC &2 not found |
| 048 | Mapping structure for telegram type &1 of PLC &2 not found |
| 049 | Telegram category or telegram type must be entered |
| 050 | Communication channel &1 (&2) already or currently being synchronized |
| 051 | Communication channel &1 (&2 &3) has already been stopped |
| 052 | Entry &1 in app. table &2 deleted since missing from Customizing table &3 |
| 053 | Entry &1 in app. table &2 generated since exists in Customizing table &3 |
| 054 | Unable to access table &1 |
| 055 | Specify a maximum of one object for the status query |
| 056 | You have not specified an object for the status query |
| 057 | Application data was synchronized with Customizing data of warehouse &1 |
| 058 | No MFS error maintained for telegram error &1 (&2 &3) |
| 059 | Received telegram &1 (&2 &3) does not contain a suitable start sequence |
| 060 | Received telegram &1 (&2 &3) does not contain a suitable end sequence |
| 061 | Received telegram &1 (&2) has an unexpected length (&3 vs. &4) |
| 062 | Received telegram &1 (&2 &3) does not contain a suitable sequence number |
| 063 | Received telegram &1 (&2 &3) contains unexpected recipient &4 |
| 064 | Received telegram &1 (&2 &3) contains unexpected sender &4 |
| 065 | Changing communication channel &1 (&2) not possible |
| 066 | Communication channel &1 (&2) was stopped by user &3 |
| 067 | Status telegram is not provided for storage bin |
| 068 | Function module for sending telegrams is missing for PLC &1 (&2) |
| 069 | Specify the function module for sending telegrams for PLC &1 |
| 070 | Specify either a resource type or a communication point type |
| 071 | & PLC objects were created |
| 072 | Data transfer to communication layer of PLC &1 failed (&2) |
| 073 | No exception code maintained for communication error &1 (&2 &3) |
| 074 | Only outbound telegrams can be resent |
| 075 | Fill either the communication point or queue field for an entry |
| 076 | Unable to change entry &1 &2 &3 |
| 077 | Entry &1 &2 &3 is already being processed |
| 078 | Do you really want to delete &1 entries? |
| 079 | Unable to delete some entries due to locks |
| 080 | No clarification communication point maintained for commun. point &1 (&2) |
| 081 | HU &1 cannot be moved since conveyor segment &2 is not ready |
| 082 | Set either an end point or clarification communication point indicator |
| 083 | Deleting HU error only possible for start bin, end bin, or clarific. bin |
| 084 | No queue defined for PLC &1 (&2) |
| 085 | Communication error occurred in communication layer of PLC &1 |
| 086 | Internal error occurred in communication layer of PLC &1 |
| 087 | Specify the capacity, capacity mode, and exception code |
| 088 | Communication channel not defined for host &1 and port &2 |
| 089 | Enter either host and port, or warehouse, PLC, and communication channel |
| 090 | Unable to lock handling unit &1 while determining warehouse task |
| 091 | Interleaving and max. no. of telegrams is greater than 1; see field help |
| 092 | Warehouse task for HU &1 not sent to PLC due to exception code &2 |
| 093 | HU &1 discharged to clarification commun. point due to exception code &2 |
| 094 | Warehouse task for HU &1 not created due to exception code &2 |
| 095 | No active warehouse task exists for HU &1 |
| 096 | Unable to access communication channel &1 (&2) |
| 097 | Customizing of execution environment and resource are different |
| 098 | Enter the host and port |
| 099 | Host and port combination used for entry &1; combination must be unique |
| 100 | &1 data records deleted with a date prior to &2 &3 |
| 101 | Location in telegram not filled (field &1) |
| 102 | Additional warehouse task only possible for end or clarif. commun. point |
| 103 | Additional warehouse task only possible for start bin |
| 104 | Clarif. storage section type must also be specified for clarif. bin |
| 105 | Clarif. storage type must also be specified for clarif. storage section |
| 106 | Specify a warehouse process type for an additional WT |
| 107 | Mapping structure for telegram category &1 of PLC type &2 not found |
| 108 | Mapping structure for telegram type &1 of PLC Type &2 not found |
| 109 | No conveyor segment determined; HU &1 cannot be moved |
| 110 | No header data structure specified for PLC &1 (&2) |
| 111 | No structure specified for telegram type &1 of PLC &2 (&3) |
| 112 | Specified function module &1 (for &2) does not exist |
| 113 | Could not find entry &1 &2 &3 |
| 114 | Unable to determine PLC for sender &1 or recipient &2 |
| 115 | Telegram was transmitted |
| 116 | Unable to transmit telegram correctly |
| 117 | Unable to lock HU &1 during start point processing |
| 118 | Unable to lock HU &1 during WT confirmation |
| 119 | No clarification communiction point can be set for NIO indicator |
| 120 | Telegram is too long; maximum telegram length is 4096 characters |
| 121 | No active warehouse task exists for HU &1 |
| 122 | Unable to reach PLC &1 (&2); restart of communication channel &3 |
| 123 | Communication channel &1 (&2) is locked by another process |
| 124 | A dummy HU is being created because HU &1 is at the wrong location |
| 125 | WO &1 must be finished first, WO &2 not processed |
| 126 | . |
| 128 | Resource &1 is inactive with exception code &2 |
| 129 | Create WT for HU &1 to resource error storage bin &2 |
| 130 | Processing internal process code &1 (Storage Bin Empty) |
| 131 | Processing internal process code &1 (Storage Bin Full) |
| 132 | Processing internal process code &1 (HU Not Identifiable) |
| 133 | Processing internal process code &1 (Undo Cancelation Request) |
| 134 | Processing internal process code &1 (Undo Order to PLC) |
| 135 | Processing internal process code &1 (Move to Clarification Bin) |
| 150 | ***** Start FM /SCWM/MFS_WT_DET_PREP for PLC &1 (&2) and CP &3 ***** |
| 151 | ***** End FM /SCWM/MFS_WT_DET_PREP ***** |
| 152 | ***** Start FM /SCWM/MFS_WT_DET ***** |
| 153 | ***** End FM /SCWM/MFS_WT_DET ***** |
| 154 | Queue &1 does not belong to an MFS resource; entry will be ignored |
| 155 | Checking queue &1 |
| 156 | Checking communication point &1 &2 |
| 157 | No HUs at communication point &1 &2 |
| 158 | Communication point &1 &2 is locked by a parallel process |
| 159 | Checking HU &1 |
| 160 | WT &1 not yet sent to PLC; WT will be sent |
| 161 | WT &1 was not sent; check for MP &2 &3 canceled |
| 162 | WT &1 already sent to PLC |
| 163 | Cancelation request exists for WT &1 |
| 164 | No open WT exists for HU &1 |
| 165 | HU &1 is at the end of automatic storage retrieval; no WT required |
| 166 | Creating WT for HU &1 |
| 167 | Unable to create WT; checking of communication point &1 &2 stopped |
| 168 | ***** Start FM /SCWM/MFS_WT_CREA_FOLLUP ***** |
| 169 | ***** End FM /SCWM/MFS_WT_CREA_FOLLUP ***** |
| 170 | ***** Start FM /SCWM/MFS_HU_ADJ_LOC for HU &1 ***** |
| 171 | ***** End FM /SCWM/MFS_HU_ADJ_LOC ***** |
| 172 | Communic. point &1 &2 is ID point; no WT created for HU &3 |
| 173 | ***** Start FM /SCWM/MFSACT_SP for HU &1 (&2) ***** |
| 174 | ***** End FM /SCWM/MFSACT_SP ***** |
| 175 | Start date/time &1 for telegram &2 |
| 176 | WT created for HU &1 from &2 to &3 |
| 177 | Unable to create WT |
| 178 | As HU &1 is unknown, a dummy HU is being created |
| 179 | Dummy HU &1 was created |
| 180 | Telegram for HU &1 contains MFS error &2 |
| 181 | HU data of HU &1 being adjusted to data of telegram |
| 182 | WT created for clarific. bin &1 outside of automatic storage retrieval |
| 183 | Determining storage control data for WT &1 |
| 184 | Determining storage control data for communication point &1 &2 |
| 185 | Unable to create WT as storage control date could not be determined |
| 186 | ***** Start FM /SCWM/MFSACT_WT_CONFIRM for HU &1 (&2) ***** |
| 187 | ***** End FM /SCWM/MFSACT_WT_CONFIRM ***** |
| 188 | ID point functions |
| 189 | Inactive WT &1 will be canceled |
| 190 | Confirming active WT &1 HU &2 from &3 to &4 |
| 191 | WT confirmed immediately for storage bin &1 is being created |
| 192 | WT confirmation functions |
| 193 | No active or inactive warehouse task for HU &1 |
| 194 | Creating WT in direction of clarification bin &1 |
| 195 | Deleting MFS error &1 of HU &2 |
| 196 | Processing resource &1 &2 |
| 197 | WT &1 HU &2 from &3 to &4 determined |
| 198 | Processing communication point &1 &2 |
| 199 | WT &1 created |
| 201 | Lock user copied from WT_DET_CONF |
| 202 | /SCWM/MFS_WT_DET with table of queues called |
| 203 | /SCWM/MFS_WT_DET with queue &1 called |
| 204 | /SCWM/MFS_WT_DET with warehouse task &1 called |
| 205 | Resource &2 determined for queue &1 |
| 206 | No resource determined for queue &1 -> conveyor segment |
| 207 | Resource &1 current value: &2 |
| 208 | Resource &1 does not have free capacity |
| 209 | Resource &1 has no current location -> no interleaving |
| 210 | Resource &1 is to execute stock removal for interleaving |
| 211 | Warehouse orders with the status 'Started' were found |
| 212 | Warehouse orders with the status 'Open' were found |
| 213 | No matching warehouse order were found for interleaving |
| 214 | Matching warehouse order were found for interleaving |
| 215 | No warehouse orders to be processed were found for queue &1 |
| 216 | Processing warehouse order &1 |
| 217 | Warehouse task &1 HU &2 from &3 to &4 is to be sent |
| 218 | Calling /SCWM/MFS_WT_DET_PREP for communication point &1 |
| 219 | Res. &1 reached maximum capacity after sending; continue with next queue |
| 220 | PLC is blocked by exception &1 |
| 221 | Segment and/or communication point are not ready to receive |
| 222 | Warehouse task &1 was sent with telegram &2 |
| 223 | Setting pseudo MFS error &1 for HU &2 |
| 224 | Queue &1 of WT &2 for HU &3 is not MFS-relevant |
| 225 | Resource &1 is to perform putaway for interleaving |
| 226 | Process ID &1 of server &2 |
| 227 | Start date/time &1 |
| 228 | Warehouse task &1 has already been sent by another process |
| 229 | End date/time &1 |
| 230 | HU &1 at the end of the automatic storage retrieval; sending not required |
| 231 | WT &1 not relevant for sub system, but is in automatic storage retrieval |
| 232 | WT &1 has been added to the buffer for outgoing telegrams |
| 233 | BAdI to change destination data of inactive WT for HU &1 will be called |
| 234 | Destination data of inactive WT was not changed in BAdI |
| 235 | /SCWM/MFS_WT_DET_PREP returns without warehouse order |
| 236 | Index entries made up of transferred warehouse tasks |
| 237 | ***** Start FM /SCWM/MFSACT_STATUS ***** |
| 238 | ***** End FM /SCWM/MFSACT_STATUS ***** |
| 239 | EWM exception code &1 found for PLC error code &2 |
| 240 | Exception code &1 set for conveyor segment &2 |
| 241 | Exception code &1 set for conveyor segment group &2 |
| 242 | Exception code &1 set for resource &2 |
| 243 | Exception code &1 set for communication point &2 |
| 244 | ***** Start FM /SCWM/MFSACT_LOC_EMPTY for CP &1 ***** |
| 245 | ***** End FM /SCWM/MFSACT_LOC_EMPTY ***** |
| 246 | Sub system status of WT &1 changed to "Sent to External System" |
| 247 | ***** Start FM /SCWM/MFSACT_REPLENISH for CP &1 ***** |
| 248 | ***** End FM /SCWM/MFSACT_REPLENISH ***** |
| 249 | Replenishment triggered for storage bin &1 |
| 250 | ***** Start FM /SCWM/MFSACT_WT_CONFIRM_CANC for HU &1 (&2) ***** |
| 251 | ***** End FM /SCWM/MFSACT_WT_CONFIRM_CANC ***** |
| 252 | Telegram counter of resource &1 reduced by 1 to &2 |
| 253 | Telegram counter of resource &1 reduced by 1 at telegram receipt |
| 254 | Telegram counter of resource &1 increased by 1 to &2 |
| 255 | Check whether WT for HU &1 can be sent to PLC |
| 256 | Resource &1 has to finish HU movement of WO &2 |
| 257 | Unable to create WT - communication point &1 &2 is scanner point |
| 258 | Communication point &1 &2 is scanner point - checking current HU |
| 259 | Called in background task (called at &1 from online part) |
| 260 | ***** Start FM &1 at &2 ***** |
| 261 | ***** End FM &1 at &2 ***** |
| 262 | Received telegram &1 (&2 &3) contains invalid content |
| 263 | Logical destination category &1 was already assigned to CP &2 &3 &4 |
| 264 | Routing entry for &1 &2 &3 &4 could not be found |
| 265 | Logical destination for PLC &1 has to be unique for CP &2 &3 &4 |
| 266 | ***** Start FM &1 for HU &2 (&3) ***** |
| 267 | HU &1 was checked with negative result in BAdI |
| 268 | HU &1 contains MFS error &2 |
| 269 | CP &1 &2 and storage bin &3 determined for HU movement posting |
| 270 | HU &1 is empty |
| 271 | Logical destination for PLC &1 determined &2 &3 &4 |
| 272 | &1 &2 &3: enter a logical destination for EWM or an activity area |
| 273 | For the logical dest. for PLC &1 &2 &3 &4 the CP must be the same |
| 274 | HU &1 already booked to storage bin &2; no change necessary |
| 275 | For category &1 &2 no logical destination for EWM is maintained |
| 276 | Logical destination for EWM &1 &2 does not exist |
| 277 | Logical destination with initial value is not valid |
| 278 | Routing entry for &1 &2 &3 with category &4 could not be found |
| 279 | HU &1 is updated with exception code &2 |
| 280 | No warehouse order and warehouse task exist for HU &1 |
| 281 | BAdI returns with WT: &1, change WT: &2, bin: &3, log. destination: &4; |
| 282 | BAdI to determine destination data for HU &1 is called |
| 283 | Destination bin &1 and activity area &2 determined for HU &3 and WT &4 |
| 284 | Routing decision determination for HU &1 is called |
| 285 | Activity area &1 and logical destination &2 set |
| 286 | BAdI for checking HU &1 is called |
| 287 | And returns with HUtype: &1; update dim.: &2; dst.: &3; exception: &4 |
| 288 | Destination location &1 &2 &3 and logical destination &4 determined |
| 289 | No activity area and no logical destination was set |
| 290 | MFS error &1 is mapped to exception code &2 |
| 291 | Open warehouse task &1 with activity area &2 determined |
| 292 | Telegram with logical destination for PLC &1 is send to the PLC |
| 293 | Asynchronous call of action function module deactivated |
| 294 | Unable to change HU &1 |
| 295 | Unable to confirm warehouse task |
| 296 | Unable to cancel warehouse task |
| 297 | Unable to change warehouse task |
| 298 | Logical dest. for PLC could not be determined; no telegram send to PLC |
| 299 | Looking for routing entry with &1 &2 &3 and log. destination &4 |
| 300 | Looking for routing entry with &1 &2 &3 and activity area &4 |
| 301 | Default routing entry for &1 &2 &3 could not be found |
| 302 | Routing entry for &1 &2 &3 and log. destination PLC &4 could not be found |
| 303 | MFS error &1 is not mapped to an exception code |
| 304 | Queue determination for warehouse task &1 started |
| 305 | Activity area &1 set |
| 306 | Logical destination &1 set |
| 307 | Trigger telegram processing for PLC &1 is not necessary (case conveyor) |
| 308 | ***** Start FM &1 for warehouse &2, PLC &3, channel &4 ***** |
| 309 | Maximum number of work processes reached |
| 310 | Telegrams for CP/resource &1 are processed by another parallel process |
| 311 | Start action FM &1 at &2 |
| 312 | End action FM &1 at &2 |
| 313 | Action FM descided not to execute asynchronous action FM &1 |
| 314 | Transaction ID &1 used |
| 315 | Start asynchronous action FM &1 at &2 (on server group &3) |
| 316 | *** Telegram &1 for HU &2, telegram type &3 processed for CP/resource &4 |
| 317 | No (further) telegrams to be processed found |
| 318 | The selected telegrams are processed by a different process |
| 319 | &1: Telegram was deleted by a different process |
| 320 | &1: Telegram could not be deleted; wait 1s for update task of WT |
| 321 | &1: Telegram successfully deleted in outgoing telegram queue |
| 322 | WT cannot be determined |
| 323 | WT &1 for HU &2 from &3 to &4 determined |
| 324 | WO &1 should get processed |
| 325 | Start time set for WO &1 |
| 326 | &1: KZSUB of WT &2 set to &3 |
| 327 | &1: Searching for waiting outgoing telegrams of PLC &2, channel &3 |
| 328 | &1: Found telegram for HU &2 from &3 to &4 |
| 329 | &1: Triggering sending of telegram |
| 330 | &1: Lock attempt for HU &2 |
| 331 | &1: HU &2 could not be locked |
| 332 | WT &1 could not be selected |
| 333 | &1: HU &2 could be locked and was unlocked again |
| 334 | There is already a process running taking care of telegram repetition |
| 335 | &1: Process will be stopped because all channels are stopped |
| 336 | Communication channel &1 &2 locked, halted or not synced |
| 337 | Process is stopped on user request |
| 338 | Process mismatch; stop for safety reasons |
| 339 | No wait interval could be determined |
| 340 | &1: Telegram &2 for HU &3 found in outgoing telegram buffer |
| 341 | &1: Telegram could not be locked; check next channel |
| 342 | Telegram &1 was sent |
| 343 | Checking PLC &1, channel &2 |
| 344 | LIFE telegram generated for PLC &1, channel &2 |
| 345 | Wait interval for telegram not passed, yet |
| 346 | &1: max. retries executed; trigger communication exception handling |
| 347 | ***** End FM &1 at &2 (duration &3 ms) ***** |
| 348 | End date/time &1 (duration &2 ms) |
| 349 | Telegram contains MFS error &1 |
| 350 | Warehouse task &1 has already been sent, delete mfsdelay entry |
| 351 | &1 telegram(s) read |
| 352 | CP &1 dequeued |
| 353 | /SCWM/MFS_WT_DET called with warehouse order &1 |
| 354 | FM &1 called in retry mode |
| 355 | WT &1 is a product warehouse task, cannot be sent |
| 356 | No storage bin found for HU &1; HU stays at CP &2 |
| 357 | Telegram &1 was sent. Retry: &2 |
| 358 | Resource &1 is blocked with HU &2; check next HU |
| 359 | Telegram repetition could not be scheduled |
| 360 | HU &1 does not exist anymore; data inconsistency |
| 361 | Warehouse order &1 already exists for HU &2 |
| 362 | HU &1 will be transferred from storage bin &2 |
| 363 | Warehouse order could not be created for HU &1 |
| 364 | Move HU &1 to clarification bin &2 |
| 365 | WO for HU &1 to clarification bin &2 could not be created |
| 366 | Warehouse order &1 for stock transfer of HU &2 created |
| 367 | HU &1 depth &2 must be transferred before HU &3 depth &4 can be removed |
| 368 | No source storage bin transferred to BAdI /SCWM/EX_MFS_MD_REARR_HU |
| 369 | No stock transfer HU transferred to BAdI /SCWM/EX_MFS_MD_REARR_HU |
| 370 | BAdI implementation can only transfer stock of &1 HU but &2 HU transfered |
| 371 | Customer decided to select WO without using standard coding (&1) |
| 372 | No WO from previous BAdI transferred; stock transfer not possible |
| 373 | No WT from previous BAdI transferred; stock transfer not possible |
| 374 | Customer selected WO on his own; stock transfer done in standard coding |
| 375 | WO &1 should be processed but couldn't be found by system |
| 376 | WPT for stock transfer not maintained in warehouse &1 and PLC &2 |
| 377 | Error destination for resource &1 not maintained |
| 378 | Stock transfer could not be processed |
| 379 | BAdI didn't return next WO to be processed |
| 380 | No WT found; stock tranfer not possible |
| 381 | Start of stock transfer at &1 |
| 382 | End of stock transfer at &1 |
| 383 | Check necessity of future stock transfer |
| 384 | Warehouse order &1 will be checked for stock transfer |
| 385 | Check didn't find a need for stock transfer |
| 386 | BAdI decided to prevent telegram sending |
| 387 | Unable to set lock for CP group &1 HU &2 at CP &3 for aisle determination |
| 388 | WO &1 with status &2 can not be processed |
| 389 | No destination from aisle determination |
| 390 | Processing HU &1 |
| 391 | WT(s) of Warehouse order &1 were sent with telegram &2 |
| 392 | &1: Retry of incoming telegram(s) triggered based on telegram &2 |
| 393 | Open WT &1 exists for HU, but not for this aisle / level |
| 394 | WT &1 already exists for HU &2 and will be used for put away |
| 395 | &1: Periodic (custom) logic triggered in separate task |
| 396 | Bin depth of WT &1 changed from &2 to &3 |
| 397 | BAdI implementation (/SCWM/EX_MFS_PERIOD_ACT) led to an exception |
| 398 | Retry functionality for CP &1 not activated |
| 399 | All aisles and resources are long term blocked |
| 400 | No follow-up flag can be set only for scanner point |
| 401 | Resource &1 is idle; trigger stock transfer check |
| 402 | &1: trigger communication exception handling |
| 403 | Rough bin determination for HU &1 is called |
| 404 | No bin depth is maintained |
| 405 | Configuration issue during rough bin determination detected |
| 406 | BAdI for checking HU-Identification &1 is called |
| 407 | HU &1 does not exist in EWM - skip confirmation for this HU |
| 408 | Open WT &1 exists for HU, but is a product WT |
| 409 | Telegram is set to retry |
| 410 | Create and confirm WT to CP &1 &2 (storage bin &3) |
| 411 | Open WO &1 with activity area &2 exists |
| 412 | Open WT &1 with activity area &2 exists |
| 413 | Open HUMOVE entry with activity area &1 exists |
| 414 | No HUs returned by BAdI; no further processing necessary |
| 415 | No storage bin search possible due to missing configuration |
| 416 | No compatible section and bin type found |
| 417 | &1 telegram(s) without WT reference were deleted |
| 418 | Exception code &1 set in BAdI |
| 419 | Stock removal out of MFS controlled storage type |
| 420 | Resource &1 is blocked with exception code &2 |
| 421 | Realignment for HU &1 necessary (Moves: &2 / Max. moves &3) |
| 422 | Change of destination bin failed; stock transfer stopped |
| 423 | No realignment for HU &1 necessary (Moves: &2 / Max. moves &3) |
| 424 | Enqueue lock fails for communication point group &1 |
| 425 | &1 telegram(s) for HU &2 with status 'RETRY' are marked for deletion |
| 426 | &1 telegram(s) with status 'Marked for Deletion' were found |
| 427 | &1 telegram(s) with status 'Marked for Deletion' have reference to WT |
| 428 | &1 telegram(s) with WT reference were deleted |
| 429 | Delete outdated incoming telegrams (Whse &1, PLC &2, channel &3) |
| 430 | Telegram(s) marked for deletion found; trigger deletion |
| 431 | Telegram has been added to the buffer for outgoing telegrams |
| 432 | Open warehouse tasks exist for handling unit &1 |
| 433 | Root context ID &1 and connection ID &2 used |
| 434 | No WT created because no process type was determined - HU &1 is skipped |
| 435 | conf. to dest. of inactive WT &1, canceling WT and conf active WT instead |
| 436 | Host information not supported for the PLC's communication mode |
| 437 | Enter port information directly in the SAP router string |
| 439 | Warehouse order &1 cannot be processed in this context |
| 440 | The resource &1 is locked. |
| 441 | HU &1 is not at CP &2 &3 anymore; checking next HU |
| 442 | BAdI /SCWM/EX_MFS_WT_DET determined that resource can handle multiple WTs |
| 443 | &1: Triggering stop of communication channel &2 &3 |
| 444 | &1: Triggering start of communication channel &2 &3 |
| 445 | &1: Triggering restart of communication channel &2 &3 |
| 446 | Specify a destination for programmable logic controller &1 |
| 447 | Handle for TCP communication missing |
| 448 | Start of communication channel &1 &2 failed; asynchronous RFC issue |
| 449 | &1: HU &2 could not be locked, attempting to read WT |
| 450 | &1: WT was not found on database after failed lock on HU &2 |
| 451 | &1 superfluous jobs canceled |
| 452 | TCP/IP connection in wrong state (&1); stop triggered |
| 453 | Repeated attempt to stop TCP/IP connection failed |
| 454 | Host &1 and port &2 are used |
| 455 | Connection established |
| 456 | Variable byte code page &1 can lead to truncated or overlapping telegrams |
| 457 | Communication points for PLC &1 have been checked recently |
| 458 | Skipping check of communication points for PLC &1 |
| 459 | Checking all communication points for PLC &1 |
| 460 | Channel &1 is locked by another process |
| 461 | Error trying to start new task in server group &1 |
| 463 | Create follow-up warehouse task(s) to clarification bin |
| 464 | &1 Channel &2 was halted manually; no automatic restart |
| 465 | Rechecking selected CPs for PLC &1 that ended with errors |
| 466 | Rechecking communication point &1 PLC &2 warehouse &3 |
| 467 | Destination PLC &1 determined |
| 468 | Telegram string contains characters that can't be converted to binary |
| 469 | ICM not available. Channel &1 &2 cannot be restarted |
| 470 | Tare weight of the HU is set to zero |
| 471 | MFS integration is not supported |
| 480 | PLC and PLC Object combination is used &1; Combination must be unique |
| 481 | Enter the EWM object and PLC object |
| 500 | Maintain aisle and/or level |
| 501 | Maintain CP, PLC and Storage Type |
| 502 | Maintain Resource and Storage Type |
| 510 | Synchronization start telegram found in telegram buffer |