| PPERPP114 |
Internal error: The application object type of action point &1 is missing |
| PPERPP115 |
Internal error: Incorrect application object type for action point &1 |
| PPERPP116 |
The reporting point type &1 at &2 &3 does not exist |
| PPERPP117 |
Report. point with type &3 cannot be assigned at the beginning of &1 &2 |
| PPESCMPV500 |
**************** Messages for Release of Change Number *************** |
| PPESCMPV501 |
Status &1 is not known |
| PPESCMPV502 |
Release of &2 is invalid: &1 has not reached a status that allows &3 |
| PPESCMPV503 |
Specify an object type for the person responsible |
| PPESCMPV504 |
Could not determine a person responsible |
| PPESCMPV505 |
Select the required rows for this function |
| PPESCMPV506 |
Select one row only for this function |
| PPESCMPV507 |
There is no long text for the variant |
| PPESCMPV508 |
Release completed |
| PPESCMPV509 |
Display has been refreshed |
| PPESCMPV510 |
Workflows have been generated for the selected status objects |
| PPESCMPV511 |
Data has been saved. |
| PPESCMPV512 |
No attachments exist for the selected status object |
| PPESCMPV513 |
Status object selected without specifying person responsible |
| PPESCMPV514 |
Status object is already in the workflow |
| PPESCMPV600 |
***************** Messages for Evaluation Report ********************** |
| PPESCMPV601 |
You must make an entry on the selection screen |
| PPESCMPV602 |
No status objects exist for this selection |
| PPESCMPV603 |
Selection only possible using template and single value |
| PPESCMPV604 |
Selection only possible using interval and single value |
| PPESCMPV605 |
Function not possible; status cockpit is already loaded |
| PPESCMPV606 |
Select at least one field in the workflow area |
| PPESCMPV701 |
No object type has been created for status &1 (cross-application object) |
| PPESCMPV702 |
Status &1 had an incorrect object type (cross-application object) |
| PPESCMPV703 |
Create predecessor status &1 for current status &2 first |
| PPESCMPV704 |
Status &1 must have the same parameters as predecessor &2 |
| PPESCMPV800 |
************************* Connection of CMP Variants to Status |
| PPESCMPV801 |
Variants &1 must be on level &2 |
| PPESCMPV802 |
Status graph &1 does not exist |
| PPESCMPV803 |
API error status &1: TOPCSID has not been filled |
| PPESCMPV804 |
API error status &1: TOPCSID cannot be changed |
| PPESCMPV805 |
&1 application object type is not allowed for status &2 for &3 |
| PPESCMPV810 |
Error locking &1 against changes with &2 |
| PPESCMPV811 |
&1 successfully locked against changes with &2 |
| PPESCMPV812 |
Object management record &1 for change number &2 has not been closed |
| PPESET100 |
****************** PRSET ************************************************ |
| PPESET101 |
&1 from &2 to &3 cannot be deleted (dependent &4) |
| PPESET102 |
Select a node |
| PPESET103 |
Node is already selected |
| PPESET104 |
There is no material for &1 &2 |
| PPESET105 |
Node &1 |
| PPESET106 |
A &1 cannot be merged with itself |
| PPESET107 |
Enter a valid &1 |
| PPESET108 |
Set variant &1 in set node &2 already exists in set node &3 |
| PPESET109 |
There is no link between a structure node and set node &1 |
| PPESET110 |
Node &1 is dependent on the selected node(s) |
| PPESET111 |
&1 &2 has been merged with &1 &3 |
| PPESET112 |
&1 &2 has been separated into &1 &3 |
| PPESET113 |
Select at least one object |
| PPESET114 |
&1 &2 is consistent |
| PPESET115 |
&1 cannot be decomposed into itself |
| PPESET409 |
&1 &2 already exists |
| PPESNP000 |
The type 'Teardown' is not supported for &1 &2. |
| PPESNP001 |
The &3 &4 specified for &1 &2 does not exist |
| PPESNP002 |
&1 of resource &2 must be the same as &1 at mode &3 |
| PPESNP003 |
Resource &1 is already defined as a secondary resource/reqmnt at &2 &3 |
| PPESNP004 |
Please choose an activity type |
| PPESNP005 |
A blank line to insert is already available |
| PPESNP006 |
Activity &1 was moved |
| PPESNP007 |
No scrap can be maintained for activities of type 'Teardown' and 'Setup' |
| PPESNP008 |
The SNP plan &1 must have at least one activity |
| PPESNP009 |
'Continous' consumption is allowed for &1 from &2 to &3 |
| PPESNP010 |
Offset time for &1 &2 is not supported at &3 &4 |
| PPESNP011 |
Activity &1 is already assigned to &2 &3 |
| PPESNP012 |
Activity &1 was added |
| PPESNP013 |
The APO resource &2 at iPPE resource &1 does not exist |
| PPESNP014 |
Resource type &1 cannot be used for capacity planning in the SNP plan |
| PPESNP015 |
The APO resource for resource &1 was not maintained |
| PPESNP016 |
No resource has been defined for maintaining cap. reqmts at &1 &2 |
| PPESNP017 |
The fixed duration of &1 &2 must contain multiple days |
| PPESNP018 |
No setup group is allowed for &1 &2 |
| PPESNP019 |
&1 &2 is already assigned to &3 &4 |
| PPESNP020 |
At least one SNP activity must be assigned to &1 &2 |
| PPESNP021 |
Check of hierarchy relationships from &1 &2 starting |
| PPESNP022 |
Check of hierarchy relationships from &1 &2 completed |
| PPESNP023 |
&1 &2 can only have one maximum break for CTM planning |
| PPESNP024 |
&1 &2 can only have several modes for CTM planning |
| PPESNP025 |
Requirement unit and dimension of bucket resource &1 do not match |
| PPESNP026 |
Enter a mode number when maintaining &1 &2 |
| PPESNP027 |
The value of scrap &1 &2 can be a maximum of 100 percent |
| PPESNP028 |
The selected activity &1 does not have a mode |
| PPESNP029 |
Selected activity &1 is not assigned to a component |
| PPESNP030 |
&1 &2 does not have the type SNP plan |
| PPESNP031 |
The activity &1 already exists with a different internal key |
| PPESNP032 |
The scrap at &1 &2 is not included for SNP planning |
| PPESNP033 |
Activity &1 was inserted |
| PPESNP034 |
The sequence relationships of the activities under &1 &2 contain errors |
| PPESNP035 |
The sequence relationships of the activities under &1 &2 were corrected |
| PPESTATUS000 |
**************** Customizing ******************************* |
| PPESTATUS001 |
Key field must be filled |
| PPESTATUS002 |
Object-specific statuses should also be created for the new status |
| PPESTATUS003 |
Data records still exist for status &1 |
| PPESTATUS004 |
Status &1 still exists as a predecessor status |
| PPESTATUS005 |
Object-specific statuses should also be deleted |
| PPESTATUS006 |
Status value 'initial' can only exist once |
| PPESTATUS007 |
There are still object-specific entries for status &1 with value &2 |