<html>
<P>Mike, </P>
<P>just a suggestion....but did you try setting your condition to Business Partner in the Role of Employee, rather than User? US is associated with BP in that role only. In EBP SRM, when you "ale" Persons and attach them to Positions, you are also creating two more behind-the-scenes objects: Centeral Persons (CP) and Business Partners (BP), so maybe you'll find your attributes searching for CP or BP rather than among A, C, O, S, or US...<BR>
<BR>
<BR>
<BR>
<B>On Mon Sep 12 9:09 , 'Mike Pokraka' <wug.replies@workflowconnections.com> sent:<BR>
<BR>
</P></B>
<BLOCKQUOTE style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #5167c6 2px solid; MARGIN-RIGHT: 0px">Grumble... after testing this on another system I found the answer to<BR>
seeing OBJ.ATTR having a few entries but still testing false for their<BR>
existence. Since it's a sneaky combo of two buglets (= "not sure if it's a<BR>
bug or not") I thought I'd share it:<BR>
<BR>
There's an evaluation path WF_ORGUS ("All users for an object of type A,<BR>
C, O, S, or US"). Fairy nuff methinks, you feed it any org object and it<BR>
spits out US-users, right? Not quite: we tested it no prob, then we<BR>
introduced persons. A position with a person also returns the "user" 'P<BR>
12345678' as well as the US-userid. Hmmm... evaluation path doesn't quite<BR>
do what it says on the tin.<BR>
<BR>
Enter a multiline attribute of USR01 objects: a piece of code uses<BR>
WF_ORGUS, doesn't check for 'US' and generates a couple of empty objects<BR>
along with real ones. However, it seems that EX in a condition actually<BR>
checks the object instance of the first element in the multliline - so<BR>
even though there are a few objects in the multline tab it still fails<BR>
because of the empty first object. Another 'Hmmm'... should EX fail<BR>
because of a blank first element in a table?<BR>
<BR>
Cheers<BR>
Mike<BR>
<BR>
Mike Pokraka wrote:<BR>
<FONT color=red>> Hi all,</FONT><BR>
<FONT color=red>> Someone please tell me I'm not going insane:</FONT><BR>
<FONT color=red>></FONT><BR>
<FONT color=red>> &MULTILINEOBJ& EX --> True</FONT><BR>
<FONT color=red>> &OBJECT.MULTILINEOBJ& EX --> False</FONT><BR>
<FONT color=red>></FONT><BR>
<FONT color=red>> In both cases multilineobj contains data, the only difference is that it's</FONT><BR>
<FONT color=red>> a container element in one case and an attribute in another. Quite</FONT><BR>
<FONT color=red>> straightforward to test in the condition editor using the test feature.</FONT><BR>
<FONT color=red>></FONT><BR>
<FONT color=red>> Anyone seen this?</FONT><BR>
<FONT color=red>> Cheers</FONT><BR>
<FONT color=red>> Mike Pokraka</FONT><BR>
<FONT color=red>> Senior Consultant</FONT><BR>
<FONT color=red>> Workflow Connections Ltd.</FONT><BR>
<FONT color=red>> Mobile: +44 (0)7786 910 855</FONT><BR>
<FONT color=red>> _______________________________________________</FONT><BR>
<FONT color=red>> SAP-WUG mailing list</FONT><BR>
<FONT color=red>> <A href="javascript:top.opencompose('SAP-WUG@mit.edu','','','')">SAP-WUG@mit.edu</A></FONT><BR>
<FONT color=red>> <A href="parse.pl?redirect=http%3A%2F%2Fmailman.mit.edu%2Fmailman%2Flistinfo%2Fsap-wug" target=_blank><FONT color=red>http://mailman.mit.edu/mailman/listinfo/sap-wug</FONT></A></FONT><BR>
<FONT color=red>></FONT><BR>
<BR>
<BR>
Mike Pokraka<BR>
Senior Consultant<BR>
Workflow Connections Ltd.<BR>
Mobile: +44 (0)7786 910 855<BR>
_______________________________________________<BR>
SAP-WUG mailing list<BR>
<A href="javascript:top.opencompose('SAP-WUG@mit.edu','','','')">SAP-WUG@mit.edu</A><BR>
<A href="parse.pl?redirect=http%3A%2F%2Fmailman.mit.edu%2Fmailman%2Flistinfo%2Fsap-wug" target=_blank><FONT color=red>http://mailman.mit.edu/mailman/listinfo/sap-wug</FONT></A><BR>
<BR>
</BLOCKQUOTE>
</html><BR>