SWWDHEX starts a French workflow

Ali Husain mr_mago40 at hotmail.com
Tue Jan 24 01:01:50 EST 2012



Hello Paul,
Why don't you cancel the existing workflow and start a new one manually in SWUE with the same key field and see if that fixes the issue?
I was also wondering if the language issue for the deadline job might be fixed if a new user who's logged in 'EN' and have the proper authorization run the automatic customizing in SWU3.
Regards,Ali


> From: sap-wug-request at mit.edu
> Subject: SAP-WUG Digest, Vol 86, Issue 23
> To: sap-wug at mit.edu
> Date: Mon, 23 Jan 2012 23:21:54 -0500
> 
> 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. SWWDHEX starts a French workflow
>       (Paul.Bakker at osr.treasury.qld.gov.au)
>    2. RE: SWWDHEX starts a French workflow (Dart, Jocelyn)
>    3. RE: SWWDHEX starts a French workflow
>       (Paul.Bakker at osr.treasury.qld.gov.au)
>    4. RE: SWWDHEX starts a French workflow (Dart, Jocelyn)
>    5. RE: SWWDHEX starts a French workflow
>       (Paul.Bakker at osr.treasury.qld.gov.au)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Tue, 24 Jan 2012 12:17:56 +1000
> From: Paul.Bakker at osr.treasury.qld.gov.au
> Subject: SWWDHEX starts a French workflow
> To: sap-wug at mit.edu
> Message-ID: <201201240218.q0O2I4F7008815 at mailhub-dmz-3.mit.edu>
> Content-Type: text/plain; charset="us-ascii"
> 
> 
> Regular readers of the WUG group might remember my question from a few
> weeks ago:
> 
>         How is the WorkItemLanguage of a workflow set?
> 
> I had an urgent problem: mining engineers in the outback were receiving
> workflow emails in French, and they weren't happy about it.
> 
> Using advice from Florin W. I tracked down the culprit: the deadline job
> SWWDHEX (!). This job had been set up from SWU3 with a language of 'FR' (in
> the 'step' tab).
> 
> When a workitem deadline expires, SWWDHEX (under user WF-BATCH) terminates
> the current workitem. The workflow continues on and approves the
> procurement  document (at the current release level), and this triggers a
> new approval workflow for the next level.
> 
> This new workflow is started with the WorkItemLanguage copied from the
> SWWDHEX job. Presumably the language id 'FR' is stored in SY-LANGU  at the
> time that the workflow is triggered.
> 
> My question is now: how can I change SY-LANGU in the ABAP code, before the
> next workflow is triggered?
> 
> In the code just before BAPI_REQUISITION_RELEASE_GEN I have tried:
> - sy-langu = 'EN'.
> - 'SET LOCALE LANGUAGE 'E'.
> 
> But neither have had any effect.
> 
> Is there a better approach? Or is there another way to stop the evil
> influence of the SWWDHEX job?
> 
> thanks
> Paul Bakker
> 
> 
> *********************************************************************************************
> Only an individual or entity who is intended to be a recipient of this e-mail may access or use the information contained in this e-mail or any of its attachments.  Opinions contained in this e-mail or any of its attachments do not necessarily reflect the opinions of Queensland Treasury.
> 
> The contents of this e-mail and any attachments are confidential and may be legally privileged and the subject of copyright.  If you have received this e-mail in error, please notify Queensland Treasury immediately and erase all copies of the e-mail and the attachments.  Queensland Treasury uses virus scanning software.  However, it is not liable for viruses present in this e-mail or in any attachment.  
> ***************************************************************************************************
> 
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Tue, 24 Jan 2012 03:56:56 +0100
> From: "Dart, Jocelyn" <jocelyn.dart at sap.com>
> Subject: RE: SWWDHEX starts a French workflow
> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> Message-ID:
> 	<8C507B5E0BA5114E933C3C6E2E9729E007674CEE85 at DEWDFECCR01.wdf.sap.corp>
> Content-Type: text/plain; charset="us-ascii"
> 
> Hi Paul, 
> Maybe you should just get them to set on the inbox Personal Workflow Settings to translate work items to your own language (English) temporarily?
> Or is the problem that French isn't giving you any text at all?
> 
> You could also try just updating WI_LANG on table SWWWIHEAD which should do the same thing.
> Regards,
> Jocelyn 
> 
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Paul.Bakker at osr.treasury.qld.gov.au
> Sent: Tuesday, 24 January 2012 1:18 PM
> To: sap-wug at mit.edu
> Subject: SWWDHEX starts a French workflow
> 
> 
> Regular readers of the WUG group might remember my question from a few
> weeks ago:
> 
>         How is the WorkItemLanguage of a workflow set?
> 
> I had an urgent problem: mining engineers in the outback were receiving
> workflow emails in French, and they weren't happy about it.
> 
> Using advice from Florin W. I tracked down the culprit: the deadline job
> SWWDHEX (!). This job had been set up from SWU3 with a language of 'FR' (in
> the 'step' tab).
> 
> When a workitem deadline expires, SWWDHEX (under user WF-BATCH) terminates
> the current workitem. The workflow continues on and approves the
> procurement  document (at the current release level), and this triggers a
> new approval workflow for the next level.
> 
> This new workflow is started with the WorkItemLanguage copied from the
> SWWDHEX job. Presumably the language id 'FR' is stored in SY-LANGU  at the
> time that the workflow is triggered.
> 
> My question is now: how can I change SY-LANGU in the ABAP code, before the
> next workflow is triggered?
> 
> In the code just before BAPI_REQUISITION_RELEASE_GEN I have tried:
> - sy-langu = 'EN'.
> - 'SET LOCALE LANGUAGE 'E'.
> 
> But neither have had any effect.
> 
> Is there a better approach? Or is there another way to stop the evil
> influence of the SWWDHEX job?
> 
> thanks
> Paul Bakker
> 
> 
> *********************************************************************************************
> Only an individual or entity who is intended to be a recipient of this e-mail may access or use the information contained in this e-mail or any of its attachments.  Opinions contained in this e-mail or any of its attachments do not necessarily reflect the opinions of Queensland Treasury.
> 
> The contents of this e-mail and any attachments are confidential and may be legally privileged and the subject of copyright.  If you have received this e-mail in error, please notify Queensland Treasury immediately and erase all copies of the e-mail and the attachments.  Queensland Treasury uses virus scanning software.  However, it is not liable for viruses present in this e-mail or in any attachment.  
> ***************************************************************************************************
> 
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
> 
> 
> 
> ------------------------------
> 
> Message: 3
> Date: Tue, 24 Jan 2012 13:17:41 +1000
> From: Paul.Bakker at osr.treasury.qld.gov.au
> Subject: RE: SWWDHEX starts a French workflow
> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> Message-ID: <201201240317.q0O3GVEk013986 at mailhub-dmz-3.mit.edu>
> Content-Type: text/plain; charset=US-ASCII
> 
> 
> Thanks for that. Unfortunately, Inbox settings won't help.
> 
> The problem is that the workflow is using 'SendTaskDescriptio'n to send
> emails containing the workitem text.
> Because WorkitemLanguage = 'FR', it is always choosing to send the
> translated French text in the email.
> 
> (I know - it should have been built to use Extended Notifications
> instead.... I'm just the maintenance guy)
> 
> Also, it's not so easy to change the WI language - once the WI Language of
> the toplevel workflow is set, it flows through to every subsequent
> workitem.
> 
> +++
> 
> This is a bit of a worrying 'feature' of deadlines - any new workflows
> kicked off by deadline handling will inherit a hardcoded language..... the
> logon language of the guy who happened to run SWU3 in Production!
> 
> cheers
> Paul Bakker
> 
> 
> 
> From:	"Dart, Jocelyn" <jocelyn.dart at sap.com>
> To:	"SAP Workflow Users' Group" <sap-wug at mit.edu>
> Date:	24/01/2012 01:00 PM
> Subject:	RE: SWWDHEX starts a French workflow
> Sent by:	sap-wug-bounces at mit.edu
> 
> 
> 
> Hi Paul,
> Maybe you should just get them to set on the inbox Personal Workflow
> Settings to translate work items to your own language (English)
> temporarily?
> Or is the problem that French isn't giving you any text at all?
> 
> You could also try just updating WI_LANG on table SWWWIHEAD which should do
> the same thing.
> Regards,
> Jocelyn
> 
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
> Paul.Bakker at osr.treasury.qld.gov.au
> Sent: Tuesday, 24 January 2012 1:18 PM
> To: sap-wug at mit.edu
> Subject: SWWDHEX starts a French workflow
> 
> 
> Regular readers of the WUG group might remember my question from a few
> weeks ago:
> 
>         How is the WorkItemLanguage of a workflow set?
> 
> I had an urgent problem: mining engineers in the outback were receiving
> workflow emails in French, and they weren't happy about it.
> 
> Using advice from Florin W. I tracked down the culprit: the deadline job
> SWWDHEX (!). This job had been set up from SWU3 with a language of 'FR' (in
> the 'step' tab).
> 
> When a workitem deadline expires, SWWDHEX (under user WF-BATCH) terminates
> the current workitem. The workflow continues on and approves the
> procurement  document (at the current release level), and this triggers a
> new approval workflow for the next level.
> 
> This new workflow is started with the WorkItemLanguage copied from the
> SWWDHEX job. Presumably the language id 'FR' is stored in SY-LANGU  at the
> time that the workflow is triggered.
> 
> My question is now: how can I change SY-LANGU in the ABAP code, before the
> next workflow is triggered?
> 
> In the code just before BAPI_REQUISITION_RELEASE_GEN I have tried:
> - sy-langu = 'EN'.
> - 'SET LOCALE LANGUAGE 'E'.
> 
> But neither have had any effect.
> 
> Is there a better approach? Or is there another way to stop the evil
> influence of the SWWDHEX job?
> 
> thanks
> Paul Bakker
> 
> 
> *********************************************************************************************
> 
> Only an individual or entity who is intended to be a recipient of this
> e-mail may access or use the information contained in this e-mail or any of
> its attachments.  Opinions contained in this e-mail or any of its
> attachments do not necessarily reflect the opinions of Queensland Treasury.
> 
> The contents of this e-mail and any attachments are confidential and may be
> legally privileged and the subject of copyright.  If you have received this
> e-mail in error, please notify Queensland Treasury immediately and erase
> all copies of the e-mail and the attachments.  Queensland Treasury uses
> virus scanning software.  However, it is not liable for viruses present in
> this e-mail or in any attachment.
> ***************************************************************************************************
> 
> 
> _______________________________________________
> 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
> 
> 
> 
> 
> ------------------------------
> 
> Message: 4
> Date: Tue, 24 Jan 2012 04:33:20 +0100
> From: "Dart, Jocelyn" <jocelyn.dart at sap.com>
> Subject: RE: SWWDHEX starts a French workflow
> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> Message-ID:
> 	<8C507B5E0BA5114E933C3C6E2E9729E007674CEE9D at DEWDFECCR01.wdf.sap.corp>
> Content-Type: text/plain; charset="us-ascii"
> 
> Hi Paul, 
> Is there some reason why you can't just fix the job in SM37 in Prod? Yes its scheduled by SWU3 but that's a matter of convenience ... the job is just a job. 
> Cheers, 
> Jocelyn  
> 
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of Paul.Bakker at osr.treasury.qld.gov.au
> Sent: Tuesday, 24 January 2012 2:18 PM
> To: SAP Workflow Users' Group
> Subject: RE: SWWDHEX starts a French workflow
> 
> 
> Thanks for that. Unfortunately, Inbox settings won't help.
> 
> The problem is that the workflow is using 'SendTaskDescriptio'n to send
> emails containing the workitem text.
> Because WorkitemLanguage = 'FR', it is always choosing to send the
> translated French text in the email.
> 
> (I know - it should have been built to use Extended Notifications
> instead.... I'm just the maintenance guy)
> 
> Also, it's not so easy to change the WI language - once the WI Language of
> the toplevel workflow is set, it flows through to every subsequent
> workitem.
> 
> +++
> 
> This is a bit of a worrying 'feature' of deadlines - any new workflows
> kicked off by deadline handling will inherit a hardcoded language..... the
> logon language of the guy who happened to run SWU3 in Production!
> 
> cheers
> Paul Bakker
> 
> 
> 
> From:	"Dart, Jocelyn" <jocelyn.dart at sap.com>
> To:	"SAP Workflow Users' Group" <sap-wug at mit.edu>
> Date:	24/01/2012 01:00 PM
> Subject:	RE: SWWDHEX starts a French workflow
> Sent by:	sap-wug-bounces at mit.edu
> 
> 
> 
> Hi Paul,
> Maybe you should just get them to set on the inbox Personal Workflow
> Settings to translate work items to your own language (English)
> temporarily?
> Or is the problem that French isn't giving you any text at all?
> 
> You could also try just updating WI_LANG on table SWWWIHEAD which should do
> the same thing.
> Regards,
> Jocelyn
> 
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
> Paul.Bakker at osr.treasury.qld.gov.au
> Sent: Tuesday, 24 January 2012 1:18 PM
> To: sap-wug at mit.edu
> Subject: SWWDHEX starts a French workflow
> 
> 
> Regular readers of the WUG group might remember my question from a few
> weeks ago:
> 
>         How is the WorkItemLanguage of a workflow set?
> 
> I had an urgent problem: mining engineers in the outback were receiving
> workflow emails in French, and they weren't happy about it.
> 
> Using advice from Florin W. I tracked down the culprit: the deadline job
> SWWDHEX (!). This job had been set up from SWU3 with a language of 'FR' (in
> the 'step' tab).
> 
> When a workitem deadline expires, SWWDHEX (under user WF-BATCH) terminates
> the current workitem. The workflow continues on and approves the
> procurement  document (at the current release level), and this triggers a
> new approval workflow for the next level.
> 
> This new workflow is started with the WorkItemLanguage copied from the
> SWWDHEX job. Presumably the language id 'FR' is stored in SY-LANGU  at the
> time that the workflow is triggered.
> 
> My question is now: how can I change SY-LANGU in the ABAP code, before the
> next workflow is triggered?
> 
> In the code just before BAPI_REQUISITION_RELEASE_GEN I have tried:
> - sy-langu = 'EN'.
> - 'SET LOCALE LANGUAGE 'E'.
> 
> But neither have had any effect.
> 
> Is there a better approach? Or is there another way to stop the evil
> influence of the SWWDHEX job?
> 
> thanks
> Paul Bakker
> 
> 
> *********************************************************************************************
> 
> Only an individual or entity who is intended to be a recipient of this
> e-mail may access or use the information contained in this e-mail or any of
> its attachments.  Opinions contained in this e-mail or any of its
> attachments do not necessarily reflect the opinions of Queensland Treasury.
> 
> The contents of this e-mail and any attachments are confidential and may be
> legally privileged and the subject of copyright.  If you have received this
> e-mail in error, please notify Queensland Treasury immediately and erase
> all copies of the e-mail and the attachments.  Queensland Treasury uses
> virus scanning software.  However, it is not liable for viruses present in
> this e-mail or in any attachment.
> ***************************************************************************************************
> 
> 
> _______________________________________________
> 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
> 
> 
> 
> ------------------------------
> 
> Message: 5
> Date: Tue, 24 Jan 2012 14:21:32 +1000
> From: Paul.Bakker at osr.treasury.qld.gov.au
> Subject: RE: SWWDHEX starts a French workflow
> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> Message-ID: <201201240421.q0O4Lghv018437 at mailhub-dmz-4.mit.edu>
> Content-Type: text/plain; charset=US-ASCII
> 
> Jocelyn,
> 
> The French users might storm the Bastille if I did that! :-)
> 
> I don't want any language to be hardcoded, if it controls the translation
> of the emails.
> 
> Our idea is to have sy-langu transferred from the original
> (deadline-terminated) workflow to the new one.
> I have all the bindings in place to do that, but SY-LANGU just doesn't want
> to be changed..
> 
> merci
> Paul
> 
> 
> 
> From:	"Dart, Jocelyn" <jocelyn.dart at sap.com>
> To:	"SAP Workflow Users' Group" <sap-wug at mit.edu>
> Date:	24/01/2012 01:37 PM
> Subject:	RE: SWWDHEX starts a French workflow
> Sent by:	sap-wug-bounces at mit.edu
> 
> 
> 
> Hi Paul,
> Is there some reason why you can't just fix the job in SM37 in Prod? Yes
> its scheduled by SWU3 but that's a matter of convenience ... the job is
> just a job.
> Cheers,
> Jocelyn
> 
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
> Paul.Bakker at osr.treasury.qld.gov.au
> Sent: Tuesday, 24 January 2012 2:18 PM
> To: SAP Workflow Users' Group
> Subject: RE: SWWDHEX starts a French workflow
> 
> 
> Thanks for that. Unfortunately, Inbox settings won't help.
> 
> The problem is that the workflow is using 'SendTaskDescriptio'n to send
> emails containing the workitem text.
> Because WorkitemLanguage = 'FR', it is always choosing to send the
> translated French text in the email.
> 
> (I know - it should have been built to use Extended Notifications
> instead.... I'm just the maintenance guy)
> 
> Also, it's not so easy to change the WI language - once the WI Language of
> the toplevel workflow is set, it flows through to every subsequent
> workitem.
> 
> +++
> 
> This is a bit of a worrying 'feature' of deadlines - any new workflows
> kicked off by deadline handling will inherit a hardcoded language..... the
> logon language of the guy who happened to run SWU3 in Production!
> 
> cheers
> Paul Bakker
> 
> 
> 
> From:		 "Dart, Jocelyn" <jocelyn.dart at sap.com>
> To:		 "SAP Workflow Users' Group" <sap-wug at mit.edu>
> Date:		 24/01/2012 01:00 PM
> Subject:		 RE: SWWDHEX starts a French workflow
> Sent by:		 sap-wug-bounces at mit.edu
> 
> 
> 
> Hi Paul,
> Maybe you should just get them to set on the inbox Personal Workflow
> Settings to translate work items to your own language (English)
> temporarily?
> Or is the problem that French isn't giving you any text at all?
> 
> You could also try just updating WI_LANG on table SWWWIHEAD which should do
> the same thing.
> Regards,
> Jocelyn
> 
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
> Paul.Bakker at osr.treasury.qld.gov.au
> Sent: Tuesday, 24 January 2012 1:18 PM
> To: sap-wug at mit.edu
> Subject: SWWDHEX starts a French workflow
> 
> 
> Regular readers of the WUG group might remember my question from a few
> weeks ago:
> 
>         How is the WorkItemLanguage of a workflow set?
> 
> I had an urgent problem: mining engineers in the outback were receiving
> workflow emails in French, and they weren't happy about it.
> 
> Using advice from Florin W. I tracked down the culprit: the deadline job
> SWWDHEX (!). This job had been set up from SWU3 with a language of 'FR' (in
> the 'step' tab).
> 
> When a workitem deadline expires, SWWDHEX (under user WF-BATCH) terminates
> the current workitem. The workflow continues on and approves the
> procurement  document (at the current release level), and this triggers a
> new approval workflow for the next level.
> 
> This new workflow is started with the WorkItemLanguage copied from the
> SWWDHEX job. Presumably the language id 'FR' is stored in SY-LANGU  at the
> time that the workflow is triggered.
> 
> My question is now: how can I change SY-LANGU in the ABAP code, before the
> next workflow is triggered?
> 
> In the code just before BAPI_REQUISITION_RELEASE_GEN I have tried:
> - sy-langu = 'EN'.
> - 'SET LOCALE LANGUAGE 'E'.
> 
> But neither have had any effect.
> 
> Is there a better approach? Or is there another way to stop the evil
> influence of the SWWDHEX job?
> 
> thanks
> Paul Bakker
> 
> 
> *********************************************************************************************
> 
> 
> Only an individual or entity who is intended to be a recipient of this
> e-mail may access or use the information contained in this e-mail or any of
> its attachments.  Opinions contained in this e-mail or any of its
> attachments do not necessarily reflect the opinions of Queensland Treasury.
> 
> The contents of this e-mail and any attachments are confidential and may be
> legally privileged and the subject of copyright.  If you have received this
> e-mail in error, please notify Queensland Treasury immediately and erase
> all copies of the e-mail and the attachments.  Queensland Treasury uses
> virus scanning software.  However, it is not liable for viruses present in
> this e-mail or in any attachment.
> ***************************************************************************************************
> 
> 
> 
> _______________________________________________
> 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
> 
> _______________________________________________
> 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
> 
> 
> End of SAP-WUG Digest, Vol 86, Issue 23
> ***************************************
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20120124/62a9aa73/attachment-0001.htm


More information about the SAP-WUG mailing list