WF not working correctly after UPGRADE (URGENT)

Thu May 13 04:48:21 EDT 2004

Praveen,

Seems like the underlying data definition of your parameter has changed. =
Container elements are usually based on table fields , which are based =
on data elements. If the data element has changed (eg the length) during =
the upgrade it could very well be that the data that you expect to be =
stored in there can't be stored anymore (as the field is now to short, =
of a different type or doesn't exist altogether in 4.7).

I would try to remove the container element definition and recreate it =
using an appropriate field.=20

Regards,

Jeroen

-----Original Message-----
From: Praveen Johri [mailto:pjohri at csc.com]
Sent: 13 May 2004 10:24
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: WF not working correctly after UPGRADE (URGENT)

Hi Jeroen,

Runtime Environment is properly set up..........other workflow templetes
and config is working fine except this perticular..........
i was wondering is there a possibility that while transporting to 4.7
something with binding or attributes has gone wrong.....the problem i m
facing is while executing the same scenario in 4.5 box and 4.7 box one
container attribute is not holding proper value in 4.7 but in 4.5 it is =
as
4.7 box contains the exact replica of 4.5 box ...........i m not able to
figure out what is wrong and where........

Thanks & Regards

Praveen Johri
SAP Practice
Extn : 2597
Ph    : 91-0120-2582323
Fax   : 91-0120-2582322
Computer Science Corporation India Ltd.

-------------------------------------------------------------------------=
---------------

This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit =
written
agreement or government initiative expressly permitting the use of =
e-mail
for such purpose.
-------------------------------------------------------------------------=
---------------

                      "Van der Burg,
                      Jeroen JA                To:      =
SAP-WUG at MITVMA.MIT.EDU
                      SITI-ITABEE"             cc:
                      <jeroen.vanderbu         Subject: Re: WF not =
working correctly after UPGRADE (URGENT)
                      rg
                      @shell.com>
                      Sent by: SAP
                      Workflow
                      <Owner-SAP-WUG

                      05/13/2004 12:58
                      PM
                      Please respond
                      to "SAP Workflow
                      Users' Group"

Hi Praveen,

'Workflow is not working' really doesn't give much pointers, so not much =
we
can help you with. Assuming you checked SWU3 and SWUB, did you also =
verify
the wf-batch user authorisation (SAP_ALL and SAP_NEW)?

Some further questions:
Are workflows started but not processed (WF-Batch or logical system
issues), or are workflows not starting at all (authorisation issues)?
Are events actually published or do they not show up in the event log
(event queue issue)?

Regards,

Jeroen

-----Original Message-----
From: Praveen Johri [mailto:pjohri at csc.com]
Sent: 13 May 2004 09:13
To: SAP-WUG at MITVMA.MIT.EDU
Subject: WF not working correctly after UPGRADE (URGENT)

Hi All,

Either my question was too silly to be answered or no body get =
it.......in
both the cases queries and suggestions are welcomed.

one bonus question ..................after upgrade WF is not working =
what
areas to look in and how?????  Right now i m manually comparing the
container elements and task bindings between two systems ........such a
tedious job.......PLEASE get me out of it...

Thanks & Regards

Praveen Johri
SAP Practice
Extn : 2597
Ph    : 91-0120-2582323
Fax   : 91-0120-2582322
Computer Science Corporation India Ltd.

-------------------------------------------------------------------------=
---------------

This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit =
written
agreement or government initiative expressly permitting the use of =
e-mail
for such purpose.
-------------------------------------------------------------------------=
---------------

----- Forwarded by Praveen Johri/GTS/CSC on 05/13/2004 12:37 PM -----

                      Praveen Johri
                      /GTS/CSC                 To:      "SAP Workflow
Users' Group" <SAP-WUG at MITVMA.MIT.EDU>
                                               cc:
                      05/12/2004 12:16         Subject: WF not working
correctly after UPGRADE (URGENT)(Document link: Praveen
                      PM                       Johri)

Hi All,

Here i m again with one ususal question..................we had an =
upgrade
from 4.5 to 4.7 SR1,there is a customized WF for buyer =
assignement:...the
discription goes as.....when a PR is created it is assigned to a buyer =
for
PO creation. Buyer assignemnt is determined against the table entries of
buyer load. When PR is assigned the buyer load is increased by 1 and =
when
PO is created it is decreased by 1.
The problem is the task used to update buyer load is passed with buyer =
id
from WF against which the load has to be updated.In 4.5 it is working
correctly(which is a copy of previous Production ) but in 4.7 the buyer =
id
from WF to task is not coming (it is blank always).
I have compared all the bindings and the all the mehtods their
intefaces..........but was not able to figure out why it is happening in
4.7

this issue has become highly critical in the list of prod. problems i =
have
to solve..........................any help or ideas are welcome....

Thanks & Regards

Praveen Johri
SAP Practice
Extn : 2597
Ph    : 91-0120-2582323
Fax   : 91-0120-2582322
Computer Science Corporation India Ltd.

-------------------------------------------------------------------------=
---------------

This is a PRIVATE message. If you are not the intended recipient, please
delete without copying and kindly advise us by e-mail of the mistake in
delivery. NOTE: Regardless of content, this e-mail shall not operate to
bind CSC to any order or other contract unless pursuant to explicit =
written
agreement or government initiative expressly permitting the use of =
e-mail
for such purpose.
-------------------------------------------------------------------------=
---------------