<&ELEMENT& not found> in workitem text

Mike Pokraka asap at workflowconnections.com
Wed Apr 26 10:17:09 EDT 2006


Hi Sue,
Good point, auths are a regular culprit, but in this case it's all in DEV
and the odd thing is that it seems to depend on the name of the attribute.
I've renamed it a few times and just can't seem to fathom it.
Thanks for our feedback in any case!
Cheers,
Mike

Sue Doughty wrote:
> I've had this issue if the security on the object data is such that I
> don't have authority to read it.  In the test environment I have SAP ALL
> and can read data that I cannot read in the Quality and PRD systems.  So,
> when I am looking at the workflow log in the Quality or PRD systems, I see
> the data not found message.
>
> Yesterday, we had a workflow that was in an error condition on the Quality
> system.  It had failed on a send mail step. I manually completed that step
> and tried to restart the workflow, but it failed.  The next step, which
> was a condition step, was reading an attribute on the object that I cannot
> view, so I could not restart the workflow because I could not get past the
> condition that was checking the attribute data.  I went to Basis, who has
> all authority, and they could restart the workflow because they had
> authority to read the data.
>
> Hope this helps.
>
> Regards,
>
> Sue T. Doughty
> Workflow Specialist
> Old Dominion Freight Lines, Inc.
> Office:(336)822-5189 Fax:(336)822-5149
> sue.doughty at odfl.com
>
>
>
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu]On Behalf
> Of Mike Pokraka
> Sent: Wednesday, April 26, 2006 8:50 AM
> To: sap-wug at mit.edu
> Subject: <&ELEMENT& not found> in workitem text
>
>
> G'Day folks,
> I have an odd one here - 4.7/620 SP54:
>
> I use an attribute &OBJ.DUE_DATE& in a WI text. It spews out:
> < OBJ.DUE_DATE not found >
>
> It's there, it exists in the container, I've even hardcoded the date in
> there. Clutching at desperate measures I changed it to DATE_DUE and it
> works. Change it back to DUE_DATE and it doesn't.
> Try it on a different system and it works fine both ways....
>
> I've fixed it already, so it's mostly a matter of curiosity. It would be a
> small consolation for the nearly 3 hours spent fighting with it if anyone
> could shed some light.
>
> Cheers,
> Mike Pokraka
> Senior Consultant
> Workflow Connections Ltd.
> Mobile: +44 (0)7786 910 855
>
>
> _______________________________________________
> 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
>




More information about the SAP-WUG mailing list