WF task not a potential task to be started

Sat Jul 7 13:31:45 EDT 2001

I figured out why the Event Simulation (SWU0) was not showing that the WF would
be Successfully started, after debugging the report. It turns out that the
report does an authorization check (function RH_BASE_AUTHORITY_CHECK). As I did
not have the auth that this function checks, the result of the report shows that
WF task will not be started.

Actually, everything is fine and workflow did start up correctly when the
application went live. Obviously WF-BATCH userid which starts the workflow has
all the necessary authorizations.

However, I believe it doesn't make sense to do this auth check in a simulation
report run. The report is run just to check if every thing is OK with the WF
task, event and linkage. Somebody running this report is not actually starting
the workflow, just verifying.

Thank you all, esp. Jocelyn and Stefan, for your helpful tips.

                    "Dart,
                    Jocelyn"             To:     "'Rsahasranam at Worldbank.Org'" <Rsahasranam at Worldbank.Org>
                    <jocelyn.dart        cc:
                    @sap.com>            Subject:     RE: WF task not a potential task to be started

                    07/04/2001
                    07:52 PM

Hi Robin,
It's worth trying that.
Unless you are using a check function module, I'd suggest
deleting the entry in SWE2, then reactivating from the workflow
triggering event section so that the SWE2 entry is regenerated cleanly.

If it still doesn't transport cleanly - try doing the same in production.

Regards,
Jocelyn.

-----Original Message-----
From: Rsahasranam at worldbank.org [mailto:Rsahasranam at worldbank.org]
Sent: Thursday, 5 July 2001 4:41 AM
To: Dart, Jocelyn
Subject: Re: WF task not a potential task to be started

Hi Jocelyn,

The event linkage looks OK. SWE2 shows an entry in the Event Linkage table.
The
triggering event in the Workflow definition also shows that it is activated.
Finally Event Simulation shows no errors. Do you think deactivating and the
reactivating the linkage in Development and retransporting might solve the
problem?

Thank you for your reply and am grateful for any other assistance you can
provide.

(See attached file: EvtLinkage.gif)(See attached file: SWE2.gif)(See
attached
file: EventSim.gif)

                    "Dart, Jocelyn"

                    <jocelyn.dart at sap.co        To:
Sap-Wug at Mitvma.Mit.Edu
                    m>                          cc:

                    Sent by: SAP                Subject:     Re: WF task not
a potential task to be started
                    Workflow

                    <Owner-SAP-WUG at MITVM

                    A.MIT.EDU>

                    07/03/2001 10:25 PM

                    Please respond to

                    SAP Workflow Users'

                    Group

Hi Robin,
I agree with Stefan, your event linkage has not been created correctly.
Activate the event linkage from your Workflow > Triggering events section
and try again.
Regards,
Jocelyn.

-----Original Message-----
From: Baeuerle, Stefan
Sent: Wednesday, 4 July 2001 1:06 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: WF task not a potential task to be started

 Hi Robin,

it look like the event is not defined at your task WS98900016 but is entered
in the event-linkage-table (SWE2 or SWETYPV). Please make sure that the
event is specified at the task.

best regards,
Stefan

-----Original Message-----
From: Robin Sahasranam
To: SAP-WUG at MITVMA.MIT.EDU
Sent: 03.07.01 14:57
Subject: Re: WF task not a potential task to be started

Hi Jocelyn,

Thank you for taking the time to reply. I hope you don't mind my direct
response
to you, rather than via the list server.

Event Simulation does not show any exception codes on the right. (See
attached
file: EventSim.gif)

We do have other workflows productive on a 4.0b client. All the
workflows are
custom built and are of the type WF and TS. The new workflow I am
building is of
the type WS and T, my first attempt at these types. Since WF and TS are
no
longer supported in 4.6, we are now gradually moving our workflows to
types WF
and TS. We have had no problems with the WF and TS workflows, in
transporting or
activating them. I have tried every diagnostic step that I am aware of
and can't
find the reason Event Simulation won't work.

I am grateful for any help you can provide.

Robin Sahasranam

                    "Dart, Jocelyn"
                    <jocelyn.dart at sap.co        To:
Sap-Wug at Mitvma.Mit.Edu
                    m>                          cc:
                    Sent by: SAP                Subject:     Re: WF task
not a potential task to be started
                    Workflow
                    <Owner-SAP-WUG at MITVM
                    A.MIT.EDU>

                    07/02/2001 08:27 PM
                    Please respond to
                    SAP Workflow Users'
                    Group

Hi Robin,
Event Simulation gives you a one-character code to the right of each
unsuccessful workflow explaining why it could not be started.
At the bottom of the report is a list of what these codes mean.
So have a look and see what the simulation is saying is the problem?

I assume you already have other workflows in this system/client and
you have checked the workflow runtime environment is operational
through transaction SWU3?
Regards,
        Jocelyn Dart
Consultant (BBP, Ecommerce, Internet Transaction Server, Workflow)
SAP Australia
Email jocelyn.dart at sap.com <mailto:jocelyn.dart at sap.com>
Tel: +61 412 390 267
Fax: +61 2 9935 4880

-----Original Message-----
From: Robin Sahasranam [mailto:Rsahasranam at worldbank.org]
Sent: Tuesday, 3 July 2001 5:52 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: WF task not a potential task to be started

I am almost ready to implement a new Workflow task (WS).  However, the
Event
Simulation for the task in the Production client shows as "Other
receivers -
Tasks  which do not use this event". In the Development and Integrated
Test
clients the Event Simulation for the task shows as "Potential tasks to
be
started - Successfully started".

The task has been tested succesfully in Development and Integrated Test
client.
All the transports to the Production client have been successfully
imported.
I
have run all the diagnostic steps, consistency checks on objects and
tasks,
generated the business objects, verified  the event linkage is enabled
and
the
task is activated and refreshed the org. environment.  No problems were
reported
in any diagnostic step. However the event simulation still shows the
workflow as
"Other receivers - Tasks  which do not use this event". I did not have
to do
anything special in the Integrated Test client, for the workflow to be
started.

Will the workflow be successfully started when the triggering event is
fired
when the application goes live? Do I have to do anything else to show
that
the
workflow will be Successfully started in the Event Simulation.?

Thank you for your assistance.

 <<EventSim.gif>>