Requisition Release Workflow - "Error Message: OL 826 : Object does not exist "

[Nat 4 Govender]

Hi Vinod,
 
>From our experience we found that this problem was caused due to databa=
se
update being slower that the workflow going to the next step.
 
Regards
Nat Govender
Toyota South Africa
SAP Support  - SAP Workflow
Ext.              : 32645
Direct Line : 031 - 910 2645
Fax              : 031 - 902 9633
E-Mail         : ngovender4 at toyota.co.za
 
 
 
 
                                                                       =
 
             Vinod Ramchandani                                         =
 
             <vinod.ramchandan                                         =
 
             i at patni.com>                                              =
 To
             Sent by: SAP              SAP-WUG at MITVMA.MIT.EDU          =
 
             Workflow                                                  =
 cc
             <Owner-SAP-WUG at MI                                         =
 
             TVMA.MIT.EDU>                                         Subj=
ect
                                       Requisition Release Workflow -  =
 
                                       "Error Message: OL 826 : Object =
 
             2004/02/09 09:20          does not exist "                =
 
             AM                                                        =
 
                                                                       =
 
                                                                       =
 
             Please respond to                                         =
 
               "SAP Workflow                                           =
 
               Users' Group"                                           =
 
             <SAP-WUG at MITVMA.M                                         =
 
                  IT.EDU>                                              =
 
                                                                       =
 
                                                                       =
 
 
 
 
 
Hi all,
 
We have transported Overall Requisition Release Workflow in Production =
few
months back. Workflow is working fine so far.
 
We have come across one incidence where we are getting the above error =
that
says Requisition Object doesnot exist in the system though Requsition
already exists in the system.
 
I have seen Workflow Log and It shows that Workflow was triggered
successfully.
 
Summary of Technical Log is as per shown below.
-----------------------------------------------------------------------=
-----
 
------------------------------------------------
Green Light 1) Workflow for approving Preq nnnnnnnnnn
Green Light -- 1a) username       -  (Sub) workflow
        - date - time
Green Light -- 1b) username       -
              - date - time
Green Light -- 1c) username       -  Work item created after
      -  date - time
Red Light    -- 1d) WF Manager   -  SWP_CALLBACK_WI_DONE         -  dat=
e -
time
Red Light    -- 1e)                       - Message OL 826
-----------------------------------------------------------------------=
-----
 
------------------------------------------------
If I create 'releasestepcreated' (triggering event) again and simulate =
the
steps then i get similar kind of error again.
( I cannot simulate with toggling Container Debugger ON, because this i=
s
not
authorized to anyone in production )
 
Graphical Log shows Green Line upto first condition step.
 
I have define two container steps before moving to first condition step=
.
 
1) Container Step - 1
-- Clearing the Approved Flag
-- where 'Approved Flag' is parameter of Workflow Container
 
2) Container Step - 2
-- Assigning 'Relase Indicator' - value of Requisition object to wf
container parameter 'RELEASE INDICATOR'
 
3) Condition step
-- I am checking the value of 'RELEASE INDICATOR' in this step.
-- May be here Workflow giving the above error.
 
 
This is the first time when we have come across this error, otherwise
Workflow is working fine.
We are not able to simulate the same error in Development System so tha=
t we
can track it from debugging workflow container values.
 
Has anyone faced similar kind of problem before ?
Any kinds of inputs are appericiated.
 
Thanks in advance.
Vinod Ramchandani.
 
                        Vinod Ramchandani
                        SAP Workflow Consultant  Patni Computer Systems=
 
Ltd.
                        Maestros House,
                        Millenium Business Park,
                        MIDC,Mahape,
                        Mumbai - 400701
                        vinod.ramchandani at patni.com  tel:
                              fax:
                              mobile:  +91 (022) 27781008
                              +91 (022) 27781007
                              +91-9892067819
 
 
 
 
            Signature powered by Plaxo Want a signature like this?
 
 
This message is a privileged and private communication and may be
read,copied and used only by the intended recipient (s).
If you are not an intended recipient, please let us know by return
email/fax.Please then delete the message and do not disclose its conten=
ts
to any person.
Neither the sender nor Toyota South Africa Motors accepts any liability=
 
whatsoever as a result of the further dissemination of this message.
Whilst all reasonable steps are taken to avoid corruption of data or
information, we do not accept any liability should such corruption occu=
r.=