Loosing OO References in Workflow

Question

Hello,
I have strange Problem when using ABAP classes in Workflow:
I'm using a persistent class as main object in a workflow definition. The object is created and changed by a small application. The application triggers an OO Event which triggers the workflow and passes the instance to the workflow container - so far everything works fine.
The first task in the workflow calls a change method of the object - which brings up the application where the user can make changes to the object data and finally saves the object. The DB updates work fine and the persistent object is updated correctly.
But when the next task in the worklfow is processed the container element that should contain the reference to the object is initial and the task cannot be processed (errors: (NULL reference).
If I change the task container manually and reenter the object ID, then the task works fine again, but afterwards the reference is lost again...!
I checked the data bindings in all steps (WF->Task->Method) but everything seems correct.
Has anyone experienced that problem?
This issue is pretty urgent for me, as it is the critical component of the current project.
We are working on a 6.20 system.
Thanks in advance for any hint.
Michael

Answer 1

Hi,
I checked again the BI_PERSISTENT~LPOR method and that was really the problem - the field INSTID was initial at that point. I had filled the structure lpor before in a different method, but somehow at that the key values were not filled correctly.
I changed coding in BI_PERSISTENT~LPOR to directly build the key there and now it seems to work fine.
Thanks for the hint - I just did not look in the right place
bye
Michael