WA - Meldungen aus dem Workflow Ereignismanager
 The following messages are stored in message class WA: Meldungen aus dem Workflow Ereignismanager.
It is part of development package SWE in software component BC-BMT-WFM. This development package consists of objects that can be grouped under "Business Workflow: Events".
 It is part of development package SWE in software component BC-BMT-WFM. This development package consists of objects that can be grouped under "Business Workflow: Events".
| Message Nr ▲ | Message Text | 
|---|---|
| 000 | --------------Start event wizard------------------------------------- | 
| 001 | Error occurred | 
| 002 | Time specified is not in the past | 
| 003 | Choose an event or select "Extend object type" | 
| 004 | &1 queue entries in status "&2" were deleted | 
| 005 | No entries found | 
| 100 | Object type extensions only allowed in expert mode | 
| 101 | & is supplied by SAP and must not be modified | 
| 102 | Enter a name for event & | 
| 103 | Enter a description for event & | 
| 104 | & already exists | 
| 105 | Enter a name for & | 
| 106 | Enter a description for & | 
| 107 | LIS exception & does not exist | 
| 110 | &1&2&3&4 | 
| 129 | Business object type &1 has status &2. Linkage not possible. | 
| 130 | Business object type & does not exist | 
| 131 | Package & does not exist | 
| 132 | Open FI exit & does not exist | 
| 133 | Open FI product already exists | 
| 134 | Function module & already exists | 
| 135 | Linkage with workflow for open FI event & not permitted | 
| 136 | Application & does not exist | 
| 137 | Table & does not exist | 
| 138 | The name of & does not begin with X, Y or Z | 
| 139 | Table &1 has no field &2, or &1 cannot be used | 
| 140 | Table or structure & does not exist | 
| 141 | Function module & does not exist | 
| 142 | The name & belongs to the SAP namespace | 
| 143 | Error activating & | 
| 144 | Error writing data in last wizard step | 
| 145 | Type linkage entered successfully | 
| 146 | The name of the change document must not begin with X, Y or Z | 
| 147 | Function group & does not exist | 
| 148 | Business object type & could not be created | 
| 149 | Change document object & could not be created | 
| 150 | Event & could not be created in Business Object Repository | 
| 151 | Linkage between &1 and &2 could not be created | 
| 152 | Linkage for change document object & could not be saved | 
| 153 | Linkage entry for open/FI event & could not be saved | 
| 154 | Function module & could not be created | 
| 155 | Event &2 of business object type &1 could not be modified | 
| 156 | Linkage for LIS exception & could not be entered | 
| 157 | Key data of change document object & has errors | 
| 158 | Make entries in all fields | 
| 159 | Select an event creation date/time | 
| 160 | No change document object for business object type &1 | 
| 161 | The existing subtype &1 is used for the extension | 
| 162 | Program name &1 is already assigned | 
| 163 | Change document &1 does not exist | 
| 164 | Event linkage not possible for change document &1 | 
| 165 | Delegation between &1 and &2 could not be created | 
| 166 | Event & for object type & does not exist | 
| 167 | &1 is not an event of object type &2 | 
| 168 | & is in customer namespace | 
| 170 | No authorization to execute using RFC | 
| 321 | No subobject type selected | 
| 400 | Event not correctly selected | 
| 410 | --------------End event wizard--------------------------------------- | 
| 411 | -----------Start: Test environment for change documents----------------- | 
| 412 | Test object & already exists | 
| 413 | Test object & does not exist yet | 
| 414 | Objekt data not changed | 
| 415 | Table entry for object & was & | 
| 416 | Test object & & - object deleted | 
| 417 | Test object & &; object is (still) in the database | 
| 430 | ----------Consistency checks for event linkages ----------------------- | 
| 431 | Event receiver linkages already optimized | 
| 432 | Event receiver linkages optimized | 
| 433 | No critical entries found | 
| 434 | The problem cannot be cleaned up automatically | 
| 450 | Enter an object type | 
| 451 | Enter a receiver type | 
| 452 | Receiver function module & can only be used for type linkages | 
| 453 | Receiver FM & can only be used for instance linkages | 
| 454 | Receiver function module & can only be used for BOR objects | 
| 520 | Field restriction(s) with errors deleted | 
| 521 | No field restrictions with errors found | 
| 522 | Error deleting a complex field restriction | 
| 523 | All modules must support the same type of interface | 
| 600 | Number range object & not found | 
| 601 | Number for number range object & could not be generated | 
| 602 | Object type & for event & not found | 
| 603 | Object type & not allowed for automatic type linkage | 
| 610 | No entries found corresponding to the selection criteria | 
| 611 | No table entry selected | 
| 612 | Event trace was switched off | 
| 613 | Event trace was switched on | 
| 614 | Status of event trace was not changed | 
| 615 | The selected events were deleted | 
| 616 | The contents of the event trace table were deleted | 
| 617 | Internal messages were deleted from the event trace table | 
| 620 | Instance linkage between & & and & & cannot be deleted | 
| 621 | Instance linkages event & receiver & cannot be deleted | 
| 622 | Linkage number cannot be generated | 
| 623 | Instance linkage between & & and & & cannot be entered | 
| 624 | Instance linkage between & & and & &: Type linkage cannot be entered | 
| 625 | Instance linkage between & & and & &: Type linkage cannot be activated | 
| 626 | Instance linkages for & & cannot be copied to & & | 
| 627 | Instance linkages to task & cannot be deleted | 
| 630 | Type linkage between & & and &: Not possible to change check funct.mod.& | 
| 631 | Type linkage between & & and &: Deletion not possible | 
| 632 | Type linkage between & & and &: Deactivation not possible | 
| 633 | Type linkage between & & and &: Activation not possible | 
| 634 | Type linkage between & & and &: Insertion not possible | 
| 635 | Type linkage betw. & & and &: Not possible to change receiver funct.mod.& | 
| 636 | Type linkage betw.& & and &: Not possible to change rec.type determ. FM & | 
| 637 | Type linkage & & for &: Indicator for type linkage not set | 
| 638 | Type linkage & & for &: Indicator for type linkage not deleted | 
| 639 | Type linkage between & & and &: No entry found | 
| 640 | Type linkage betw. & & and &: Exception & when checking transport object | 
| 641 | Type linkage betw. & & and &: Exception & when inserting transport object | 
| 642 | Type linkage between & & and &: Entry exists with other secondary data | 
| 643 | Type linkages to task & cannot be deleted from table & | 
| 644 | Type linkage &1-&2 <--> &3 cannot be updated | 
| 645 | Type linkage between & & and &: Status "no errors" cannot be set | 
| 650 | Receiver function module & not found | 
| 651 | Receiver function module &: Error determining interface | 
| 652 | Receiver function module &: Invalid name for a function module | 
| 653 | Receiver function module &: Parameter & has an invalid reference & | 
| 654 | Receiver function module &: Parameter & is not optional | 
| 655 | Receiver function module & not identified as RFC-compatible | 
| 660 | Check function module & not found | 
| 661 | Check function module &: Error determining interface | 
| 662 | Check function module &: Invalid name for a function module | 
| 663 | Check function module &: Parameter & has an invalid reference & | 
| 664 | Check function module &: Parameter & is not optional | 
| 670 | Receiver type determination function module & not found | 
| 671 | Receiver type determination func. module &: Error determining interface | 
| 672 | Receiver type determination func. module &: Invalid name for a func. mod. | 
| 673 | Receiver type determination FM &: Parameter & has invalid reference & | 
| 674 | Receiver type determination func. mod. &: Parameter & is not optional | 
| 675 | & linkage entries deleted | 
| 676 | Error deleting obsolete linkage entries | 
| 680 | & & not found | 
| 681 | & &: Error determining interface | 
| 682 | & &: Name not valid for function module | 
| 683 | & &: Parameter & does not exist | 
| 684 | & &: Parameter & has invalid reference & | 
| 685 | & &: Parameter & is not optional | 
| 698 | Select an event | 
| 699 | Program error occurred | 
| 700 | Event creation not possible for this work item type | 
| 701 | Work item does not exist or cannot be reached from here | 
| 702 | No (active) event receivers exist | 
| 703 | Event receivers of type & cannot be displayed | 
| 750 | ----------------Messages workflow administration | 
| 751 | Table buffer synchronized | 
| 752 | Error synchronizing table buffers | 
| 754 | Number of events per read access was set to &1. | 
| 790 | ------------Events with linkages that have errors ---------------------- | 
| 791 | Select an event before & | 
| 792 | Linkage & & to & was set to "&" | 
| 793 | Coupling &1 &2 on &3 deactivated | 
| 798 | Event linkage not active | 
| 800 | Transaction aborted - no entry deleted | 
| 801 | ----------------------Messages event queue------------------------- | 
| 802 | &1 events triggered by &3 (in &2 seconds). | 
| 845 | The event has not yet been delivered | 
| 846 | Data included in request &1 | 
| 847 | Error reading event | 
| 848 | Error saving administration data | 
| 849 | The event cannot be delivered in status "&" | 
| 850 | Data has been changed in the meantime - the action is canceled | 
| 851 | Background job & deleted | 
| 852 | Background job & scheduled | 
| 853 | Background job & not deleted | 
| 854 | Background job & could not be scheduled | 
| 855 | Events in event queue and transmission information deleted | 
| 856 | Event queue could not be deleted | 
| 857 | Error reading event queue | 
| 858 | Background job scheduling not changed | 
| 859 | Browser started ... | 
| 860 | Event does not exist | 
| 861 | & not possible for multiple selection (select one entry) | 
| 862 | Restrictions for event trace saved | 
| 863 | Restrictions for event trace not saved | 
| 864 | Select an entry in the event queue | 
| 865 | Event not in the event queue (any longer) | 
| 866 | Event not (yet) delivered, not in trace or created asynchronously | 
| 867 | Event not in event trace | 
| 868 | Work item cannot be displayed | 
| 869 | Background job RSWWDHEX for deadline monitoring deleted | 
| 870 | Background job RSWWDHEX for deadline monitoring not deleted | 
| 871 | Cannot display background job for restarting WIs with temporary errors | 
| 872 | Background job for restarting work items with temporary errors deleted | 
| 873 | Background job for restarting WIs with temporary errors not deleted | 
| 874 | Background job for operating the event queue scheduled | 
| 875 | Background job for operating the event queue not scheduled | 
| 876 | Background job for operating the event queue deleted | 
| 877 | Background job for operating the event queue not deleted | 
| 878 | Event not in event queue (any longer) or already delivered | 
| 879 | Event read from event queue and being delivered | 
| 880 | Error sending event | 
| 881 | No events meeting the selection conditions in the event queue | 
| 882 | Event container does not contain any more container elements | 
| 883 | Event queue deactivated | 
| 884 | Event queue activated | 
| 885 | Background job & does not exist | 
| 886 | Background job & for operating event queue not scheduled | 
| 887 | Background job & not deleted | 
| 888 | Background job & scheduled | 
| 889 | & is not a defined server group | 
| 890 | Event cannot be displayed | 
| 891 | No application server found | 
| 892 | Data written to shared buffer | 
| 893 | Event queue administration data saved | 
| 894 | Customizing data cannot be transported to client & | 
| 895 | Event queue data selected | 
| 896 | No event is selected | 
| 897 | Event already delivered and cannot be delivered again | 
| 898 | Specify the number of events to be read per access | 
| 899 | Specify a time period to the next read access |