/SCMTMS/MSG - General Message for TMS
The following messages are stored in message class /SCMTMS/MSG: General Message for TMS.
It is part of development package /SCMTMS/CMN_DDIC in software component TM-CF. This development package consists of objects that can be grouped under "TM Common DDIC".
It is part of development package /SCMTMS/CMN_DDIC in software component TM-CF. This development package consists of objects that can be grouped under "TM Common DDIC".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Earliest start date must not be later than latest start date |
| 001 | Earliest end date must not be later than latest end date |
| 002 | Latest start date must not be later than earliest end date |
| 003 | Location &1 does not exist |
| 004 | Location &1 has another location type |
| 005 | &1 start date must not be later than end date |
| 006 | &1 &2 is not valid |
| 007 | &1 requested time period should be within acceptable time period |
| 008 | Pick-up date must be before delivery date |
| 009 | Location standard ID does not match location |
| 010 | Location standard ID does not exist |
| 011 | Location standard ID is missing |
| 012 | Location &1 (type: &2) does not exist |
| 013 | Loading period and delivery period must not overlap |
| 014 | Prefix: &1 |
| 015 | Unit of measure &1 is unknown |
| 016 | Unit of measure &1 and dimension &2 do not fit together |
| 017 | Business partner &1 (role: &2) does not exist |
| 018 | Business partner standard ID does not match party |
| 019 | Indicate an ID and a schema agency ID |
| 020 | &1 period and &2 period must not overlap |
| 021 | No key definition maintained for data type &1 |
| 022 | Product &1 does not exist |
| 023 | &1 quantity type code &2 incompatible with unit of measure &3 |
| 024 | &1 enter quantity type code, unit of measure, and value for quantity |
| 025 | Order of pick-up dates is incorrect |
| 026 | Order of delivery dates is incorrect |
| 027 | Order of acceptable dates is incorrect |
| 028 | Enter at least one date |
| 029 | Latest given pick-up date is later than earliest given delivery date |
| 030 | &1 quantity type code &2 does not exist in Customizing |
| 031 | External number ranges are not allowed |
| 032 | Quantity role code &1 and dimension &2 do not fit together |
| 033 | Fields with resource master data changed |
| 034 | &1 requested delivery date is in the past |
| 035 | &1 requested pick-up date is in the past |
| 036 | &1 accepted delivery date is in the past |
| 037 | &1 accepted pick-up date is in the past |
| 038 | &1 start date is in the past |
| 039 | &1 end date is in the past |
| 040 | Requested delivery dates are outside accepted delivery dates |
| 041 | Requested pick-up dates are outside accepted pick-up dates |
| 042 | &1 enter seal ID |
| 043 | &1 seal ID &2 not unique |
| 044 | Code &1 contains invalid characters (see long text) |
| 045 | No calculation of product quantities due to Customizing for the &1 |
| 046 | No calculation of product quantities as no suitable unit could be found |
| 047 | No location ID for Incoterm location &1 |
| 048 | Incoterm location ID mandatory for Incoterm &1 |
| 049 | Settings allow only one product per item |
| 050 | Executing party of &1 &2 is unknown |
| 051 | Shipper of &1 &2 is unknown |
| 052 | Ship-to party of &1 &2 is unknown |
| 053 | Container resource or container type &1 doesn't exist |
| 054 | Vehicle resource or vehicle type &1 doesn't exist |
| 055 | There is a duplicate for nature of cargo classification code &1 |
| 056 | Enter a value for nature of cargo classification code |
| 057 | Business object &1 could not be loaded; check if incomplete |
| 058 | There is more than one Incoterm location assigned to location ID &1 |
| 059 | Location &1 does not exist (Incoterm location) |
| 060 | Source location &1 does not exist |
| 061 | Destination location &1 does not exist |
| 062 | Gross volume of TU resource &1 is smaller than the sum of gross volumes |
| 063 | Gross weight of TU resource &1 is smaller than the sum of gross weights |
| 064 | Source zone &1 does not exist |
| 065 | Destination zone &1 does not exist |
| 066 | Quantity is missing for assigned TU resources &2 in item &1 |
| 067 | Quantity of assigned TU resource &2 greater than quantity of item &1 |
| 068 | Quantity is missing for assigned TU resources &2 in package &1 |
| 069 | Quantity of assigned TU resource &2 greater than quantity of package &1 |
| 070 | Quantity is missing for assigned item &2 in package &1 |
| 071 | Quantity of item &1 is lower than quantity sum of items assignd to packge |
| 072 | Quantity of package &1 is lower than quantity of items assigned to packge |
| 073 | Approval check could not be started, condition &1 is missing or inactive |
| 074 | Unblock action could not be executed due to the approval status '&1' |
| 075 | &1&2&3&4 |
| 076 | &1 &2: Service type maintained for unknown nature of cargo |
| 077 | &1 &2: Service type maintained for unknown nature of cargo on stage &3 |
| 078 | Business partner role Carrier does not exist for business partner &1 |
| 079 | Multiple entries for value &1 of field &2 are forbidden |
| 080 | Precondition for source location &1 already exists |
| 081 | Precondition for destination location &1 already exists |
| 082 | Precondition for source zone &1 already exists |
| 083 | Precondition for destination zone &1 already exists |
| 084 | Precondition for party &1 already exists |
| 085 | Unit of measure is missing for type code &1 with value &2 |
| 086 | Strategy &1 not available |
| 087 | Error during check of strategy &1 |
| 088 | Quantity type code is missing for quantity with value &1 |
| 089 | Amount role code is missing for amount with value &1 &2 |
| 090 | Currency is missing for amount role code &1 with value &2 |
| 091 | New location &1 created from address |
| 092 | Existing location &1 matches specified address attributes and was reused |
| 093 | Technical issue - &1 &2 is not valid |
| 094 | Business partner &1 does not exist |
| 095 | Only one transportation mode can be used as the default for stage type &1 |
| 096 | Sequence number &1 is already used |
| 097 | Sales organization &1 does not exist |
| 098 | Precondition cannot be maintained for party &1 in role &2 |
| 099 | Partner function &1 does not exist |
| 100 | External strategy is initial but external determination is activated |
| 101 | Precondition rule or condition &1 is invalid |
| 102 | Stage is never relevant for planning; category is &1 |
| 103 | &4 &3: Stage type sequence of seq. no. &1 and &2 is not allowed |
| 104 | Successor seq. &1 of sequence &2 for movement type &3 is not permitted |
| 105 | Stage type code &1 of stage &2 does not exist |
| 106 | Enter forwarding order type |
| 107 | Enter Incoterms |
| 108 | Enter partner determination profile |
| 109 | Air waybill prefix and check digit mandatory for IATA airline |
| 110 | Enter air waybill prefix |
| 111 | Only MTr of type ROAD allowed |
| 112 | Zone &1 does not exist |
| 113 | Driver &1 does not exist |
| 114 | No valid driver exists |
| 115 | Stage type &1 of category &2 cannot be used for sequence definition |
| 116 | Document type &1 type is invalid |
| 117 | Invalid value &1 in field &2 |
| 120 | Address of &1 was deleted; FWO cannot be saved without address |
| 121 | Code value '&1' contains invalid characters |
| 124 | Location &1 cannot be used; it is marked for deletion |
| 125 | &1: Location &2 cannot be used; it is marked for deletion |
| 140 | Currency of &1 differs from document currency |
| 150 | Instance of BO &1 with alternative key &2 already exists |
| 151 | You can select screened by LSP only for ACS status SPX or SCO |
| 168 | For mandatory attachment type &1 no attachments exist |
| 169 | Consolidation parameter of forwarding order and booking do not match |
| 200 | &1 and &2 have to be different |
| 201 | &1 missing |
| 202 | If field &1 is filled, field &2 has to be filled as well |
| 203 | If field &1 has the value &2, field &3 has to be filled |
| 204 | If field &1 has the value &2 only value &3 is not allowed for field &4 |
| 205 | Field &1, value &2, and field &3 must not be filled together |
| 206 | Only one item classification possible; classification &1 is filled |
| 207 | The value of field &1 has to be smaller than the value of field &2 |
| 251 | Instance '&3' of BO '&1' is locked by user '&2' |
| 252 | Document '&3 &1' is locked by user '&2' |
| 253 | Document '&2 &1' is already locked by yourself in another session |
| 254 | Document &1 is currently protected against changes |
| 400 | Start: Determination of Freight Agreement Fall Thru Steps |
| 401 | |
| 404 | End: Determination of Freight Agreement Fall Through Steps |
| 410 | Start: Fall Through Logic - Step 1 |
| 415 | End: Fall Through Logic - Step 1 |
| 416 | Start: Fall Through Logic - Step 2 |
| 420 | End: Fall Through Logic - Step 2 |
| 421 | Start: Fall Through Logic - Step 3 |
| 425 | End: Fall Through Logic - Step 3 |
| 426 | Start: Fall Through Logic - Step 4 |
| 430 | End: Fall Through Logic - Step 4 |
| 431 | Start: Fall Through Logic - Step 5 |
| 435 | End: Fall Through Logic - Step 5 |
| 436 | Start: Fall Through Logic - Step 6 |
| 440 | End: Fall Through Logic - Step 6 |
| 450 | Enter a unique sequence number in profile &1 |
| 451 | Entry invalid; self-referencing association in partn. func. in profile &1 |
| 452 | Same party role and source party role in profile &1 |
| 453 | Deletion of the profile may affect other settings in the system |
| 454 | Invalid entry; cannot enter source role for source type &1 in profile &2 |
| 455 | Enter partner function |
| 456 | Define partner func. &1 before assigning it as srce part. func in prof &2 |
| 457 | Cannot enter source role for partner function &1 in profile &2 |
| 458 | Enter business partner for partner function &1 |
| 459 | Business partner irrelevant for source type &1 for party role &2 |
| 460 | Invalid precondition in item &1; enter value from list or leave blank |
| 461 | Cannot specify shipping type &2 with item &1 for transportation mode &3 |
| 462 | Business partner &1 may not exist in the system |
| 463 | Maintain a relationship category for the source type &1 in profile &2 |
| 464 | Relationship category must be maintained only for source type &1 |
| 465 | Source role is mandatory for source type &1 |
| 470 | Business partner &1 cannot be used for partner function &2 (&3) |
| 471 | Business partner &1 is blocked |
| 472 | Business partner &1 is not released |
| 473 | Business partner &1 does not exist or is marked for archiving |
| 474 | Organizational Unit &1: No data maintained for business partner &2 |
| 475 | Specify an address for the one-time account business partner &1 |
| 476 | Enter number &1 in a correct format |
| 477 | No country/region code found for &1 |
| 501 | AWB type &1 not allowed for country/region of destination location &2 |
| 511 | Related FWO of locked Freight Unit or Transportation Unit &1 is &2 |
| 512 | Related HAWB of locked Freight Unit &1 is &2 |
| 525 | Check Actual Event Date of execution event &1 |
| 801 | &1 of &4 entries processed; &2 values for &3 components found |