<?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 Version management in purchase document in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/version-management-in-purchase-document/m-p/7236708#M1525671</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Guru,&lt;/P&gt;&lt;P&gt;SAP documentation says: "To ensure that a new version is created for a purchasing document, all messages must be transferred" and the question is: it's possible to modify this behavior? In other words: we can obtain automaticaly new version also if there is a message not transferred by modify one or more print-relevant fields in a relesed PO?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;P&gt;CDB.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 07 Sep 2010 15:37:00 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2010-09-07T15:37:00Z</dc:date>
    <item>
      <title>Version management in purchase document</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/version-management-in-purchase-document/m-p/7236708#M1525671</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Guru,&lt;/P&gt;&lt;P&gt;SAP documentation says: "To ensure that a new version is created for a purchasing document, all messages must be transferred" and the question is: it's possible to modify this behavior? In other words: we can obtain automaticaly new version also if there is a message not transferred by modify one or more print-relevant fields in a relesed PO?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;P&gt;CDB.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Sep 2010 15:37:00 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/version-management-in-purchase-document/m-p/7236708#M1525671</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2010-09-07T15:37:00Z</dc:date>
    </item>
    <item>
      <title>Re: Version management in purchase document</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/version-management-in-purchase-document/m-p/7236709#M1525672</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Claudio,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can restrict this behavior,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;create the version reason code =XXXX, if you want to restrict the output to be triggered for these changes.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Create a Routine help of the development team where version reason code = XXXX, restrict to generate the&amp;nbsp; output.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;And assign this routine in customization SPRO--&amp;gt; MM--&amp;gt;purchasing--&amp;gt;Messages--&amp;gt;Output Control--&amp;gt;Define Message Schema for Purchase Order (in releveant procedure).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;San&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Apr 2016 07:13:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/version-management-in-purchase-document/m-p/7236709#M1525672</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2016-04-08T07:13:05Z</dc:date>
    </item>
  </channel>
</rss>

