<?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 Header condition - Routine for automation in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/header-condition-routine-for-automation/m-p/7627692#M1570923</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have business transaction where PO is getting created automatically. In real time, user is entering header condition manually, because header conditions are not allowed to have access sequence. It is difficult for users on tracking header condition manual entry details. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can anyone throw some lights for using routine to have automatic entry of header condition while PO is created automatically ? Which routine to be explored to achieve automation of header condition value in PO ? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rgds,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 16 Feb 2011 02:03:48 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2011-02-16T02:03:48Z</dc:date>
    <item>
      <title>Header condition - Routine for automation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/header-condition-routine-for-automation/m-p/7627692#M1570923</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have business transaction where PO is getting created automatically. In real time, user is entering header condition manually, because header conditions are not allowed to have access sequence. It is difficult for users on tracking header condition manual entry details. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can anyone throw some lights for using routine to have automatic entry of header condition while PO is created automatically ? Which routine to be explored to achieve automation of header condition value in PO ? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rgds,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Feb 2011 02:03:48 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/header-condition-routine-for-automation/m-p/7627692#M1570923</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2011-02-16T02:03:48Z</dc:date>
    </item>
    <item>
      <title>Re: Header condition - Routine for automation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/header-condition-routine-for-automation/m-p/7627693#M1570924</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;I have an idea but let us know if get to meet this requirement in someother better way.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can trigger a UPDATE function module from one of the user exit/BADI and update the header conditions by using some  BAPI like BAPI_PO_CHANGE. PO locking has to be taken care in the UPDATE FM. Check for the lock status of the PO before calling BAPI. Because if you have many outputs to be triggered in the PO, then lock may not get released by the time your update FM is triggered. So you have to wait till the lock is released. This logic is similar to standard SAP functionality of creating automatic delivery on saving the order.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Vinod.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Feb 2011 05:09:52 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/header-condition-routine-for-automation/m-p/7627693#M1570924</guid>
      <dc:creator>vinod_vemuru2</dc:creator>
      <dc:date>2011-02-16T05:09:52Z</dc:date>
    </item>
  </channel>
</rss>

