Transporting Workflows - missing container elements

[Nicholas Brand]

Memo from Nicholas N Brand of PricewaterhouseCoopers
 
-------------------- Start of message text --------------------
 
Thank you for sharing your experience.
On the client dependant/independant issue as we only have one client in our
PROD system I couldn't take this approach.
 
I've solved the problem and I wanted to give something back to the group on
what I found.
 
After activating the workflow on the source system I went into transaction
SWUD and ran a consistency check on the workflow and sub-workflow. This
seems to ensure that all areas of the workflow are activated and saved to
the new transport.
I then released the transport and moved it to PROD (via QA). I went into
PFTC on the PROD client and the missing container elements were there.
 
Although it is solved, I'm still unsure about the reliability of
transporting workflows. I've had problems before and I know other
workflowers with similar war-stories.
 
The story continues...
 
 
Kind regards,
Nicholas
 
 
 
 
 
 
 
Patrick D. Green/GBPO/Price Waterhouse at Americas-US@MITVMA.MIT.EDU> on
26/03/2002 18:15:38
 
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:    Re: Transporting Workflows - missing container elements
 
 
Nicholas,
 
As I understand it, the distinction between dependent versus independent
transports has only to do with how clients are targeted after a transport
has been created.  There is no option in the SAP prompt to create one or
the other.   In our shop, the dependent / independent designation serves
only as instructions to our Basis team to tell them where / how to send the
transport.
 
Independent transports can be targeted to the system (000) client, or to
another specific client within the target system.  Any truly independent
elements included within the transport will then be available to all other
clients.  But any dependent elements in the transport will only go to the
specific client targeted (i.e.,  PR5-000,  not PR5-100).
 
We use a client-dependent flag for transports when we want to ensure all
elements included in a transport go to all clients in an environment.
 
My reference to "migration" instead of "transport" stems from our use of a
"Migration database" in Lotus Note to track & group transports into
packages for mass movement at scheduled intervals.  I get a little careless
(provincial?) from time to time and use the terms interchangeably.
 
 Hope this makes sense and is not too different from the way other
companies handle the process.
 
All Best,  -- Patrick.
 
 
 
 
Nicholas N Brand/UK/MCS/PwC at EMEA-UK@MITVMA.MIT.EDU> on 03/26/2002 11:01:07
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:    Re: Transporting Workflows - missing container elements
 
 
Memo from Nicholas N Brand of PricewaterhouseCoopers
 
-------------------- Start of message text --------------------
 
Patrick,
 
Thanks for the ultra-quick reply.
Could you give me more information on this?
By a 'client-dependant migration' do you mean a client-dependant transport?
What changes did you make to get SAP to prompt you for a client-dependant
(customising) request?
 
 
Nicholas
 
 
 
James J Seiter
03/26/2002 11:01 AM
To:    SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
cc:    Patrick D. Green/GBPO/Price Waterhouse
Subject:    Re: Transporting Workflows - missing container elements
       (Document link: Patrick D. Green)
 
Nicholas,
 
      As Patrick stated, we just recently experienced this.
      The solution I used was:
            Regenerate/activate runtime version from pristine client which
requested transport.
            Click the SAVE icon before exiting.
            Transport to target.
            In target, regenerate sub then main workflow objects (ZFIPP,
FIPP in our case)
            Refresh buffers with SWU_OBUF, make sure the REFRESH icon is
pressed.
            Event simulation SWU0
James
 
 
Patrick D. Green/GBPO/Price Waterhouse at Americas-US@MITVMA.MIT.EDU> on
26/03/2002 16:32:40
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:    Re: Transporting Workflows - missing container elements
 
Hi Nicholas,
 
Have you tried re-transporting as a client-dependent migration?  That
worked for us recently in a 4.6C environment, patch level 20 (w/ IS-Oil).
We were a bit puzzled as the changes we'd made - changing some container
element assignments - were expected to be to client-independent tables.
 
-- Patrick
 
Nicholas N Brand/UK/MCS/PwC at EMEA-UK@MITVMA.MIT.EDU> on 03/26/2002
09:49:27AM
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:    Transporting Workflows - missing container elements
 
Memo from Nicholas N Brand of PricewaterhouseCoopers
 
-------------------- Start of message text --------------------
 
Hello,
 
A short while ago there were a few mails going around our group about
problems with transporting workflows.
 
I am currently transporting several workflows from UAT to our PROD
environment. The workflows are all working fine on QA.
When I looked at the workflows that had been transported to PROD I noticed
that some of them had transported correctly, but with others some of the
workflow container elements had not transported.
These container elements are used in binding to a sub workflow. The
sub-workflow has transported correctly and so the the main workflow is
showing errors when I run a check on it.
The same sub-workflow is used by 2 workflows, one of them has transported
correctly, the other has container elements missing.
 
To try and solve this I generated a new version of the workflow in DEV and
transported this via UAT to PROD and then refreshed the runtime buffer.
However, this has not solved the problem.
 
Has anyone else had a problem like this - what did you do to solve it?
 
We're on v4.6c patch 25.
 
Thank you for your help.
 
Kind regards,
Nicholas
 
--------------------- End of message text --------------------
----------------------------------------------------------------
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.
 
 
--------------------- End of message text --------------------
 
This e-mail is sent by the above named in their
individual, non-business capacity and is not on
behalf of PricewaterhouseCoopers.
 
PricewaterhouseCoopers may monitor outgoing and incoming
e-mails and other telecommunications on its e-mail and
telecommunications systems.
----------------------------------------------------------------
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.