Agent Detemination using Org Structure

[Bhupinder]

Hi Harish,

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.

Regards,
Bhupinder

On Sat, Jul 17, 2010 at 7:13 PM, harishraj <harishraj2805 at gmail.com> wrote:

> Hello Yegorm,
>
> Thank you very much for your kind help.
>
> Yes, the evaluation path B003 provides me the list of positions under the
> organizational unit. I have tested this with the function module suggested
> by you; it is providing me the list of positions under the org unit.
>
> Sorry to trouble you again, but the function module RH_STRUC_GET receives
> the object id as parameter, so I have to give my org unit object ID as
> parameter, when I transport the org unit to production environment, should
> I
> change function module parameter?
>
> Thanks
> Harish
>
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of
> yegorm
> Sent: Saturday, 17 July 2010 2:24 PM
> To: SAP Workflow Users' Group
> Subject: Re: Agent Detemination using Org Structure
>
> Hello, Harish!
>
> As i get it, here is what you need:
>
> input: a purchase org, a merchandise category, an org unit
> output:
>  list of positions
> requierment:
> resulting list should be defined as the intersection of two lists:
> 1) positions attached to given purchase org or merchandise category
> 2) positions belonging to given org unit
>
> To get the second list you can use fm RH_STRUC_GET with an appropriate
> evaluation path (something like O-O-S - I'm sorry I don't have access
> to a sap system right now to give you exact name. you can test if you
> chose the right eval path in transaction PPST)
>
>
>
> On Sat, Jul 17, 2010 at 1:09 AM, harishraj <harishraj2805 at gmail.com>
> wrote:
> > Hello All,
> >
> >
> >
> > We are planned use org structure (purely for workflow) for agent
> > determination in our workflow. We have more than 50 positions attached to
> > different org unit.
> >
> > For Example
> >
> > Org Unit A
> >
> > -          Position A1
> >
> > -          Position A2
> >
> > -          Position A3
> >
> > Org Unit B
> >
> > -          Position B1
> >
> > -          Position B2
> >
> > -          Position B3
> >
> >
> >
> > Within the Org Unit, the positions will be attached to SAP Business
> Object
> > like Purchase Org, Merchandise Category, etc.
> >
> >
> >
> > And we are planning to use the custom function module to determine the
> > position attached purchase org and merchandise category, up to this point
> > everything works fine. But here the challenge is we want only the
> positions
> > under Org Unit A having relevant purchase org and merchandise category,
> but
> > the custom function module will determine all positions having these two
> > parameters across all org units.
> >
> >
> >
> > Is there any best way to determine the agent for this scenario without
> hot
> > coding Org Unit. Currently we are exploring other possibility of
> attaching
> > custom attribute to position to identify it is belongs to Org Unit A or B
> > etc. Or following naming convention against org unit and filtering
> positions
> > within org unit and applying the objects search.
> >
> >
> >
> > Apologise for lengthy question.
> >
> >
> >
> > I greatly appreciate your valuable suggestions and feedbacks.
> >
> >
> >
> > Thanks
> >
> > Harish
> >
> >
> >
> >
> >
> > _______________________________________________
> > 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
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20100717/965da817/attachment.htm