Restart without error status !!

[Dart, Jocelyn]

Hi Parag Joshi,
I don't think HR structural authorisations show in USR07
- they are a special HR thing that would result in data not
being available rather than any authorisation error appearing.
Talk to your HR people.
Jocelyn
 
-----Original Message-----
From: Parag Joshi [mailto:paragjoshi at ureach.com]
Sent: Monday, 19 August 2002 5:13 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Restart without error status !!
 
 
Hi Jocelyn,
 
Thanks for the input again.
 
Though manual change to the WI to 'ERROR' and then restarting
does work. But I am ending up doing for all triggerred WFs.
 
Meanwhile, you brought up ineteresting point about
authorisations check for dialog users but there is no trace of
any authorization failures for any of them. I checked USR07 for
all users in WF.
 
To re-affirm, this happens in production only. So it should be
authorization bug somewhere.
 
Thanks again.
 
Regards,
Parag Joshi.
Workflow Consultant.
Representing SAP-SI America.
 
 
 
 
 
________________________________________________
Get your own "800" number
Voicemail, fax, email, and a lot more
http://www.ureach.com/reg/tag
 
 
---- On    , Dart, Jocelyn (jocelyn.dart at sap.com) wrote:
 
> Hi Parag Joshi,
> Yes that sounds suspiciously like a binding issue to me
> as well.  As its about an HR object there is a chance it
could also be
> a knock on effect of HR structural authorisations if you have
that
> turned on, i.e. the user under whose authority the step was
created/executed
> did not have sufficient structural authorisation for the
object instance
> to be created correctly.   You might want to check the
workflow log
> to see whose authority was being used at the time - don't
assume its
> WF-BATCH even for a background step as the advance with
dialog option
> can affect it.
> But glad you fixed your current problem.
> Regards,
>         Jocelyn Dart
> Consultant (SRM, EBP, Workflow)
> and co-author of the book
> "Practical Workflow for SAP"
> SAP Australia
> email: jocelyn.dart at sap.com
> phone: +61 412 390 267
> fax:   +61 2 9935 4880
>
>
>
>
> -----Original Message-----
>> From: Parag Joshi [mailto:paragjoshi at ureach.com]
> Sent: Thursday, 15 August 2002 10:06 PM
> To: SAP-WUG at MITVMA.MIT.EDU
> Subject: Re: Restart without error status !!
>
>
> Hi Jocelyn,
>
> Thanks for the input. I checked the deadlock race, no luck.
> Object 'Employeet' is an attribute of calling object BUS2089.
> So the instance of the object EMPLOYEET is created when event
> BUS2089.CREATED is triggered. Infact, it successfully pulls
> data from the instance and pushes to other earlier steps.
>
> I am suspecting binding is a problem, though it worked
> successfully in DEV and test environments. Nor does it show up
> as any binding errors.
>
> I had tried SWPC, but did not select the work item. Finally, I
> manually changed the status of the work item through
> SWW_WI_STATUS_CHANGE_NEW to ERROR. Restarted through SWPR and
> it worked.  WF completed successfully.
>
>
> Regards.
>
> Parag Joshi.
> Workflow Consultant.
> Re-presenting SAP-SI America.
>
>
>
>
>
> ________________________________________________
> Get your own "800" number
> Voicemail, fax, email, and a lot more
> http://www.ureach.com/reg/tag
>
>
> ---- On    , Dart, Jocelyn (jocelyn.dart at sap.com) wrote:
>
> > Hi Parag,
> > Suggest you check the workflow container - could be a
> formatting issue or
> > a bad binding.
> >
> > Also check whether the object was created new - might be a
> deadlock race
> > issue (i.e. step tried to run before object was actually
> there).
> >
> > The greater probablity with a new workflow is that it is a
> design fault
> > that wasn't picked up during testing, so suggest you check
> what is
> > instantiating the object instance and why.
> >
> > To restart you could try SWPC (restart after system crash)
or
> SWI1
> > Edit > work item and just execute the workflow instance.
> >
> > Regards,
> >         Jocelyn Dart
> > Consultant (SRM, EBP, Workflow)
> > and co-author of the book
> > "Practical Workflow for SAP"
> > SAP Australia
> > email: jocelyn.dart at sap.com
> > phone: +61 412 390 267
> > fax:   +61 2 9935 4880
> >
> >
> >
> >
> > -----Original Message-----
> > From: Parag Joshi [mailto:paragjoshi at ureach.com]
> > Sent: Thursday, 15 August 2002 12:10 PM
> > To: SAP-WUG at MITVMA.MIT.EDU
> > Subject: Restart without error status !!
> >
> >
> > Folks,
> >
> > I have a interesting problem. Never came across like this
> > before.
> >
> > A new workflow that was transported to production, a step
> > failed abruptly after a decision task. Interestingly, the
> > workflow does not assume 'error' status. So it does not show
> up
> > on 'restart after error' screen. Overall status of the
> workflow
> > is 'started' !!!?!!!
> >
> > Secondly, the error is that 'instance of the
object 'EMPLOYEET
> > with the key 105020020814 could not be created'. When I
> > manually tried to create the instance with the same key
> through
> > SWO1 it worked.
> >
> > * Any idea how to restart without in error.
> > * Any idea about the object problem.
> >
> >
> > Regards.
> >
> > Parag Joshi.
> >
> >
> > ________________________________________________
> > Get your own "800" number
> > Voicemail, fax, email, and a lot more
> > http://www.ureach.com/reg/tag
> >
> >
>
>