/SCMTMS/TAL
150 mensajes en esta área
Cada fila muestra el número de mensaje y el texto en inglés. Enlaces profundos con #msg-123.
| Mensaje | Texto del mensaje |
|---|---|
| 1 | Minimum value is greater than maximum value |
| 2 | Start date is after end date |
| 3 | Bucket type of carriers is different; only relative change is possible |
| 4 | Maximum value is lower than current value for one or several allocations |
| 5 | Maximum value is lower than minimum value; no changes are possible |
| 6 | Minimum value is lower than 0; value is set to 0 |
| 7 | Maximum value is lower than 0; value is set to 0 |
| 8 | Customizing for allocations cannot be read |
| 9 | Allocation could not be created; enter a carrier |
| 10 | Decimal values are rounded to integers when the unit of measure is "each" |
| 11 | Hierarchy inconsistency |
| 12 | Hierarchy check error |
| 13 | Allocations are not created if planning period or capacity is missing |
| 14 | Allocation &1 &2 &3 &4 already exists |
| 15 | Incorrect transp. orientation type; no allocations are created |
| 16 | Allocation could not be created; define a trade lane |
| 17 | Allocation &2 was not created; allocation &1 contains conflicting data |
| 20 | Business partner/supplier & does not exist |
| 21 | No valid source location/transportation zone was entered |
| 22 | No valid destination location/transportation zone was entered |
| 23 | No valid business partner/supplier was entered |
| 24 | No valid means of transport was entered |
| 25 | Change value is greater than maximum value |
| 26 | Allocation overbooked |
| 27 | Order &1 cannot be booked |
| 28 | Error during allocation update for order &1 |
| 29 | Validity date must cover a complete horizon (from/to must be filled) |
| 30 | Transp. lane from &1 to &2 and MTr &3; incompl. allocation data |
| 31 | No transportation lanes could be found based on selection criteria |
| 32 | Planning period '&' does not completely fit into the validity period |
| 33 | Allocation from &1 to &2 with MTr &3 and carrier &4 could not be created |
| 34 | Validity period is shorter than the chosen planning period |
| 35 | Specify a source transportation zone for orientation "O" ("Outbound") |
| 36 | Specify a destination transportation zone for orientation "I" ("Inbound") |
| 37 | Specify identical transportation zones for orientation "W" ("Within") |
| 38 | Number of periods &1 exceeds limit of &2; specify shorter range of dates |
| 40 | Values have been changed due to their unit of measure |
| 41 | Allocation type &1 is schedule-based; select a different allocation type |
| 42 | Too many combinations for allocations found; specify sel. criteria |
| 43 | Validity interval is too large; specify an interval smaller than 68 years |
| 45 | Unit of total quantity for &2 cannot be converted |
| 46 | You have to activate usage of allocations |
| 47 | You have to activate usage of allocations |
| 48 | &1 buckets deleted |
| 49 | Only A, F and O orientations are valid for lane reference |
| 50 | TRMID &1: bucket type does not fit to requested validity interval |
| 51 | Change of &1 violates bucket &2 of allocation &3 |
| 52 | Allocation &1: &2 buckets were updated with existing orders |
| 53 | Quantity aggregation postponed for &1 buckets |
| 54 | Carrier &1 has no capacity for &2 according to allocation &3 (&4) |
| 55 | Not all buckets could be generated for allocation &1 |
| 56 | Bucket &1 of allocation &2 has overwritten &3 existing bucket(s) |
| 57 | You have to activate usage of allocations |
| 58 | Allocation creation interrupted |
| 59 | Start time is after end time |
| 60 | Bucket has been created in the past |
| 61 | Sub-bucket rate must be between 0 and 100% |
| 62 | Sum of sub-bucket proportions has to be greater than zero |
| 63 | Process terminated due to failed locking |
| 64 | &1 trade lanes skipped; allocation checkbox on trade lanes not selected |
| 65 | Cannot determine allocation-relevant quantities for &1 |
| 66 | Allocation type &1 is not used for attributes |
| 67 | Specify the validity dates |
| 68 | Allocation &1 already exists for &2 |
| 69 | Error while generating allocation |
| 70 | Allocation &1 generated for &2 |
| 71 | Enter an allocation type for schedule type &1 |
| 72 | No matching carrier could be found; allocation not created |
| 73 | Allocation locked; your changes to &1 buckets will be applied later |
| 74 | Allocation locked; your changes to &1 allocations will be applied later |
| 76 | Enter a valid allocation ID; allocation ID &1 invalid |
| 77 | Enter a validity start date |
| 78 | Enter a validity end date |
| 79 | 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 |
Los textos se muestran como referencia técnica. SAP, SAP TM, SAP EWM, SAP GTS, SAP S/4HANA y otros nombres son marcas de SAP SE.