Activating workflow without using SWDD tcode

[Mike Pokraka]

A workflow course could be considered a behaviour-changing conversation.
If you really don't have any workflow skilled people then I would highly
recommend some training.
It will save your company good money in the long run - you have already
spend over two days on a problem that should take an hour at most to
resolve.



On Fri, July 2, 2010 8:09 am, Patil, Priyank wrote:
> Joce,
>           Here we don't have any WF developers. We need to take care of
> everything. Could you tell me some details on behavior-changing
> conversation. Actually what is it and how it works?
>
> Thanks
> PD
>
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Dart, Jocelyn
> Sent: Friday, July 02, 2010 12:11 PM
> To: SAP Workflow Users' Group
> Subject: RE: Activating workflow without using SWDD tcode
>
> No difference at all - event activation is event activation no matter
> where you do it.
> But that's why you want to watch the Linkages in Errors tab regularly -
> because if it's getting deactivated due to an error that's where it will
> appear.
> Of course if it's new transports deactivating it then you want to go and
> have a behaviour-changing conversation with your workflow developers.
> Regards
> Jocelyn
>
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Patil, Priyank
> Sent: Friday, 2 July 2010 4:07 PM
> To: SAP Workflow Users' Group
> Subject: RE: Activating workflow without using SWDD tcode
>
> Thanks Jocelyn its quite informative...But this is only to activate the
> event(swu0) attached to the WF I guess. But once iam done with it , don't
> you think it will get deactivate again??.Because I feel its same like
> getting into SWDD and activate the event.I don't find any difference in
> SWU0 and getting into SWDD to reactivate the event . What is the
> difference in SWU0 and getting into SWDD(reactivate the event).
>
> Thanks
> PD
>
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Dart, Jocelyn
> Sent: Friday, July 02, 2010 11:19 AM
> To: SAP Workflow Users' Group
> Subject: RE: Activating workflow without using SWDD tcode
>
> Ok - If neither of them are the event you are looking for then another way
> to fix event activation issues is through transaction SWU0 - simulate
> event.
>
> Run the simulation on the event in question and it will show if there is
> any problem with the activation - e.g. if the workflow itself is not
> activated.  If everything this is fine but it's just the event that is
> deactivated you can double click on the event activation line and you'll
> get a pop-up where you can change the event activation flag and save it.
>
> When you've done that run SWU0 again to check everything is ok.
> Regard,s
> Jocelyn
>
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Patil, Priyank
> Sent: Friday, 2 July 2010 3:38 PM
> To: SAP Workflow Users' Group
> Subject: RE: Activating workflow without using SWDD tcode
>
> In that tab, we have 2 objects and associated events assigned to them. And
> linkage status/activation are marked I green color.
>
> Thanks,
> PD
>
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Dart, Jocelyn
> Sent: Friday, July 02, 2010 11:00 AM
> To: SAP Workflow Users' Group
> Subject: RE: Activating workflow without using SWDD tcode
>
> Yes Patil that's fine... but transaction SWEQADM has 5 different tabs and
> you are describing the settings on the Basic Data tab.
> The settings you are using are correct and mean that you should then see
> any failed events in the Linkages with Errors tab..
>
> So what Paul and I are asking is what are you seeing in the Linkages with
> Errors tab.  So just try moving over to that Tab and see if the offending
> event is listed.
>
>
> Regards,
> Jocelyn
>
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Patil, Priyank
> Sent: Friday, 2 July 2010 3:19 PM
> To: SAP Workflow Users' Group
> Subject: RE: Activating workflow without using SWDD tcode
>
> How long!!..Its hard to find out but I guess, we merged 2 servers to one
> single instance. So on that time it may caused this issue.Anyways I
> changed in the basic event  tab as 'Linkages with errors'. Under this the
> entries are -
> 1)Event linkages with errors must be set manually to "No errors"
> 2)Events can be redelivered to the receiver after errors
>
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Rick Bakker
> Sent: Friday, July 02, 2010 10:41 AM
> To: SAP Workflow Users' Group
> Subject: Re: Activating workflow without using SWDD tcode
>
> Hello,
>
> How long has SWEQADM been set to that value, do you know?
> Any entries under the "Linkages with errors" tab?
>
> regards
> Rick Bakker
> Hanabi Technology
>
>
>
> On Fri, Jul 2, 2010 at 12:57 PM, Patil, Priyank
> <Priyank.Patil at keane.com<mailto:Priyank.Patil at keane.com>> wrote:
> In SWEQADM its   'MARK LINKAGE AS HAVING ERRORS'.
>
> Thanks
> PD
>
> 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 Rick Bakker
> Sent: Thursday, July 01, 2010 6:07 PM
>
> To: SAP Workflow Users' Group
> Subject: Re: Activating workflow without using SWDD tcode
>
> Depends what the System Default is. What's the setting in SWEQADM?
> On Thu, Jul 1, 2010 at 8:21 PM, Patil, Priyank
> <Priyank.Patil at keane.com<mailto:Priyank.Patil at keane.com>> wrote:
>
> Some workflows its 'MARK LINKAGE AS HAVING ERRORS' and for some others its
> SYSTEM DEFAULTS.I guess this should not be a problem.
>
>
>
> Thanks
>
> PD
>
>
> 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 Rick Bakker
> Sent: Thursday, July 01, 2010 5:46 PM
>
> To: SAP Workflow Users' Group
> Subject: Re: Activating workflow without using SWDD tcode
>
> What's the setting in SWEQADM?
> On Thu, Jul 1, 2010 at 8:08 PM, Patil, Priyank
> <Priyank.Patil at keane.com<mailto:Priyank.Patil at keane.com>> wrote:
> No, it was set to 'Mark linkage as having errors'.
>
> Thanks,
> PD
>
> 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 Neumann, Marcia
> Sent: Thursday, July 01, 2010 5:33 PM
>
> To: SAP Workflow Users' Group
> Subject: RE: Activating workflow without using SWDD tcode
>
> We have 'Behavior Upon Error Feedback' set to 'Do not change linkage' in
> event linkage SWETYPV for all our workflows.  Is your set to 'Deactivation
> on linkage'?
> [cid:image001.jpg at 01CB19E3.9424C760]
>
>
> Marcia Neumann
> IT Claims/CSU Development & Support
> Ext 4461
>
> Confidentiality notice: The information included in this e-mail, including
> any attachments, is for the sole use of the intended recipient and may
> contain information that is confidential and protected. Any unauthorized
> review, use, disclosure, distribution or similar action is prohibited. If
> you are not the intended recipient, please contact the sender and delete
> all copies of the original message immediately.
>
> ________________________________
> 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 Patil, Priyank
> Sent: Thursday, July 01, 2010 7:57 AM
> To: SAP Workflow Users' Group
> Subject: RE: Activating workflow without using SWDD tcode
>
> The triggering event attached to WF is getting deactivated all the time.
> Its creating a huge problem to us. And it's a customized workflow not a
> standard one.
>
> Thanks
> Priyank
>
> 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 Bhupinder
> Sent: Thursday, July 01, 2010 5:18 PM
> To: SAP Workflow Users' Group
> Subject: Re: Activating workflow without using SWDD tcode
>
> Hi Priyank,
>
> Normally at production system, we are simply activating the triggering
> event attached to WF which sometimes deactivated.
>
> Is this the case in your scenario or WF definition itself gets
> deactivated?
>
> To activate the event, you can either use OOCU tcode or using PFTC.
>
> Best Regards,
> Bhupinder
> On Thu, Jul 1, 2010 at 5:03 PM, Patil, Priyank
> <Priyank.Patil at keane.com<mailto:Priyank.Patil at keane.com>> wrote:
> Wuggers,
>                     Can we activate our workflow without going into
> SWDD.Suppose I have  created one workflow for PO
> approval.Actuallly we don't have access to SWDD tcode
> in production and often the WF is getting inactive
> once its activated. Now is there any way to activate
> workflow using any tcodes or standard program.
>
> ______________________
> Thanks and Regards,
> Priyank Dev Patil
>
>
> ______________________________________________________________________
> Disclaimer: This email message and any attachments are for the sole use of
> the intended recipient(s) and may contain information that is
> confidential, legally privileged or otherwise exempt from disclosure under
> applicable law. If you are not the intended recipient(s) or have received
> this message in error, you are instructed to immediately notify the sender
> by return email and required to delete this message from your computer
> system. This communication does not form any contractual obligation on
> behalf of the sender, the sender's employer or such employer's parent
> company, affiliates or subsidiaries.
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu<mailto:SAP-WUG at mit.edu>
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
> ______________________________________________________________________
> Disclaimer: This email message and any attachments are for the sole use of
> the intended recipient(s) and may contain information that is
> confidential, legally privileged or otherwise exempt from disclosure under
> applicable law. If you are not the intended recipient(s) or have received
> this message in error, you are instructed to immediately notify the sender
> by return email and required to delete this message from your computer
> system. This communication does not form any contractual obligation on
> behalf of the sender, the sender's employer or such employer's parent
> company, affiliates or subsidiaries.
>
> ______________________________________________________________________
> Disclaimer: This email message and any attachments are for the sole use of
> the intended recipient(s) and may contain information that is
> confidential, legally privileged or otherwise exempt from disclosure under
> applicable law. If you are not the intended recipient(s) or have received
> this message in error, you are instructed to immediately notify the sender
> by return email and required to delete this message from your computer
> system. This communication does not form any contractual obligation on
> behalf of the sender, the sender's employer or such employer's parent
> company, affiliates or subsidiaries.
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu<mailto:SAP-WUG at mit.edu>
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
> ______________________________________________________________________
> Disclaimer: This email message and any attachments are for the sole use of
> the intended recipient(s) and may contain information that is
> confidential, legally privileged or otherwise exempt from disclosure under
> applicable law. If you are not the intended recipient(s) or have received
> this message in error, you are instructed to immediately notify the sender
> by return email and required to delete this message from your computer
> system. This communication does not form any contractual obligation on
> behalf of the sender, the sender's employer or such employer's parent
> company, affiliates or subsidiaries.
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu<mailto:SAP-WUG at mit.edu>
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
> ______________________________________________________________________
> Disclaimer: This email message and any attachments are for the sole use of
> the intended recipient(s) and may contain information that is
> confidential, legally privileged or otherwise exempt from disclosure under
> applicable law. If you are not the intended recipient(s) or have received
> this message in error, you are instructed to immediately notify the sender
> by return email and required to delete this message from your computer
> system. This communication does not form any contractual obligation on
> behalf of the sender, the sender's employer or such employer's parent
> company, affiliates or subsidiaries.
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu<mailto:SAP-WUG at mit.edu>
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
> ______________________________________________________________________
> Disclaimer: This email message and any attachments are for the sole use of
> the intended recipient(s) and may contain information that is
> confidential, legally privileged or otherwise exempt from disclosure under
> applicable law. If you are not the intended recipient(s) or have received
> this message in error, you are instructed to immediately notify the sender
> by return email and required to delete this message from your computer
> system. This communication does not form any contractual obligation on
> behalf of the sender, the sender's employer or such employer's parent
> company, affiliates or subsidiaries.
>
> ______________________________________________________________________
> Disclaimer: This email message and any attachments are for the sole use of
> the intended recipient(s) and may contain information that is
> confidential, legally privileged or otherwise exempt from disclosure under
> applicable law. If you are not the intended recipient(s) or have received
> this message in error, you are instructed to immediately notify the sender
> by return email and required to delete this message from your computer
> system. This communication does not form any contractual obligation on
> behalf of the sender, the sender's employer or such employer's parent
> company, affiliates or subsidiaries.
>
> ______________________________________________________________________
> Disclaimer: This email message and any attachments are for the sole use of
> the intended recipient(s) and may contain information that is
> confidential, legally privileged or otherwise exempt from disclosure under
> applicable law. If you are not the intended recipient(s) or have received
> this message in error, you are instructed to immediately notify the sender
> by return email and required to delete this message from your computer
> system. This communication does not form any contractual obligation on
> behalf of the sender, the sender's employer or such employer's parent
> company, affiliates or subsidiaries.
>
> ______________________________________________________________________
> Disclaimer:  This email message and any attachments are for the sole use
> of the intended recipient(s) and may contain information that is
> confidential, legally privileged or otherwise exempt from disclosure under
> applicable law. If you are not the intended recipient(s) or have received
> this message in error, you are instructed to immediately notify the sender
> by return email and required to delete this message from your computer
> system. This communication does not form any contractual obligation on
> behalf of the sender, the sender's employer or such employer's parent
> company, affiliates or
> subsidiaries._______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>