EBP Upgrade from 2.0 to 3.5 WF not working---------Urgent re qquirement of suggestions

[Griffiths, Mark]

Use transaction SWB_COND.  It is customising.
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of 'Praveen Johri'
Sent: 23 December 2003 10:44
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: EBP Upgrade from 2.0 to 3.5 WF not working---------Urgent re qquirement of suggestions
 
 
Hi Mark
 
How can i add Start Cond to std. workflow.........i guess i have to go for
customized one
 
 
Praveen
 
(Embedded image moved to file: pic21425.pcx)
 
 
 
                      "Griffiths, Mark"
                      <mark.griffiths at sap        To:       SAP-WUG at MITVMA.MIT.EDU
                      .com>                      cc:
                      Sent by: SAP               Subject:  Re: EBP Upgrade from 2.0 to 3.5  WF not working---------Urgent re qquirement
                      Workflow                    of suggestions
                      <Owner-SAP-WUG at MITV
                      MA.MIT.EDU>
 
 
                      12/23/2003 03:56 PM
                      Please respond to
                      SAP Workflow Users'
                      Group
 
 
 
 
 
 
Have you tried using start conditions (SWB_COND) rather than function
modules?  This would be the more standard approach.
 
Regards,
 
Mark
 
SAP UK.
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU] On Behalf Of
'Praveen Johri'
Sent: 23 December 2003 06:33
To: SAP-WUG at MITVMA.MIT.EDU
Subject: EBP Upgrade from 2.0 to 3.5 WF not working---------Urgent
reqquirement of suggestions
 
 
Hi All,
 
I have a problem that my client went for upgrade from EBP 2.0 to EBP 3.5
after that the Standard workflow WS1000060 is not working properly.
It is linked with event SAVED of business object BUS2121.The Bus Obj is
extended and delegated properly we are using a Functional module to trigger
the appropriate sub-WF for NO-Approval or Single Step Approval or Two stem
approval. This functional module decide this on the basis of Price entered
and set the flag. this flag is read in WF and appropriate sub-WF is
triggered.Func mod. is called in GET_PROPERTY Code of a Virtual Attribute
in BUS2121.
Now there are two problems...
 
1. when in the upgraded version i ran trans.. BBPPU99 which triggers WF .WF
definations are bieng read and BUS2121 object is bieng instantiated but i
cannot see a single entry in SWI2_FREQ which indicates that WF is not bieng
triggered or the Application is not raising the Event.
 
2.just for a hunch i put a break-point in object program where the rule
func. module is bieng called (it should not have gone in Debugger but it is
going)
there i found that they are doing ABAP IMPORTING of the structure
containing the Price value but the SY-SUBRC is 4 in which case they are
trying to fetch it from Database which again is resulting in SY-SUBRC = 4
and with wrong price value the wrong flag is going to set but then also it
is not sending any work item to inbox stating no approval required which in
this case it should. that again means WF is not triggered.
 
Can any body point out what Config issues are to tb dealt with or if
somebody has faced simmilar prob and has any Doc regarding it please send
me offline.
 
Please help its really urgent............
 
 
 
(Embedded image moved to file: pic17773.pcx)
 
 
 
 
 
 
 
Whilst this email has been checked for all known viruses, recipients should
undertake their own virus checking as Xansa will not accept any liability
whatsoever.
 
This email and any files transmitted with it are confidential and protected
by client privilege.  It is solely for the use of the intended recipient.
Please delete it and notify the sender if you have received it in
error. Unauthorised use is prohibited.
 
Any opinions expressed in this email are those of the individual and not
necessarily the organisation.
 
Xansa, Registered Office: Campus 300, Maylands Avenue,
Hemel Hempstead, HP2 7TQ, UK.
Registered in England No.1000954.
t  +44 (0)8702 416181
w  www.xansa.com
 
 
 
 
 
Whilst this email has been checked for all known viruses, recipients should undertake their own virus checking as Xansa will not accept any liability whatsoever.
 
This email and any files transmitted with it are confidential and protected by client privilege.  It is solely for the use of the intended recipient.
Please delete it and notify the sender if you have received it in
error. Unauthorised use is prohibited.
 
Any opinions expressed in this email are those of the individual and not
necessarily the organisation.
 
Xansa, Registered Office: Campus 300, Maylands Avenue,
Hemel Hempstead, HP2 7TQ, UK.
Registered in England No.1000954.
t  +44 (0)8702 416181
w  www.xansa.com