Error OL 808 Object with runtime '0' not defined

[de Valensart Schoenmaeckers, Patrick]

Robin,
 
This is a bug that I experienced with decision tasks, and maybe it also
applies to your task, so I think it is worth a try :
In decision tasks (Standard TS00008267 or copies of that task), the Object
method binding (binding between task-container and
methodparameter-container) should always be blank. When you enter the task
in change mode, the system will automatically put a binding there by
default. The only way not to have such binding is :
 
1. Enter the task in change mode
2. Go in the Binding OM definition
3. Delete the binding via menu path Binding - Delete
4. Go back (F4) twice, and once the systems ask you if you want to save your
changes, say yes.
 
Any other way to save a task will re-put a default binding, so this has to
be done everytime you enter your task in change mode.
 
Hope this will help.
 
Patrick de Valensart
Associate IS Analyst
Philip Morris Benelux M&S
 
 
 
-----Original Message-----
From: Robin Sahasranam [mailto:Rsahasranam at worldbank.org]
Sent: Tuesday, October 16, 2001 3:41 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Error OL 808 Object with runtime '0' not defined
 
 
Flavio,
 
Thanks very much for your response. The OSS Note 0319949 is not relevant to
my
problem or release. The Note is for displaying mail output and applies to
4.5
upwards. I did not find any relevant notes for my release 4.0b.
 
The change I made was to create a new container element, Approver, to
capture
the name of the Workflow Initiator to display in Work Item text for the
task.
The element I am interested in is
&_WORKITEM.WORKITEMFATHER.CREATEDBYUSER.EMPLOYEE.NAME&. I want the workitem
text
to appear as "Trip 123456 for John Doe was approved by Jane Doe", where Jane
Doe
would be the contents of the above variable. But if I use the above element
directly, the Work Item Text for assigning text variables becomes too long.
So I
created a task container element Approver to which I bound the above
element.
Since the length of the new variable &APPROVER& is a lot shorter than the
other
one, I thought this would be a way out. The revised workflow gets the run
time
error OL808 at the step where the foreground task is created. When I undo my
changes, the Workflow again works.
 
I am grateful for any help in resolving this problem.
 
Robin Sahasranam
World Bank
 
 
 
 
                    Flavio Oliveira
                    <oliveiraflavio at hotm        To:
Sap-Wug at Mitvma.Mit.Edu
                    ail.com>                    cc:
                    Sent by: SAP                Subject:     Re: Error OL
808 Object with runtime '0' not defined
                    Workflow
                    <Owner-SAP-WUG at MITVM
                    A.MIT.EDU>
 
 
                    10/16/2001 08:23 AM
                    Please respond to
                    SAP Workflow Users'
                    Group
 
 
 
 
 
 
 
 
At the first look, I thought that the problem could be with the
instantiation of your object. If the WF tries to instantiate it and the
object instance is not found (this verification is normally done by the
ExistenceCheck method), some error message can be sent back. You can try to
verify if the object is being created correctly.
 
But looking at OSS I found the note 0319949 that is about your problem.
 
You can try to look at it too.
 
Regards,
Flavio.
 
>From: Robin Sahasranam <Rsahasranam at worldbank.org>
>Reply-To: SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
>To: SAP-WUG at MITVMA.MIT.EDU
>Subject: Error OL 808 Object with runtime '0' not defined
>Date: Mon, 15 Oct 2001 16:54:28 -0400
>
>I have developed and tested a workflow template in 4.0B which has two
>activities: a background standard task executing sync object method
>followed by
>a foreground task executing a  synch object dialog method. The workflow was
>working fine initially. Then I added a new container element to the dialog
>task
>and completed the binding from workflow and saved and generated the
>workflow.
>
>The revised workflow however goes into error after the background step
>completes. The error message is OL 808 "Object with runtime number '0' not
>defined".  I am not able to figure out what is causing this problem. The
>extended check on the workflow shows no problems.
>
>Your help in resolving this is much appreciated.
>
>Robin Sahasranam
>World Bank
 
 
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp