Packages & Application components

[Michael Pokraka]

Hmmm, I suppose one reply in nearly 4 weeks does constitute the opinion o=
f
the majority :-)  I guess the reality is that most people don't bother wi=
th
separating functional areas into packages.
 
I would agree with you, and have only had this discussion yesterday. Once
again I'm faced with a 'everyone else just uses the same dev class for
everything' situation however, so it's back to a single dev class for all
workflow stuff for this project.
 
Thanks for the feedback.
Cheers
Mike
 
Kjetil Kilhavn wrote:
> I try to put it in the same development class as the other solutions in
> that area. For instance, say we have made a solution for individual
> development plans and they want a workflow for that. I would find it
> natural that the workflow was put in the same development class as the
> other code for individual development plans. Of course this is not alwa=
ys
> possible, but at least I think it is the ideal solution. The developmen=
t
> class should contain related solutions.
>
> Different workflows don't really have anything more in common than
> different function modules or different programs using batch input. No-=
one
> would think of putting all those in the same development class just bec=
ause
> they use a certain technique.
> --
> Kjetil Kilhavn
>
>
>
>
>                     Michael Pokraka
>                     <workflow at quirky.me.        To:
> SAP-WUG at MITVMA.MIT.EDU
>                     uk>                         cc:     (bcc: Kjetil
> Kilhavn)
>                     Sent by: SAP                Subject:     Packages &
> Application components
>                     Workflow
>                     <Owner-SAP-WUG at MITVM
>                     A.MIT.EDU>
>
>
>                     28.06.2004 19:31
>                     Please respond to
>                     "SAP Workflow Users'
>                     Group"
>
>
>
>
>
>
> Hi all,
> I've a small opinion poll: Does anyone actually use different packages
> (development classes) & application components for their workflow
> development? If so, what strategy do you use?
> I haven't seen that much 'real' use of packages / development classes -=
 WF
> tends to just use one package and that's the end of it.
> In order to get custom WF's into the application hierarchy however, one
> would have to create and assign packages for each WF that's in a differ=
ent
> area (SD, MM, FI-AP etc...). Another approach would be to assign WF's t=
o a
> dev class / package belonging to the module specialists rather than hav=
e
> any
> workflow-specific ones.
> Does anyone follow either of these strategies? Is it worth the effort j=
ust
> for the benefit of being able to find the flows via the application
> hierarchy?
>
> Any thoughts appreciated,
> Cheers
> Mike
>
>
>
>
> -------------------------------------------------------------------
> 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 th=
e
> addressee, please notify the sender immediately by return e-mail and de=
lete
> this message.
> Thank you.
>
>