no workitems

[Baeuerle, Stefan]

Hi Jan,
 
you are right. The reason for the brackets is the receiver type FM. You will
see this brackets only in the event log to get the information that this
receiver has been set dynamically. The receiver FM will be called with the
given receiver without brackets (to start the workflow).
 
Your workflow definition needs the specified event to be able to start. You
will also need this event to specify bindings for your workflow. If you
activate the event at the workflow definition, you will get double entries
in the log because two linkages will be found (the dynamic and the static
one). The workflow would be started twice. Therefore deactivate the event at
the workflow definition. Nevertheless, the workflow will be started by the
(second) linkage with the receiver type FM.
 
Workitems will only be created, if there is a correct binding at the
workflow definition between the event and the workflow container. Another
reason may be that there is no agent for the first workitem (set the task to
general to check if this is the reason and refresh the org.assignments). If
the system detects an error, no workitem will be created.
 
hope this helps
Stefan
 
-----Original Message-----
From: Jan, Angeline [mailto:AJan at KHOV.COM]
Sent: Mittwoch, 6. Dezember 2000 20:04
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: no workitems
 
 
 
Hi Michael,
 
My event log shows the event for my workflow, but it's in brackets i.e.
(WS90500002).  The reason for this is probably because it's found by the
receiver type FM.
 
I've added the event in to the workflow before and it results in a double
entry in the event log.  However If I remove the rec. type FM, no event
appears in the log.
 
Do you have any other suggestions?
 
Angie
 
-----Original Message-----
From:   Michael Pokraka [SMTP:MPokraka at samsungsemi.co.uk]
Sent:   Wednesday, December 06, 2000 12:48 PM
To:     SAP-WUG at MITVMA.MIT.EDU
Subject:        Re: no workitems
 
Hi,
What does your event log show for the event - specifically what receiver
type? If it doesn't show your task you wish to start, then your problem's
there.
 
 
If not (though I've not had to work with receiver type FM's) from what I can
gather you still need a triggereing event in your WF.
 
The event linkage basically sets up the link (OK, that was an obvious phrase
:)  Your task still needs the trigger in order to 'react' to receiving this
event so to speak.
 
If you set up a standard linkage (without rec.type FM) to a task and don't
have it as a trigger in the task, it will show up as 'Tasks which do not use
this event' from SWU0.
 
HTH
Michael
 
 
-----Original Message-----
From: Jan, Angeline [ mailto:AJan at KHOV.COM <mailto:AJan at KHOV.COM> ]
Sent: 06 December 2000 16:38
To: SAP-WUG at MITVMA.MIT.EDU
Subject: FW: no workitems
 
 
 
Just to elaborate on the problem stated below:
 
The workflow we're using is being triggered off from a milestone in a
network activity.  No triggering event is inserted in to the workflow as the
event is resolved via the standard object itself.  If you have a look at the
event type linkage table, the object (mlst_netw) has a receiver type FM:
CN_MS_EVENT_RECEIVER_TYPE_GET.  This is the FM that resolves the event.
 
When the network is confirmed (with the milestone) and event is triggered,
but no workitem appears.
 
I've done a SWU0, and none of my tasks associated with the object shows
appears.
 
Any suggestions?
 
Thanks
Angie
 
-----Original Message-----
From:   Jan, Angeline
Sent:   Wednesday, December 06, 2000 10:30 AM
To:     'Workflow'
Subject:        no workitems
 
Hi,
 
I have triggered off a workflow.  There is an event in the log, but no
workitem in the workitem selection log.  I have checked the workflow (SWUD)
and everything is correct.
 
Any suggestions?
 
Thanks
Angie
 
 
 
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the sender or system manager.
 
This footnote also confirms that this email message has been swept
for the presence of computer viruses.
**********************************************************************
 << File: ATT02903.txt >>