/SCMTMS/TOR_INT - Messages from TOR related SOA msg processing (Integration)
The following messages are stored in message class /SCMTMS/TOR_INT: Messages from TOR related SOA msg processing (Integration).
It is part of development package /SCMTMS/TOR in software component TM-FRM-FRO. This development package consists of objects that can be grouped under "BO TOR".
It is part of development package /SCMTMS/TOR in software component TM-FRM-FRO. This development package consists of objects that can be grouped under "BO TOR".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Element &1 of message &2 has value &3 not defined in code list of GDT &4 |
| 002 | Element &1 of message &2 has value &3 not defined in Customizing table &4 |
| 003 | Element &1 of message &2 specifies a value &3 that is not supported. |
| 004 | Element &1 of message &2, node &3: Value &4 is not supported. |
| 005 | Element &1 of node &2 specifies a value &3 that is not supported |
| 006 | Internal error for message &1: Invalid combination of parameters &2 + &3 |
| 007 | Element &1 of message &2, node &3: Value &4 not defined in GDT code list |
| 008 | Element &1 of node &2 invalid: Val. &3 contradicts Customizing f. type &4 |
| 009 | Integrity fault at node &1 of message &2: Neither &3 nor &4 was specified |
| 010 | Message &1 node &2: No location matches the specified StandardIDs |
| 011 | Message &1 node &2: Location standard ID &3 from agency &4 does not exist |
| 012 | Business document with base BTD ID &1 and type code &2 does not exist |
| 013 | Element &1 of message &2, node &3: No location matches InternalID &4 |
| 014 | Element &1 of message &2, node &3: InternalID &4 overridden by StandardID |
| 015 | Internal ID &1 of sender party has more than 10 characters |
| 016 | Element &1 of node &2 invalid: Val. &3 contradicts Customizing f. mode &4 |
| 017 | Element &1 of message &2, node &3: Value &4 cannot be used in a booking |
| 018 | Element &1 of message &2: existing value &3 cannot be changed into &4 |
| 019 | Field &1 derived from elem. &2: curr. value &3 cannot be changed into &4 |
| 020 | Element &1 of node &2: value &3 is not feasible for category &4 |
| 021 | Message &1 node &2: Elements &3 and &4 must not be combined in same node |
| 022 | Message &1 node &2: Illegal attempt to change ExecutingCarrier &3 into &4 |
| 023 | Message &1 node &2: Illegal attempt to unassign ExecutingCarrier &3 |
| 024 | Message &1 node &2: Illegal attempt to change carrier &3 into &4 |
| 025 | Message &1 node &2: Illegal attempt to unassign carrier &3 |
| 026 | Default discrepancy type for subcategory &1 does not exist |
| 027 | Discrepancy is surplus quantity but actual quant. is less than planned |
| 028 | Discrepancy is insuff. quantity but actual quant. is more than planned |
| 029 | Discrepancy is missing cargo but actual quant. is more than 0 |
| 030 | Freight agreement with external ID &1 and version &2 do not exist |
| 031 | Freight agreement with external ID &1 does not exist |
| 032 | Freight agreement &1 with version &2 does not exist |
| 033 | Freight agreement &1 does not exist |
| 034 | Item &2 of freight agreement with external ID &1 does not exist |
| 035 | Item &2 of freight agreement &1 does not exist |
| 036 | Message &1: Item of item category &2 is missing |
| 037 | The version of requirement &1 in document &2 is outdated |
| 038 | Ready for Import Declaration not set on any selected customs group |
| 039 | Goods Receipt missing for items in at least one selected customs group |
| 040 | Ready for Import Declaration set for at least one selected customs group |
| 041 | Customs Group is not up to date (referenced item no longer exists) |
| 050 | More than one vehicle resource with same packag. material planned |
| 051 | Passive resources only allowed for frght. ord. &2; res. &1 not created |
| 052 | Delivery &1 does not belong to freight order &2 |
| 053 | ERP package does not belong to any vehicle resource |
| 054 | No packaging material defined for passive vehicle resource of &1, item &2 |
| 055 | No packaging material defined for container of freight order &1, item &2 |
| 056 | Item &1 cannot be added as new package |
| 057 | If &1 is specified both in node &2 and in &3 item, values must be equal |
| 058 | If &1 is specified more than once for location &2, values must be equal |
| 059 | Package material &1 is unknown in customizing of ERP shipment integration |
| 060 | No Package Material maintained for Active Vehicle Resource &1 |
| 061 | Package Item has neither a Package ID nor a Delivery Reference |
| 062 | Vehicle Item can't be determined (Item ID &1) |
| 063 | Package Material &1 not found |
| 081 | Freight booking to be confirmed could not be identified |
| 082 | Value &2 of element &1 and value &4 of element &3 are different |
| 101 | &1 is not a valid space allocation action code |
| 102 | &1 is not a valid space allocation advice code |
| 103 | The stage contains a space allocation advice code without an action code |
| 104 | Allotment cannot be empty |
| 105 | Node &1: &2 &3 and TypeCode &4 do not uniquely determine a TUR category |
| 106 | Document &1 is not in external number range &2-&3 |
| 150 | ************************** EWM Integration *************************** |
| 151 | EWM relevance does not match with EWM relevance of predecessor doc. &1 |
| 152 | Package hierarchy: Parent item ID &1 not found |
| 153 | Freight document &1 has no item with BTD item reference &2 |
| 154 | Delivery document &1 &2 &3 for delivery split is missing |
| 155 | Item &1 has different warehouse number than the other items |
| 156 | Goods issue has not yet been posted for delivery document &1 |
| 157 | Delivery document not found for BTD reference &1 &2 &3 |
| 158 | Unloading request has not been sent; location is not warehouse-relevant |
| 159 | Loading request has not been sent; location is not warehouse-relevant |
| 160 | (Un)loading request has not been sent; no relevant wareh. locations found |
| 161 | Freight document has no delivery reference |
| 162 | Freight doc. has references to inbound/outbound deliveries for stop &1 |
| 163 | Freight document has stops for multiple EWM warehouses |
| 164 | Trigger &1 has to be processed first |
| 165 | Length of Package Type Codes must not exceed four characters |
| 166 | Freight document can't be sent, package ID doesn't exist for package item |
| 167 | Document &1 cannot be found |
| 168 | One or more freight units or transportation units cannot be locked |
| 169 | More than one EWM-relevant stop in the freight document |
| 170 | Because of locking the Freight Unit was not assigned to the target object |
| 171 | Freight Unit not found for BTD reference &1 &2 &3 |
| 172 | Freight document has warehouse-relevant items (Adv. SR and not Adv. SR) |
| 200 | *********************** Field-/Completeness-Check *********************** |
| 201 | Booking is incomplete; specify Carrier Code |
| 202 | Booking is incomplete; specify MAWB Number |
| 203 | Booking is incomplete; specify Pieces Value &1 |
| 204 | Booking is incomplete; specify Pieces Unit &1 |
| 205 | Booking is incomplete; specify Gross Weight &1 |
| 206 | Booking is incomplete; specify Gross Weight Unit &1 |
| 207 | Booking is incomplete; specify Flight Number |
| 208 | Booking is incomplete; specify Airport of Departure |
| 209 | Booking is incomplete; specify Space Allocation Code |
| 210 | Booking is incomplete; specify Allotment ID |
| 211 | Booking is incomplete: Notes contain no entry for Special Service Request |
| 212 | Booking is incomplete: specify Airline Code in Carrier Routing |
| 213 | Booking is incomplete; specify ULD Type &1 |
| 214 | Booking is incomplete; specify ULD Count &1 |
| 215 | Booking is incomplete; specify ULD Weight &1 |
| 216 | Booking is incomplete; specify Airport of Arrival |
| 217 | Booking is incomplete; specify Date of Departure |
| 218 | Booking is incomplete; specify ULD Number &1 |
| 219 | Booking is incomplete; specify Airport of Arrival |
| 220 | Shipping Instruction is incomplete; specify Shipper |
| 221 | Shipping Instruction is incomplete; specify Ship-to Party |
| 222 | Shipping Instruction is incomplete; specify IATA Agent Code |
| 223 | Shipping Instruction is incomplete; specify Pieces Value &1 |
| 228 | Shipping Instruction is incomplete; specify Date of Arrival |
| 229 | Shipping Instruction is incomplete; specify MAWB Number |
| 230 | Shipping Instruction is incomplete; specify Airport of Departure |
| 231 | Shipping Instruction is incomplete; specify ULD Type &1 |
| 232 | Shipping Instruction is incomplete; specify ULD Count &1 |
| 233 | Shipping Instruction is incomplete; specify ULD Weight &1 |
| 234 | Shipping Instruction is incomplete; specify ULD Weight Unit &1 |
| 235 | Shipping Instruction is incomplete; specify Date of Departure |
| 236 | Shipping Instruction is incomplete; specify ULD Number &1 |
| 237 | Shipping Instruction is incomplete; specify Airport of Arrival |
| 238 | Shipping Instruction is incomplete; specify HAWB Number &1 |
| 239 | Shipping Instruction is incomplete; specify Consignment Rating Details |
| 240 | Shipping Instruction is incomplete; specify MAWB Issuing Date |
| 241 | Shipping Instruction is incomplete; specify Freight Term |
| 242 | Booking is incomplete: Notes contain no entry for Description of Goods |
| 243 | Booking is incomplete; specify Date of Arrival |
| 244 | Invalid UoM; use KG or LB for Gross Weight &1 |
| 245 | Invalid UoM; use a valid UoM (cm�, ft�, m�, in�) for Volume &1 |
| 246 | Booking is incomplete; items qty. is less than total booked qty. |
| 247 | Booking is incomplete; enter dimensions of loose cargo &1 |
| 248 | Invalid UoM; use valid UoM (cm, ft, m, in) for gross dimensions &1 |
| 249 | Items quantity exceeds total booked quantity. |
| 250 | Specify a maximum of 3 lines for Special Service Request |
| 251 | BP '&1': Name is limited to 35 characters in external EDI standard |
| 252 | BP '&1': Street is limited to 35 characters in external EDI standard |
| 254 | No of decimals for &1 exceeds the maximum of &2 &3 |
| 255 | Value for &1 exceeds the length of &2 &3 |
| 256 | Value for &1 exceeds the length of &2 &3 |
| 257 | Flight Number must have the correct format |
| 258 | Chargeable Weight must be numeric and a maximum of 7 digits |
| 259 | HAWB Number is limited to 12 characters in external EDI standard &1 |
| 260 | Freight Order is incomplete; specify Carrier |
| 261 | Freight Order is incomplete; specify Purchasing Organization |
| 262 | Completeness check executed without errors |
| 263 | Consignment order &1 is incomplete; specify carrier |
| 264 | Consignment order &1 is incomplete; specify purchasing organization |
| 299 | File content of Attachment folder must be specified |
| 300 | Stop for Loc. '&1' with Cat. '&2' is missing in Booking Conf. Message |
| 301 | *****A2A Freight Order Charges Update |
| 302 | Item and stage reference filled; charge item cannot be determined |
| 303 | Charge item not found for business partner &1 |
| 304 | Charge Item not found for item &1 |
| 305 | Charge Item not found for freight order &1 and business partner &2 |
| 306 | Charge item not found for stage &1 |
| 307 | Standard Charge element with line no &1 and type code &2 does not exist |
| 308 | Charge element &1 with resolution base &2 and charge type &3 not found |
| 309 | &1 texts exist for charge element &2; only one is allowed |
| 310 | Parent charge element with line no &1 does not exist |
| 311 | Calculation base &1 does not exist for charge element &2 |
| 312 | Non-numeric calculation base &1 in charge element &2 cannot be updated |
| 313 | Rate Currency missing for charge element &1 |
| 314 | Sender party is required in message header |
| 315 | Field 'Base Quantity' is not relevant for charge update (chrg. elmnt. &1) |
| 316 | Currency &1 in charge element &2 differs from document currency &3 |
| 317 | Recipient Party is missing or does not correspond to sender party |
| 318 | Purchase org (&1) for sender party differs from document &2 (&3) |
| 319 | No organizational unit assigned to business partner &1 |
| 320 | Calculation base update is not supported for new charge element &1 |
| 321 | Final Amount is mandatory for charge element &1 |
| 322 | The service interface does not support charge type &1 |
| 400 | ************************** Update Handler *************************** |
| 401 | Creation of package units not possible |
| 402 | &1 package units not created; preced. requirement stages already planned |
| 403 | For document &1 load plan of item &2 is not finalized |
| 404 | For document &1 the number of relevant requirement stages is less than 2 |
| 405 | For document &1 action is not possible; execution has already started |
| 406 | For document &1 and requirement &2 some stages have already been planned |
| 407 | Processing canceled; some documents couldn't be locked |
| 408 | Processing canceled; some requirement documents are already assigned |
| 409 | Processing canceled; data received is not valid |
| 410 | Processing canceled; versions of some requirement documents do not match |
| 411 | Creation of &1 is requested for item &2 |
| 412 | Creation of &1 can't be requested for item &2 |
| 413 | Doc. &1: No items relevant for cancellation or merging have been selected |
| 414 | Cancellation of &1 is requested for item &2 |
| 415 | Cancellation of &1 not possible; planning for other stages exists |
| 416 | Creation of &1 not possible; load plan of selected items is not finalized |
| 417 | &1 creation for item &2 not possible; &3 is not completely packed in pkgs |
| 418 | Cancellation of &1 not possible; &2 is missing in selection |
| 419 | &1 package units not created; no common preceding requirement stages |
| 420 | Goods movement for delivery &1 failed |
| 421 | Goods movement for delivery &1 successfully posted |
| 500 | *** Delivery Split Checks |
| 501 | Removal of &1 not allowed; EWM-based deliveries must not be split in TM |
| 502 | Removal of &1 not allowed; goods mvt status doesn't allow delivery split |