TS01000051 - Unlock address changes for employee

[Soady, Phil]

This type of activity can occur when the Infotype is deleted outright.
So the task tries to refer to an address that no longer exists.
This could even happen if it is just delimited.
 
Send Endda is in the key.
 
So you workflow using ts01000051 should also have a parallel fork
waiting for the events ADDRESSEMP.requestcancelled, ADDRESSEMP.deleted
and perhaps even ADDRESSEMP.changed.
 
In which cause you may like to gracefully terminate your workflow when
one of these events occurs. (Process control step).
 
hth
 
Phil Soady
Senior Consultant
Business Technologies
SAP Australia
* : 0412 213 079
* : phil.soady at sap.com
 
 
 
 
 
-----Original Message-----
From: Rick Sample [mailto:Rick.Sample at gbe.com]
Sent: Friday, April 18, 2003 2:34 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: TS01000051 - Unlock address changes for employee
 
 
It is in WF, so therefor I am "supposed" to know why these are getting hosed. Ha! Not my stuff but I would like to give someone an answer on why there are errors.
 
I get errors for this task. About all I can do is logically delete after HR does their thing. (whatever that is) Not sure what they are doing or what they are supposed to be doing that cause this error.
 
Any clues would help my first level Admin. Here is the error. I am assuming the users are coming through Portals.
 
Work item 000000023290: Object handle for object cannot be created
 
Workflow 000000023027 wait step 0000000148: Instead of object type 'ADDRESSEMP', 'ADDRESSEMP' expecte Object does not exist