LMD_ROUTE_HUB - Route Hub Messages
The following messages are stored in message class LMD_ROUTE_HUB: Route Hub Messages.
It is part of development package LMD_ROUTE_HUB in software component LE-LMD-RE. This development package consists of objects that can be grouped under "LMD Route Hub".
It is part of development package LMD_ROUTE_HUB in software component LE-LMD-RE. This development package consists of objects that can be grouped under "LMD Route Hub".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Route builder implem. class &1 does not exist. Select an existing class. |
| 001 | "build" method of route builder class &2 missing. Add a "build" method. |
| 002 | Route builder &1 could not recover desired data. Data is not available. |
| 003 | Exception occurred. Technical key missing in process step (&1). |
| 004 | Cannot register route status event handler for observer &1. |
| 008 | Please configure a mapping between route type and freight order type &1. |
| 009 | Please configure a builder sequence for route type &1. |
| 010 | Please configure at least one builder class name for builder sequence &1. |
| 011 | Please configure an action sequence for route type &1. |
| 012 | Route update for freight order &1 with this status is not supported. |
| 013 | Please configure a status mapping for route type &1. |
| 018 | Departure shipping point is missing. |
| 019 | Arrival shipping point is missing. |
| 020 | Driver "&1" does not exist. |
| 021 | Location "&1" does not exist. |
| 022 | Business partner "&1" does not exist. |
| 023 | Resource "&1" does not exist. |
| 024 | At least 1 transport item has no delivery or delivery item reference: &1. |
| 025 | An exception was raised during route builder processing. |
| 026 | Route creation for freight order &1 with this status is not supported. |
| 027 | Process "&1" could not be started due to the precondition. |
| 028 | Route &1 could not be processed due to missing authorization. |
| 029 | Message from "&1" was not processed, because it is outdated. |
| 030 | Route &1 was successfully prepared for assembling during creation. |
| 031 | Route &1 was successfully prepared for assembling during update. |
| 032 | Route &1 was successfully assembled. |
| 033 | Route &1 was successfully validated. |
| 034 | Route &1 was successfully withdrawn. |
| 035 | Route &1 was successfully canceled. |
| 036 | Execution was successfully triggered for route &1. |
| 037 | Route &1 was successfully saved. |
| 038 | The route has no stops. |
| 039 | Transport does not contain any item of type "Product". |
| 040 | Delivery &1 does not exist. |
| 041 | Sales order &1 does not exist. |
| 042 | Corresponding item of delivery &1 does not exist for transport item &2. |
| 044 | Distribution channel is missing for sales order &1. |
| 045 | Division is missing for sales order &1. |
| 046 | Sales organization is missing for sales order &1. |
| 047 | Ship-to party address ID is missing for delivery &1. |
| 048 | The route status is not unique. Route &1 cannot be settled. |
| 049 | Status &1 prevents route &2 from being settled. |
| 050 | The settlement process of route &1 has already started. |
| 051 | Route &2 has status &1. This does not reflect the real processing status. |
| 052 | Route &1 is currently locked. Please try again later. |
| 053 | Status &1 prevents route &2 from being deleted. |
| 054 | Deletion of route process could not be completed due to an error. |
| 055 | Route &1 and all dependent data were successfully deleted. |
| 056 | Settlement process has started. |
| 057 | Route &1 could not be deleted. For more information, check the log. |
| 058 | Process could not be restarted. |
| 059 | Process was successfully restarted. |
| 060 | Settlement of route &1 already started. Updates are no longer possible. |
| 061 | Route &1 has already been executed. Updates are no longer possible. |
| 062 | Route &1 is already completed. Updates are no longer possible. |
| 063 | BAdI for assembling extensions returned an error for route &1. |
| 064 | Mobile device data of route &1 was successfully saved in the back end. |
| 065 | Timeout occurred. Status of route &1 was set to Error. |
| 066 | Exception during route processing. Check ST22 or contact administrator. |
| 067 | Last retry of failed process failed. Status of route &1 was set to Error. |
| 068 | Manual settlement was enabled. |
| 069 | Manual settlement could not be enabled. |
| 070 | Manual settlement was reset. |
| 071 | Manual settlement could not be reset. |
| 072 | Resending of route was successfully triggered. |
| 073 | Resending of route could not be triggered. |
| 074 | Handover to settlement failed for route &1. |
| 075 | Route &1 received from mobile device was sent to settlement. |
| 076 | Manual route data entry could not be disabled. |
| 077 | Manual route data entry could not be enabled. |
| 078 | Route creation for freight order &1 without loading end is not supported. |
| 079 | Route update failed for route &1 |
| 080 | Mandatory parameter "&1" is missing. |
| 081 | Parameter "&1" must be greater or equal zero. |
| 082 | No address ID was found for location &1 of stop &2. |
| 083 | Route &1 is already in execution. Status cannot be set to "Open". |
| 084 | Delivery &1 is not completely processed. |
| 085 | Route was successfully canceled. |
| 086 | Route builder class &1 does not exist. Check configuration settings. |
| 100 | Settlement for stops has started. |
| 101 | Route with route UUID &1 was not found. |
| 102 | Departure location ID is missing. |
| 103 | Arrival location ID is missing. |
| 104 | Status of visit list &1 could not be updated. |
| 105 | Generic batch is different for route stock of plant &1 and plant &2. |
| 106 | Route &1 is already in execution. Only partial update is possible. |
| 107 | Status &1 prevents the intermediate settlement of route &2. |
| 108 | The route settlement status is still initial. Route &1 cannot be settled. |
| 109 | Batch management information in document item &1 was ignored. |
| 110 | Batch management information for product &2 was ignored. |
| 111 | Batch management information for document item &1 was corrected. |
| 112 | Batch management information for product &2 was corrected. |
| 113 | Status &1 prevents route &2 from being canceled. |
| 114 | Route &1 was successfully canceled. |
| 115 | Route cancellation failed. |
| 116 | Authorization missing |
| 117 | Delivery &1 was added to route &2 with status "In Execution". |
| 118 | Delivery &1 was removed from route &2 with status "In Execution". |
| 119 | Stop &1 has already been executed. Delivery &2 cannot be added. |
| 120 | Stop &1 has already been executed. Delivery &2 cannot be removed. |
| 121 | Delivery &1 was added again to route &2 with status "In Execution". |
| 122 | Delivery &1 was removed again from route &2 with status "In Execution". |
| 123 | Stop &1 was added to route &2 with status "In Execution". |
| 124 | Stop &1 was removed from route &2 with status "In Execution". |
| 125 | Stop &1 was not found in the assigned visit lists. |
| 126 | Delivery &1 could not be assigned to a visit. |
| 127 | Delivery &1 was already reassigned in Transportation Management. |
| 128 | New visit for referenced document &1 was added to route. |
| 129 | Document &1 was updated with the values of referenced document &1. |
| 130 | Stop &1 was already uploaded. No data was changed. |
| 131 | &1 stops were uploaded. &2 stops were expected for the route. |
| 132 | No. of uploaded stops (&1) less than no. of stops expected for route (&2) |
| 133 | Upload for route &1 is not complete. &2 stops were not uploaded. |
| 134 | Upload for route &1 is not complete. &2 stop was not uploaded. |