PPEACT - Nachrichten der ACT-Anwendung des iPPE (Aktivit�ten)
The following messages are stored in message class PPEACT: Nachrichten der ACT-Anwendung des iPPE (Aktivit�ten).
It is part of development package CPPEACT0C in software component AP-PPE. This development package consists of objects that can be grouped under "Customizing for iPPE Process Structure".
It is part of development package CPPEACT0C in software component AP-PPE. This development package consists of objects that can be grouped under "Customizing for iPPE Process Structure".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Object &1 could not be created because of an error |
| 001 | Object &1 could not be read because of an access error |
| 002 | Resource &1 could not be read because of an access error |
| 003 | No corresponding relationship type found for object &1 &2 &3 &4 |
| 004 | Could not find a valid relationship type |
| 005 | Assignment relationship could not be created because of an error |
| 006 | Relationship could not be created because of an error |
| 007 | Relationship could not be deleted because of an error |
| 008 | Assignment relationship could not be deleted because of an error |
| 010 | Object dependency is not allowed for routing type &1 |
| 011 | Enter a routing type |
| 012 | Object dependencies cannot be maintained for &1 &2 |
| 013 | Usage for object dependencies must be activated for routing type &1 |
| 014 | Original status could not be reestablished |
| 051 | Start: Generally set the indicator MATFLOW in database table PRSEQ |
| 052 | Errors occurred when accessing database table PRSEQ |
| 053 | End: Generally set the indicator MATFLOW in database table PRSEQ |
| 054 | &1 entries from table PRSEQ were updated |
| 100 | ********************Object Check*************************** |
| 101 | Supply area assgmnts not allowed at the &1 &2 of type 'setup/tear down' |
| 102 | Component assignments at &1 &2 of type 'setup/tear down' are not allowed |
| 103 | Variable time data is not allowed at &1 &2 of type 'setup/tear down' |
| 104 | Multi-resources are not allowed at &1 &2 of type 'setup/tear down' |
| 105 | Variable capacity reqmts are not allowed at &1 &2, type 'setup/tear down' |
| 106 | No plant/location is maintained for &1 &2 |
| 107 | No primary resource is maintained for &1 &2 |
| 108 | Scheduling data is incomplete for &1 &2 |
| 109 | No capacity requirements maintained at &1 &2 for resource &3 |
| 110 | Type 'setup/tear down' is no longer supported for &1 &2 |
| 111 | The object dependency at &1 &2 is not active |
| 112 | No scrap can be maintained at &1 &2 for type 'Teardown/Setup' |
| 113 | &1 &2 cannot have a master reporting point because of the scrap |
| 114 | &1 &2 must have a reporting point type because of activity scrap |
| 115 | There can only be one activity with a scrap value under &1 &2 |
| 116 | Scrap is only possible at the last production activity under &1 &2 |
| 117 | Scrap for &1 &2 is only possible for capacity planning of a resource |
| 118 | Master reporting point for &1 &2 with scrap value in &3 &4 not allowed |
| 119 | The activity scrap at &1 &2 must be less than 100% |
| 120 | Reporting point allowed only at the last production activity under &1 &2 |
| 121 | Only the first setup activity under &1 &2 can have a setup group |
| 122 | There can be only one activity with a reporting point under &1 &2 |
| 123 | Setup act. with setup group below &1 &2 can only be located at beginning |
| 124 | Change numbers &1 and &2 at &3 &4 have the same "Valid from" date |
| 125 | &1 &2 requires a reporting point that posts goods movements |
| 126 | No primary resource has been specified at &1 &2 |
| 127 | Specify a reporting point for each change status of &1 &2 |
| 200 | *************** Messages for Context Menu ************************ |
| 201 | There are no relationships at object &1 |
| 202 | Object type of &1 cannot be changed because of relationships |
| 203 | No suitable object types found for object &1 |
| 204 | Select a valid object type |
| 400 | ************************ACT general************************************* |
| 401 | Routing header &1 is still used in a production version |
| 402 | Could not delete the old change status &2 of mode &1 |
| 403 | Object with predecessor-successor relatshp cannot be an assignment obj. |
| 405 | Reporting point type &1 at &2 &3 is not recognized |
| 406 | Plant/location &3 in setup group/synch. charact. at &1 &2 does not exist |
| 407 | No synchronization characteristic allowed at &1 &2 of type 'setup' |
| 408 | You cannot define a reporting point type at &1 &2 of type 'setup' |
| 409 | Type &1 of &2 &3 is not supported |
| 410 | Setup group/sync. charact.and plant must be maintained together at &1 &2 |
| 411 | Supply area and plnt/location must always be maintained together at &1 &2 |
| 412 | Plant/location &3 of a supply area assignment at &1 &2 does not exist |
| 413 | Supply area &3 does not exist in plnt/locat. &4 in SA assignment at &1 &2 |
| 414 | Mode of a SA assignment at &1 &2 with plant &4 and SA &3 does not exist |
| 415 | &1 &2 of a SA assignment at &3 &4 is not assigned to the latter |
| 416 | SA assignment is ambiguous at &1 &2 for mode &3 and component &4 |
| 417 | Component in a SA assignment at &1 &2 with plant &3 does not exist |
| 418 | &1 &2 is used in a supply area assignment at &3 &4 |
| 419 | No action/reporting point can be defined at &1 &2 of type 'setup' |
| 420 | Setup group/synch. char. &4 is not defined in plant/location &3 at &1 &2 |
| 421 | Fixed times are maintained at &1 &2; the type cannot be changed |
| 422 | &1 &2 does not have type 'Setup' and cannot be assigned a setup group |
| 423 | &1 &2 cannot have a setup group and setup key |
| 450 | **********************COMPONENTS*************************************** |
| 451 | Component &1 &2 &3 &4 is unknown |
| 452 | Variant &1 of object &2 &3 &4 has already been assigned |
| 453 | Variant &1 is already indirectly assigned through the object &2 &3 &4 |
| 454 | Component &1 &2 &3 &4 must be completely described |
| 455 | Object &1 &2 &3 &4 must be completely described |
| 456 | Component &1 &2 is not assigned to activity &3 |
| 457 | Component &2 cannot be assigned to setup activity &1 |
| 458 | Only 'start' or 'no' consumption allowed in the &1 from &2 to &3 |
| 459 | The object &1 &2 &3 &4 is already assigned |
| 500 | ********** ACT Application Object ************************************** |
| 501 | Application object type &1 of &2 &3 is not supported by module |
| 502 | PVS object type &1 of &2 &3 is not supported by module |
| 503 | Resource &1 &2 &3 has not been created |
| 504 | Relationship type &1 is not supported by the module |
| 506 | Plant &1 does not exist |
| 508 | Resource &1 at &2 &3 is not set for capacity planning |
| 509 | APO master data could not be found for resource &1 |
| 512 | Unit and duration at &1 &2 must be maintained together |
| 513 | Unit and requirements at &1 &2 requirements &3 must be maintained togeth. |
| 516 | Plant &1 of secondary resource &2 must be the same as plant &3 in mode &4 |
| 524 | General error when creating the mode |
| 525 | General error when deleting the mode |
| 526 | Min. interoperation time is greater than the max.for &1 between &2 and &3 |
| 527 | Mode &1 does not exist at node &2 |
| 530 | General error when deleting additional capacity requirements |
| 531 | &1 is not a time unit in the &2 between &3 and &4 |
| 532 | Enter a unit for the &1 between &2 and &3 |
| 533 | Changes are only possible with change number |
| 534 | Specified unit of measure &1 is not defined for requirements &4 of &2 &3 |
| 535 | &1 is not a time unit at &2 &3 |
| 538 | Plant &2 of resource &3 must be the same as plant &1 in mode &4 |
| 539 | Mode &1 not found |
| 540 | Plant in reqmt &1 does not match primary resource &2 in &3 &4 |
| 542 | Capacity requirement &1 is relevant to scheduling at &3 &2 |
| 543 | Specified capacity requirement &1 is assigned more than once at &2 &3 |
| 544 | Capacity requirement at mode &1 - &2 will be deleted when you save |
| 545 | Resource &1 is already defined as a secondary resource/reqmnt at &2 &3 |
| 546 | Enter a mode number |
| 547 | No standard value determination type is defined for time analysis |
| 548 | Plant &1 for requirements &2 does not match plant &3 in mode &4 |
| 549 | Mode &1 with change status &2 has already been historically deleted |
| 550 | Mode &1/&2 can only be changed with the same change number in filter mode |
| 551 | Reporting point at &1 &2 must be constant for all change statuses |
| 576 | Mode linkage at &1 requires identical modes at &2 and &3 |
| 577 | Resource linkage at &1 requires identical resources at &2 and &3 |
| 578 | Variable times and variable requirements are maintained at &1 &2 |
| 579 | You have not specified a mode priority at &1 &2 |
| 580 | Variable and fixed requirements are maintained for resource &3 at &1 &2 |
| 581 | You can only assign the calendar indicator once at &1 &2 |
| 582 | Unit &1 of requirement for secondary resource &2 on &3 &4 is not allowed |
| 583 | Variable and fixed times are maintained at &1 &2 |
| 585 | You must maintain the unit and duration of max. break at &1 &2 together |
| 586 | Unit &1 for the maximum break at &2 &3 is not a unit of time |
| 587 | Primary resource &1 at &4 &2 cannot be used for planning &3 |
| 588 | Plant at &1 &2 does not match the one in setup group/sync. characteristic |
| 589 | Setup activity in &1 &2 prevents you entering reporting points |
| 590 | ************** Enhancements to Mode ****************************** |
| 591 | New mode &1 that you wish to create with change status &2 already exists |
| 592 | Mode priority &3 specified at &1 &2 is not supported |
| 593 | Plant/location &3 specified at &1 &2 does not exist |
| 594 | Only resources of type 'single' or 'multi' are allowed at &1 &2 |
| 595 | Setup activity of &1 &2 allows 'single' resources only |
| 596 | You must specify an action point at &2 &1 |
| 597 | Setup activity of &2 &1 allows fixed times only |
| 598 | Single resource at &2 &1 does not allow fixed times |
| 599 | You have not made a selection |
| 600 | ******************** Relationships ************************************* |
| 601 | Make one selection only |
| 602 | ************** Relationships ******************************** |
| 603 | Object type &4 of &2 is different from object type &3 of &1 |
| 604 | The objects to be linked, &1 and &2, are not of type 'node' |
| 606 | Objects &1 and &2 are indirectly linked on a lower level |
| 607 | Only one relationship is allowed between activity &2 and &3 |
| 608 | Objects &1 and &2 are not assigned to the same object |
| 609 | Only two relationships are allowed between &2 and &3 at &1 |
| 610 | No superior object found for object &1 |
| 611 | Mult. constraints at &1 between &2 and &3 are only allowed for activities |
| 612 | &1 between &2 and &3 must have different relationships |
| 613 | &1 between &2 and &3 would cause a parallel sequence |
| 614 | Relationship between &1 type &3 and &2 type &4 cannot be maintained |
| 615 | Activity &1 has already been assigned to object &2 |
| 616 | You must specify an object type for the object &1 &2 &3 |
| 617 | You must specify the exact type for the activity &1 &2 &3 |
| 618 | Relationship is not valid between &1 type &3 and &2 type &4 |
| 619 | No relationships start from the object &1 &2 &3 |
| 620 | *************** Assignment List ************************************* |
| 621 | The process structure &1 &2 &3 does not exist |
| 622 | This version is not allowed in iPPE |
| 623 | No iPPE routing is assigned to the access |
| 624 | Assignment cannot be deleted because it is not assigned to an activity |
| 625 | The assigned activity &1 does not belong to the routing of assignmnt list |
| 626 | The product structure &1 &2 &3 &4 does not exist |
| 627 | Only mode linkage is allowed between primary resources under &1 &2 |
| 628 | Under &1 &2 only 'end-start' relationships are allowed between &3 and &4 |
| 629 | There must be subordinate objects for the &1 between &2 and &3 |
| 630 | There is an indirect &1 on operation-level for activities &2 and &3 |
| 631 | &1 between activities &2 and &3 is only valid below operations |
| 632 | 'Continual res. load' in &1 from &2 to &3 only poss. in res-mode linkage |
| 633 | 'Continual res. load' in &1 from &2 to &3 only poss. in 'end-start' rel. |
| 634 | Unit and minimum transition must be maintained in &1 from &2 to &3 |
| 635 | Unit and maximum transition must be maintained in &1 from &2 to &3 |
| 636 | Transition times in &1 from &2 to &3 can not be converted |
| 637 | 'Continual load res.' must be set between &3 and &4 below &1 &2 |
| 638 | You must specify a relationship type for the &1 between &2 and &3 |
| 640 | ****************Part_of Relationships**************** |
| 641 | Hierarchy relationship between &1 and &2 cannot be deleted |
| 642 | Hierarchy relationship is not allowed between &1 type &3 and &2 type &4 |
| 645 | No usage authorization for &1 &2 exists |
| 700 | ***********************Mode Enhancements******************************* |
| 701 | Change status &1 at &2 &3 is not recognized |
| 702 | Change status &1 at &2 &3 does not have a purely temporal validity |
| 703 | Inconsistency in mode linkage between &1 and &2 at mode &3 |
| 704 | Inconsistency in resource linkage between &1 and &2 at resource &3 |
| 710 | Durations at &1 &2 are only accurate up to 3 decimal places |
| 711 | Capacity requirements at &1 &2 are only accurate up to 3 decimal places |
| 750 | ************** Time Analysis - Start ********************************** |
| 751 | Time analysis control could not be linked |
| 752 | Internal error creating or changing a time analysis |
| 753 | Internal error deleting a time analysis |
| 754 | Time analysis &1 is still used and cannot be deleted |
| 755 | You do not have authorization to maintain time analysis &1 |
| 756 | There is no time analysis defined in the user profile |
| 757 | Customizing for the time analysis control could not be read |
| 758 | Internal error when reading a mode |
| 759 | Internal error in dialog with time analysis control |
| 760 | Internal error calling the data provider |
| 761 | Change can be made only with change number &1 |
| 763 | Internal error reading a time analysis |
| 765 | An internal error occurred when assigning the time analysis |
| 766 | Time analysis is already assigned to mode &1 |
| 769 | No time analysis assigned to mode &1 |
| 770 | Assignment of time analysis at mode &1 could not be deleted |
| 771 | Assignment of time analysis at mode &1 deleted |
| 772 | Select a mode |
| 773 | Key field must be filled |
| 774 | Only one determination type can be transferred to the time analysis |
| 799 | ************** Time Analysis - End ************************************* |
| 800 | **************Consistency Check*********************** |
| 801 | Consistency check on &1 &2 was started at &3 |
| 802 | Consistency check on &1 &2 was finished at &3 |
| 803 | General errors reading data when accessing &1 &2 |
| 804 | Beginning to check the attributes of subordinate objects of &1 &2 |
| 805 | Finished checking the attributes of subordinate objects of &1 &2 |
| 806 | Errors occurred during the consistency check on &1 &2 |
| 807 | No errors occurred during the consistency check on &1 &2 |
| 808 | Beginning structure check for &1 &2 |
| 809 | Finished structure check for &1 &2 |
| 810 | Beginning to check the relationships of &1 &2 |
| 811 | Finished checking the relationships of &1 &2 |
| 812 | &1 &2 is not included in the relationships of &3 &4 |
| 813 | Relationships between activities at &1 &2 are interrupted &3 times |
| 814 | Object &1 &2 is used several times in &3 &4 |
| 815 | The reporting/action point &1 is used several times in &2 &3 and &4 |
| 816 | At least one mode at &1 &2 must be available for automatic selection |
| 817 | There must be an activity of type 'operation' under &1 &2 |
| 818 | There can only be one activity of type 'setup' under &1 &2 |
| 819 | There can only be one activity of type 'tear down' under &1 &2 |
| 820 | Component assignment to &1 &2 requires capacity planning for resource &3 |
| 821 | &1 &2 is not designed for planning - only one mode is possible |
| 822 | Beginning the check on the assignment relationships from &1 &2 |
| 823 | Check on the assignment relationships from &1 &2 has finished |
| 824 | Component &1 is used several times at &2 &3 and &4 |
| 825 | You have not maintained an activity in &1 &2 |
| 826 | You have not maintained a mode for &1 &2 |
| 827 | &1 &2 does not belong to task list type &3 |
| 828 | Recursive relationships have been maintained under &1 &2 |
| 829 | Check of supply area assignments was completed successfully |
| 830 | Short dump avoids inconsistent data when archiving the objects |
| 850 | **************CTM Checks***************************** |
| 851 | CTM planning for &1 &2 only allows linear assigned activities |
| 852 | CTM planning only allows one end-start relationship at &1 from &2 to &3 |
| 853 | CTM planning does not supprt any setup groups and keys at &1 &2 |
| 854 | CTM planning does not allow any offset times at &1 from &2 to &3 |
| 855 | CTM planning disallows &1 at &2 as only allowed at last activity |
| 856 | CTM planning disallows use of Engineering Change Management for &1 &2 |
| 857 | CTM planning only allows mode linkage by resources at &1 from &2 to &3 |
| 870 | ******* Customizing ******* |
| 871 | The changes made do not affect existing production data structures in APO |