/SCMB/LDDD - Message Class for RC LDDD
The following messages are stored in message class /SCMB/LDDD: Message Class for RC LDDD.
It is part of development package /SCMB/LDDD in software component SCM-BAS-LDD. This development package consists of objects that can be grouped under "Lane, Distance, and Duration Determination".
It is part of development package /SCMB/LDDD in software component SCM-BAS-LDD. This development package consists of objects that can be grouped under "Lane, Distance, and Duration Determination".
Message Nr ▲ | Message Text |
---|---|
000 | Request &1: Incomplete request data - determination failed |
001 | Means of transport &1: define speeds |
002 | Means of transport &1: define distance factor |
003 | IGS call failed for at least 1 request |
004 | Distance and duration buffer updated (&1 entries) |
005 | Request &1: Distance could not be determined (MTr &2) |
006 | Request &1: Duration could not be determined (MTr &2) |
007 | Transportation lanes could not be determined for &1 &2 &3 |
008 | No TSP / carrier -specific data exists for &1 &2 &3 |
009 | Means of transport &1 does not exist or has errors |
010 | Location with GUID &1 does not exist |
011 | GIS call failed: No IGS available |
012 | &1 Distance and duration requests answered from buffer for strategy &2 |
013 | &1 Distance and duration requests answered by IGS calls |
014 | &1 Distance and duration requests answered with strategy &2 |
015 | Distance and duration buffering failed; no speed profiles available |
016 | Speed profile can not be created for means of transport &1 |
017 | Distance and duration buffer access failed |
018 | &1 IGS requests submitted |
019 | Distance and duration buffer: &1 entries deleted |
020 | Lane manager could not be initialized |
021 | Buffer could not be filled; inconsistent request data |
022 | Location data could not be read; MDL access failed |
023 | Location &1 is not geo-coded |
024 | Request &1: Distance and duration calculation failed |
025 | Error while starting DDD task &1; no free work process available |
026 | Error while starting DDD task &1; &2 |
027 | Error while receiving DDD task &1 result; &2 |
028 | Error while updating DDD buffer |
030 | Define a transportation zone hierarchy RELH_ZONE |
031 | Parallel processing failed |
040 | Internal error with request &1,&2,&3 |
041 | Request &1; determination option unknown |
050 | Request &1; no means of transport supplied |
051 | Request &1; no valid start location supplied |
052 | Request &1; no valid destination location supplied |
054 | GIS not enabled; determination option set to straight line calculation |
055 | Request &1; determination option set according to means of transport &2 |
056 | Request &1; determination option set to straight line calculation |
057 | Request &1; no transportation lane found (no start supplied) |
058 | Request &1; no transportation lane found (no destination supplied) |
059 | Request &1; no transportation lane found (no means of transport supplied) |
060 | Request &1; no transportation lane found (no time supplied) |
063 | Request &1; fallback strategy for distance and duration determinat. used |
064 | Fallback strategy for DDD used in total for &1 requests |
066 | |
067 | |
068 | |
069 | |
070 | |
071 | |
072 | |
073 | |
074 | |
075 | |
076 | |
077 | |
080 | ***** GEO CODING Messages *********************** |
081 | &1 detailed location geo coordinates updated |
082 | Geocoding failed: Location with GUID &1 does not exist |
083 | &1 unique standard determination answered &2 Geocoding requests |
086 | Access to geocoding level coordinates failed |
087 | No geocoding level coordinates for location &1 exist |
088 | Geocoding level coordinates incomplete or missing |
089 | Request &1: processing not possible; geocoordinates missing for loc &2 |
090 | No. of Successful Requests:&1 |
091 | No. of Failed Requests:&1 |
092 | Errors occured during geocoding simulation |
093 | Geocoding simulation was successful |
094 | Geocoding simulation for location &1 was not successful |
095 | Geocoding failed: insufficient input |
096 | Geocoding failed |
097 | Geocoding failed with Strategy &1 |
100 | Program &1: calculation error (overflow, and so on) |
102 | Region specific geocoordinates are not maintained in GEOT005s |
103 | Country/region-specific geocoordinates are not maintained in GEOT005 |
120 | ***** GEO ROUTING Messages *********************** |
121 | Georouting failed: incomplete request data |
122 | No valid Start Location supplied |
123 | No valid Destination Location supplied |
124 | No Means of Transport supplied for Georouting |
125 | Georouting failed with Strategy &1 |
126 | Georouting failed |
200 | Request &1: Strategy determination has failed; strategy &2 is being used |
201 | Request &1: Error when converting unit of measure |
202 | Request &1: Start location not buffered |
203 | Request &1: Destination location not buffered |
204 | Request &1: Means of transport &2 not buffered |
205 | Strategy Determination: Error when reading GIS zone assignments |
206 | Strategy Determination: Error when reading DDD strategy customizing |
207 | Error when determining parents of MTr &1 |
208 | Strategy Determination: No GIS zone assigments maintained |
209 | Strategy Determination: No DDD strategy Customizing maintained |
210 | Request &1: strategy determination has failed; GC level &2 is being used |
211 | DDD Strategy Customizing: straight line distance interval incomplete |
212 | DDD Strategy Customizing: different UoM for distance interval; &1 and &2 |
213 | DDD Strategy Customizing: entry is distance dependent and independent |
214 | Request &1: GC level &2 w/o strategy provided; GC level &3 is being used |
300 | GUID for location &1 could not be created |
301 | Error when accessing the test data container |
302 | Location &1 not buffered in variant &2 |
303 | Incorrect number of requests returned in variant &1 |
304 | Request &1 missing in variant &2 |
305 | Request &1 incorrect in variant &2 |
306 | Incorrect number of results returned in variant &1 |
307 | Result for request &1 missing in variant &2 |
308 | Result for request &1 incorrect in variant &2 |
309 | Return code for request &1 missing in variant &2 |
310 | Incorrect number of return codes returned in variant &1 |
311 | Variant &1 unknown |
312 | Return code for request &1 incorrect in variant &2 |
400 | You are not authorized to display the log |
401 | Error while displaying the log; contact technical support |
500 | &1 negative Transportation Lane Determination buffer entries created |
501 | No new negative Transportation Lane Determination buffer entries created |
502 | Change Notification Agent for Transportation Lane is not active |
503 | Negative Transportation Lane Determination buffer can not be used |
530 | ****Buffer Transfer Messages********************************* |
531 | RFC Destination &1: No buffer entries found in /SCMB/DDD_BUFFER |
532 | RFC Destination &1: No speedprofile entries found in /SAPAPO/TRSPEEDS |
533 | Unable to connect to &1. Contact your system administrator |
534 | No buffer entries exist in source system |
535 | Business Function: &1 is not active. Functionality is not available |
536 | Customizing setting for speedprofile usage is not activated |
537 | Error during application log creation. Contact your system administrator |
538 | Error during reading of speedprofile entries. Check customizing settings |
539 | RFC Destination &1: Speedprofile usage is not activated in source system |
540 | RFC Destination &1: Switch is not activated in source system |
541 | RFC Destination &1: Error during reading speedprofiles.Check Customizing |
542 | Total no. of transfered buffer entries: &1 |
543 | Number of newly-created buffer entries: &1 |
544 | Number of already exisiting buffer entries: &1 |
545 | No. of not updated buffer entries: &1 |
546 | No. of newly-created speedprofiles: &1 |
547 | No. of MTR with newly-created speedprofiles: &1 |
548 | No. of unknown speedprofiles: &1 |
549 | No MTR exist in current system. Buffer Transport is not possible. |
550 | Application log cannot be written |
551 | Application log entry cannot be created |
552 | Message could not be added to the application log |
553 | Error during ALV creation |
554 | Number of updated buffer entries: &1 |