MPLAN - Messages for Maintenance Plan API
The following messages are stored in message class MPLAN: Messages for Maintenance Plan API.
It is part of development package MPLAN_API in software component PM-PRM-MP. This development package consists of objects that can be grouped under "Maintenance Plan API".
It is part of development package MPLAN_API in software component PM-PRM-MP. This development package consists of objects that can be grouped under "Maintenance Plan API".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Unknown error |
| 002 | The log could not be initialized |
| 003 | Save canceled by customer enhancement |
| 004 | Use date format YYYYMMDD for parameter & |
| 005 | Use time format HHMMSS for parameter & |
| 006 | Only use numbers for parameter & |
| 007 | Only use values I or E (not &2) for selection option &1 |
| 008 | Selection option &1: &2 cannot be interpreted |
| 009 | Enter at least one selection criteria |
| 010 | Cannot import memory ID & |
| 011 | Nothing was selected |
| 012 | & maintenance plans were selected |
| 013 | Enter a maintenance plan number |
| 014 | & maintenance items were selected |
| 015 | Maintenance item &1 does not exist in maintenance plan template &2 |
| 016 | Activity & not defined |
| 017 | Maintenance cycle &1 does not exist in maintenance plan template &2 |
| 018 | Specify an item number |
| 019 | Activity & not allowed |
| 020 | Cannot convert "&!" into a number |
| 021 | General parameter error: & & & & |
| 022 | The following messages concern maintenance plan & |
| 023 | The following messages concern maintenance item & |
| 024 | No value for field &1 -> the value &2 was inserted |
| 025 | Field & contains administrative data and is filled automatically |
| 026 | Field & cannot be filled -> value reset |
| 027 | Data was not checked before update |
| 028 | Long texts without a key are ignored |
| 029 | Long texts for item & cannot be assigned |
| 030 | Field &1 for reference object view: &2 not possible -> value reset |
| 031 | Stability studies are not supported |
| 032 | Entry possible in only one of the following fields: & & & |
| 033 | Maintenance plan and maintenance item require the same plan category |
| 034 | Authorization group &1 does not exist |
| 100 | The maintenance plan category cannot be changed |
| 101 | Multiple counter plan does not allow a strategy (overwrite value) |
| 102 | Cannot change from: & to: & is not possible |
| 103 | User name & is not valid (maintenance plan header) |
| 104 | "Last changed By" not allowed for newly created maintenance plan |
| 105 | Creator (user name) of a maintenance plan cannot be changed |
| 106 | User name & for last changer of maintenance plan header is invalid |
| 107 | Maintenance plan number changed from &1 to &2 |
| 108 | Cannot change the maintenance strategy of the maintenance plan |
| 109 | Maintenance strategy & sets a value for the parameter & |
| 110 | Specify maintenance plan header text |
| 111 | Specify maintenance plan category |
| 112 | The maintenance plan category cannot be changed |
| 113 | Reverse deactivation for maintenance plan & |
| 114 | Deletion flag for maintenance plan & reset |
| 115 | Administrative maintenance plan parameter & -> entry not considered |
| 116 | Scheduling type: & does not match maintenance strategy: & |
| 117 | Field &1 of maintenance plan &2 cannot be changed -> value reset |
| 118 | Maintenance plan & is already inactive |
| 119 | Maintenance plan & is already active |
| 120 | Maintenance strategy of maintenance item cannot be changed |
| 201 | Functional location &1 does not correspond with equipment &2 |
| 202 | Cannot read ILOA data &1 |
| 203 | Maintenance plan must have at least one maintenance item |
| 204 | Maintenance item & was transferred more than once |
| 205 | Value of maintenance plan item for maintenance item set from & to & |
| 206 | Maintenance plan cetagory & sets a value for parameter & |
| 207 | Maintenance strategy & transferred to maintenance item |
| 208 | Task list factor is 0 |
| 209 | User name & is not valid (maintenance plan item) |
| 210 | "Last Changed By" is not allowed for newly created maintenance item |
| 211 | You are not allowed to change the creator (user name) of a maint. item |
| 212 | User name & for last changer of maintenance item is invalid |
| 213 | Cannot delete new maintenance plans created by Wpos |
| 214 | Obligatory parameter & of maintenance item is not filled |
| 215 | Maintenance planning plant for the maintenance item is invalid |
| 216 | No autorization for transaction code: & category: & field: & |
| 217 | Creation of settlement rule not supported |
| 218 | Maintenance activity type & is not valid |
| 219 | Business area transferred from maintenance object |
| 220 | Cannot read table 399J |
| 221 | Change of order type in maintenance item & |
| 222 | Error when reading the equipment & |
| 223 | Error when reading functional location & |
| 224 | Error when determining controlling area & |
| 225 | Error when determining customer order: & item: & |
| 226 | Maintenance item & cannot be created again since it already exists |
| 227 | Error when reading the maintenance planning plant & |
| 228 | Error when reading notification type & |
| 229 | Error when checking physical sample & |
| 230 | Error when checking inspection plan parameters PLNTY: & PLNNR: & PLNAL: & |
| 231 | Error during authorization check for equipment / functional location |
| 232 | Existing data for maintenance item & is not available |
| 233 | Cannot process maintenance item without maintenance plan reference |
| 234 | Maintenance item was assigned to the maintenance plan |
| 235 | Invalid activity & -> maintenance item is ignored |
| 236 | Activity invalid for maintenance item -> Activity changed to create |
| 237 | Assignment of maintenance item to maintenance plan removed |
| 238 | Stability study only possible in connection with task list category Q |
| 239 | Material number or serial number is missing! |
| 240 | View of reference object & is not available |
| 241 | View of reference object & is not valid for maintenance items |
| 242 | Reference object for parameter(s) & & is not available |
| 243 | Value of parameter & is not permitted. Value & was inserted |
| 244 | No / invalid parameter value for stability study inspection type |
| 245 | System condition & not available -> value reset |
| 246 | Maintenance play category Service Procurement is not supported |
| 247 | Material number & is invalid -> value reset |
| 248 | Serial number & for material & is invalid -> both values reset |
| 249 | Item & is not assigned to a maintenance plan |
| 250 | Error when reading the work center: & |
| 251 | Selection by field name & is not supported for the maintenance item |
| 252 | For selection of the maint. plan category, MPTYP was replaced by MITYP |
| 254 | "&1" is not valid for maintenance plan category &2 - will be reset |
| 255 | "&1" is not valid for maintenance item category &2 - will be reset |
| 300 | More than one maintenance cycle was transferred with the same number |
| 301 | Maintenance plan &1 was already scheduled. Dimension change not possible |
| 302 | Activity invalid for maintenance cycle -> activity changed to create |
| 303 | Error during dimension comparison counter & and maintenance cycle unit & |
| 304 | Cycle & is not time-dependent and needs at least one counter |
| 305 | Counter plans that are not multiple can only contain max. one cycle |
| 306 | Maintenance plan must contain at least one cycle |
| 307 | Maintenance plan does not contain a unit for cycle & |
| 308 | Activity scheduling does not permit time-dependent counters (&1) |
| 309 | Cycle length of cycle & must be a multiple of one day |
| 310 | Offset length for cycle & must be a multiple of one day |
| 311 | Cycle & does not have a cycle or a offset |
| 312 | Cycle & is already scheduled. Changed plan date is ignored |
| 313 | Cycle & is already scheduled. Changed planned counter reading is ignored |
| 314 | Cycle & is not available. Cannot change/delete |
| 315 | Action & that is to be carried out for cycle & is not valid / recognized |
| 316 | Maintenance cycle & is already scheduled |
| 317 | Maintenance plan sorting & is not available |
| 318 | Error when reading the counter: & |
| 319 | Counter reading for counter & cannot be negative! |
| 320 | Check not possible: maintenance plan does not have key date schedule |
| 321 | Cycle set sequence of cycle & cannot be changed |
| 322 | Invalid maintenance cycle activity & -> cycle & is ignored |
| 323 | Maintenance cycle & does not have a counter |
| 324 | Time dimension of maintenance plan must be bigger than/equal to day |
| 325 | Entered factory calendar was ignored |
| 326 | Maintenance plan contains cycle with the number 00 |
| 327 | Maintenance plan does not contain a counter or a counter unit |
| 328 | Maintenance cycle & does not contain a counter or a counter unit |
| 329 | There are is no maintenance cycle data -> cannot change |
| 330 | Counter for maint. cycle & changed. Start counter reading not changed. |
| 331 | Varying recurrence rates for cycles in cycle set & |
| 332 | Specify a cycle number |
| 333 | A strategy plan cannot contain more than one cycle |
| 334 | Cannot delete strategy plan cycles |
| 335 | Time-based strategy plan does not allow maintenance cycles |
| 336 | Cycle for counter-based strategy plan requires a counter |
| 401 | Tests started |
| 402 | Single test |
| 403 | Mass test |
| 404 | Runtime &1 |
| 405 | Maintenance plan &1 not selected during mass selection |
| 406 | Number of entries is different: &1, &2 |
| 407 | Consistency checks |
| 408 | Difference in &1 (&2)(&3) |
| 409 | Internal error: DDIC structure & not found. |
| 410 | Check &1 |
| 411 | &1 &2 not selected during mass selection |
| 412 | Check maintence plan &1 |
| 413 | &1 &2 not selected when reading item |
| 414 | &1 &2 &3 &4 |
| 415 | Position &1 does not have any ILOA data |
| 416 | Enter a valid service contract item |
| 417 | Contract item &1 of contract &2 is not released or contains errors |
| 418 | The planned date is not within the service contract validity period |
| 419 | Enter a valid service order template |
| 420 | Service order template &1 is not released or contains errors |
| 421 | The planned date is not within the service order template validity period |
| 422 | Enter valid service contract and item |
| 424 | Enter a valid service template |
| 425 | Enter an order type |
| 501 | Maintenance plan &1: function &2 not executable - still without calls |
| 502 | Maintenance plan &1: enter cycle start for counter reading |
| 503 | Maintenance plan &1: inconsistency - call without history |
| 504 | Maintenance plan &1: only the following functions are allowed: &2 |
| 505 | No entry found in table MMPT for cycle set seq. &1 and rep. factor &2 |
| 506 | Setting &1 to &2 |
| 507 | Enter a call number |
| 508 | Specified call number &1 does not exist in maintenance plan &2 |
| 509 | Enter package counter: maintenance plan &1 |
| 510 | No entry for package &1 and strategy &2 found in T351X |
| 511 | Scheduling could not be executed: maintenance plan &1 |
| 512 | Maintenance plan &1: method &2 not executable - multiple counter plan |
| 513 | Maintenance plan &1 does not have a call number &2 |
| 514 | No entry in &1 found for &2 |
| 515 | Performance-based plans and multiple counter plans cannot be fixed |
| 516 | Enter the next planned date |
| 517 | Start of scheduling for maintenance plan &1 function &2 |
| 518 | Call number &1 is already skipped |
| 519 | Unit of measurement &1 not in table MMPT |
| 520 | Maintenance plan &1 - method &2 not executable - single cycle plan |
| 521 | Inconsistency - there are gaps in the sequence of call numbers |
| 522 | Maintenance plan &1 is time dependent; do not enter counter readings |
| 523 | See transaction IP03 for significance of both fields |
| 524 | Maintenance plan &1 call number &2 released |
| 525 | Maintenance plan &1 call number &2 fixed |
| 526 | Maintenance plan &1 call number &2 skipped |
| 527 | Maintenance plan &1 manual call number &2 added |
| 528 | Maintenance plan &1 call number &2 completed |
| 529 | Error when reading text for field &1 &2 |
| 530 | Counter reading entry not relevant for this maintenance plan category &1 |
| 531 | Time/date entry not relevant for this maintenance plan category &1 |
| 532 | Only the following fields are read for maintenance plan category &1: |
| 533 | &1 |
| 534 | Entries in other fields will be ignored |
| 550 | The fields of the call horizon (&1, &2, &3) are inconsistent |
| 551 | Field &1 is not supported |
| 552 | The multiple counter plan does not support a call horizon in days |
| 553 | You cannot deactivate business function LOG_EAM_CI_6 |
| 554 | A function of this BF is restricted in a distributed system landscape |
| 555 | Define the call horizon in percent |
| 556 | Maintenance item was added without object list &1 |
| 557 | Call &3 is outside of validity period of service contract item &1/&2 |
| 558 | Service contract item &1/&2 is not released |
| 559 | Call &2 is outside of validity period of service order template &1 |
| 560 | Service order template &1 is not released |
| 561 | The required order type is invalid |
| 562 | Service contract item &1/&2 does not exist |
| 563 | Service order template &1 does not exist |
| 564 | The service order is not saved for call &1 |
| 565 | Service order &1 is generated with errors for call &2 |
| 566 | Service order &1 is generated for call &2 |
| 567 | You are not allowed to access service contract &1 |
| 568 | You are not allowed to access service order template &1 |
| 569 | You are not allowed to create a service order |
| 570 | Start of scheduling for maintenance plan &1 - &2 |
| 571 | Screen has not been adjusted according to Service Planner authorization |
| 572 | Screen has not been adjusted according to Maint. Planner authorization |
| 573 | Enter either a technical object or a product |
| 574 | Technical object and Product cannot be filled at the same time |
| 575 | Product &1 is flagged for deletion |
| 576 | Product &1 is invalid |
| 577 | Enter a valid service contract |
| 578 | Maintenance Plan number is initial |
| 579 | Maintenance Item number is initial |
| 580 | A runtime error occurs BAdI CRMS4_MPLAN_SCHEDULING_MODIFY |