OSS note 378487 WARNING

Mon Mar 19 13:34:54 EST 2001

Good news.

I sent a note to OSS to discribe my problem.
They have created a new version (ver. 20) of OSS note 378487 that takes care of
WF workflows.

Greg

---------------------- Forwarded by Gregory Kowalik on 03/19/2001 01:31 PM
---------------------------

Gregory Kowalik
03/05/2001 03:07 PM

To:   SAP-wug at mitvma.mit.edu
cc:
Subject:  OSS ntoe 378487 WARNING

Actually the problems occurs when:
- you are in release 4.5 or later
- and you have running WF type workflows in your target system,

another words, it does not matter if you changed them or not in the new release.
Greg

---------------------- Forwarded by Gregory Kowalik on 03/05/2001 03:05 PM
---------------------------

Gregory Kowalik
03/05/2001 08:27 AM

To:   "SAP Workflow Users' Group" <SAP-WUG at MITVMA.MIT.EDU>
cc:
Subject:  OSS ntoe 378487 WARNING  (Document link: Gregory Kowalik)

There is a problem with that note in the following case:
- you have upgraded from release prior to 4.5
- you have WF type workflows running in your production system, that you didn't
change to WS type
- you did not make any modifications to those WF workflows after upgrade.

In this case if you look at table SWD_HEADER, you will not have version 9999 for
your WF workflow.
Well, in this case every time you start a new workflow or even if you are in the
middle of one, whenever function module RH_GET_WFD_ID gets called, it will
return an error, and you as an end user will get a message informing you that
your task does not exist.

I was banging my head against the wall for 9 hours Saturday night after I sent
that OSS note to production and no WF workflow was running.
Finally I debugged the SWUS transaction and found out that the system checks
change time and generation time every time new workflow gets started or a new
step is created. Well, for all WF workflows in my system the generation time was
off 20-30 seconds, which makes sense (generation step during transport comes
after the import step).
I didn't think long and updated that table directly via SQL plus making those 2
fields equal. That helped and everything is working fine now.

But I thought I will share it with you guys and save you some time in case you
ran into a similar situation.

If I was to do it again, I would probably make a invisible change to my WF
workflows and transport them right before applying that note.
That would make version 9999 to be created in the target system, and everything
would be beautiful.

Greg

"Roehlen, Peter" <PRoehlen at powercor.com.au> on 02/07/2001 08:18:22 PM

Please respond to "SAP Workflow Users' Group" <SAP-WUG at MITVMA.MIT.EDU>

To:   SAP-WUG at MITVMA.MIT.EDU
cc:    (bcc: Gregory Kowalik)
Subject:  FW: Alan's warning :Workflow transport problems

Alan & all,

I've been informed by one of our basis consultants that OSS note 378487
(released 7th Feb) corrects the problems with transporting workflows.

Could anyone confirm if this note actually resolves all workflow
transporting problems they have experienced in association with the below
support packages?

Thanks in advance

Peter Roehlen.

-----Original Message-----
From: Roehlen, Peter
Sent: Monday, 5 February 2001 16:44
To: 'SAP Workflow Users' Group'
Subject: RE: Alan's warning :Workflow transport problems

Alan,

Thanks for the below information.  We have now decided to delay our planned
implementation of support packages 19 to 23 (46b) until after a solution is
found.

To that end, could you advise this distribution list when the solution is
ready?

Kind regards

Peter Roehlen.

-----Original Message-----
From: Rickayzen, Alan [mailto:alan.rickayzen at sap.com]
Sent: Saturday, 3 February 2001 2:28 am
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Alan's warning :Workflow transport problems

Hi Myra,
Here's your list:

Release   Hotpackage
45B       35
46A         30
46B         22
46C         11
46D         04

I don't usually like to address OSS problems through this channel but in
this case I'm trying to save some of you some unnecessary discomfort. A
solution should be ready very soon.

Alan

____________    ____________________

-----Original Message-----
From: Myra H Gill [mailto:Myra.Gill at ipaper.com]
Sent: Friday, February 02, 2001 1:32 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Alan's warning :Workflow transport problems

Alan,
Do you know which HOT-PACKAGES caused the problem?

"Rickayzen, Alan" <alan.rickayzen at sap.com>@MITVMA.MIT.EDU> on 02/02/2001
02:22:48 AM

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:  Alan's warning :Workflow transport problems

Hi WF administrator,

I'm sorry to hear that 378487 did not correct the problem.

The error appears to be have caused by one of the latest HOT-PACKAGES and
affects systems 4.5 - 4.6d.

Needless to say, our Q-team is working feverishly to provide a solution,
but
until this is available I would recommend  postponing transporting
workflows
into the production system.

I'll send a confirmation through this listserver as soon as we've got this
licked.

Alan Rickayzen
SAP AG

-----Original Message-----
From: <Thiemo> <Geisberger> [mailto:tgeisberger at bmw.co.at]
Sent: Friday, February 02, 2001 8:02 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Antwort: Workflow transport problems

Hi Aravindan!

Maybe OSS-note 378487 will help you! We have the same problem but in our
system
this note doesn't solve the problem!

Good luck!
Thiemo

Aravindan Kalaimannan <ibm_akalaimanan at 1stsi.com> am 02.02.2001 07:29:22

Bitte antworten an "SAP Workflow Users' Group" <SAP-WUG at MITVMA.MIT.EDU>

 An:    SAP-WUG at MITVMA.MIT.EDU

 Kopie: (Blindkopie: Thiemo Geisberger/STEYR/BMW/AT)

 Thema: Workflow transport problems

HI All,
  I am facing problems, when transport workflow templates into QA &
Production systems. First time, transports are fine, but after making
changes in Development and on transporting, it creates a inactive
version in QA. And still continues to work with the pervious runtime
version. What is to be done to have to corrected version active in QA or

Production. We are using 4.6B version.

Also having a new problem, when copying workflow (WS) into new name and
transporting it only the workflow template is found transported (WS) all
the
links to the task (TS) are missing. Any idea why this is happenning?

Help will be highly appreciated.

Thanks in advance.
Aravindan.
**********************************************************************
Powercor Australia Ltd. This email and any file attachments are
confidential and intended solely for the use of the individual or
entity to whom they are addressed. If you have received this email in
error please tell us immediately by return email and delete the
document.
**********************************************************************