PPEFLO - Nachrichten f�r iPPE-Anwendungsobjekt FLO
The following messages are stored in message class PPEFLO: Nachrichten f�r iPPE-Anwendungsobjekt FLO.
It is part of development package CPPEFLO in software component AP-PPE. This development package consists of objects that can be grouped under "iPPE - Factory Layout Share".
It is part of development package CPPEFLO in software component AP-PPE. This development package consists of objects that can be grouped under "iPPE - Factory Layout Share".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Program error: application object &3 is not allowed (&1 &2) |
| 002 | No plant is maintained at &1 &2 |
| 003 | No location is maintained at &1 &2 |
| 004 | Short dump avoids inconsistent data when archiving the objects |
| 101 | You cannot change the number of takts for &1 &2 |
| 102 | Supply area &1 / &2 does not exist (&3) |
| 103 | &1 &2 will be created when you save |
| 104 | &1 &2 will be changed when you save |
| 105 | &1 &2 will be deleted when you save |
| 106 | &1 between &2 and &3 is not possible |
| 107 | &1 between &2 and &3 is not possible |
| 108 | &1 &2 is already assigned to &3 &4 |
| 109 | &1 &2 is not a line node: resource assignment has not been transferred |
| 110 | Assign &1 &2 to a line resource |
| 111 | Resource &1 is not a line resource |
| 112 | Line resource &1 is already assigned to &2 &3 |
| 113 | Node &1 does not exist |
| 114 | &1 between &2 and &3 will be created when you save |
| 115 | &1 between &2 and &3 will be changed when you save |
| 116 | &1 between &2 and &3 will be deleted when you save |
| 117 | &1 is not allowed for &2 &3 |
| 118 | &1 &2 already has alternatives |
| 119 | Alternatives cannot be created for &1 &2 |
| 120 | Specified alternative does not exist |
| 121 | &1 &2 is not a valid production line |
| 122 | You cannot copy FLO objects at present |
| 123 | Error when creating a line resource (proxy object) |
| 124 | The number of takts for &1 &2 is 0 |
| 125 | Plants of &1 (&2) and &3(&4) are not identical |
| 126 | Locations for &1(&2) and &3(&4) are not identical |
| 127 | &1 still has line balances and cannot be deleted |
| 128 | &1 &2 cannot be created by copying an object of type &3 |
| 129 | &1 is still being used in production version &2, &3, &4 |
| 130 | Goto is not supported with unsaved data. Please save your data first. |
| 131 | The priority for alternative line &1 (&2 &3) still has to be maintained |
| 401 | Action points &1 (&2) and &3 (&4) are at the same position on the line |
| 402 | Line explosion: Invalid object type &1 (&2) |
| 403 | Line explosion for &1 &2 is not allowed |
| 404 | Line explosion in execution mode is not allowed for &1 &2 |
| 405 | Standard path indicator is missing for &1 &2. Alternative &3 selected |
| 406 | Standard path indicator not clear for &1 &2. Alternative &3 selected |
| 407 | In line balance relatshp &1 to &2, &1 is not within line bal. line (&3) |
| 408 | Colored material &1 does not exist |
| 409 | Mode &2 to &3 in line balance &1 results in repeated activity in order |
| 410 | &1 is not assigned to alternative line &2 (&3) (Assignment created) |
| 411 | &1 &2 does not belong to &3 &4 (restricted line network for RPM) |
| 412 | Mode &1 not relevant |
| 413 | Mode &1 is not assigned to line &2 |
| 414 | Mode &1 was not assigned in an active line balance |
| 415 | &1 &2 is used within &3 &4 several times |
| 416 | Assignmt of altern. line from &1 &2 to part of line network &3 missing |
| 417 | Asssignment of &1 &2 to part of the line network &3 missing |
| 418 | &1 &2 does not exist |
| 419 | No valid line balance relationship exists for line structure &1 |
| 420 | Relationship between &1 &2 and &3 &4 recreated during explosion |
| 421 | You must assign a storage location at supply area &1 (&2) |
| 600 | *** Interface Messages *** |
| 601 | Alternative &1 already exists |
| 602 | Part of line network &1 already exists |