EBP java applet - bug or feature?

[LANGE, BODO]

Hi Nicholas,
do you get a short dump in your EBP system as well?
If so this might be the input data for the method call
you're executing. Try to debug the BBPPU99 via GUI or
activate ITS debugging to find out what data is passed
to the R/3 system. Most likely your OrgStructure needs
to be revised.=20
 
You can also download the latest java applet from the=20
service marketplace to make sure it is not buggy.
 
Hope this helps.
 
Bodo
 
-----Original Message-----
From: Nicholas Brand [mailto:nicholas.n.brand at uk.pwcglobal.com]
Sent: marted=EC 28 maggio 2002 13.28
To: SAP-WUG at MITVMA.MIT.EDU
Subject: EBP java applet - bug or feature?
 
 
Memo from Nicholas N Brand of PricewaterhouseCoopers
 
-------------------- Start of message text --------------------
 
Just a bit more information on this problem.
It's only the approval preview java applet that isn't working. Once the
basket has been ordered and the workflow status is viewed by the
requisitioner via the Check Status transaction the java applet is =
showing
the correct approval path.
 
At the moment I think it's because once the basket has been ordered it =
gets
created in SAP and the java applet relies on SAP data rather than =
getting
the info from memory.
However I know the standard attribute that I'm using in the test =
worklfow
(BUS2121.TotalValue) does get its value from memory if the shopping =
basket
has not yet been ordered. The code checks if the basket number starts =
with
'S' (for simulated) and if it does, gets the information from memory.
 
It sounds as if it could be a fairly common issue.
Any experience around this is welcome :-).
 
 
Thanks.
 
Nicholas
 
 
 
---------------------- Forwarded by Nicholas N Brand/UK/MCS/PwC on
28/05/2002 12:14 ---------------------------
 
 
Nicholas N Brand on 28/05/2002 09:58:10
To:    SAP-WUG at MITVMA.MIT.EDU
cc:
 
 
Subject:    EBP java applet - bug or feature?
 
        This memo has been sent or received by parties external to
                          PricewaterhouseCoopers
Memo from Nicholas N Brand of PricewaterhouseCoopers
 
-------------------- Start of message text --------------------
 
Hi,
 
I'm currently building a workflow in EBP.
I noticed the approval preview java applet wasn't displaying the =
correct
approval path for a shopping basket.
So I wanted to test the approval preview java applet independently of =
my
workflow.
I created a simple test workflow with a condition in based on a =
standard
SAP defined attribute of the shopping basket (BUS2121.TotalValue > =
100).
In each leg of the condition I sent the shopping cart for approval =
(using a
standard SAP defined task) to a different approver - a standard =
business
object was used to define the responsible users - as opposed to a
rule/position etc. as in standard workflow.
 
I then created a shopping basket and clicked on 'Approval preview' =
(only
the correct test workflow was started as a result of the start =
conditions).
The java applet displayed the correct approver defined in EACH leg of =
the
condition; in other words the simulated approval path shows both legs =
as
being valid - but this can only be true for one leg!
This feature is independant of the way the SAP defined attribute is
calculated (I'm using a standard attribute) but seems to be a bug with =
the
java applet.
Has anyone else had any similar issues  - and how did you get around =
them?
 
Thanks again.
 
 
Nicholas
 
--------------------- End of message text --------------------
 
This e-mail is intended only for the person to whom it is
addressed. If an addressing or transmission error has
misdirected this e-mail, please notify the author by replying to
this e-mail. If you are not the intended recipient you must not
use, disclose, copy, print or rely on this e-mail.
 
The principal place of business of PricewaterhouseCoopers and
its associate partnerships is 1 Embankment Place, London
WC2N 6RH where lists of the partners' names are available for
inspection. All partners in the associate partnerships are
authorised to conduct business as agents of, and all contracts
for services to clients are with, PricewaterhouseCoopers. The
UK firm of PricewaterhouseCoopers is authorised by the
Institute of Chartered Accountants in England and Wales to
carry on investment business. PricewaterhouseCoopers is a
member of the world-wide PricewaterhouseCoopers
organisation.
 
PricewaterhouseCoopers may monitor outgoing and incoming
e-mails and other telecommunications on its e-mail and
telecommunications systems.
 
----------------------------------------------------------------
Visit our website http://www.pwcglobal.com
 
 
 
--------------------- End of message text --------------------
 
This e-mail is intended only for the person to whom it is
addressed. If an addressing or transmission error has
misdirected this e-mail, please notify the author by replying to
this e-mail. If you are not the intended recipient you must not
use, disclose, copy, print or rely on this e-mail.
 
The principal place of business of PricewaterhouseCoopers and
its associate partnerships is 1 Embankment Place, London
WC2N 6RH where lists of the partners' names are available for
inspection. All partners in the associate partnerships are
authorised to conduct business as agents of, and all contracts
for services to clients are with, PricewaterhouseCoopers. The
UK firm of PricewaterhouseCoopers is authorised by the
Institute of Chartered Accountants in England and Wales to
carry on investment business. PricewaterhouseCoopers is a
member of the world-wide PricewaterhouseCoopers
organisation.
 
PricewaterhouseCoopers may monitor outgoing and incoming
e-mails and other telecommunications on its e-mail and
telecommunications systems.
 
----------------------------------------------------------------
Visit our website http://www.pwcglobal.com
 
 
----------------------------------------------------------------
The information transmitted is intended only for the person or entity =
to
which it is addressed and may contain confidential and/or privileged
material.  Any review, retransmission, dissemination or other use of, =
or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited.   If you =
received
this in error, please contact the sender and delete the material from =
any
computer.