/SCMTMS/TEND - Tendering Messages
The following messages are stored in message class /SCMTMS/TEND: Tendering Messages.
It is part of development package /SCMTMS/TENDERING in software component TM-FRM-FRT. This development package consists of objects that can be grouped under "Tendering Objects".
It is part of development package /SCMTMS/TENDERING in software component TM-FRM-FRT. This development package consists of objects that can be grouped under "Tendering Objects".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Assign tendering manager to tendering plan |
| 001 | User &1 not valid tendering manager |
| 002 | Query not possible; no Internet user maintained for user &1 |
| 003 | Rejection reason code missing in FQ &1 for freight RFQ &2 |
| 004 | Amount entered in FQ &1 for freight RFQ &2 less than 0 |
| 005 | Save failed; resolve errors before restarting report |
| 006 | &3: FQ &1 for freight RFQ &2 requires review by tendering manager |
| 007 | No carrier assigned to freight RFQ &1 |
| 008 | Address data not available or not valid for contact person &1 |
| 009 | Step &1 of &2 does not contain any carriers |
| 010 | General settings for tendering not maintained |
| 011 | Stop dates inconsistent or outside acceptable time frame |
| 012 | Amount entered in freight RFQ &1 of step &2 less than 0 |
| 013 | Carrier not specified |
| 014 | Error in tendering plan of &1; visibility profile &2 does not exist |
| 015 | User &1 not valid tendering manager |
| 016 | Assign tendering manager |
| 017 | Tendering for &1 started. To be published and saved. |
| 018 | Tendering restarted successfully due to changes to &1 |
| 019 | Tendering plan consistent |
| 020 | Tendering publication triggered for &1 |
| 021 | Tendering not published for &1 |
| 022 | Start step &1 of tendering process &2 of &3 |
| 023 | Freight RFQ &1 created |
| 024 | Start tendering failed for &1 |
| 025 | &1 not a valid carrier |
| 026 | Selection contains &1 road freight orders |
| 027 | &1 road freight orders selected to stop tendering |
| 028 | Tendering stopped successfully for &1 road freight orders |
| 029 | Tendering not stopped for &1 road freight orders |
| 030 | Restart of tendering failed; changes made to &1 |
| 031 | Restart and publication of tendering failed; changes made to &1 |
| 032 | Exception occured during evaluation of tendering conditions |
| 033 | &1 objects selected for start tendering |
| 034 | Tendering started successfully for &1 objects |
| 035 | Start tendering failed for &1 objects |
| 036 | Document &1: cannot subcontract as road freight order |
| 037 | No selection profile or road freight order specified |
| 038 | Tendering manager does not exist |
| 039 | &1: No subcontracting in status for tendering |
| 040 | &1&2&3&4 |
| 041 | Cannot convert currency &1 into currency &2 |
| 042 | Currency conversion of quoted price of FQ &1 in freight RFQ &2 failed |
| 043 | Tendering restarted successfully for &1 |
| 044 | Tendering restart failed for &1 |
| 045 | Tendering profile &1 already exists; choose different name |
| 046 | &1: Calculation of tendering exchange rates not possible |
| 047 | Tendering exchange rates calculated for &1 |
| 048 | Tendering profile &1 not found |
| 049 | Enter tendering process mode in all steps |
| 050 | Invalid process mode &1 |
| 051 | No authorization to display requested tendering profiles |
| 052 | Carrier &1 already assigned to &2; assignment could change |
| 053 | Price limit not calculated according to visibility profile settings |
| 054 | No authorization to display all data of tendering profile |
| 055 | Visibility setting &1 in freight RFQ &2 of step &3 invalid |
| 056 | Tendering profile &1 loaded successfully into tendering plan of &2 |
| 057 | Tendering profile &1 created and saved |
| 058 | Cannot create tendering profile &1 |
| 059 | Description of tendering profile missing |
| 060 | Cannot propose carrier for &1; no carrier settings in Customizing |
| 061 | Amount in step &1 less than 0 for &2 |
| 062 | Can accept just one FQ for &1 |
| 063 | Description missing in tendering profile |
| 064 | ID missing in tendering profile |
| 065 | Stop dates inconsistent in FQ &1 of freight RFQ &2 |
| 066 | Tendering type missing in step &1 |
| 067 | Invalid tendering type &1 in step &2 |
| 068 | Relative price limit in step &1 less than 0 for &2 |
| 069 | Maximum response time in step &1 must be greater than 0 for &2 |
| 070 | Tendering profile &1 already exists |
| 071 | Step &2: tendering visibility setting &1 does not exist |
| 072 | Enter currency code in FQ &1 of freight RFQ &2 |
| 073 | Carrier assignment not possible from &1; carrier missing |
| 074 | &1 not a valid contact person |
| 075 | Select a valid maximum response time in step &1 |
| 076 | Select a valid maximum response time in freight RFQ &1 |
| 077 | Select a valid total price limit in freight RFQ &1 |
| 078 | No valid contact persons specified for carrier &1 |
| 079 | Select a valid total price limit in step &1 |
| 080 | No carriers retrieved from ranking list for &1 |
| 081 | Proposed carriers added to step &1 of tendering plan for &2 |
| 082 | Enter a tendering type for step &1 of &2 |
| 083 | Tendering type &1 invalid for step &2 of &3 |
| 084 | &2: maximum response time reached for freight RFQ &1 |
| 085 | Sending of e-mails triggered successfully |
| 086 | Tendering profile &1 already exists |
| 087 | Max. resp. duration limited to max. value specified in general settings |
| 088 | Max. response time in freight RFQ &1 of step &2 must be greater than 0 |
| 089 | Tendering plan inconsistent for &1 |
| 090 | Cannot retrieve carrier information from transportation lane of &1 |
| 091 | Tender request KEY &1 of tender request &2: stop date group is initial |
| 092 | FQ &1 of freight RFQ &2 inconsistent |
| 093 | Automatic restart of tendering for &1 after cancellation not possible |
| 094 | Max. resp. time in freight RFQ &1 of step &2 of tend. profile less than 0 |
| 095 | Visiblitity settings not determined for step KEY &1 of step &2 |
| 096 | &3: evaluation result is &4 for FQ &1 of freight RFQ &2 |
| 097 | Tendering type missing in step &1 of tendering profile |
| 098 | Tendering type &1 in step &2 of tendering profile invalid |
| 099 | Cannot retrieve default tendering manager from Customizing |
| 100 | Tendering process mode &1 not valid |
| 101 | Carrier not maintained in freight RFQ &1 of step &2 |
| 102 | &1: FQ &2 for freight RFQ &3 contains an invalid stop date |
| 103 | &1: deviating stop date in FQ &2 for freight RFQ &3 |
| 104 | Visibility setting &1 does not exist |
| 105 | Cannot retrieve default visibility settings from Customizing |
| 106 | &1: start evaluation for FQ &2 of freight RFQ &3 |
| 107 | Relative price limit in step &1 of tendering profile is less than 0 |
| 108 | Amount entered in FQ &1 for freight RFQ &2 of &3 is less than 0 |
| 109 | Rejection reason code missing in FQ &1 for freight RFQ &2 of &3 |
| 110 | Rejection reason code &1 in FQ &2 for freight RFQ &3 is invalid |
| 111 | Visibility setting &1 in step &2 us invalid |
| 112 | Carrier assignment strategy not specified in step &1 |
| 113 | Carrier assignment strategy &1 specified in step &2 invalid |
| 114 | Request visibility settings inconsistent in step &1 of &2 |
| 115 | Response code &1 not allowed in FQ &2 for freight RFQ &3 of &4 |
| 116 | Profile &1 determined for tendering plan of &2 |
| 117 | Tendering stopped for &1 |
| 118 | Tendering for &1 requires review by tendering manager |
| 119 | Tendering successful; carrier awarded |
| 120 | All FQs for &1 rejected by tendering manager |
| 121 | No acceptable result for tendering for &1 |
| 122 | Invalid node &1 for "Set Consistency Status" |
| 123 | Cannot send alerts for unsuccessful tendering processes |
| 124 | No freight RFQ assigned to tendering step &1 |
| 125 | No steps specified in tendering plan for &1 |
| 126 | No active tendering process for subcontracting &1 |
| 127 | Visibility setting &1 of freight RFQ &2 of tendering profile not valid |
| 128 | Tendering plan &1 of &2 copied successfully |
| 129 | Carrier information for &1 updated successfully from tendering execution |
| 130 | Cannot update carrier information for &1 from tendering execution |
| 131 | Submitted price in &1 updated successfully from tendering execution |
| 132 | Cannot update amount information for &1 from tendering execution |
| 133 | Stop information for &1 updated successfully from tendering execution |
| 134 | Cannot update stop information for &1 from tendering execution |
| 135 | No valid default tendering profile created in general settings |
| 136 | Carrier assignment strategy missing in step &1 of tendering profile |
| 137 | Carrier assignment strategy &1 in step &2 of tendering profile invalid |
| 138 | Visibility setting &1 in step &2 of tendering profile not valid |
| 139 | Visib. settings for freight RFQs in step &1 of tend.profile inconsist. |
| 140 | Max. response time in step &1 of tend. profile must be greater than 0 |
| 141 | Road freight order &1 locked in another process |
| 142 | Carrier not selected in freight RFQ &1 of step &2 of tendering profile |
| 143 | Tendering profile inconsistent |
| 144 | Profile key not found for &1 |
| 145 | Tendering process sequence number &1 not valid |
| 146 | Tendering process result &1 not valid |
| 147 | Tendering for &1 step &2 carrier &3: cannot propose price limit |
| 148 | Tendering for &1 step &2 carrier &3: proposed price limit &4 |
| 149 | Stop tendering failed for &1 |
| 150 | Error in tendering for &1: cannot restore original carrier assignment |
| 151 | Error in tendering for &1: cannot restore original submitted price |
| 152 | Error in tendering for &1: cannot restore original stop information |
| 153 | Error in tendering for &1: original carrier assignment restored |
| 154 | Error in tendering for &1: original submitted price restored |
| 155 | Error in tendering for &1: original stop information restored |
| 156 | No STOP text maintained |
| 157 | Cannot read STOP text &1 |
| 158 | STOP text &1 read with default language; no text exists for language &2 |
| 159 | No text selected for sent freight RFQ |
| 160 | Send tender request text could not be read |
| 161 | Send request text read with default language; no text exists for lang. &2 |
| 162 | Freight RFQ &1 of &2 accepted successfully |
| 163 | Freight RFQ &1 of &2 rejected successfully |
| 164 | Cannot create FQ for freight RFQ &1 of &2 |
| 165 | FQ &1 for freight RFQ &2 of &3 sent successully |
| 166 | Cannot send FQ &1 for freight RFQ &2 of &3 |
| 167 | Tendering process stopped; changes made to &1 |
| 168 | Freight quotation &1 for freight RFQ &2 consistent |
| 169 | Action not allowed for selected objects |
| 170 | Action not allowed for some of selected objects |
| 171 | Condition for tendering settings determination missing for FO type &1 |
| 172 | No default communication settings selected in Customizing for tendering |
| 173 | No default process settings selected in Customizing for tendering |
| 174 | No tendering settings selected in Customizing for document type &1 |
| 175 | Tend. settings not found using condition specified for document type &1 |
| 176 | Define at least one freight RFQ for step &1 in tendering process for &2 |
| 177 | Action not allowed for &1 &2 |
| 178 | Cannot create freight quotation for freight RFQ key &1 |
| 179 | FQ for freight RFQ &1 of &2 already exists in status "Draft" |
| 180 | Freight order &1 is of type &2 |
| 181 | Process settings for freight order type &1: |
| 182 | Parameter &1 = &2 |
| 183 | ---------------------------------------------- |
| 184 | Default communication settings &1 |
| 185 | Default process settings: &1 |
| 186 | Attempting to evaluate condition &1 |
| 187 | Cannot evaluate condition &1 |
| 188 | Communication settings from condition &1: &2 |
| 189 | Process settings from condition &1: &2 |
| 190 | Effective process settings for &1: |
| 191 | Cannot determine document currency of &1 |
| 192 | Default tendering profile not maintained in process settings &1 |
| 193 | No e-mails sent |
| 194 | Carrier &1 already exists in the same tendering step |
| 195 | Price limit currency not specified in step &1 of tendering process for &2 |
| 196 | Cannot convert price limit currency &1 into document currency &2 |
| 197 | Invalid price limit currency &1 in step &2 of tendering process for &3 |
| 198 | Invalid currency &1 in freight quotation &2 of freight RFQ &3 |
| 199 | Sending of e-mails failed |
| 200 | Creation of B2B message &1 for tendering request key &2 failed |
| 201 | Cannot determine your business system; check your system landscape |
| 202 | Creation of message &1 for freight RFQ &2 failed |
| 203 | Message &1 for freight RFQ &2 created successfully |
| 204 | Enter name for profile |
| 205 | Tendering for &1 step &2: cannot propose price limit |
| 206 | Tendering for &1 step &2: proposed price limit &3 |
| 207 | Customizing for tendering contains errors |
| 208 | No e-mail text object defined in tend. Customizing for sent freight RFQs |
| 209 | No e-mail text obj. defined in tend. Customizing for sending freight RFQs |
| 210 | No e-mail text obj. defined in tendering Customizing for cancelled tend. |
| 211 | No e-mail text object defined in tendering Customizing for awarded FQs |
| 212 | No e-mail text object defined in tendering Customizing for rejected FQs. |
| 213 | No e-mail text object defined in tend. Customizing for freight RFQ info. |
| 214 | No e-mail text object defined in tendering Customizing for tend. info. |
| 215 | No e-mail text object defined in tendering Customizing for FQ info. |
| 216 | No e-mail text object defined in tendering Customizing for subject field |
| 217 | No contact persons selected for carrier &1; cannot send e-mail |
| 218 | Doc. for e-mail text &1 not available in requested or default language |
| 219 | Default communication language not selected in Customizing for tendering |
| 220 | Error while processing e-mail: &1 |
| 221 | Sender determ. failed for freight RFQ &1; check inb. user in Customizing |
| 222 | E-mail for sent freight RFQs sent to contact person &1 |
| 223 | E-mail for tendering cancellation sent to contact person &1 |
| 224 | E-mail for awarded FQ sent to contact person &1 |
| 225 | E-mail for rejected FQ sent to contact person &1 |
| 226 | Freight RFQ &1 sent by e-mail to contact person &2 |
| 227 | TAN incorrect for freight RFQ &1; cannot create FQ |
| 228 | Cannot retrieve document &1 in language &2 |
| 229 | Cannot retrieve text symbols for document &1 in language &2 |
| 230 | Cell phone not maintained for SMS recipient &1 |
| 231 | No SMS text object defined in tendering Customizing for sent freight RFQs |
| 232 | No SMS text obj. defined in tend. Customizing for sending freight RFQs |
| 233 | No SMS text obj. defined in tendering Customizing for cancelled tend. |
| 234 | No SMS text object defined in tendering Customizing for awarded FQ |
| 235 | No SMS text object defined in tendering Customizing for rejected FQ. |
| 236 | Road freight order &1: Only active tendering processes can be stopped |
| 237 | Error notification sent to recipient &1 |
| 238 | Default ctry/reg for formatting not selected in Customizing for tendering |
| 239 | Default time zone for formatting not selected in tendering Customizing |
| 240 | SMS for sent freight RFQs sent to contact person &1 |
| 241 | SMS for tendering cancellation sent to contact person &1 |
| 242 | SMS for awarded freight quotation sent to contact person &1 |
| 243 | SMS for rejected freight quotation sent to contact person &1 |
| 244 | Freight RFQ &1 sent by SMS to contact person &2 |
| 245 | FO &1 already in a tendering process or cannot be subcontracted |
| 246 | You are not authorized to execute this action for the tendering profile |
| 247 | You are not authorized to create a tendering profile |
| 248 | You are not authorized to edit this tendering profile |
| 249 | You are not authorized to delete this tendering profile |
| 250 | Customizing error: No keyword with text &1 exists for tend. process &2 |
| 251 | No valid freight RFQ number provided in e-mail &1 |
| 252 | E-mail &1 does not contain required keyword &2 |
| 253 | Invalid value &1 for keyword &2 in e-mail &3 |
| 254 | Invalid acceptance code &1 in e-mail &2 |
| 255 | Keyword values not defined for "Yes" and "No" in Cstmzng for tend. &1 |
| 256 | Fatal error while determining contact persons |
| 257 | Sender &1 not valid contact person for freight RFQ &2 |
| 258 | Processing of e-mail inbox finished; check application log |
| 259 | Process mode not selected |
| 260 | Maximum response duration must be greater than 0 |
| 261 | No freight RFQ number range interval selected in tendering Customizing |
| 262 | Freight RFQ number range interval &1 |
| 263 | Requested tendering profile not found |
| 264 | Document &1 cannot be locked |
| 265 | Maximum response duration cannot be greater than &1 hours. |
| 266 | Valid range for relative price limit is 0% to 999% |
| 267 | No maximum response duration entered in freight RFQ &1 of step &2 |
| 268 | Tendering profile must contain at least one step |
| 269 | Tendering profile contains errors |
| 270 | Tendering profile consistent |
| 271 | Conversion error; number too high |
| 272 | Stop dates cannot be in the past &1 |
| 273 | Enter rejection reason with no spaces or special characters |
| 274 | Rejection reason cannot be initial |
| 275 | You can only award one FQ for each tendering process |
| 276 | Item missing |
| 277 | Plan Setup Mode &1 not valid |
| 278 | Currency required at step &1 if carriers are to be able to submit a price |
| 279 | Award not possible for FQ &1 of freight RFQ &2 |
| 280 | Parallel processing profile &1 does not exist |
| 281 | Tendering process settings &1 do not exist |
| 282 | Tendering communication settings &1 do not exist |
| 283 | Visibility settings &1 request price, but type &2 not enabled for charges |
| 284 | Process settings &1 request calc., but type &2 not enabled for charges |
| 285 | Visibility sett. &1 request new price, but type &2 not enabled for settl. |
| 286 | Price limit not calculated; document not enabled for charge calculation |
| 287 | Price limit not calculated; no default carrier maintained |
| 288 | Changes to the charge hierarchy are not allowed and are therefore ignored |
| 289 | Enter dates and times for the specified stops &1 |
| 290 | Save changes before executing a tendering or subcontracting action |
| 291 | Creation of quotation for RFQ &1 failed; internal inconsistency |
| 292 | Cannot determine communication system for communication scenario &1 |
| 293 | Bus. system &1 from TM system differs from bus. system of com. system &2 |
| 294 | Logical system is missing in communication system &1 |
| 300 | Logical system &1 unknown |
| 301 | Freight RFQ &1 does not exist |
| 302 | Cannot read freight RFQ &1 |
| 303 | Cannot create freight quotation for freight RFQ &1 |
| 304 | Freight RFQ not provided in message |
| 305 | Road freight order not provided in message |
| 306 | Road freight order &1 does not exist |
| 307 | Cannot read road freight order &1 |
| 308 | Cannot confirm road freight order &1 |
| 309 | Content of message &1 causes conflicting updates |
| 310 | Invalid successor reference in shipment confirmation message |
| 311 | Shipment BTD ID not provided in shipment confirmation message |
| 312 | Successor reference in shipment confirmation has invalid type code &1 |
| 313 | Base BTD reference type code &1 is invalid. Type code 1122 is required |
| 314 | Freight RFQ &1 does not exist |
| 315 | Cannot create freight quotation for freight RFQ &1 |
| 316 | Invalid acceptance status code &1 |
| 317 | Start evaluation of &1 freight quotations |
| 318 | Element &1 must not be specified in combination with stages information |
| 319 | Base BTD version &1 does not exist for road freight order &2 |
| 320 | Confirmation relates to an outdated version of freight order &1 |
| 321 | Confirmation cannot be related to freight order &1 without a version ID |
| 322 | Freight booking not provided in message |
| 323 | Freight booking &1 does not exist |
| 324 | Confirmation relates to an outdated version of freight booking &1 |
| 325 | Base BTD version &1 does not exist for freight booking &2 |
| 326 | Confirmation cannot be related to freight booking &1 without a version ID |
| 327 | Cannot confirm freight booking &1 |
| 328 | Freight booking type '&1' does not exist |
| 329 | Adding new carrier not possible due to internal error |
| 330 | Adding new step not possible due to internal error |
| 331 | Action not possible due to internal error |
| 332 | Loading tendering profile not possible due to internal error |
| 333 | Base BTD reference of message &1 is incomplete |
| 334 | Business document with base BTD ID &1 and type code &2 already exists |
| 335 | More than one business doc. with base BTD ID &1 and type code &2 exists |
| 336 | Creation of quotation for RFQ &1 failed; charge item &2 miss. in message |
| 337 | Creation of quotation for RFQ &1 failed; charge elem. &2 miss. in message |
| 338 | Creation of quotation for RFQ &1 failed; charge elem. &2 does not exist |
| 339 | Creation of quotation for RFQ &1 failed; changes to charges not allowed |
| 340 | Cannot confirm document; sent data has already been changed |
| 341 | Creation of quotation for RFQ &1 failed; stage &2 does not exist |
| 342 | Stop dates inconsistent &1 |
| 343 | Award B2B-message can not be sent as FO &1 is incomplete. Award cancelled |
| 344 | Duplicate response sequence number &1 for Freight RFQ &2 |
| 345 | XML Tag '&1' is not supported; Message is rejected |
| 346 | Item category &1 is not supported |
| 347 | Cloud system supports only messages that replicate planned freight orders |
| 348 | Party role code &1 is not supported |
| 350 | Not possible to create external URL, alias &1 is not maintained |
| 351 | Not possible to create external URL |
| 352 | Creation of external URL is not possible; you must specify an alias |
| 353 | Cannot create URL with custom theme; SAP client not specified |
| 355 | SubmittedNetPriceAmount is allowed in direct tendering with price limit |
| 357 | Freight RFQ accepted and freight quotation submitted. |
| 358 | Freight RFQ rejected. |
| 401 | Error in ConfMsg: Element &1 of item &2 contradicts element on root level |
| 402 | Error in ConfMsg: Element &1 of item &2 contradicts element of item &3 |
| 403 | Error in ConfMsg: Time stamp conversion failed for root element &1 |
| 404 | Error in ConfMsg: Time stamp conversion failed for element &1 of item &2 |
| 405 | Error in ConfMsg: Time stamp conversion failed for element &1 |