<?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: number generation in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/number-generation/m-p/4250165#M1014481</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;EM&gt;create an object in SNRO and use&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;CALL FUNCTION 'NUMBER_GET_NEXT'&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;is used by standard programs. &lt;/P&gt;&lt;P&gt;so when ever you want to update new number you need to call the Function using the Object created in SNRO.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;creat a custom table where i maintain the current number and the next number.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But for Normal Table appraoch is exactly the same as SNRO and NUMBER_GET_NEXT function behaves. so you are replicating the whole process.&lt;/P&gt;&lt;P&gt;instead you can reuse the Standard Functionality&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 04 Aug 2008 15:22:18 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-08-04T15:22:18Z</dc:date>
    <item>
      <title>number generation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/number-generation/m-p/4250162#M1014478</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 need sequence numbers for a field. there r two ways i can do this...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;create an object in SNRO and use&lt;/P&gt;&lt;P&gt;CALL FUNCTION 'NUMBER_GET_NEXT'&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;or&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;creat a custom table where i maintain the current number and the next number.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;which is a better approach ? does any have adv/disadv over the other ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Aug 2008 15:17:39 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/number-generation/m-p/4250162#M1014478</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-08-04T15:17:39Z</dc:date>
    </item>
    <item>
      <title>Re: number generation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/number-generation/m-p/4250163#M1014479</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The first is the best way to do it, why? Becasue that is how SAP does it.  Most every genreated number in R/3 uses the number range object approach.  It supports buffering, and locking automatically so you don't have to worry about this in your custom table.  Use the number range object and the function.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Rich Heilman&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Aug 2008 15:21:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/number-generation/m-p/4250163#M1014479</guid>
      <dc:creator>RichHeilman</dc:creator>
      <dc:date>2008-08-04T15:21:10Z</dc:date>
    </item>
    <item>
      <title>Re: number generation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/number-generation/m-p/4250164#M1014480</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just use the standard way SAP Provides using SNRO. Advantage is the fact that you don't have to create custom development objects and SAP provides all the standard functionality like number range buffering, different ranges to be maintained, standard FM like (NUMBER_GET_NEXT).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Aug 2008 15:21:36 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/number-generation/m-p/4250164#M1014480</guid>
      <dc:creator>Sm1tje</dc:creator>
      <dc:date>2008-08-04T15:21:36Z</dc:date>
    </item>
    <item>
      <title>Re: number generation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/number-generation/m-p/4250165#M1014481</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;EM&gt;create an object in SNRO and use&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;CALL FUNCTION 'NUMBER_GET_NEXT'&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;is used by standard programs. &lt;/P&gt;&lt;P&gt;so when ever you want to update new number you need to call the Function using the Object created in SNRO.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;creat a custom table where i maintain the current number and the next number.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But for Normal Table appraoch is exactly the same as SNRO and NUMBER_GET_NEXT function behaves. so you are replicating the whole process.&lt;/P&gt;&lt;P&gt;instead you can reuse the Standard Functionality&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Aug 2008 15:22:18 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/number-generation/m-p/4250165#M1014481</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-08-04T15:22:18Z</dc:date>
    </item>
  </channel>
</rss>

