Activating workflow without using SWDD tcode

[Rick Bakker]

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>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] *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>
> 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] *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>
> 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] *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’?
>
>
>
> 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] *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] *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>
> 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
> 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
> 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
> 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
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20100702/de7944e9/attachment.htm
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 12825 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/sap-wug/attachments/20100702/de7944e9/attachment.jpg