Message no. OL 826 - EMPLOYEET Not Instantiated

Fri Jul 28 11:07:14 EDT 2006

When you pass the object ID in your programs it had better include the prefixing zeros I would think. Otherwise I'd be surprised, because SAP *should* in Tom's case interpret the identifier passed as employee number 16529200 and date 60726. Not only is the employee number most likely incorrect, the date isn't perfect either.
-- 
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 Munday,Sherie J.
> Sent: 28. juli 2006 15:23
> To: SAP Workflow Users' Group
> Subject: RE: Message no. OL 826 - EMPLOYEET Not Instantiated
> 
> Tom,
> We have seen this message on many occasions.  It means that 
> some piece of the object is missing.  Use SWO1 and check 
> every attribute on the object, specifically infotype 0105 
> subtype 0010 (email address) if you are trying to send mail.  
> Another common missing piece of info is the date.  We 
> consider this a "dirty data" message.  :o) Also, the 
> additional two zeros are because the object id is an 8 digit 
> number, but we have never had to include the extra zeros when 
> binding into the object.
> Best Wishes,
> Sherie
> 
> -----Original Message-----
> From: sap-wug-bounces at mit.edu 
> [mailto:sap-wug-bounces at mit.edu] On Behalf Of Kjetil Kilhavn
> Sent: Friday, July 28, 2006 1:29 AM
> To: SAP Workflow Users' Group
> Subject: RE: Message no. OL 826 - EMPLOYEET Not Instantiated
> 
> [Changed the subject back to the original] One more 
> possibility to look into, since I don't really have any idea 
> what may be wrong, is the object key. I see in the error 
> message you have included that the employee number is not 
> prefixed with zeros, so if you have copied the error message 
> text correctly it seems you are loosing the first three 
> characters of the employee number somewhere. I just tested 
> EMPLOYEET here with an invalid employee number, and the error 
> message text includes two zeros in front of my six-digit test 
> employee number.
> --
> 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: 27. juli 2006 20:21
> > To: sap-wug at mit.edu
> > Subject: Re: SAP-WUG Digest, Vol 20, Issue 79
> > 
> > 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
> > 
> 
> 
> -------------------------------------------------------------------
> The information contained in this message may be CONFIDENTIAL 
> and is intended for the addressee only. Any unauthorised use, 
> dissemination of the information or copying of this message 
> is prohibited. If you are not the addressee, please notify 
> the sender immediately by return e-mail and delete this message.
> Thank you.
> 
> _______________________________________________
> 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
> 


-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you.