status :Workflow transport problems

Thu Feb 8 18:23:54 EST 2001

We have a transport problem that is similar to what is being discussed here.
I want to confirm that the error we are encountering is also covered in this
OSS Note.

We transported a new workflow version from DV to QA.  The old version became
inactive, but the new version does not appear at all in QA.  There is no
sign that it ever made it to QA and the transport logs have no errors.  This
is a little different from the reports found in this e-mail.  Is this the
same issue?  Does this note 378487 address this issue?

Thanks in advance.

Phil Evans

 -----Original Message-----
From:   Rickayzen, Alan [mailto:alan.rickayzen at sap.com]
Sent:   Thursday, February 08, 2001 4:04 AM
To:     SAP-WUG at MITVMA.MIT.EDU
Subject:        Re: status :Workflow transport problems

Peter,

I'm sorry that we couldn't confirm any earlier that the problem was solved.
Not only does the solution have to be verified in a customer system (done)
but in addition the solution has to undergo a code review (also taken place)
and finally the q-team performs a set of checks themselves (including the
quality of the Note itself).

If you are under extreme time pressure, you could consider implementing note
378487 for Releases 4.6x. I'll post a new message when the note covers
Release 4.5x.

If you are not under time pressure, or do not have workflow transports
awaiting import into your production system, then you should wait for the
final clearance from me.

I understand that the note was not deactivated for the whole duration of the
problem so if you have applied the note already, please check that your code
is up to date. The last change was made to the function module
SWD_CHECK_ACTIVE_VERSION. You should check that the first mention of e274
has been commented out (search for e274).

The problem does NOT affect WF or T tasks.

Alan

-----Original Message-----
From: Roehlen, Peter [mailto:PRoehlen at powercor.com.au]
Sent: Thursday, February 08, 2001 2:18 AM
To: SAP-WUG at MITVMA.MIT.EDU
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.
**********************************************************************