Message no. OL 826 - EMPLOYEET Not Instantiated

[Dart, Jocelyn]

Sounds like HR Structural authorisations strikes again. 

Check which user was being used at that point in the workflow - they 
may not have access to view that employee. 


Regards,
Jocelyn Dart
Senior Consultant
SAP Australia Pty Ltd.
Level 1/168 Walker St.
North Sydney 
NSW, 2060
Australia
T   +61 412 390 267
M   + 61 412 390 267
E   jocelyn.dart at sap.com
http://www.sap.com

The information contained in or attached to this electronic transmission is confidential and may be legally privileged. It is intended only for the person or entity to which it is addressed. If you are not the intended recipient, you are hereby notified that any distribution, copying, review, retransmission, dissemination or other use of this electronic transmission or the information contained in it is strictly prohibited. If you have received this electronic transmission in error, please immediately contact the sender to arrange for the return of the original documents. 
Electronic transmission cannot be guaranteed to be secure and accordingly, the sender does not accept liability for any such data corruption, interception, unauthorized amendment, viruses, delays or the consequences thereof.
Any views expressed in this electronic transmission are those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views of SAP AG or any of its subsidiaries. SAP AG, its subsidiaries, and their directors, officers and employees make no representation nor accept any liability for the accuracy or completeness of the views or information contained herein. Please be aware that the furnishing of any pricing information/ business proposal herein is indicative only, is subject to change and shall not be construed as an offer or as constituting a binding agreement on the part of SAP AG or any of its subsidiaries to enter into any relationship, unless otherwise expressly stated. 


-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Tom Peou
Sent: Friday, 28 July 2006 4:23 AM
To: sap-wug at mit.edu
Subject: Re: Message no. OL 826 - EMPLOYEET Not Instantiated

Hi Kjetil,

It's a funny problem. When the WF is trigerred, the main object and
the EMPLOYEET objects are instantiated correctly.

Even at the Decision step, the instance of EMPLOYEET is read in
correctly into the task bindings. The problem occurs after a decision
is made, and stops at the send-mail task and produces the 'object does
not exist' error. The WF sits in a status of 'In Process'. The
send-mail task reads in the EMPLOYEET instance for the email body and
recipient.

After investigating the WF log, the diagnosis is: "You tried to create
an instance of the object type EMPLOYEET with the key 1652920060726.
No instance of this kind exists".

However, the instance DOES exist and was never changed as part of the
decision step. The executor of this step is WF-BATCH which has SAP-ALL
authorizations.

Every step leading up to the 'decision result' has been fine. The
EMPLOYEET instance was never modified or re-instantiated.

Yes, I can instantiate EMPLOYEET through SWO1 correctly. The Initiator
of the WF and the user making the decision both have sufficient
authorization.

So, what else can I look at? I've built many workflows and this is the
very first time I've experienced this problem.

Can anyone help please?

Many thanks in advance,
Tom


> ---------- Forwarded message ----------
> From: "Kjetil Kilhavn" <KJETILK at statoil.com>
> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> Date: Thu, 27 Jul 2006 09:23:00 +0200
> Subject: RE: Message no. OL 826 - EMPLOYEET Not Instantiated
> Hmmm.... Can you instantiate the object manually in SWO1?
> Does the executing user have sufficient authorisation?
> --
> Kjetil Kilhavn, Statoil ØFT KTJ BAS DEV SAP
>
>
> > -----Original Message-----
> > From: sap-wug-bounces at mit.edu
> > [mailto:sap-wug-bounces at mit.edu] On Behalf Of Tom Peou
> > Sent: 26. juli 2006 13:16
> > To: sap-wug at mit.edu
> > Subject: Message no. OL 826 - EMPLOYEET Not Instantiated
> >
> > Dear All,
> > I am experiencing a problem on SAP 4.6C for a workflow I've developed.
> > After the decision step I have set up and email task and it
> > passes in an Instance of the EMPLOYEET object into the email.
> > I get an Object does not exist Message no. OL 826 after a
> > "Decision" is made.
> > (Diagnosis: You tried to create an instance of the object
> > type EMPLOYEET with the key 1652920060726. No instance of
> > this kind exists).
> >
> > However, all the emails prior to this are sent fine.
> > The bindings are correct as they are the same as all emails
> > prior to the decision step.
> >
> > What could be the problem?
> >
> > Kind regards,
> > Tom
> > _______________________________________________
> > SAP-WUG mailing list
> > SAP-WUG at mit.edu
> > http://mailman.mit.edu/mailman/listinfo/sap-wug
> >
>

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug