Org Management for custom approval structures

Mark Pyc mark.pyc at gmail.com
Wed May 11 05:53:54 EDT 2005


Side question / Clafication:

Does anyone make use of parallel plan versions? I know that you can
navigate to the config for maintaining the plan version but I was lead
to believe that there is only 1 active plan version. That is, that WF
will always use the current HR active plan version.

However as Kjetil points out the code does support two versions. These
are implemented in table T77S0 with a SEMID of 'PLOGI' for HR and
'WORKF' for workflow. The help in SWU3 only mentions the use of PLOGI
and states that only 1 version can be active.

Has anyone made successful use of this split version functionality?

And I'm not talking about two trees in the same forrest - two
structures within the same plan version - I'm interested in completely
seperate and concurrent plan versions.

Thanks,
Mark

On 5/11/05, Kjetil Kilhavn <kjetilk at statoil.com> wrote:
> 
> By "role function" I mean the function module used in a role of type F. I
> assume that is what you have already implemented (you called them "custom
> function modules for agent determination"). We use such functions to look
> for exception specifications before using the standard OM information. It
> is a bit different from your requirement as it seems you will normally not
> be using the standard OM information.
> 
> I'm afraid I don't know anything about your follow-up question. I would
> *assume* you don't have to think about it, because SAP takes care of all
> that for you.
> --
> Kjetil Kilhavn
> 
>                    "Kunkel, Susan"
>                    <skunkel at ci.tac        To:     "SAP Workflow Users' Group" <sap-wug at mit.edu>
>                    oma.wa.us>             cc:     (bcc: Kjetil Kilhavn)
>                    Sent by:               Subject:     RE: Org Management  for custom approval structures
>                    sap-wug-bounces
>                    @mit.edu
> 
>                    09.05.2005
>                    19:31
>                    Please respond
>                    to "SAP
>                    Workflow Users'
>                    Group"
> 
> The business rules for the process require that journal entries (that can
> be
> created in any part of our organization) be approved by a member of the
> Finance Department. For example: A document creator may be in the Police
> Department but the direct supervisor (chief position) in Police does not
> have the knowledge to quality check this financial document, therefore,
> expertise by a financial supervisor is desired.
> 
> I think I understand your comments in the first paragraph but would you
> explain further your meaning of "role function"?
> 
> And...a follow-up question...
> 
> There are roles and tasks associated with this approval workflow. Would the
> roles and tasks be maintained in the active or workflow plan version of OM?
> 
> Susan Kunkel
> 
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
> Kjetil Kilhavn
> Sent: Sunday, May 08, 2005 10:42 PM
> To: SAP Workflow Users' Group
> Subject: Re: Org Management for custom approval structures
> 
> We use plan version 01 for workflow as well as for other purposes.
> However, since RH_GET_PLVAR (which calls RH_GET_ACTIVE_WF_PLVAR, which
> calls
> RH_INTERNAL_ACTIVE_WF_PLVAR, which actually selects something instead of
> calling another function or form!) returns two plan versions, one for WF
> and
> one "regular" it seems it is just a matter of setting a customising option
> (and double maintenance).
> 
> What I have trouble understanding (assuming you already have OM in use) is
> why you wouldn't use the OM data in the active plan version. There may be a
> good reason, but the disadvantage of double maintenance is a big one.
> Instead of maintaining the data in a Z-table as today you could perhaps
> create a role function which finds the same information from your existing
> OM data. But then again, it is hard to understand the thinking that goes on
> in Washington. It is the home of Microsoft.
> 
> Good luck.
> --
> Kjetil Kilhavn
> 
>                    "Kunkel, Susan"
> 
>                    <skunkel at ci.tac        To:     Workflow Listserv
> <SAP-WUG at MIT.EDU>
>                    oma.wa.us>             cc:     (bcc: Kjetil Kilhavn)
> 
>                    Sent by:               Subject:     Org Management  for
> custom approval structures
>                    sap-wug-bounces
> 
>                    @MIT.EDU
> 
>                    03.05.2005
> 
>                    22:13
> 
>                    Please respond
> 
>                    to "SAP
> 
>                    Workflow Users'
> 
>                    Group"
> 
> Hello all,
> 
> I am interested in using Org Management (OM) to set up another version to
> support a custom approval structure for Workflow. Our company is reluctant
> to adopt this way of maintaining an approval structure. The data is now
> kept
> in a custom table with custom function modules for agent determination.
> 
> If there is anyone out there using an alternate plan version in OM for a
> workflow approval structure? If so, I'd like to discuss the pros and cons
> of
> this type of solution.
> 
> Thanks!
> 
> Susan Kunkel
> City of Tacoma_______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
> 
> -------------------------------------------------------------------
> The information contained in this message may be CONFIDENTIAL and is
> intended for the addressee only. Any unauthorised use, dissemination of the
> information or copying of this message is prohibited. If you are not the
> addressee, please notify the sender immediately by return e-mail and delete
> this message.
> Thank you.
> 
> _______________________________________________
> 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
> 
> -------------------------------------------------------------------
> The information contained in this message may be CONFIDENTIAL and is
> intended for the addressee only. Any unauthorised use, dissemination of the
> information or copying of this message is prohibited. If you are not the
> addressee, please notify the sender immediately by return e-mail and delete
> this message.
> Thank you.
> 
> _______________________________________________
> 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