Workflow will not transport to next client

Mon Jul 14 03:38:49 EDT 2014

Hi All,

               Problem solved – here is the history. Thanks to all the wuggers out there who tried to help with the issue I was having. I followed your every instruction and in the end it went down to a customized BOR Object.

BUS2015 has BUS2012 as part of it and then it was found that there was a ZBUS2012 introduced by a previous contractor to use FM:CHANGE_DOCUMENT_READ_HEADERS. The business idea behind the contractor change was to find somebody to whom they could send an email using the purchase order creator. However, in some cases the PO creator has long since left the business. So the ZBUS2012 code was put in place to look for a change document that could pick up the last person who changed the PO.

While trying to find the problem we discovered that our CDCLS and CDHDR tables are horribly too large and need archiving. The result of such large tables is that the system reads these very large tables sequentially and causes the SWDD to just spin around. Of course it will also never find  an empty change record and the workflow never activates because at there is no change object entry when SWDD is started. So to correct the problem a simple check statement has been placed before the FM: CHANGE_DOCUMENT_READ_HEADERS  in the customized code and if there is no object then by pass looking for it.

Main thing is we are on the road to recovery because once we get our change to production we can use SWEQADM and let our banked up workflows flow.

Thanks for all the suggestions, it helps to keep one focussed and not so isolated.

Regards,

Margaret.

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Claude Bourque
Sent: Friday, 11 July 2014 2:36 AM
To: SAP Workflow Users' Group
Subject: RE: Workflow will not transport to next client

Margaret,

I think what Eddie said below is bang on. I've seen similar scenarios where a new attribute (or method) was NOT transported on the ABAP side since someone else made the change.

Regards

Claude

>>> "Morris, Eddie" <eddie.morris at sap.com<mailto:eddie.morris at sap.com>> 2014/07/10 11:45 AM >>>
Hi Margaret,

What changes did you make to the workflow in the first place?

I would concentrate on any changes made to container elements and any business object changes. What could be happening is that you may have an endless loop in a new virtual attribute or new method (That may be called via a virtual attribute). There may be an endless loop because you are passing in an empty object instance when trying to open the workflow builder in PFTC or SWDD. The workflow builder will check all container elements and if you have an implementation that requires a valid object instance you may be running into trouble when it is empty.

Regards,
Eddie

From: sap-wug-bounces at mit.edu<mailto:sap-wug-bounces at mit.edu> [mailto:sap-wug-bounces at mit.edu] On Behalf Of Margaret Jaco
Sent: 10 July 2014 16:25
To: SAP Workflow Users' Group
Subject: RE: Workflow will not transport to next client

When I use SWDM I get two panels. The left panel has the workflows and all the tasks. When I highlight a workflow the workflow and its tasks show up in the right hand panel. I do not get an extras, tab or dropdown.

Margaret.

From: sap-wug-bounces at mit.edu<mailto:sap-wug-bounces at mit.edu> [mailto:sap-wug-bounces at mit.edu] On Behalf Of Margaret Jaco
Sent: Friday, 11 July 2014 1:12 AM
To: SAP Workflow Users' Group
Subject: RE: Workflow will not transport to next client

Hi,

Where do I go to change these settings?

Margaret.

From: sap-wug-bounces at mit.edu<mailto:sap-wug-bounces at mit.edu> [mailto:sap-wug-bounces at mit.edu] On Behalf Of Srinivas Reddy
Sent: Friday, 11 July 2014 12:56 AM
To: SAP Workflow Users' Group
Subject: Re: Workflow will not transport to next client

Hi Margaret.

When you open transaction SWDM you will see a pop-window with tabs including extras tab. Click on Extras tab and select the check box 'Transported Workflows' and you will see the status of the transported workflows. May be you can find the reason why the workflow is not seen in SWDD.

You should definitely see Extras tab if not need to change the settings.

On Thu, Jul 10, 2014 at 3:28 PM, Margaret Jaco <Margaret.Jaco at staples.com.au<mailto:Margaret.Jaco at staples.com.au>> wrote:
Thanks for that. I am getting a bit further. I did not use exactly what you said because I could not find Extras-Selec…using SWDM. Instead SWDM allowed me to do a  Quick View and the workflow opened. It said it was active and saved and it is on the version I expected it to be (same as source client).

Why does SWDD not open the workflow but SWDM open it. What extra thing is required by SWDD that stops it from opening the workflow. Or in other words  what is it that SWDM bypasses so as to be able to open the workflow when SWDD cannot.

Anyway, can you imagine my joy when I saw an Active, Saved workflow. So I tried to release some of the entries in SWEQADM that have been waiting to get going. Nothing doing! I think this is because the workflow is marked as having errors. It is past midnight here in Australia. Tomorrow I am going to get the basis guys to open the ECX client so that I can use SWU0 to set the workflow on its feet again (no errors).

I am not hopeful though because I decided to do a syntax check on the  workflow. It started up quite nicely reported a couple of entries where the container is ‘written but not read….’ Etc.  and the icon at the bottom moved along swiftly. It got to 76 % checked and is now spinning away and wont complete the syntax check. Surely if there is something wrong it say ‘binding error or some such thing but to just spin away is very frustrating.

I’ll let you know how I go after SWU0.

From: sap-wug-bounces at mit.edu<mailto:sap-wug-bounces at mit.edu> [mailto:sap-wug-bounces at mit.edu<mailto:sap-wug-bounces at mit.edu>] On Behalf Of Srinivas Reddy
Sent: Thursday, 10 July 2014 11:09 PM

To: SAP Workflow Users' Group
Subject: Re: Workflow will not transport to next client

Hi Margaret,

Just give a try with SWDM on the target system to find the status of transported workflows. Go to SWDM-Extras-Select transported workflows. You might find some answer here.

Thanks and Regards,
Srini..
+447466659113<tel:%2B447466659113>

On Thu, Jul 10, 2014 at 1:21 PM, Margaret Jaco <Margaret.Jaco at staples.com.au<mailto:Margaret.Jaco at staples.com.au>> wrote:
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> [mailto: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<mailto: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> [mailto: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<mailto: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.

[cid:image001.jpg at 01CF9F8A.7833D600]<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<tel:%2B61%202%209335%200555> or Staples New Zealand Limited on +64 9 271 7600<tel:%2B64%209%20271%207600> 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<mailto:SAP-WUG at mit.edu>
http://mailman.mit.edu/mailman/listinfo/sap-wug

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu<mailto:SAP-WUG at mit.edu>
http://mailman.mit.edu/mailman/listinfo/sap-wug

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu<mailto:SAP-WUG at mit.edu>
http://mailman.mit.edu/mailman/listinfo/sap-wug

--
Thanks and Regards
Srini..
SAP Technical Consultant

_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu<mailto:SAP-WUG at mit.edu>
http://mailman.mit.edu/mailman/listinfo/sap-wug

--
Thanks and Regards
Srini..
SAP Technical Consultant
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20140714/614d357d/attachment-0001.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 7139 bytes
Desc: image001.jpg
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20140714/614d357d/attachment-0001.jpg