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