SAP-WUG Digest, Vol 36, Issue 31

Albina Fernando albinafernando at gmail.com
Thu Nov 15 20:47:23 EST 2007


Hi Mark,

   Thank you so much for your reply. This option worked..

Thanks
Albina


On 11/14/07, sap-wug-request at mit.edu <sap-wug-request at mit.edu> wrote:
>
> 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. Difference in views "Organization and Staffing" &
>      "Organization and Staffing (workflow)" (Tom Peou)
>   2. Removing work item from UWL (Albina Fernando)
>   3. Re: Removing work item from UWL (Mark Pyc)
>   4. Configure Extended Notifications in QA/PRD (Mike Pokraka)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 14 Nov 2007 09:12:28 +1100
> From: "Tom Peou" <tompeou at gmail.com>
> Subject: Difference in views "Organization and Staffing" &
>        "Organization and       Staffing (workflow)"
> To: sap-wug at mit.edu
> Message-ID:
>        <a420e49e0711131412y1d20168uc6f47bedbcf57f6d at mail.gmail.com>
> Content-Type: text/plain; charset="windows-1252"
>
> Hi Khawaja,
>
> Yes. Both transactions are synchronised. The workflow view includes
> additional detail (Basic data) of Workflow and Tasks "agent assignment",
> standard WF role/rule, etc that are specific to Workflow.
>
> Cheers,
> Tom
>
> ---------- Forwarded message ----------
> From: <b_khawaja at ppl.com.pk>
> To: <sap-wug at mit.edu>
> Date: Tue, 13 Nov 2007 16:48:41 +0500
> Subject: Difference in views "Organization and Staffing" & "Organization
> and
> Staffing (workflow)"
>
>
> We are using the PPOME "Organization and Staffing" in a workflow for Role
> Resolution.
>
> The Standard Role "0000157" (Superior ?chief Position- ) is to be used,
> which will require a *restructuring* of the Org Structure.
>
>
>
> Therefore,  I need to know,
>
> The difference between the two views  "Organization and Staffing" &
> "Organization and Staffing (workflow)",
>
> and if these two views are synchronized.
>
>
>
> And if there is difference between the two views then how to configure the
> view ""Organization and Staffing (workflow)" for using in the workflow.
>
>
>
>
>
> Regards,
>
>
>
> Khawaja  Bilal Sohaib.
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://mailman.mit.edu/pipermail/sap-wug/attachments/20071114/28e3f503/attachment-0001.htm
>
> ------------------------------
>
> Message: 2
> Date: Wed, 14 Nov 2007 00:52:22 -0700
> From: "Albina Fernando" <albinafernando at gmail.com>
> Subject: Removing work item from UWL
> To: SAP-WUG at mit.edu
> Message-ID:
>        <780731090711132352n7c89f4a7t516733ba8d209d6f at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi,
>
> We have a scenario wherein..  we are using Sequential approval.
> i.eWorkflow gets triggerred and all the approvers selected receive the
> work
> items and email at the same time. So what we have done is first a method
> that will fetch the approvers. then we have used a Loop that will loop
> through all the approvers and send each approver a work item and an email.
> So within the loop we have used a Fork to  achive this.this is the main
> workflow. Now each time the work item is to be sent, we have used an event
> creator step in the main workflow that creates an event to send the
> workitem
> to the approvers. And this event is in turn trigerred in another workflow.
> And that workflow will send the work items.
> Once the approver rejects the request, a mail shld be sent to the
> requestor , the workflow should be terminated and all the Work items
> should
> be removed from the other approvers UWL who have not approved yet. Now
> since
> this Sending of work items to different approvers is in a separate
> Workflow,
> is there any way to achieve this scenario, i.e removing the Work items
> from
> other approvers UWL. To remove the work items from the approvers UWL
> atleast
> we should have the reference of the main workflow. Using that we can find
> out. but we do not have any such reference. The approval is actually
> random..and any approver can approve at any point.
> Can anyone provide inputs on the same? Can we use a Custom Ztable or
> something that will store the Workitem ids along with the main workflow id
> and we can store this detail when the workitem is created. And then once
> the
> approver rejects then from this Ztable we can fetch the workitems for this
> main workflow id and then use the WAPI delete func module to logically
> delete the workflow. Is this approach correct?
>
> Thanks
> Albina
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://mailman.mit.edu/pipermail/sap-wug/attachments/20071114/8e5d3148/attachment-0001.htm
>
> ------------------------------
>
> Message: 3
> Date: Wed, 14 Nov 2007 09:46:43 +0000
> From: "Mark Pyc" <mark.pyc at gmail.com>
> Subject: Re: Removing work item from UWL
> To: "SAP Workflow Users' Group" <sap-wug at mit.edu>
> Message-ID:
>        <23f0a78a0711140146s3762da38ye8dc3063922247db at mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> G'day Albina,
>
> There has been a discussion about this very concept in the last week (the
> solution for which have been attributed to me <BLUSH!>)
>
> Instead of using an event creation step to generate your individual WFs
> you
> can use dynamic parallel processing. You create a single subflow step (an
> activity step where you reference a WS instead of a TS) where you can pass
> in a single agent and any other info. On the one of the last steop tabs
> (other data or miscellaneous depending on release) you set your agent
> table as the 'Multline Element'. When you do the binding to the subflow
> you'll have a special option for binding the table of agents into the
> subflow. What happens is that for each agent in the table the system will
> create a subflow passing in 1 agent into each subflow.
>
> The point of all this is that you can put this call to the subflow in one
> branch of a 1 of 2 fork. In the other fork you wait for an event. When any
> of the approvers reject you should raise this event from the subflow. This
> will shut down the fork and all outstanding subflows will be logically
> delelted.
>
> The convo recently has been about having deadlines over subflows, but it's
> almost the same.
>
> So the recommendation is to have event communication from subflow to
> mainflow on rejection, but to use dynamic parallel processing to generate
> the subflows.
>
> Have fun,
> Mark
>
>
>
>
> On 14/11/2007, Albina Fernando <albinafernando at gmail.com> wrote:
> >
> > Hi,
> >
> >   We have a scenario wherein..  we are using Sequential approval.
> i.eWorkflow gets triggerred and all the approvers selected receive the
> work
> > items and email at the same time. So what we have done is first a method
> > that will fetch the approvers. then we have used a Loop that will loop
> > through all the approvers and send each approver a work item and an
> email.
> > So within the loop we have used a Fork to  achive this.this is the main
> > workflow. Now each time the work item is to be sent, we have used an
> event
> > creator step in the main workflow that creates an event to send the
> workitem
> > to the approvers. And this event is in turn trigerred in another
> workflow.
> > And that workflow will send the work items.
> >   Once the approver rejects the request, a mail shld be sent to the
> > requestor , the workflow should be terminated and all the Work items
> should
> > be removed from the other approvers UWL who have not approved yet. Now
> since
> > this Sending of work items to different approvers is in a separate
> Workflow,
> > is there any way to achieve this scenario, i.e removing the Work items
> > from other approvers UWL. To remove the work items from the approvers
> UWL
> > atleast we should have the reference of the main workflow. Using that we
> can
> > find out. but we do not have any such reference. The approval is
> actually
> > random..and any approver can approve at any point.
> >   Can anyone provide inputs on the same? Can we use a Custom Ztable or
> > something that will store the Workitem ids along with the main workflow
> id
> > and we can store this detail when the workitem is created. And then once
> the
> > approver rejects then from this Ztable we can fetch the workitems for
> this
> > main workflow id and then use the WAPI delete func module to logically
> > delete the workflow. Is this approach correct?
> >
> > Thanks
> > Albina
> >
> >
> >
> > _______________________________________________
> > 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/20071114/9a58aad5/attachment-0001.htm
>
> ------------------------------
>
> Message: 4
> Date: Wed, 14 Nov 2007 15:13:12 -0000 (UTC)
> From: "Mike Pokraka" <asap at workflowconnections.com>
> Subject: Configure Extended Notifications in QA/PRD
> To: sap-wug at mit.edu
> Message-ID:
>        <
> 51147.212.157.152.235.1195053192.squirrel at pluto.workflowconnections.com>
>
> Content-Type: text/plain;charset=iso-8859-1
>
> Hi Wuggers,
>
> Quick question: How do I configure extended notifications in non-dev
> systems?
>
> Everything gets transported, including system-specific settings like the
> sender address and the system to log onto, and I cannot change it.
>
> Or am I missing something obvious?
>
> TIA,
> Mike
>
>
>
>
> ------------------------------
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>
>
> End of SAP-WUG Digest, Vol 36, Issue 31
> ***************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20071115/b60d1718/attachment.htm


More information about the SAP-WUG mailing list