Workflow will not transport to next client

[Margaret Jaco]

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.


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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20140709/b9e6cd49/attachment.htm