<?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: Requirement Routine in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/requirement-routine/m-p/2991897#M706619</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;Requirement Routine will be done in T. Code : VOFM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Under this, there are many options available under the Menu &amp;lt;b&amp;gt;Requirements&amp;lt;/b&amp;gt;.&lt;/P&gt;&lt;P&gt;Based on the need, you have to create Requirement(e.g : Pricing, Output Control).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It will create a new Requirement &amp;amp; have to give a numeric no, greater than 900 for user defiend requirement. While creating it will ask for a Access Key where u can get from OSS(for this u need to have UserID &amp;amp; Password).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For Example, if you are choosing Output type, then it will be used whether the Output type have to be created or not based on your requirement needs.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 31 Oct 2007 10:12:50 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2007-10-31T10:12:50Z</dc:date>
    <item>
      <title>Requirement Routine</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/requirement-routine/m-p/2991896#M706618</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Experts,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is Requirement Routine.Please explain me with any one of the example.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 Oct 2007 09:34:22 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/requirement-routine/m-p/2991896#M706618</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-31T09:34:22Z</dc:date>
    </item>
    <item>
      <title>Re: Requirement Routine</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/requirement-routine/m-p/2991897#M706619</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;Requirement Routine will be done in T. Code : VOFM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Under this, there are many options available under the Menu &amp;lt;b&amp;gt;Requirements&amp;lt;/b&amp;gt;.&lt;/P&gt;&lt;P&gt;Based on the need, you have to create Requirement(e.g : Pricing, Output Control).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It will create a new Requirement &amp;amp; have to give a numeric no, greater than 900 for user defiend requirement. While creating it will ask for a Access Key where u can get from OSS(for this u need to have UserID &amp;amp; Password).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For Example, if you are choosing Output type, then it will be used whether the Output type have to be created or not based on your requirement needs.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 Oct 2007 10:12:50 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/requirement-routine/m-p/2991897#M706619</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-31T10:12:50Z</dc:date>
    </item>
    <item>
      <title>Re: Requirement Routine</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/requirement-routine/m-p/2991898#M706620</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Requirement routine for billing header&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FORM BEDINGUNG_PRUEFEN_021.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI level="1" type="ul"&gt;&lt;P&gt;Only when there is a division&lt;/P&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;  IF VBRK-SPART IS INITIAL.&lt;/P&gt;&lt;P&gt;    MESSAGE E054.&lt;/P&gt;&lt;P&gt;  ENDIF.&lt;/P&gt;&lt;P&gt;ENDFORM.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 31 Oct 2007 10:30:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/requirement-routine/m-p/2991898#M706620</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-10-31T10:30:05Z</dc:date>
    </item>
  </channel>
</rss>

