<div dir="ltr"><div>Hi Harish,</div>
<div> </div>
<div>FM parameters cannot be fixed, in production system orgunit would be different.So you program should need to find out the orgunit itself before sending it to the RH_STRUC_GET. There are manu FM's which are giving the list of orgunits.you can try RH_READ_OBJECT, i forget the exact name.simply search for it.</div>
<div> </div>
<div>Regards,</div>
<div>Bhupinder <br><br></div>
<div class="gmail_quote">On Sat, Jul 17, 2010 at 7:13 PM, harishraj <span dir="ltr"><<a href="mailto:harishraj2805@gmail.com">harishraj2805@gmail.com</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">Hello Yegorm,<br><br>Thank you very much for your kind help.<br><br>Yes, the evaluation path B003 provides me the list of positions under the<br>
organizational unit. I have tested this with the function module suggested<br>by you; it is providing me the list of positions under the org unit.<br><br>Sorry to trouble you again, but the function module RH_STRUC_GET receives<br>
the object id as parameter, so I have to give my org unit object ID as<br>parameter, when I transport the org unit to production environment, should I<br>change function module parameter?<br><br>Thanks<br>Harish<br>
<div>
<div></div>
<div class="h5"><br>-----Original Message-----<br>From: <a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a> [mailto:<a href="mailto:sap-wug-bounces@mit.edu">sap-wug-bounces@mit.edu</a>] On Behalf Of<br>yegorm<br>
Sent: Saturday, 17 July 2010 2:24 PM<br>To: SAP Workflow Users' Group<br>Subject: Re: Agent Detemination using Org Structure<br><br>Hello, Harish!<br><br>As i get it, here is what you need:<br><br>input: a purchase org, a merchandise category, an org unit<br>
output:<br> list of positions<br>requierment:<br>resulting list should be defined as the intersection of two lists:<br>1) positions attached to given purchase org or merchandise category<br>2) positions belonging to given org unit<br>
<br>To get the second list you can use fm RH_STRUC_GET with an appropriate<br>evaluation path (something like O-O-S - I'm sorry I don't have access<br>to a sap system right now to give you exact name. you can test if you<br>
chose the right eval path in transaction PPST)<br><br><br><br>On Sat, Jul 17, 2010 at 1:09 AM, harishraj <<a href="mailto:harishraj2805@gmail.com">harishraj2805@gmail.com</a>> wrote:<br>> Hello All,<br>><br>><br>
><br>> We are planned use org structure (purely for workflow) for agent<br>> determination in our workflow. We have more than 50 positions attached to<br>> different org unit.<br>><br>> For Example<br>><br>
> Org Unit A<br>><br>> - Position A1<br>><br>> - Position A2<br>><br>> - Position A3<br>><br>> Org Unit B<br>><br>> - Position B1<br>><br>> - Position B2<br>
><br>> - Position B3<br>><br>><br>><br>> Within the Org Unit, the positions will be attached to SAP Business Object<br>> like Purchase Org, Merchandise Category, etc.<br>><br>><br>><br>
> And we are planning to use the custom function module to determine the<br>> position attached purchase org and merchandise category, up to this point<br>> everything works fine. But here the challenge is we want only the<br>
positions<br>> under Org Unit A having relevant purchase org and merchandise category,<br>but<br>> the custom function module will determine all positions having these two<br>> parameters across all org units.<br>
><br>><br>><br>> Is there any best way to determine the agent for this scenario without hot<br>> coding Org Unit. Currently we are exploring other possibility of attaching<br>> custom attribute to position to identify it is belongs to Org Unit A or B<br>
> etc. Or following naming convention against org unit and filtering<br>positions<br>> within org unit and applying the objects search.<br>><br>><br>><br>> Apologise for lengthy question.<br>><br>><br>
><br>> I greatly appreciate your valuable suggestions and feedbacks.<br>><br>><br>><br>> Thanks<br>><br>> Harish<br>><br>><br>><br>><br>><br>> _______________________________________________<br>
> SAP-WUG mailing list<br>> <a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br>> <a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
><br>><br><br>_______________________________________________<br>SAP-WUG mailing list<br><a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
<br><br>_______________________________________________<br>SAP-WUG mailing list<br><a href="mailto:SAP-WUG@mit.edu">SAP-WUG@mit.edu</a><br><a href="http://mailman.mit.edu/mailman/listinfo/sap-wug" target="_blank">http://mailman.mit.edu/mailman/listinfo/sap-wug</a><br>
</div></div></blockquote></div><br></div>