IP - Messages for preventive maintenance
The following messages are stored in message class IP: Messages for preventive maintenance.
It is part of development package IPRM in software component PM-PRM-TL. This development package consists of objects that can be grouped under "Application Development R/3 Preventive Maintenance".
It is part of development package IPRM in software component PM-PRM-TL. This development package consists of objects that can be grouped under "Application Development R/3 Preventive Maintenance".
Message Nr ▲ | Message Text |
|---|---|
| 050 | Maintenance plan not classified |
| 051 | Changing the strategy will affect schedules of related maintenance plans. |
| 094 | Maintenance item & is locked |
| 095 | Maintenance item & locked by & |
| 096 | Maintenance item & is assigned to maintenance plan & |
| 097 | Maintenance plan & is locked |
| 098 | Maintenance plan & locked by & |
| 100 | Unit of measure & is not time-based |
| 101 | Unit of measure & is not performance-based |
| 102 | Unit does not have dimension & & |
| 103 | Unit of measurement & is not defined |
| 104 | Measuring point & is not a counter |
| 105 | Assign a counter that is not already assigned to a maintenance cycle |
| 106 | Unit & and counter unit & have different dimensions |
| 107 | You have not selected any cycles for deletion |
| 108 | Select a cycle first |
| 109 | Time-based cycle; enter counters only for performance-based cycles |
| 110 | The cycle length must be a multiple of one day |
| 111 | Offset will be recalculated from the planned counter reading |
| 112 | The maintenance plan only contains one maintenance item |
| 113 | The offset length must be a multiple of one day |
| 114 | Displaying counter info. is not possible with time-based maint. cycles |
| 115 | The maintenance plan already contains a time cycle |
| 116 | Maintain a measurement document for the counter |
| 117 | Maintain a counter for the maintenance cycle |
| 118 | Maintenance item is already allocated a task list |
| 119 | Specify a piece of equipment before creating an equipment task list |
| 120 | Specify a functional location before creating a FuncLoc task list |
| 121 | Remove functional location before creating an equipment task list |
| 122 | Next planned counter reading must be larger than total counter reading |
| 123 | Offset to next planned counter reading must be larger than 0 |
| 124 | Only counters that run forwards can be entered |
| 125 | Counter readings not possible for time-based maintenance cycles |
| 126 | Maintain either a cycle or an offset |
| 127 | Cycle entered after scheduling; specify relevant dates |
| 128 | Only values without post-decimal places are allowed |
| 129 | Multiple counter plans cannot be calculated |
| 130 | No maintenance plan costing |
| 131 | Indicate a time unit for the call interval |
| 132 | The chosen time unit & is not time-dependent |
| 133 | No line selected; select a line |
| 134 | Status "Inactive" set for maintenance plan & |
| 135 | Status "Deletion flag" set for maintenance plan & |
| 136 | Only 'order' call object permitted for maint. plan cat. with contract |
| 137 | Maintenance plan not adapted by resetting of date of acceptance |
| 138 | Maintenance plan not adapted by resetting of technical completion |
| 139 | Maintenance plan not adapted by resetting of notification completion |
| 140 | No unit is defined for 'DAY' |
| 141 | An error has occurred during editing of the maintenance plan |
| 142 | Status "Deletion indicator" set for maintenance plan & |
| 143 | The cycle length must be one month or a multiple of one month |
| 144 | Enter a catalog profile for the maintenance plan category |
| 146 | &1 is not a valid origin; enter a valid one |
| 147 | Completion Data indicator is not supported for Service order call object |
| 148 | Outl. Agreement indicator is not supported for Service order call object |
| 149 | For Maint. Plan cat. Service Order the Ref.object O100 can be set only |
| 150 | *--------------Maintenance plan costing (RISTRA40) |
| 151 | No maintenance plan costing has been performed |
| 152 | This report can only be executed in the background |
| 153 | No error log exists |
| 154 | Error when saving error log |
| 155 | No maintenance plans were selected |
| 156 | An error occurred when calculating maintenance plan &1 |
| 157 | Package &1 is no longer used in item &3 of plan &2 |
| 158 | Costing for Maintenance Plan &1 |
| 159 | Order Simulation for Maintenance Item &1 Incorrect |
| 160 | Maintenance plan of Service Order category is not available in SAP GUI |
| 161 | You are not allowed to schedule maintenance plans for service order |
| 162 | You are only allowed to schedule maintenance plans for service order |
| 164 | Maintenance Item of Service Order category is not available in SAP GUI |
| 166 | |
| 200 | Maintenance plan & created |
| 201 | Maintenance plan & changed |
| 202 | Maintenance plan & scheduled |
| 203 | Scheduling data changed for maintenance plan & |
| 204 | Start of scheduling for maintenance plan & |
| 210 | Maintenance item & created |
| 211 | Maintenance item & changed |
| 212 | Maintenance item & deleted |
| 213 | Maintenance plan & created with maintenance item(s) |
| 214 | Maintenance plan & changed with maintenance item(s) |
| 215 | No changes were made |
| 216 | Select only one cycle |
| 217 | Maintenance cycle changed - restart maintenance plan |
| 300 | *-------------Maintenance Plan/Item (SAPMIPM0)-----------------------* |
| 302 | Enter a maintenance plan |
| 303 | Enter a maintenance item |
| 304 | Maintenance plan category & not available |
| 305 | Field &1 is not relevant for service order call object |
| 306 | Location data not found |
| 307 | Maintenance plan has no maintenance items |
| 308 | Maintenance strategy does not exist |
| 309 | Maintenance plan number not valid |
| 310 | Maintenance item &1 does not exist |
| 312 | MaintItem is assigned to MaintPlan & - only display possible |
| 314 | Maintenance item & already exists |
| 315 | Neither FunctLocation nor equipment number entered in MaintItem |
| 316 | Maintenance planner group & does not exist |
| 317 | Maintenance plan will be deleted when you save your changes |
| 318 | Maintenance plan & incorrect for counter & |
| 319 | Maintenance plan & already locked |
| 320 | Maintenance plan & does not exist |
| 321 | Maintenance plan & already exists |
| 322 | Number range not found |
| 323 | Number range is not external |
| 324 | Number is not in external interval |
| 325 | Maintenance item has no object list |
| 326 | No contract for the reference object could be selected |
| 327 | Enter a planning plant |
| 328 | Enter an order type |
| 329 | Enter maintenance activity type |
| 330 | Work center & does not exist |
| 331 | Task list data reversed because of change of object |
| 332 | Enter a text |
| 333 | Function for displaying object is not supported in this field |
| 334 | No maintenance plan exists for strategy & |
| 335 | No maintenance plan was selected |
| 336 | No valid maintenance activity type exists |
| 337 | You can choose between an internal and an external number |
| 338 | Task list does not contain any maintenance packages |
| 339 | Assignment not possible! Maintain strategy texts in language & |
| 340 | No maintenance item exists |
| 341 | Only order types with internal number assignment are allowed |
| 342 | Task list & & & is not available for key date & |
| 343 | Company codes of maintenance plan and settlement rule are different |
| 344 | Enter a task list type |
| 345 | Task list type not supported |
| 346 | Task list & & & does not exist |
| 347 | SYSTEM: task list status & does not exist |
| 348 | Task list not free for use |
| 349 | New maintenance planner group has default order type & |
| 350 | Maintenance item not allocated to a technical object |
| 351 | Maintenance item has not been allocated an assembly |
| 352 | Maintenance item has not been allocated a technical object |
| 353 | Maintenance item already assigned to the maintenance plan |
| 354 | Last maintenance item of the maintenance plan |
| 355 | Task list data reversed because of change of object |
| 356 | Task list entered not suitable for strategy: & |
| 357 | Maintenance plan not yet scheduled |
| 358 | Scheduling record could not be found |
| 359 | Maintenance plan is not performance-based |
| 360 | First maintenance item of the maintenance plan |
| 361 | Task list not yet saved |
| 362 | No task list has yet been assigned to the maintenance item |
| 363 | No packages have yet been assigned to the maintenance plan |
| 364 | No packages have yet been assigned to the maintenance item & |
| 365 | Maintenance item and sales document have different controlling areas |
| 366 | Maintenance item and sales document have different plants |
| 367 | Enter a main work center |
| 368 | Sales document & & is canceled |
| 369 | Check the settlement rule |
| 370 | Order type of maintenance item changed; check the settlement rule |
| 371 | Inspection plan & & & is not available |
| 372 | Maintain initial counter reading |
| 373 | Enter confirmation counter reading |
| 374 | Entered counter reading greater than last entered counter reading |
| 375 | Confirmation counter reading smaller than initial counter reading |
| 376 | Confirmation counter reading smaller than last confirm. counter reading |
| 377 | A task list was selected |
| 378 | Only purchase orders with reference to a service package are possible |
| 379 | The purchase order is not possible since already delivered |
| 380 | The purchase order is not possible since already settled |
| 381 | The purchase order is not possible since deletion indicator set |
| 382 | Always enter purchase order number and purchase order item together |
| 383 | The purchase order item has no goods receipt indicator |
| 384 | Specify G/L account and order number, order item not assigned to account |
| 385 | Counter &2 is proposed from reference object &1 |
| 386 | Check whether a counter has been proposed for all counter intervals |
| 387 | Only cycle set allowed for multiple counter plans |
| 388 | No cycle set allowed for strategy task lists |
| 389 | Purchase order has no GR-related invoice verification |
| 390 | Purch. order for maint. item requires account assignment cat. 'U' or 'F' |
| 391 | No service entry sheet could be generated -> long text |
| 392 | Caution: Maintenance plan already scheduled, check scheduling |
| 393 | The maintenance plan only allows task lists without a strategy reference |
| 394 | The settlement profile of the order type does not allow a settlement |
| 395 | Sales document & & is canceled |
| 396 | Enter a piece of equipment as reference object |
| 397 | Enter a functional location as reference object |
| 398 | Counter &1 is INACTIVE; scheduling maintenance plan &2 not possible |
| 399 | No valid packages are assigned to item &1 for key date &2 |
| 400 | Release not possible as MaintPlan already released, called or skipped |
| 401 | Maintenance plan &1: Predecessor (call number &2) still on hold |
| 402 | No scheduling records exist yet |
| 403 | Fixing not possible as MaintPlan already released, called or skipped |
| 404 | Call is already marked as skipped |
| 405 | Call can no longer be skipped |
| 406 | No maintenance packages exist for maintenance item & |
| 407 | Call on & will be skipped |
| 408 | No order exists for maintenance date &, maintenance item & |
| 409 | No maintenance packages are due |
| 410 | Rescheduling necessary because of change in package |
| 411 | Enter a start date |
| 412 | Enter a completion confirmation date |
| 413 | New completion confirmation date is before the old CompConf. date & |
| 414 | Enter a call date |
| 415 | Planned date is in the past |
| 416 | Maintenance call has already been called; fixing not possible |
| 417 | Fixing date not possible before previous completion confirmation date |
| 418 | Fixing date is before the previous planned date |
| 419 | Fixing date is after the next planned date of & |
| 420 | Shift > 100% is not allowed |
| 421 | Tolerances > 100% are not allowed |
| 422 | Cycle Modification factor must be a whole number with key date scheduling |
| 423 | No start offset has been set |
| 424 | More scheduling records will be created |
| 425 | Original schedule restored |
| 426 | Maintenance plan & still without maintenance packages |
| 427 | New completion confirmation date < start date & |
| 428 | Scheduling record already confirmed |
| 429 | Call horizon > 100% is not allowed |
| 430 | The first call date has been reached |
| 431 | The last call date has been reached |
| 432 | Maintenance plan preview not possible |
| 433 | No scheduling notifications exist |
| 434 | Order for maintenance date &, maintenance item & |
| 435 | No maintenance call object exists for planned date & |
| 436 | No manual calls have been made yet |
| 437 | Function not possible as scheduling currently locked |
| 438 | No order number was read |
| 439 | Scheduling not possible, no maintenance items have yet been assigned |
| 440 | Further scheduling not possible until last call is confirmed |
| 441 | The maintenance schedule has not been assigned a task list |
| 442 | Planned date & cannot be confirmed |
| 443 | Inconsistency with object list number: & |
| 444 | Caution: Possible deletion of data entered when selecting |
| 445 | Skipping of this call not possible |
| 446 | Warning: Planned date with call number &1 cannot be confirmed |
| 447 | No annual performance entered for measuring point & |
| 448 | No counter reading entered yet for unit, & measuring point & |
| 449 | Scheduling will occur with a start offset |
| 450 | Scheduling will be performed based on current counter readings : & |
| 451 | No active maintenance cycles exist |
| 452 | A start in the cycle was executed for maintenance plan &1 |
| 453 | Maintain a time unit |
| 454 | Scheduling performed on the basis of current counter readings |
| 455 | Only ONE time-based maintenance cycle without counter allowed at a time |
| 456 | No counter assigned for performance-dependent maintenance cycles |
| 457 | No editing of maintenance items for service processing purchasing |
| 458 | Enter a notification type |
| 459 | Predecessor to & not yet confirmed |
| 460 | Maintenance plan &: Order created without reference to the task list |
| 461 | Task list & & & does not belong to the equipment |
| 462 | Task list & & & does not belong to the functional location |
| 463 | Select a counter |
| 464 | No maintenance plan was scheduled |
| 465 | A counter could not be defined for the reference object |
| 466 | You have not entered a reference object in the maintenance item |
| 467 | Annual performance of counter & is less than or equal to 0 |
| 468 | The customer enhancement IPRM0005 (active) requires a start in the cycle |
| 469 | Long text for maintenance item & not maintained in language & |
| 470 | Maintenance plant & planning plant of task list/gen. task list different |
| 471 | Maint. plan generates notifications; package selection may be irrelevant |
| 472 | Long text for routing from WItem & is not maintained for language & |
| 473 | No task list was integrated with the maintenance item |
| 474 | No reference object is maintained for the counter proposal |
| 475 | Waiting calls from the last restart receive the status "Skipped" |
| 476 | Maintenance-item-relevant data was changed in the reference object |
| 477 | Maintenance plan has more than 99 positions. Current position is &/&. |
| 478 | No called call is available to be completed |
| 479 | Scheduling postponed for maintenance plan & |
| 480 | Counter &1 is used more than once in cycle set sequence &2 |
| 481 | Item &1 is not assigned to a cycle set sequence maintained in the plan |
| 482 | Cycle set sequence &1 is not assigned to a maintenance item |
| 483 | The cycle set sequence of this cycle cannot be changed |
| 484 | The cycle including the cycle set sequence cannot be deleted |
| 485 | The functionality is not possible with a call interval bigger than zero |
| 486 | Next planned date is set; call interval not possible. |
| 487 | Maint.Plan &1: Daily performance of counter &2 is bigger than the cycle |
| 488 | Daily performance of counter &1 is bigger than the corresponding cycle |
| 489 | Repeat factor must be greater than 0 and less than 100 |
| 490 | First maintain a cycle |
| 491 | Maximum number of 99 cycles are already maintained for maint. plan &1 |
| 492 | First change to the detail view of a maintenance item |
| 493 | Cycle set sequence &1 contains more than one purely time-based cycle |
| 494 | Mutliple counter plan &1: Start time may not be in the future |
| 495 | Basic dates of order &1 are adjusted after saving |
| 496 | Basic dates of order &1 are adjusted |
| 497 | Start dates of notification &1 adjusted after being saved |
| 498 | Start dates of notification &1 have been adjusted |
| 499 | Dates updated beginning with date &1; Maintenance plan &2 |
| 500 | *----------------- Messages for reports |
| 501 | No maintenance item was selected. See long text. |
| 502 | Multiple counter plan enhancement is not activated |
| 503 | Fixing date before the start date is not possible |
| 504 | Work centers do not exist |
| 505 | Field &1 is required for service order call object |
| 550 | *---------- Messages for archiving maintenance plans ------------------ |
| 551 | Program &1 started: &2 &3 |
| 552 | Program &1 started: &2 &3 in test mode |
| 553 | Program &1 ended: &2 &3 |
| 554 | Program &1 ended in test mode: &2 &3 |
| 555 | Statistics: |
| 556 | Number of maintenance plans selected: & |
| 557 | Number of maintenance items selected: & |
| 558 | & maintenance plans could not be processed for the following reasons |
| 559 | Deletion indicator set for & maintenance plans |
| 560 | => Processing terminated |
| 561 | No database delimitation performed (selection options are blank) |
| 562 | Selection conditions (selection options) are too complex |
| 563 | Internal error in function module & |
| 564 | Maintenance plans which are used in PRT equipment: & |
| 565 | Maintenance plans for which unconfirmed calls exist: & |
| 566 | Maintenance plans which are locked: & |
| 567 | No authorization to set the deletion indicator: & |
| 568 | Deletion flag set for & maintenance plans |
| 569 | No maintenance plan was selected |
| 570 | System error in program & (&) |
| 571 | You have not maintained any selection conditions: no selection occurs |
| 572 | Maintenance plan & is locked |
| 573 | You can set the deletion flag for & maintenance plans |
| 574 | Status change for & maintenance plans is not possible |
| 575 | Status change not possible for maintenance plan & |
| 576 | Maintenance plan &: Deletion flag set/possible |
| 577 | Maintenance plan &: No authorization to set the deletion flag |
| 578 | Function module &1: No (further) data was found |
| 579 | Function module &1: Costing was called with incorrect parameter |
| 580 | Task list &1 (category &2, counter &3): No consideration (Deletion) |
| 581 | Maintenance plan &1: No consideration (Deletion or inactivation) |
| 582 | Maintenance plan &1: No consideration (Costing not supported) |
| 583 | Task list &1 (category &2, counter &3): Error during costing |
| 584 | Maintenance item &1 (maintenance plan &2): Error during costing |
| 585 | Maintenance item &1 (maintenance plan &2) No valid calls |
| 586 | Maintenance item &1 (maintenance plan &2): No task list integrated |
| 587 | Costing for task lists completed, Amount of generated records = &1 |
| 588 | Costing for maintenance plans completed, Amount of generated records = &1 |
| 589 | Costing for package number &1 completed, Amount of generated records = &2 |
| 590 | Costing for task lists started, reference date = &1 |
| 591 | Costing for maintenance plan started, start date = &1, end date = &2 |
| 600 | *--------------------RIMHIS00-------------------------------------------* |
| 601 | No maintenance items were selected |
| 602 | There are no calls for maintenance plan & |
| 603 | Saving is possible only in maintenance plan simulation |
| 604 | Maintenance plan &1 was restarted several times |
| 605 | Maintenance plan & already blocked, maint.plan simulation not possible |
| 606 | Error when blocking maintenance plan & |
| 607 | Please position cursor on a call or order |
| 608 | Previous calls not yet released |
| 609 | Fixed calls no longer convertible in normal calls on hold |
| 610 | System error when reading order no. & |
| 611 | Only calls on hold can be moved with successor |
| 612 | Only calls on hold and fixed calls can be moved |
| 613 | Call cannot be changed |
| 614 | & maintenance plans were selected without calls |
| 615 | Call may not be before previous call |
| 616 | Fixed call may not be after the subsequent call |
| 617 | The moved sequence contains fixed dates which are exceeded |
| 619 | Calls of perf.-based maint. plans/multiple counter plans cannot be fixed |
| 620 | You do not have authorization for maintenance plan & |
| 621 | Preventive maintenance plan simulation not possible: no authorization |
| 622 | You do not have authorization to change calls for maintenance plan & |
| 623 | No processed maintenance plans available for maintenance plan simulation |
| 624 | No calls exist for maintenance plan & in the analysis period |
| 625 | Message log contains no entries |
| 626 | You can also find the collected messages in the message log |
| 627 | Maintenance items that were found cannot be displayed |
| 628 | No maintenance plans with calls were found |
| 629 | You do not have authorization for maintenance item & |
| 630 | Maintenance plan & already has deletion indicator, so no graphic display |
| 631 | No maintenance plan simulation possible |
| 632 | No capacity display possible owing to incorrect task list data |
| 633 | No maintenance items selected owing to maintenance plan status set |
| 634 | Incomplete simulation of additional dates for maintenance plan &1 |
| 650 | *--- Maintenance plan with reference to outline agreement --------------* |
| 651 | Outline agreement or outline agreement item not available |
| 652 | Outline agreement item not available |
| 653 | Outline agreement expired |
| 654 | Order default values not maintained for service product & |
| 655 | No task list is maintained in the order default values for & |
| 656 | Task list &1 &2 &3 already deleted |
| 657 | Task list &1 &2 &3 cannot be used owing to deletion flag set |
| 658 | Use a maintenance plan category with reference to the outline agreement |
| 659 | Maintenance plan &3 already exists for contract item &1 &2 |
| 660 | Program error for & |
| 661 | Outline agreement item already completed (see overall status) |
| 662 | Outline agreement item is partially rejected |
| 663 | Outline agreement item is rejected |
| 664 | Outline agreement item is incomplete |
| 665 | Use a maintenance plan category without reference to outline agreement |
| 666 | Inspection plan &1 &2 &3 already deleted |
| 667 | Task list &1 &2 &3 cannot be used owing to deletion flag set |
| 670 | Maintenance plan can only be scheduled until end of contract |
| 671 | A fixed date may not exceed the contract end & |
| 672 | A manual maintenance call may not exceed the contract end & |
| 673 | You can only specify the contract and contract item together |
| 675 | Task list category not allowed for this maintenance plan category |
| 676 | Order type not allowed for the maintenance plan category |
| 678 | No date could be determined for plan &1 within the contract term |
| 700 | *----------Reserved for Scheduling Module-------------------------------* |
| 701 | Strategy & does not exist |
| 702 | Strategy & has no packages |
| 703 | Unit & does not exist |
| 704 | All onetime packages for maintenance plan & have been called |
| 705 | New plan offset is faulty |
| 706 | Start offset is negative |
| 707 | Cycle length is less than zero |
| 708 | Completion confirmation date is before the start date & |
| 709 | Calculated planned date & is before the last completion confirmation & |
| 710 | No operations can be determined for plan &1 and item &2 for this date |
| 711 | No package selected |
| 712 | Key date scheduling not possible with the date & |
| 713 | Save or reverse the manual call first |
| 714 | Manual call not possible as scheduling already carried out |
| 715 | Maintenance plan already scheduled |
| 716 | No further maintenance calls attached |
| 717 | Negative extrapolation value: Maintain counter reading |
| 718 | You cannot enter negative counter readings |
| 719 | No call object issued for item &1 and call &2 |
| 720 | Scheduling record not yet saved: display not possible |
| 721 | Caution: Maintenance calls will be deleted |
| 722 | Delete -> Release data |
| 723 | No call for maintenance item & occurs despite due date |
| 724 | The original planned date is reproduced |
| 725 | Maintain a factory calendar |
| 726 | No call object exists because the relation object was inactive at call |
| 727 | Fixing not possible; Maintenance package &1 is not valid for &2 |
| 728 | No meas.document available before &1 and &2 for counter &3. Plan &4 |
| 729 | Counter reading for counter &1 and time &2 &3 not up to date |
| 730 | Factory calendar ID &1 does not exist or is inactive; Maint. plan &2 |
| 731 | Date &1 is after the end of factory calendar &2; Maint. plan &3 |
| 732 | Date &1 is before the start of factory calendar &2; Maint. plan &3 |
| 733 | Calculated date is after end of factory calendar &1; maintenance plan &2 |
| 734 | Maintenance plan & was not scheduled |
| 735 | Maintenance plan & was not scheduled in Parallel Processing |
| 736 | Enter an end date for scheduling that is after the start of cycle date |
| 737 | Enter a start of cycle date that is before the end date for scheduling |
| 738 | Enter an end date for scheduling that is after the current date |
| 739 | Define the end date for scheduling for the maintenance plan |
| 740 | End counter for scheduling is lower than the last counter reading |
| 741 | Open calls may remain in the database |
| 742 | You cannot define an end counter for scheduling for maintenance plan & |
| 743 | Enter a manual call date that is before the end date for scheduling |
| 744 | Enter an end date for scheduling that is after the start date |
| 745 | Enter a start date that is before the end date for scheduling |
| 746 | You cannot generate more scheduling calls for maintenance plan & |
| 747 | Invalid offset for maintenance plan &1 |
| 748 | The validity of maintenance plan & has expired |
| 749 | Reschedule the maintenance plan |
| 750 | The system does not support validation values for the selected order type |
| 751 | Error in maintenance plan &1 |
| 752 | Enter a filter value for Counter Unit |
| 753 | Maintenance call object must not be a service order; see long text |
| 760 | *--- Miscellaneous |
| 761 | Place the cursor on the screen section you want to scroll |
| 762 | Maintain the corresponding date |
| 763 | Function of the Stability Study is Incorrect |
| 764 | * Message is obsolete |
| 770 | *--- Maintenance Plan for Service Order |
| 771 | & |
| 800 | *-----Reserved for Maintenance Strategy---------------------------* |
| 801 | The whole strategy will be deleted |
| 802 | Maintain the package number |
| 803 | Maintain the cycle length |
| 804 | Maintain the cycle short text |
| 805 | Maintain the offset |
| 806 | Maintain the offset short text |
| 807 | Maintain an offset for packages that are not called regularly |
| 808 | Maintain the hierarchy |
| 809 | Maintain the hierarchy short text |
| 810 | Maintain the item text |
| 811 | Scheduling parameters are reset |
| 812 | Define a scheduling type (time-based/performance-based) |
| 813 | Key date scheduling not possible |
| 814 | Value is greater than 100% |
| 815 | Strategy & is used in maintenance task lists |
| 816 | Strategy & is used in maintenance items |
| 817 | Strategy & is used in maintenance schedules |
| 818 | Strategy package & & is used in equipment task lists |
| 819 | Strategy & & is used in general maintenance task lists |
| 820 | Strategy & does not exist |
| 821 | No usage exists for strategy & |
| 822 | Select a valid line |
| 823 | An invalid offset was set |
| 824 | Offset set |
| 825 | Offset reversed |
| 826 | Switching only possible with mixed strategies |
| 827 | Further scrolling is not possible |
| 828 | Start schedule already reached |
| 829 | Specify the cycle duration or the offset |
| 830 | No strategy packages have been defined |
| 831 | No order exists for maintenance plan &, call number & |
| 832 | Maintain the factory calendar for the strategy |
| 833 | Factory calendar & does not exist |
| 834 | Maintain a strategy unit |
| 835 | Strategy package & & is being used in the plan by a FunctLocation |
| 836 | Save the maintenance strategy first |
| 837 | No maintenance packages have been maintained for the maintenance strategy |
| 838 | Maintain an equipment output unit |
| 839 | No package sequence display for cycle sets for multiple counter plans |
| 840 | Plant calender & is not valid in current year |
| 841 | Maintenance item is already assigned to another maintenance plan |
| 842 | Maintenance strategy of maintenance plan and item do not match |
| 843 | Error situation |
| 844 | Strategy plan not allowed for maintenance plan category & |
| 845 | The plan date entered is invalid for factory calendar &1 |
| 846 | No text found for strategy & |
| 848 | You are not authorized to change strategy & |
| 860 | ---------------------------- Change Documents ------------------------ |
| 863 | Maintenance item & is not assigned to any maintenance plan |
| 864 | Error calling up function module IWP3_READ_T399W |
| 865 | Error in program &1 |
| 870 | &1 of reference maintenance plan does not match &2 of maintenance plan |
| 871 | Reference maintenance plan is not a copy template |
| 872 | Maintenance plan cannot be created as inactive without maintenance items |
| 873 | Reference maintenance plan is not a copy template |
| 880 | No active cycle for cycle set sequence &1 exists; Maintenance plan &2 |
| 881 | No valid cycle set sequence in maintenance plan &1 exists |
| 882 | Function not possible due to several dates with status "On hold" |
| 883 | Function is not possible due to BAdI IPRM_MCP_UPD_CALLOBJ |
| 888 | Enh. multiple counter plan can no longer be deactivated after the save |
| 889 | Planned date for maintenance plan &1 was scheduled for 00.00.0000 |
| 890 | Key-date scheduling for strategy is not possible |
| 891 | Order simulation for task list group &1 is not correct |
| 893 | Field name &1 not found in maintenance plan header &2 |
| 894 | Field name &1 not found in maintenance plan item &2 |
| 895 | No data was changed |
| 896 | Structure &1 contains fields without required data element assignment |
| 897 | Total maximum number of structures that can be appended is 10 |
| 898 | Maintenance plan &1 cannot be changed |
| 899 | Strategy cannot be changed |