<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Logic for workflow in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/logic-for-workflow/m-p/1045037#M87624</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ame,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check out this link for the workflows.thie will really help u.Detailed desc of the workflow is given in this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2005/helpdata/en/d9/506642ea59c753e10000000a1550b0/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2005/helpdata/en/d9/506642ea59c753e10000000a1550b0/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps u,&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Nagarajan.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 08 Dec 2005 11:01:40 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2005-12-08T11:01:40Z</dc:date>
    <item>
      <title>Logic for workflow</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/logic-for-workflow/m-p/1045035#M87622</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;Kindly help me out with the logic building for this scenario:&lt;/P&gt;&lt;P&gt;There is a customized workflow attached with Purchase Requisition approval. This workflow has an Org structure based on departments. The approver is determined based on admin id or the workflow initiator.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Issue is : if the same user has to create a PR for different department, he/she will have to login with the admin's id for that department.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Requirement : Same user should be able to create PRs for any department. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, is there a way of adding this condition with minimum change ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Dec 2005 23:01:47 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/logic-for-workflow/m-p/1045035#M87622</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-12-07T23:01:47Z</dc:date>
    </item>
    <item>
      <title>Re: Logic for workflow</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/logic-for-workflow/m-p/1045036#M87623</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi use the following links&lt;/P&gt;&lt;P&gt;&amp;lt;a href="www.sapgenie.com/workflow/"&amp;gt;www.sapgenie.com/workflow/&amp;lt;/a&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;lt;a href="www.sapgenie.com/workflow/scenarios.htm"&amp;gt;Scenarios&amp;lt;/a&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Dec 2005 10:55:32 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/logic-for-workflow/m-p/1045036#M87623</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-12-08T10:55:32Z</dc:date>
    </item>
    <item>
      <title>Re: Logic for workflow</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/logic-for-workflow/m-p/1045037#M87624</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ame,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check out this link for the workflows.thie will really help u.Detailed desc of the workflow is given in this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_erp2005/helpdata/en/d9/506642ea59c753e10000000a1550b0/frameset.htm" target="test_blank"&gt;http://help.sap.com/saphelp_erp2005/helpdata/en/d9/506642ea59c753e10000000a1550b0/frameset.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps u,&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Nagarajan.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Dec 2005 11:01:40 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/logic-for-workflow/m-p/1045037#M87624</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-12-08T11:01:40Z</dc:date>
    </item>
    <item>
      <title>Re: Logic for workflow</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/logic-for-workflow/m-p/1045038#M87625</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;try these useful links&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;/people/ginger.gatling/blog/2005/12/01/link-workflow-business-objects-to-your-collaboration-tasks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_nw04/helpdata/en/92/bc26a6ec2b11d2b4b5006094b9ea0d/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_nw04/helpdata/en/92/bc26a6ec2b11d2b4b5006094b9ea0d/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_bw33/helpdata/en/92/bc26a6ec2b11d2b4b5006094b9ea0d/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_bw33/helpdata/en/92/bc26a6ec2b11d2b4b5006094b9ea0d/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_bw31/helpdata/en/8d/25f94b454311d189430000e829fbbd/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_bw31/helpdata/en/8d/25f94b454311d189430000e829fbbd/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards&lt;/P&gt;&lt;P&gt;Arun&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Dec 2005 11:04:53 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/logic-for-workflow/m-p/1045038#M87625</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-12-08T11:04:53Z</dc:date>
    </item>
    <item>
      <title>Re: Logic for workflow</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/logic-for-workflow/m-p/1045039#M87626</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ameekar&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As I understand it, your problem is that the current agent determination process is to select the appropriate approver based on the particular department creating the requsition.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One solution might be to change the agent determination for the approval task to select the approver based on an Organizational Unit rather than by department.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Org units are sort of free standing HR groupings.  You can create an Org unit.  Assign people to the Org unit and then designate that org unit as the agent for the approval task.  Thus in your case you could create an org unit of Approvers then assign multiple people to it and requsitions would be routed to the org unit for approval regardless of Department.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Some things to consider:&lt;/P&gt;&lt;P&gt;1. Everybody in the org unit will see the task in their worklist - first one to open it reserves it and others cannot work on it unless it's replaced back into the worklist&lt;/P&gt;&lt;P&gt;2. It's nice for when people go on vacation, automatically takes care of the workload by allowing others to execute workitems&lt;/P&gt;&lt;P&gt;3. It has the ability to deal with part time people.  When you assign a person to an org unit you can specifiy their hours of availability or the percentage of their time involvement - system automatically takes this into consideration.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Brent&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Dec 2005 16:20:04 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/logic-for-workflow/m-p/1045039#M87626</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-12-08T16:20:04Z</dc:date>
    </item>
    <item>
      <title>Re: Logic for workflow</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/logic-for-workflow/m-p/1045040#M87627</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Vijayasarathy, Nagarajan, Arun &amp;amp; Brent,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you all for your various links and suggestions but none of that solves the problem. &lt;/P&gt;&lt;P&gt;Brent to answer you, we already have Org units set up. The departments that i mentioned about are nothing else but Org units.&lt;/P&gt;&lt;P&gt;As of now each Org unit has a single admin and a single Manager but the scenario that i am looking for would have 2 or more Managers as the Possible agents. The trick is how should i select the correct Manager based on any other parameter, other than the initiator's id. &lt;/P&gt;&lt;P&gt;Thus what field in a Purchase Requisition can i make use of (i should be able to validate that field or provide with an F4 help) to select the Mgr.&lt;/P&gt;&lt;P&gt;There is a Requisitioner field available but how do i go about validating if the user entered the correct user id.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Dec 2005 23:30:55 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/logic-for-workflow/m-p/1045040#M87627</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-12-08T23:30:55Z</dc:date>
    </item>
    <item>
      <title>Re: Logic for workflow</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/logic-for-workflow/m-p/1045041#M87628</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ameekar,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The approver should be determined based on department rather than admin id or the workflow initiator. You should be able to derive the org unit based on some fields (account assignment) in the PR. Take a look at the standard agent rule 00000157. You can use this rule if you can derive the org unit.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Ramki Maley.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 09 Dec 2005 12:29:02 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/logic-for-workflow/m-p/1045041#M87628</guid>
      <dc:creator>ramki_maley</dc:creator>
      <dc:date>2005-12-09T12:29:02Z</dc:date>
    </item>
    <item>
      <title>Re: Logic for workflow</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/logic-for-workflow/m-p/1045042#M87629</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Ramki, i was looking for a solution on similar lines. Will try this and get back to you.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 10 Dec 2005 00:09:46 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/logic-for-workflow/m-p/1045042#M87629</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2005-12-10T00:09:46Z</dc:date>
    </item>
  </channel>
</rss>

