/SCMTMS/TAL - Transportation Allocations
The following messages are stored in message class /SCMTMS/TAL: Transportation Allocations.
It is part of development package /SCMTMS/TR_ALLOCATION in software component TM-PLN-TAL. This development package consists of objects that can be grouped under "BO Transportation Allocation".
It is part of development package /SCMTMS/TR_ALLOCATION in software component TM-PLN-TAL. This development package consists of objects that can be grouped under "BO Transportation Allocation".
Message Nr ▲ | Message Text |
---|---|
001 | Minimum value is greater than maximum value |
002 | Start date is after end date |
003 | Bucket type of carriers is different; only relative change is possible |
004 | Maximum value is lower than current value for one or several allocations |
005 | Maximum value is lower than minimum value; no changes are possible |
006 | Minimum value is lower than 0; value is set to 0 |
007 | Maximum value is lower than 0; value is set to 0 |
008 | Customizing for allocations cannot be read |
009 | Allocation could not be created; enter a carrier |
010 | Decimal values are rounded to integers when the unit of measure is "each" |
011 | Hierarchy inconsistency |
012 | Hierarchy check error |
013 | Allocations are not created if planning period or capacity is missing |
014 | Allocation &1 &2 &3 &4 already exists |
015 | Incorrect transp. orientation type; no allocations are created |
016 | Allocation could not be created; define a trade lane |
017 | Allocation &2 was not created; allocation &1 contains conflicting data |
020 | Business partner/supplier & does not exist |
021 | No valid source location/transportation zone was entered |
022 | No valid destination location/transportation zone was entered |
023 | No valid business partner/supplier was entered |
024 | No valid means of transport was entered |
025 | Change value is greater than maximum value |
026 | Allocation overbooked |
027 | Order &1 cannot be booked |
028 | Error during allocation update for order &1 |
029 | Validity date must cover a complete horizon (from/to must be filled) |
030 | Transp. lane from &1 to &2 and MTr &3; incompl. allocation data |
031 | No transportation lanes could be found based on selection criteria |
032 | Planning period '&' does not completely fit into the validity period |
033 | Allocation from &1 to &2 with MTr &3 and carrier &4 could not be created |
034 | Validity period is shorter than the chosen planning period |
035 | Specify a source transportation zone for orientation "O" ("Outbound") |
036 | Specify a destination transportation zone for orientation "I" ("Inbound") |
037 | Specify identical transportation zones for orientation "W" ("Within") |
038 | Number of periods &1 exceeds limit of &2; specify shorter range of dates |
040 | Values have been changed due to their unit of measure |
041 | Allocation type &1 is schedule-based; select a different allocation type |
042 | Too many combinations for allocations found; specify sel. criteria |
043 | Validity interval is too large; specify an interval smaller than 68 years |
045 | Unit of total quantity for &2 cannot be converted |
046 | You have to activate usage of allocations |
047 | You have to activate usage of allocations |
048 | &1 buckets deleted |
049 | Only A, F and O orientations are valid for lane reference |
050 | TRMID &1: bucket type does not fit to requested validity interval |
051 | Change of &1 violates bucket &2 of allocation &3 |
052 | Allocation &1: &2 buckets were updated with existing orders |
053 | Quantity aggregation postponed for &1 buckets |
054 | Carrier &1 has no capacity for &2 according to allocation &3 (&4) |
055 | Not all buckets could be generated for allocation &1 |
056 | Bucket &1 of allocation &2 has overwritten &3 existing bucket(s) |
057 | You have to activate usage of allocations |
058 | Allocation creation interrupted |
059 | Start time is after end time |
060 | Bucket has been created in the past |
061 | Sub-bucket rate must be between 0 and 100% |
062 | Sum of sub-bucket proportions has to be greater than zero |
063 | Process terminated due to failed locking |
064 | &1 trade lanes skipped; allocation checkbox on trade lanes not selected |
065 | Cannot determine allocation-relevant quantities for &1 |
066 | Allocation type &1 is not used for attributes |
067 | Specify the validity dates |
068 | Allocation &1 already exists for &2 |
069 | Error while generating allocation |
070 | Allocation &1 generated for &2 |
071 | Enter an allocation type for schedule type &1 |
072 | No matching carrier could be found; allocation not created |
073 | Allocation locked; your changes to &1 buckets will be applied later |
074 | Allocation locked; your changes to &1 allocations will be applied later |
076 | Enter a valid allocation ID; allocation ID &1 invalid |
077 | Enter a validity start date |
078 | Enter a validity end date |
079 | Deletion is not possible; departure referenced by bucket &1 exists |
100 | Transaction error; data cannot be saved |
101 | Missing parameter: &1 |
102 | No bucket of type &1 fits in the specified time interval |
103 | No valid trade lane found; no allocation created |
104 | No matching transportation lane found; no allocations created |
106 | Allocation roots processed |
107 | Processing buckets of allocation &1/&2 |
108 | Starting creation of allocations |
109 | Checking transportation lanes for allocation geographies |
110 | Bucket processing status: &1% |
111 | Unit &1 is not supported |
112 | Allocation import file could not be read |
113 | Error while parsing allocation import file |
114 | Bucket processing finished |
115 | Insufficient definition of parameters |
116 | Orientation "Along" cannot be used |
117 | Orientation "From" cannot be used |
118 | Orientation "Outbound" cannot be used |
119 | Orientation "To" cannot be used |
120 | Orientation "Inbound" cannot be used |
121 | Orientation "Within" cannot be used |
122 | Carrier &1 cannot be found |
123 | Invalid bucket type &1 |
124 | &1 buckets have been deleted |
125 | &1 buckets have been created |
126 | Corresponding allocations already exist |
127 | &1 successfully read |
128 | XML data has been parsed successfully |
129 | &1 allocations found in the upload file |
130 | &1 buckets found in the upload file |
131 | &1 allocations created |
132 | Allocation split: &1 allocations have been created |
133 | Bucket could not be added to allocation &1 |
134 | You cannot delete bucket &1 (&2); this would cause an allocation split |
135 | &1 allocations deleted |
136 | &1 buckets updated |
137 | &1 allocations updated |
139 | Could not create attributes for allocation &1; &2 and &3 are identical |
140 | &1 attributes created or changed |
141 | &1 attributes created |
142 | Invalid TAL type &1 |
143 | Error while parsing &1 in the allocation import file |
144 | Select one attribute |
145 | Attribute deleted |
150 | Details have been copied to &1 buckets |
151 | Details can only be shown for one entry; select just one |
152 | Details can only be copied from one entry; select just one |
155 | Allocation cannot be changed; business partner is blocked |
156 | Allocation cannot be created; business partner is blocked |
157 | Shipping type &1 does not exist |
158 | Contract basis &1 does not exist |
160 | ***********TAL Customizing*********************************************** |
161 | Default type already exists |
162 | Transportation mode &1 does not exist |
163 | Specify the unit of measure for carrier selection |
164 | You cannot use number range &1 for allocations |
165 | Number range object &1 is not valid; contact your system administrator |
200 | You are not authorized to use allocation &1 |
201 | You are not authorized to edit allocation &1 |
202 | You are not authorized to create allocation &1 |
203 | You are not authorized to delete allocation &1 |
300 | Allocation conversion report started in system &1, client &2 |
301 | Allocation &1 converted |
302 | Allocation &1 converted to new allocation &2 |
303 | &1 entries added to table &2 |
304 | Error in number range &1; allocation conversion report failed |
305 | &1: It is not possible to convert flight schedule-based allocations |
306 | Simulation mode; changes not saved |
307 | Allocation &1: &2 buckets converted |
308 | Allocation &1: &2 object references converted |
309 | Allocation &1, bucket from &2, dimension &3 not supported |
310 | &1: Allocation already exists with ID &2 |
311 | Allocation conversion report failed; changes could not be saved |
312 | Saving package &1 |
313 | Starting allocation conversion report for package &1 with &2 entries |
314 | Validity dates adjusted by the system; TAL buckets outside the validity |