Modification of SAP standard solution for payment blocks

[Michael Pokraka]

Hi Kjetil,
There was a discussion here a short while ago about whether anyone really
uses the SAP standard workflows. The general consensus was that SAP's are
really only guidelines, so copying the flow shouldn't be a problem -
probably even a good thing since you may be able to iron out any 'odditie=
s'.
 
I certainly have only used a standard flow once in nearly 5 years of
workflowing, and that time I got burnt.
 
I've found the original mail that started it, quoted below.
Cheers
Mike
 
Subject:   Discussion: Standard Workflow Templates Purpose
From:   "Paul Batey" <paul.batey at intelligroup.com.au>
Date:   Thu, April 15, 2004 2:53 pm
To:   SAP-WUG at MITVMA.MIT.EDU
 
Evening all,
 
I am hoping to glean the purpose of the SAP standard templates.  To me
they are basic examples to point you in the right direction for your own
further development.  I have come across several specs recently that
start off...
 
"This is a simple workflow, just copy WS######## and allow for
escalation, changes, what the weather is, and then bung in some
completely different text for the task description"
 
By the time you have copied a standard template and wedged in the client
requirements it, to me, is always quicker to get the gist from the
standard, but then build it from scratch. This may not be true for the
backgroundy idoc type of things, but I have never been able to take a
standard and just switch it on.  This makes the whole idea of
SWDD_CONFIG meaningless, and a pain when you train people to say
SWDD_CONFIG is wonderful in BIT600, because it is never used.
 
Any thoughts folks?
 
Cheers,
 
Paul
 
 
 
 
 
 
 
Kjetil Kilhavn wrote:
> In our company we use standard IT solutions. Well, nearly. Now they wan=
t to
> implement payment block with workflow release for customer credit memos=
 (in
> FI). However, they want to be able to differ on sales organisation with=
in a
> company code. I have said that this is not possible, at least not witho=
ut a
> modification of SAP standard, since one company code can only have one
> workflow variant. We can have different procedures based on document ty=
pe
> etc, but not based on sales organisation (as far as I have been able to
> find out).
>
> Using approval groups is not an option since they don't register that
> information on the customer. Perhaps we could talk them into this one..=
..
>
> Have anyone tried to modify the standard solution for FI automatic paym=
ent
> blocks? I suppose the easy route would be to modify the solution which
> finds the workflow variant, extending that with new criteria to be able=
 to
> differ on e.g. sales organisation. However, I fear endless trouble.
>
> We are on R/3 release 4.6C if it matters.
> --
> Kjetil Kilhavn
>
> -------------------------------------------------------------------
> 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.
>
>