PPECMP - Nachrichten der CMP-Anwendung der iPPE (Komponenten)
The following messages are stored in message class PPECMP: Nachrichten der CMP-Anwendung der iPPE (Komponenten).
It is part of development package CPPECMP_APPL in software component AP-PPE. This development package consists of objects that can be grouped under "Application Logic of Application Object CMP".
It is part of development package CPPECMP_APPL in software component AP-PPE. This development package consists of objects that can be grouped under "Application Logic of Application Object CMP".
Message Nr ▲ | Message Text |
---|---|
050 | ************************ PRELID ***************************************** |
051 | &1 from &2 to &3 cannot be created due to phantom reference (&4) |
052 | Phantom reference from &1 &2 to &3 &4 is not allowed. |
100 | *************************** CMP Nodes ********************************* |
101 | You cannot select 'multiple selection' and 'priority' at &1 &2 |
102 | Maximum &3 characters allowed for name (&2) of &1. |
103 | Name of &1 contains invalid characters (Characters &3 at position &4). |
104 | Use maximum &1 as number for &4 (character &2 at position &3). |
105 | Error determining the following number from the number range &1/&2 |
106 | &1 &2 has a set priority for selecting dependencies |
107 | &1 &2 cannot be changed into &2 |
108 | The archiving indicator is also set for dependent &1 |
109 | The archiving indicator is also set for dependent &1 / &2 |
110 | Number range PVS_NAME does not have an interval |
111 | Error in number range PVS_NAME |
112 | Number range interval is nearly exhausted |
113 | Number range interval is exhausted |
114 | Node &1 of type &2 cannot be copied |
182 | More than one alternative segment maintained as a document at variant &1 |
200 | ****************************** Context ********************************** |
201 | &1 &2 is locked for object changes. |
202 | Access for &1 &2 cannot be created during extraction |
203 | Access for &1 &2 cannot be created during extraction |
250 | **************************** Alternative ******************************** |
251 | &1 &2 cannot be maintained as document &1 |
300 | ************************** Variant ************************************* |
301 | obsolete: -> pper3e_cmpid 001 |
302 | Enter a unit of measure for the quantity |
303 | Unit &1 is not valid for &2 &3 |
304 | Only positive quantities are valid |
305 | Unit &1 is not defined |
306 | No decimal places are defined for unit &1 |
307 | Unit &1 can have a maximum of &2 decimal place(s) |
308 | &1 &2 of &3 causes recursion (&4) and will not be updated |
309 | Reference to &1 from &2 &3 causes recursion (&4) and will not be updated |
310 | Check caused no recursion. |
311 | &1 &2 of &3 creates recursion (&4) |
312 | Reference of &1 from &1 &2 causes recursion (&4) |
313 | Checks are only supported for &1 of level (&2) |
314 | &1 entry is not allowed for the phantom reference |
315 | Entry of quantity and/or unit is invalid without reference to object |
316 | &1 changes are not allowed in &2 of access level (&3) |
317 | Only a config. &3 is allowed at configurable &1 on access level (&2) |
318 | Enter a quantity |
319 | Variable and fixed quantity in change status &1 of &2 &3 not possible |
320 | Fixed quantity in change status &1 of &2 &3 not allowed with iPPE access |
321 | Entry of &1 is only allowed with &2 entry |
322 | Class entry for &1 &2 is not allowed |
323 | &1 &2 does not allow a class entry for &3 &4 |
324 | &1 from &2 to &3 causes recursion (&4) |
325 | &1 &2 already exists |
326 | When the standard indicator is set, object dependencies are not evaluated |
327 | Maintain the default units in Customizing (Tab. CPPE_VSI_DEFUNIT) |
328 | Enter the object type for the reference in the attributes of &1 &2 |
329 | &1 &2 points to object &3 (not a node for the &4 application) |
330 | &1 &2 does not have any object assignment to a variant |
331 | &1 &2 does not have any object assignment to a node |
332 | &1 &2 is not an access object for a variant assembly ((V)As) |
333 | Existence of &1 from &2 + color key not checked |
334 | Enter a value for variable-size item 1 |
335 | Dimension &1 has not been maintained |
336 | Dimension &1 is not planned |
337 | No formula is maintained for key &1 |
338 | Maintain the dimension for formula (key &1) |
339 | Maintain the SI unit for dimension &1 |
340 | Enter a positive quantity as a 'factor' for the phantom reference |
341 | An error occured while converting into another unit of measure |
342 | Error (&1) calculating the qty for variable-size item w/ formula (&2) &3 |
343 | Calculated variable-size item quantity is less than 0.001 |
344 | Calculated variable-size item quantity causes a field overflow |
345 | Variable-size item quantity was corrected |
346 | You cannot specify a unit of measure for the phantom reference |
347 | Only the processing of &1 for application &2 is supported |
348 | Fixed Quantity for Phantom Reference Not Allowed |
349 | &1 &2 already exists in variants on the struct. level (&3) of (v)assembly |
350 | &1 &2 already exists in variants on the access level (&3) of (v)assembly |
351 | &1 &2 of &3 &4 is still used in access object |
352 | &1 from &2 to &3 causes recursion (&4) and will not be updated |
353 | Error: low-level code > 999 for &1 &2 in maintenance of &3 &4 |
354 | Enter a &1 for the size data |
355 | &1 &2 is still used in structures (&3) |
356 | &1 &2 is still used on initial screen |
357 | iPPE access &1 / &2 / &3 could not be created |
358 | Access object is contained in the production version. Deletion not poss! |
359 | This entry is used as a template and cannot be deleted |
360 | &1 &2 is an invalid entry (&1 version) |
361 | Identification of &1 &2 for omitted part is not valid for &3 entry |
362 | A maximum of one entry for configuration data is allowed for &1 &2 |
363 | The class of &1 &2 does not match the product class of &3 &4 |
364 | A reference is valid to the object type node (&1) only |
365 | &1 &2 is already referenced by &3 &4 |
366 | Change status &1 for &2 &3 has a configuration |
367 | &1 &2 already references &3 &4. |
368 | Entry for class &3 (class type &4) has already been maintained for &1 &2 |
369 | Reference to &1 is not allowed from &2 &3 in the context environment &4. |
370 | Configuration data of &1 &2 cannot be copied to &3 &4 |
371 | DMU information for &1 &2 cannot be copied to &3 &4 |
372 | Reference of &1 &2 to &3 in &4 is not allowed. |
373 | Reference of &1 &2 to &3 from &4 is not allowed. |
374 | &1 &2 is still referenced by &3 &4 |
375 | Reference from &1 &2 to &3 is not valid (&4 exists) |
376 | &1 is not allowed in &2 (&3) |
380 | Creation of configurable materials or material variants is not allowed |
385 | ******************** Extract ************************************* |
386 | Engineering change management for objects is not allowed in &1 &2. |
387 | References to &2 are not allowed in the context of &1. |
388 | Reference to &1 &2 is outside of the context environment of &3 &4. |
395 | ******************** VSI Formula Maintenance **************************** |
396 | Cannot interpret variables in formula &1 (<>ROMS1,ROMS2,ROMS3) |
397 | &1 &2 |
398 | Make an entry for &1 |
399 | Breakdown already exists in iPPE/PVS for &1 &2 |
400 | *********************** Interface Variants ***************************** |
401 | Do you wish to delete &1 &2 with change number &3? |
402 | Delete change status &1 for &2 &3 without history? |
403 | Select a maximum of &1 assemblies to be displayed in the overview |
404 | &1 &2 is maintained as shared position for change status &3 |
409 | &1 &2 already exists for change status &3 |
410 | &1 &2 does not exist in &3 &4 |
411 | Create &1 &2? |
450 | ************************** Assembly ************************************* |
451 | &1 &2 still has a reference to a template |
452 | &1 &2 is still assigned to &3 &4 |
453 | &1 &2 is used elsewhere (used in &3 &4) |
454 | &1 &2 already exists at &3 &4 |
455 | Assemblies for &1 &2 have been moved to &3 &4 |
456 | &1 &2 does not belong to access level (&3) |
457 | &1 cannot be clearly identified |
458 | Alternative does not exist as an object for an assembly relationship |
459 | &1 &2 and &3 &4 do not belong to the same assembly |
460 | &1 between &1 &2 does not correspond to the template |
461 | &1 does not exist |
462 | &1 between &2 &3 and &4 will be deleted when you save |
463 | &1 between &2 &3 and &4 will be created when you save |
464 | &1 between &2 &3 and &4 will be changed when you save |
465 | Standard variant indicator is not allowed for &1 |
466 | Phantom reference from &1 &2 within a (variant) assembly is not allowed |
467 | &1 &2 still has assembly relationships from alternative &3 |
468 | Alternative &1 from variant &2 is still referenced by variant &3 |
469 | &1 &2 for assemblies requires node assignment for &3 &4 |
470 | Reference from &1 &2 does not point to var. assembly node alternative |
471 | &1 cannot be deleted with the action |
472 | &1 cannot be deleted (dependent &2) |
473 | &1 &2 is already used in a structure for &3 &4 |
474 | Phantom reference is not valid for an identification of omitted part |
475 | Configuration data is not allowed for &1 |
476 | Enter a &1 to maintain the &2 &3 |
477 | Multiple use of &1 from &2 &3 is not permitted |
480 | ************************ Assembly Interface *************************** |
481 | Do you wish to delete &1 &2 without history with all the items? |
482 | Assembly alternative &1/&2 already exists |
483 | Phantom reference is incomplete (iPPE node, variant, alternative) |
484 | Node name has been taken from the number range |
485 | Select End of Block |
500 | ********************** Configuration ************************************ |
501 | No configuration profile exists |
502 | No color information exists |
503 | More than one change status has been checked at variant & |
504 | There are no object dependencies to display |
505 | Change status is a deletion record |
600 | ************************ Coexistence/Variant **************************** |
601 | Material &1 in &2 creates recursion via bill of material |
602 | Material &1 in &2 creates recursion via follow-up material in BOM |
603 | Relationship of node &1 to node &2 creates recursion via bill of material |
604 | Relationship of &1 to &2 creates recursion via follow-up material in BOM |