PPEENG - Nachrichten der iPPE-Engine
The following messages are stored in message class PPEENG: Nachrichten der iPPE-Engine.
It is part of development package CPPEENG in software component AP-PPE. This development package consists of objects that can be grouped under "iPPE Engine".
It is part of development package CPPEENG in software component AP-PPE. This development package consists of objects that can be grouped under "iPPE Engine".
Message Nr ▲ | Message Text |
---|---|
000 | ************************Object Maintenance******************************* |
001 | Message was not defined (still working) |
002 | Message &1/2 is outdated; use the current message |
003 | Message &1/&2 does not exist; use the current message |
004 | Object(s) saved |
005 | &1 &2 is being used by &3 |
006 | &1 &2 does not exist |
007 | &1 &2 already exists |
010 | **************************Authorizations********************************* |
011 | No authorization to create &1 &2 |
012 | No authorization to read &1 &2 |
013 | No authorization to change &1 &2 |
014 | No authorization to delete &1 &2 |
081 | Error inserting table &: & out of & records were posted |
082 | Error updating table &: & out of & records posted |
083 | Error deleting table &: & out of & records were posted |
093 | &1 &2 was changed and can only be unlocked after you save |
094 | &1 &2 was deleted by another user |
095 | Error in the message collector |
096 | Logical system not defined |
097 | Program error: application object &3 is not allowed (&1 &2) |
098 | Program error: Object type &3 unknown (&1 &2) |
099 | Unexpected error in iPPE Engine (&1 &2) |
100 | Unexpected error generating a GUID |
101 | &1 was not identified |
102 | &1 &2 does not have a type |
103 | Type &1 of &2 &3 has not been defined |
104 | Creation of &1 &2 to &3 &4 is not allowed |
105 | Deletion of &1 &2 to &3 &4 is not allowed |
106 | No relationship type found between &1 and &2 |
107 | No relationship type was selected |
108 | &1 between &2 and &3 has no type |
109 | Type of &1 between &2 and &3 has not been defined |
110 | &1 &2 already exists with different internal key |
111 | &1 &2 already exists |
112 | &1 &2 does not exist |
113 | &1 &2 is being edited by &3 |
114 | Application object type &3 of &1 &2 cannot be changed |
115 | &1 &2 could not be maintained |
116 | Unable to delete &1 &2 |
117 | &1 between &2 and &3 already exists |
118 | &1 between &2 and &3 already exists with a different internal key |
119 | &1 between &2 and &3 is being processed by &4 |
120 | &1 between &2 and &3 does not exist |
121 | &1 &2 will be created when you save |
122 | &1 &2 will be changed when you save |
123 | &1 &2 will be deleted when you save |
124 | &1 &2 is locked |
125 | Lock on &1 &2 has been canceled |
126 | &1 &2 has been changed; changes may be lost |
127 | &1 between &2 and &3 will be created when you save |
128 | &1 between &2 and &3 will be changed when you save |
129 | &1 between &2 and &3 will be deleted when you save |
130 | &1 &2 still has relationships to other iPPE Objects |
131 | &1 &2 does not allow a reference to a class |
132 | &1 &2 requires a reference to a class |
133 | Product class does not exist for &1 &2 |
134 | &1 between &2 and &3 could not be maintained |
135 | &1 between &2 and &3 could not be deleted |
136 | &1 &2 is still used in variant(s) |
137 | &1 &2 is still used in alternative(s) |
138 | Class type &1 does not support configured objects |
139 | &1 cannot be identified unless it is assigned to an application |
140 | &1 between &2 and &3 does not allow a new relationship of type &1 |
141 | &1 between &2 and &3 does not allow a new relationship at &2 |
142 | &1 between &2 and &3 does not allow a new relationship to &3 |
143 | &1 between &2 and &3 cannot be deleted because of cardinality |
144 | &1 between &2 and &3 cannot be deleted because of cardinality to &2 |
145 | &1 between &2 and &3 cannot be deleted because of cardinality to &3 |
146 | No object found for GUID &1 of technical type &2 |
147 | No external relationship found for GUID &1 with technical type &2 |
148 | &1 &2 can only be created/edited in context &3 |
149 | &1 &2 cannot be created/edited in a context |
150 | &1 &2 and &3 &4 are assigned to different contexts |
151 | &1 between &2 and &3 must be compatible with the class hierarchy |
152 | Class &1/&2 is not a subclass of &3 |
153 | &1 &2 has dependent objects that are not compatible to class &3 |
154 | Class &1/&2 is still used in iPPE |
155 | There is no classification system connected to the iPPE Workbench |
156 | &1 between &2 and &3 not allowed because it causes recursion |
157 | &1 is not allowed between &2 and &3 (&4 exist) |
158 | &1 &2 will not be unlocked as dependentlocks still exist |
159 | Original of &1 &2 is in logical system &3 |
160 | Lock of &1 &2 reset to "shared" mode |
161 | Type &1 of variant &2 does not exist |
162 | Type &1 of alternative &2 does not exist |
163 | Type &1 of relationship between &2 and &3 does not exist |
164 | &1 &2 will be renamed as &3 when you save |
165 | &1 &2 still has variants |
166 | &1 &2 still has alternatives |
167 | &1 &2 still has dependent iPPE objects |
169 | Descriptions of &1 of type &2 may only be &3 characters long |
170 | Label for &1 &2 contains invalid character '&3' |
171 | No authorization to create &1 &2 |
172 | No authorization to change &1 &2 |
173 | No authorization to delete &1 &2 |
174 | No authorization to read &1 &2 |
175 | No authorization to create in application &1 &2 |
176 | No authorization to change in application &1 &2 |
177 | No authorization to delete in application &1 &2 |
178 | No authorization to read in application &1 &2 |
179 | &1 &2 has dependent objects |
180 | Changes to &1 &2 are not based on current data |
181 | Identifying context &1 &2 does not exist |
182 | &1 cannot be identified in the context of a &2 |
183 | A &1 can only exist in the context of a(n) &2 |
184 | Product class change for &1 that is the context or that uses context |
185 | &1,&2 and context must belong to the same product class/application |
186 | &1 &2 cannot be identified in its own context |
190 | &1 &2 has relationships that are not allowed for node type &3 |
191 | &1 &2 has dependent objects that are not allowed for node type &3 |
195 | Sort field cannot be maintained for a &1 |
196 | Sort field must have the same value for all change statuses |
200 | **************** Messages relating to copying function ***************** |
201 | &1 &2 and &3 &4 have different application types |
202 | &1 &2 has not been copied to &3 &4 |
203 | Copying of &1 &2 to &3 &4 is complete |
204 | Copying of &1 between &2 and &3 is complete |
205 | You cannot copy &1 &2 to &3 &4 in the specified environment |
206 | You cannot copy &1 between &2 and &3 in the specified environment |
207 | You cannot copy &1 to &2 (Customizing) |
250 | ****************************** Alternative ****************************** |
251 | No authorization to create a &1 (Type &2) in application &3 |
252 | No authorization to read a &1 (Type &2) in application &3 |
253 | No authorization to change a &1 (Type &2) in aplication &3 |
254 | No authorization to delete a &1 (Type &2) in application &3 |
255 | &1 &2 is still referenced by &3 &4 |
256 | &1 &2 is still used in structures (including relationship to &3 &4) |
257 | Invalid object assignment for &1 &2 |
300 | ***************************** Variant ********************************** |
301 | Change status &3 of &1 &2 will be created when you next save |
302 | Change status &3 of &1 &2 will be changed when you next save |
303 | Change status &3 of &1 &2 will be deleted when you next save |
305 | Only the name of &1 &2 can be changed |
306 | &1 &2 is not valid as part key for &3 |
307 | Maintenance of costing data allowed only for &1 on structure level (&2) |
308 | &1 &2 and &3 &4 do not belong to the same template structure |
316 | No variant(s) found |
317 | Changes to the object assignment for &1 &2 are invalid |
319 | Multiple class assignment is not allowed in a hierarchy for &1 &2 |
350 | **************************** Access Object ************************** |
351 | &1 &2 is still used in the access object and cannot be deleted |
400 | *********************** Messages for ECM ******************************** |
401 | You must use a change number to edit &1 &2 |
402 | &1 &2 does not exist for change number &3 |
403 | Change status &1 has been overwritten for &2 &3 |
404 | You are not authorized to delete a change status from the database |
405 | &1 &2 will be deleted for change status &3 when you save |
406 | obsolete ->pper3e_ecn 009 |
407 | obsolete ->pper3e_ecn 001 |
408 | obsolete -> ppeeng 401 |
409 | Change status &1 for &2 &3 will be deleted from the DB when you save |
410 | obsolete ->pper3e_ecn 011 |
411 | obsolete ->pper3e_ecn 010 |
412 | Change status &1 of &2 &3 cannot be edited with &4 |
413 | &1 from &2 to &3 does not exist for change number &4 |
414 | &1 from &2 to &3 already exists for change number &4 |
415 | &1 &2 already exists for change number &3 |
416 | &1 from &2 to &3 can be edited only with a change number |
417 | &1 from &2 to &3 cannot be edited with a change number |
418 | &1 &2 has change statuses - change number not specified |
461 | No change document exists |
500 | ************************ Convert Long Texts ***************************** |
501 | & data records have been edited |
520 | *********************** Consistency Customizing ************************* |
521 | Customizing entry &1 in table &2 incorrect - field &3 blank |
522 | Incorrect customizing entry &1 in table &2 - invalid value in &3 |
523 | Incorrect customizing entry in table &1 - type not spacified |
550 | ********************* Messages To Be Archived *************************** |
551 | Archiving selection made for &1 &2 |
552 | Archiving selection for &1 between &2 abd &3 was created |
553 | Archiving selection deleted for &1 &2 |
554 | Archiving selection for &1 between &2 and &3 was deleted |
555 | Archiving selection for &1 &2 changed |
556 | Archiving indicator for &1 between &2 and &3 was changed |
557 | No archiving selection exists for &1 &2 |
558 | No archiving selection exists for &1 between &2 and &3 |
559 | &1 &2 cannot be changed because of archiving selection |
560 | &1 between &2 and &3 cannot be changed due to archiving selection |
561 | &1 &2 cannot be deleted due to archiving selection |
562 | &1 between &2 and &3 cannot be deleted due to archiving selection |
563 | Archiving selection for &1 &2 can no longer be changed |
564 | Archiving selection for &1 between &2 and &3 can no longer be changed |
565 | Archiving selection for &1 &2 can no longer be deleted |
566 | Archiving selection of &1 between &2 and &3 can no longer be deleted |
567 | Archiving selection already exists for &1 &2 |
568 | Archiving selection for &1 between &2 and &3 already exists |
569 | No authorization for creating archiving selection in application &1 |
570 | No authorization for changing archiving selection in application &1 |
571 | No authorization for deleting archiving selection in application &1 |
572 | Archiving indicator exists for object & and/or &1 |
573 | Object &2 and/or &3 of &1 has not yet been archived |
580 | ********************** Network Graphic ********************************** |
581 | Error in the network graphic |
582 | Error; object cannot be loaded |
583 | Error when creating/changing the PVS relationship |
600 | ********************** Texts and IDs ************************************ |
601 | Language &1 is not defined |
602 | Language &1 is not supported by the current code page |
603 | Short text for language &1 is empty |
604 | Short text for language &1 is maintained more than once |
700 | ******************** XPRA Messages ************************************** |
701 | Act. &1 of client &4 is of type &2, but also contains fixed dep. values |
703 | GUID &1 for table &2 (client &4) cannot be converted |