PPESNP - Nachrichtenklasse f�r SNP-Plantyp
The following messages are stored in message class PPESNP: Nachrichtenklasse f�r SNP-Plantyp.
It is part of development package CPPEACT in software component AP-PPE. This development package consists of objects that can be grouped under "ACT-Specific iPPE Objects".
It is part of development package CPPEACT in software component AP-PPE. This development package consists of objects that can be grouped under "ACT-Specific iPPE Objects".
Message Nr ▲ | Message Text |
---|---|
000 | The type 'Teardown' is not supported for &1 &2. |
001 | The &3 &4 specified for &1 &2 does not exist |
002 | &1 of resource &2 must be the same as &1 at mode &3 |
003 | Resource &1 is already defined as a secondary resource/reqmnt at &2 &3 |
004 | Please choose an activity type |
005 | A blank line to insert is already available |
006 | Activity &1 was moved |
007 | No scrap can be maintained for activities of type 'Teardown' and 'Setup' |
008 | The SNP plan &1 must have at least one activity |
009 | 'Continous' consumption is allowed for &1 from &2 to &3 |
010 | Offset time for &1 &2 is not supported at &3 &4 |
011 | Activity &1 is already assigned to &2 &3 |
012 | Activity &1 was added |
013 | The APO resource &2 at iPPE resource &1 does not exist |
014 | Resource type &1 cannot be used for capacity planning in the SNP plan |
015 | The APO resource for resource &1 was not maintained |
016 | No resource has been defined for maintaining cap. reqmts at &1 &2 |
017 | The fixed duration of &1 &2 must contain multiple days |
018 | No setup group is allowed for &1 &2 |
019 | &1 &2 is already assigned to &3 &4 |
020 | At least one SNP activity must be assigned to &1 &2 |
021 | Check of hierarchy relationships from &1 &2 starting |
022 | Check of hierarchy relationships from &1 &2 completed |
023 | &1 &2 can only have one maximum break for CTM planning |
024 | &1 &2 can only have several modes for CTM planning |
025 | Requirement unit and dimension of bucket resource &1 do not match |
026 | Enter a mode number when maintaining &1 &2 |
027 | The value of scrap &1 &2 can be a maximum of 100 percent |
028 | The selected activity &1 does not have a mode |
029 | Selected activity &1 is not assigned to a component |
030 | &1 &2 does not have the type SNP plan |
031 | The activity &1 already exists with a different internal key |
032 | The scrap at &1 &2 is not included for SNP planning |
033 | Activity &1 was inserted |
034 | The sequence relationships of the activities under &1 &2 contain errors |
035 | The sequence relationships of the activities under &1 &2 were corrected |