BB/EBP-Workflow - Change accounting data as a workflow step

Dart, Jocelyn jocelyn.dart at sap.com
Mon May 7 22:12:25 EDT 2001


Hi Markus,=20
Yes you're right - I don't recommend that.  There's a lot of defaults =
set up
 
based on the current user's attributes when you change a shopping =
basket,=20
if your account assignment changer and your requestor have very =
different
attributes you may get weird results. =20
Even though much is coming from the existing shopping basket when you =
are in
 
change mode, not all defaults do.  Plus there are a significant number =
of=20
current user attribute reads that happen deeper down e.g. in "procdoc"
functions
or in meta-BAPIs, which would be even more tricky to navigate - all of =
which
 
assume only the requestor touches the shopping basket directly.=20
Best left alone. =20
Regards,
        Jocelyn Dart=20
Consultant (BBP, Ecommerce, Internet Transaction Server, Workflow)=20
SAP Australia
Email jocelyn.dart at sap.com <mailto:jocelyn.dart at sap.com>=20
Tel: +61 412 390 267
Fax: +61 2 9935 4880
 
 
-----Original Message-----
From: Markus Brahm [mailto:mbrahm at cscploenzke.de]
Sent: Tuesday, 8 May 2001 2:55 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: BB/EBP-Workflow - Change accounting data as a workflow =
step
 
 
Hello Jocelyn,
 
an other thinking I had was to change the owner of the shopping basket =
for
a short moment to allow an accounting person to use the "transaction" =
you
mentioned as not usable. That is a bit weird and I haven=B4t tested it =
yet,
but do I understand you correctly that you wouldn=B4t recommend this =
way.
 
Thanks a lot,
 
Markus
 
 
 
 
 
"Dart, Jocelyn" <jocelyn.dart at sap.com>@MITVMA.MIT.EDU> on 07.05.2001
03:51:36
 
Please respond to SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
 
Sent by:  SAP Workflow <Owner-SAP-WUG at MITVMA.MIT.EDU>
 
 
To:   SAP-WUG at MITVMA.MIT.EDU
cc:
 
Subject:  Re: BB/EBP-Workflow - Change accounting data as a workflow =
step
 
 
Hi Markus,
It's not going to be pretty either way but I had a similar request from
another
customer (who decided against it for now) so have done a little =
thinking
about this already.
Don't use the "jump to maintain shopping basket" approach - that's =
there
for
 
all sorts of reasons but it's not suitable for what you want to do.
 
Strongly suggest you avoid any variant on BBPPU99 or BBPPU02 as these =
have
a heavy dependence on the requestor's attribute settings, and trying to =
run
them with another user's settings a little tricky to say the least...
 
Suggest if you really want to go ahead with this (and I'm not =
recommending
it),
you do it by using webflow transaction TS_TS10008069H (i.e. program
SAPMTS10008069H) as a model.
You really want the EBP 2.0 version of this if you can get a hold
of it - as this allows you to see all the data including account
assignment.
 
 
Start by creating a standard task similar to any of the approve =
shopping
basket
workitems, make sure you include all the container elements you need.
Generate a web transaction.  Change your generated program by cutting =
and
pasting
as appropriate from SAPMTS10008069H.   Don't forget to create the
appropriate web
service and templates similar to Internet service TS_TS10008069H.
 
You should then be able to add functionality to this to allow them to
change
the account assignment on the items.  Make sure that's the ONLY thing =
that
changes.
 
Start by just opening up the fields and letting them enter values, that =
are
then
copied to the shopping basket table REQACCT.
 
Getting validation working is a little harder as you need to feed in =
the
company code, controlling area, etc. of the requestor not the "account
assignment
changer", but should be possible with a little trial and error.  The
meta-BAPI
"META_ACCSERV_CHECKASSIGNMT" (you might need to check the spelling) is =
the
one to
use for this.
 
If you don't want them to "approve" you can always preset the approval =
flag
so that
it's always approved at that point.
 
Include your task as a new step in your approve shopping basket =
workflow.
 
Finally check the end result in the approval status display applet - =
you
might have
to adjust it, but I'm afraid you're on your own there.
 
Regards,
        Jocelyn Dart
Consultant (BBP, Ecommerce, Internet Transaction Server, Workflow)
SAP Australia
Email jocelyn.dart at sap.com <mailto:jocelyn.dart at sap.com>
Tel: +61 412 390 267
Fax: +61 2 9935 4880
 
 
-----Original Message-----
From: Markus Brahm [mailto:mbrahm at cscploenzke.de]
Sent: Saturday, 5 May 2001 6:05 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: BB/EBP-Workflow - Change accounting data as a workflow step
 
 
Hello virtual colleagues,
 
I am at a project where we need a so called "accounting step" in BBP
workflows besides the pure approval steps. This requires that the =
shopping
basket can be edited (at least in part) by a person being responsible =
for
accounting. Unfortunately this feature obviously is not part of BBP or =
EBP
(2.0c). Other alternatives like refusing the basket with a note how to =
do
the accounting would ruin huge parts of the process accelerating and =
easing
aspects. As the technique for the requisitioner to change his basket is
some what strange too (not a real workflow step but a link to standard
functionality) I expect some ugly problems when trying to create a web =
form
step which allows the accounting data to be changed during the process.
 
Does anyone of you have any experiences/advice in this area?
 
Thanks a lot in advance,
 
Markus
 


More information about the SAP-WUG mailing list