<?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: procedure for workflow in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/procedure-for-workflow/m-p/2741397#M636951</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Purchase Order and Sales Order Workflow &lt;/P&gt;&lt;P&gt;Purchase Order workflow ( Transaction : ME23N) determines the approval path for the buying organization . It first goes to the buyer, buyer's manager &amp;amp; thereafter based on the cost center &amp;amp; the associated amount, it goes for approval through the Cost Center organization . &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i.e, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Buyer ( Requestor in the procurement deptt. of the buying organization) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;                                | &lt;/P&gt;&lt;P&gt;                                | &lt;/P&gt;&lt;P&gt;                                v &lt;/P&gt;&lt;P&gt;                      Procurement Manager &lt;/P&gt;&lt;P&gt;                                | &lt;/P&gt;&lt;P&gt;                                | &lt;/P&gt;&lt;P&gt;                                v &lt;/P&gt;&lt;P&gt;                      Cost Center org. approval ( based on amount &amp;amp; Sign.Authority level) &lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regarding , Sales Order( Transaction: VA01); it is created in the Sales Org of the company  &amp;amp; basically governs the pricing structure of the order .The routing of an SO is &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;                 Sales Org. ( based on the cost center of the sold item) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;                                | &lt;/P&gt;&lt;P&gt;                                | &lt;/P&gt;&lt;P&gt;                                v &lt;/P&gt;&lt;P&gt;                       Distribution Channel  &lt;/P&gt;&lt;P&gt;                                | &lt;/P&gt;&lt;P&gt;                                | &lt;/P&gt;&lt;P&gt;                                v &lt;/P&gt;&lt;P&gt;                           Division &lt;/P&gt;&lt;P&gt;                                | &lt;/P&gt;&lt;P&gt;                                | &lt;/P&gt;&lt;P&gt;                                v &lt;/P&gt;&lt;P&gt;                           Reg. Sales office &lt;/P&gt;&lt;P&gt;                                | &lt;/P&gt;&lt;P&gt;                                | &lt;/P&gt;&lt;P&gt;                                v &lt;/P&gt;&lt;P&gt;                           Sales Group &lt;/P&gt;&lt;P&gt;                                | &lt;/P&gt;&lt;P&gt;                                | &lt;/P&gt;&lt;P&gt;                                v &lt;/P&gt;&lt;P&gt;                           Sales Person &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Vasu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 12 Sep 2007 13:54:19 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-09-12T13:54:19Z</dc:date>
    <item>
      <title>procedure for workflow</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/procedure-for-workflow/m-p/2741396#M636950</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi&lt;/P&gt;&lt;P&gt; pls can any one explain step by step procedure for sales order, purchase order workflow design. Thax heaps.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Sep 2007 13:44:29 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/procedure-for-workflow/m-p/2741396#M636950</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-12T13:44:29Z</dc:date>
    </item>
    <item>
      <title>Re: procedure for workflow</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/procedure-for-workflow/m-p/2741397#M636951</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Purchase Order and Sales Order Workflow &lt;/P&gt;&lt;P&gt;Purchase Order workflow ( Transaction : ME23N) determines the approval path for the buying organization . It first goes to the buyer, buyer's manager &amp;amp; thereafter based on the cost center &amp;amp; the associated amount, it goes for approval through the Cost Center organization . &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i.e, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Buyer ( Requestor in the procurement deptt. of the buying organization) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;                                | &lt;/P&gt;&lt;P&gt;                                | &lt;/P&gt;&lt;P&gt;                                v &lt;/P&gt;&lt;P&gt;                      Procurement Manager &lt;/P&gt;&lt;P&gt;                                | &lt;/P&gt;&lt;P&gt;                                | &lt;/P&gt;&lt;P&gt;                                v &lt;/P&gt;&lt;P&gt;                      Cost Center org. approval ( based on amount &amp;amp; Sign.Authority level) &lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regarding , Sales Order( Transaction: VA01); it is created in the Sales Org of the company  &amp;amp; basically governs the pricing structure of the order .The routing of an SO is &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;                 Sales Org. ( based on the cost center of the sold item) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;                                | &lt;/P&gt;&lt;P&gt;                                | &lt;/P&gt;&lt;P&gt;                                v &lt;/P&gt;&lt;P&gt;                       Distribution Channel  &lt;/P&gt;&lt;P&gt;                                | &lt;/P&gt;&lt;P&gt;                                | &lt;/P&gt;&lt;P&gt;                                v &lt;/P&gt;&lt;P&gt;                           Division &lt;/P&gt;&lt;P&gt;                                | &lt;/P&gt;&lt;P&gt;                                | &lt;/P&gt;&lt;P&gt;                                v &lt;/P&gt;&lt;P&gt;                           Reg. Sales office &lt;/P&gt;&lt;P&gt;                                | &lt;/P&gt;&lt;P&gt;                                | &lt;/P&gt;&lt;P&gt;                                v &lt;/P&gt;&lt;P&gt;                           Sales Group &lt;/P&gt;&lt;P&gt;                                | &lt;/P&gt;&lt;P&gt;                                | &lt;/P&gt;&lt;P&gt;                                v &lt;/P&gt;&lt;P&gt;                           Sales Person &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Vasu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Sep 2007 13:54:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/procedure-for-workflow/m-p/2741397#M636951</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-12T13:54:19Z</dc:date>
    </item>
    <item>
      <title>Re: procedure for workflow</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/procedure-for-workflow/m-p/2741398#M636952</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;The following steps for PO.&lt;/P&gt;&lt;P&gt;Steps in Workflow&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;1.	Creation of Attachment by the PO creator&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;As the first step in release of PO, a Work Item will be sent to the user who created the PO. The user has to attach documents for the reference of the approvers of different release codes and then execute the Workitem. However, attachment of document is not mandatory. The user can simply execute the workitem if he/she thinks a reference document is not required for a Purchase Order. &lt;/P&gt;&lt;P&gt;This step is required only for workflow of first level release code.&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;2.	Approval of Release by the Responsibility (Silent Release)&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;Each responsibility associated with a particular Release Code will receive a Workitem for PO Release with the particular release code. Responsible person has the choice to either approve it or reject release of PO. &lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;3.	Release of PO in Background&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;When the user chooses to release the PO (in Step 2), the PO will be released in background by the Workflow.&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;4.	Reset Release&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;A Background Step resets the Release of PO for the respective Release Code when the user (in step 2) rejects the release of PO.&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;5.	Email on the status of Release to the Responsibility&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt; Email will be sent to the agent who executed Silent Release with the status of the release.&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;6.	Monitoring for External Release&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;A wait step will be monitoring for external release of PO with the Release Code of the Workflow. Receipt of the event will terminate the Workflow.&lt;/P&gt;&lt;P&gt;&amp;lt;b&amp;gt;7.	Monitoring for Change in Release Strategy&amp;lt;/b&amp;gt;&lt;/P&gt;&lt;P&gt;A wait step will be monitoring for Significant Change in Release Strategy. Receipt of the event will terminate the Workflow.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Srinu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Sep 2007 13:55:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/procedure-for-workflow/m-p/2741398#M636952</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-09-12T13:55:10Z</dc:date>
    </item>
  </channel>
</rss>

