Workflow will not transport to next client

[Andy Curtis]

I think I have seen this before. I think it was a syntax error in the
triggering event business object (I would check all business objects and
Abap Classes in the Wf Container to be safe though).

It was a longtime back, but I believe in generating a new version of the
template it needs to instantiate the business object, and this was failing.

Try it, whats the worse that can happen?

Andy


On Thu, Jul 10, 2014 at 1:22 PM, <sap-wug-request at mit.edu> wrote:

> Send SAP-WUG mailing list submissions to
>         sap-wug at mit.edu
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://mailman.mit.edu/mailman/listinfo/sap-wug
> or, via email, send a message with subject or body 'help' to
>         sap-wug-request at mit.edu
>
> You can reach the person managing the list at
>         sap-wug-owner at mit.edu
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of SAP-WUG digest..."
>
> Today's Topics:
>
>    1. Re: Workflow will not transport to next client (Mark Pyc)
>    2. RE: Workflow will not transport to next client (Margaret Jaco)
>
>
> ---------- Forwarded message ----------
> From: Mark Pyc <mark.pyc at gmail.com>
> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> Cc:
> Date: Thu, 10 Jul 2014 18:12:43 +1000
> Subject: Re: Workflow will not transport to next client
> G'day Margaret,
>
> PFTC_DIS is just spinning?? You could maybe debug to see what's happening
> because whatever happened to your WF in transit that transaction should
> work or error.
>
> What about SWDD?
>
> I'd suggest also just either importing the transport again (used to be
> standard procedure in the bad old days) or making a minor change and
> transporting again.
>
> Have fun,
> Mark
>
> Sent from my phone
>
> On 10/07/2014, at 3:47 PM, Margaret Jaco <Margaret.Jaco at staples.com.au>
> wrote:
>
>  Hi and thanks for your reply,
>
>
>
> The transport has not errors. I try PFTC_DIS in the target system and it
> just spins around.
>
>
>
> Margaret.
>
>
>
> *From:* sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu
> <sap-wug-bounces at mit.edu>] *On Behalf Of *Rick Bakker
> *Sent:* Thursday, 10 July 2014 2:53 PM
> *To:* SAP Workflow Users' Group
> *Subject:* Re: Workflow will not transport to next client
>
>
>
> Hi Margaret,
>
>
> Sorry if I'm stating the obvious but it seems the transport did not work.
> I would check for errors. It could be that related objects were not
> transported at the same time. Also, I would try PFTC_DIS in the target
> system, just in case.
>
>
>
> regards
>
> Rick Bakker
>
>
>
> On Wed, Jul 9, 2014 at 4:58 PM, Margaret Jaco <
> Margaret.Jaco at staples.com.au> wrote:
>
> Hi,
>
>
>
> I have a workflow in development that has had work done on it. The work
> was successful and the workflow activated and the trigger started the
> workflow and the workflow proceeded through it steps and completed. Several
> tests were done and the workflow performed beautifully for each test.
>
>
>
> Next the workflow was transported to the QA client. It no longer works in
> this client. Using SWDD and trying to figure out why is of no use because
> it just spins around and the workflow does not appear. I have checked the
> SWD_HEADER table and there is no sign of the workflow having reached the
> next client. The workflow is for a BOR OBJECT               BUS2015.
>
>
>
> I have seen some treads on the SDN and have tried various mechanism to try
> and prod the workflow into action. SWU0, RSWD_REPLICATE_FROM_9999, SWUD,
> RSWDACTIVATE.
>
>
>
> After the “supposed” successful transport of the workflow, the SWD_HEADER
> table has not been updated in the receiving client and one cannot see the
> workflow using SWDD or try and figure out why it has failed..
>
>
>
> Any hints on what can be done next would be greatly appreciated.
>
>
>
> Thanks,
>
>
>
> Margaret.
>
>
>
> <http://www.staplesadvantage.com.au/>
>
> The information contained in this email and any attached files are
> strictly private and confidential. This email should be read only by the
> intended addressee only. If the recipient of this message is not the
> intended addressee, please call Staples Australia Pty Limited on +61 2
> 9335 0555 or Staples New Zealand Limited on +64 9 271 7600 and promptly
> delete this email and any attachments. The intended recipient of this email
> may only use, reproduce, disclose or distribute the information contained
> in this email and any attached files with the prior written permission of
> StaplesTM. If you are not the intended addressee, you are strictly
> prohibited from using, reproducing, disclosing or distributing the
> information contained in this email and any attached files. StaplesTM
> advises that this email and any attached files should be scanned to detect
> viruses. StaplesTM accepts no liability for loss or damage (whether caused
> by negligence or not) resulting from the use of any attached files.
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
>
> ---------- Forwarded message ----------
> From: Margaret Jaco <Margaret.Jaco at staples.com.au>
> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> Cc:
> Date: Thu, 10 Jul 2014 12:21:49 +0000
> Subject: RE: Workflow will not transport to next client
>
> Thanks for replying. At least I don’t feel so lonely with this problem.
> You have a point in making a minor change. I did generate a new version and
> then transport but I did not make a change after the generate. I just took
> the transport straight through. This is very weird because the SWD_HEADER
> table is not updating in the target client. However, SWDSHEADER is being
> updated with the version in the target system.
>
>
>
> This worklow processes perfectly through to its last step and completes in
> development and transports without errors but it somehow does not reach the
> target client. Let me rephrase that. It reaches the target client but you
> cannot use SWDD or anything else to look at it.
>
>
>
> If only there were something that would enable me look at it and find the
> error.
>
>
>
>
>
> *From:* sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] *On
> Behalf Of *Mark Pyc
> *Sent:* Thursday, 10 July 2014 6:13 PM
> *To:* SAP Workflow Users' Group
> *Subject:* Re: Workflow will not transport to next client
>
>
>
> G'day Margaret,
>
>
>
> PFTC_DIS is just spinning?? You could maybe debug to see what's happening
> because whatever happened to your WF in transit that transaction should
> work or error.
>
>
>
> What about SWDD?
>
>
>
> I'd suggest also just either importing the transport again (used to be
> standard procedure in the bad old days) or making a minor change and
> transporting again.
>
>
>
> Have fun,
>
> Mark
>
> Sent from my phone
>
>
> On 10/07/2014, at 3:47 PM, Margaret Jaco <Margaret.Jaco at staples.com.au>
> wrote:
>
>  Hi and thanks for your reply,
>
>
>
> The transport has not errors. I try PFTC_DIS in the target system and it
> just spins around.
>
>
>
> Margaret.
>
>
>
> *From:* sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu
> <sap-wug-bounces at mit.edu>] *On Behalf Of *Rick Bakker
> *Sent:* Thursday, 10 July 2014 2:53 PM
> *To:* SAP Workflow Users' Group
> *Subject:* Re: Workflow will not transport to next client
>
>
>
> Hi Margaret,
>
>
> Sorry if I'm stating the obvious but it seems the transport did not work.
> I would check for errors. It could be that related objects were not
> transported at the same time. Also, I would try PFTC_DIS in the target
> system, just in case.
>
>
>
> regards
>
> Rick Bakker
>
>
>
> On Wed, Jul 9, 2014 at 4:58 PM, Margaret Jaco <
> Margaret.Jaco at staples.com.au> wrote:
>
> Hi,
>
>
>
> I have a workflow in development that has had work done on it. The work
> was successful and the workflow activated and the trigger started the
> workflow and the workflow proceeded through it steps and completed. Several
> tests were done and the workflow performed beautifully for each test.
>
>
>
> Next the workflow was transported to the QA client. It no longer works in
> this client. Using SWDD and trying to figure out why is of no use because
> it just spins around and the workflow does not appear. I have checked the
> SWD_HEADER table and there is no sign of the workflow having reached the
> next client. The workflow is for a BOR OBJECT               BUS2015.
>
>
>
> I have seen some treads on the SDN and have tried various mechanism to try
> and prod the workflow into action. SWU0, RSWD_REPLICATE_FROM_9999, SWUD,
> RSWDACTIVATE.
>
>
>
> After the “supposed” successful transport of the workflow, the SWD_HEADER
> table has not been updated in the receiving client and one cannot see the
> workflow using SWDD or try and figure out why it has failed..
>
>
>
> Any hints on what can be done next would be greatly appreciated.
>
>
>
> Thanks,
>
>
>
> Margaret.
>
>
>
> <http://www.staplesadvantage.com.au/>
>
> The information contained in this email and any attached files are
> strictly private and confidential. This email should be read only by the
> intended addressee only. If the recipient of this message is not the
> intended addressee, please call Staples Australia Pty Limited on +61 2
> 9335 0555 or Staples New Zealand Limited on +64 9 271 7600 and promptly
> delete this email and any attachments. The intended recipient of this email
> may only use, reproduce, disclose or distribute the information contained
> in this email and any attached files with the prior written permission of
> StaplesTM. If you are not the intended addressee, you are strictly
> prohibited from using, reproducing, disclosing or distributing the
> information contained in this email and any attached files. StaplesTM
> advises that this email and any attached files should be scanned to detect
> viruses. StaplesTM accepts no liability for loss or damage (whether caused
> by negligence or not) resulting from the use of any attached files.
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
>
>  _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20140710/44c7c569/attachment-0001.htm