<?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: Sequential numbers in non-buffered number range object in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/sequential-numbers-in-non-buffered-number-range-object/m-p/10396040#M1842133</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have faced the same problem in the past and what was solved to me is call the FMs&amp;nbsp; &lt;STRONG&gt;NUMBER_RANGE_ENQUEUE&lt;/STRONG&gt; and &lt;STRONG&gt;NUMBER_RANGE_DEQUEUE&lt;/STRONG&gt; before and after call the NUMBER_GET_NEXT function module respectively.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 29 Sep 2014 13:36:45 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2014-09-29T13:36:45Z</dc:date>
    <item>
      <title>Sequential numbers in non-buffered number range object</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sequential-numbers-in-non-buffered-number-range-object/m-p/10396038#M1842131</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I need some help pointing in the right direction to analyze and prevent a problem with a NON-BUFFERED custom number range object.&lt;/P&gt;&lt;P&gt;This process works well.&amp;nbsp; Once or twice however, sequences have been created with an apparent delay and are out of order.&amp;nbsp; I don't know why, or where to look to diagnose the timing, etc.&amp;nbsp; It's very difficult to recreate.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have a custom number range object; ZFSEQ in SNRO that is responsible for assigning a sequential number to a series of flat files produced by number of different interfaces.&amp;nbsp; Those interfaces all use the FM&amp;nbsp; &lt;SPAN class="L0S33"&gt;'NUMBER_GET_NEXT' and then they build a file name with that sequence number.&amp;nbsp; That object is not buffered.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S33"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S33"&gt;During heavy volume of updates (where lots of these sequences are being called and created by different interfaces, the table NRIV is locked and released by each interface.&amp;nbsp; During this time of heavy updates, w&lt;/SPAN&gt;&lt;SPAN class="L0S33"&gt;e have an infrequent problem that has occurred where a standard sales order create created a sequence number that is greater than the sequence number generated by the delivery create.&amp;nbsp; (The delivery was created a couple of minutes later than the order, yet the order created a flat file sequence number greater than that of the delivery.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S33"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S33"&gt;I hypothesize that the flat file call for the order (using the&amp;nbsp; FM&amp;nbsp; &lt;SPAN class="L0S33"&gt;'NUMBER_GET_NEXT') &lt;/SPAN&gt; was somehow delayed(because of heavy lock/usage of NRIV).&amp;nbsp; The actual order document and delivery document were created normally.&amp;nbsp; I also am thinking that buffering on the object would prevent this.&amp;nbsp; I cannot at this time implement buffering on the object, but we are working towards that.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S33"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S33"&gt;The order create originates from our e-commerce system through a webserive, and in SAP, flows like this:&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S33"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S33"&gt;Main webservice RFC:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Z_ORDER_CREATE&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S33"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S33"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Call Z_create_order_bgd&amp;nbsp; IN BACKGROUND TASK&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S33"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S33"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Call BAPI_SALESORDER_CREATEFROMDAT2 )&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S33"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S33"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S33"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; MV45AFZZ--&amp;gt; userexit_save_document&lt;SPAN class="L0S55"&gt;.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S33"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S33"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; call Z_FUNCTION_TO_GET_SEQUENCE&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S33"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S33"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; CALL FM&amp;nbsp; &lt;SPAN class="L0S33"&gt;'NUMBER_GET_NEXT'&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;---- order create sequential file created&lt;/SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S33"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S33"&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; commit work.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S33"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S33"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S33"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S33"&gt;The delivery sequential file is created in &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S33"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; MV50AFZ1&amp;nbsp; (the Delivery User Exit)&lt;/P&gt;&lt;P&gt;&lt;SPAN class="L0S33"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Where can I look to conclusively see what happened to delay our sales order sequence?&amp;nbsp; What could be done to prevent it?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Jeremy H.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 14 Jul 2014 14:26:24 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sequential-numbers-in-non-buffered-number-range-object/m-p/10396038#M1842131</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2014-07-14T14:26:24Z</dc:date>
    </item>
    <item>
      <title>Re: Sequential numbers in non-buffered number range object</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sequential-numbers-in-non-buffered-number-range-object/m-p/10396039#M1842132</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Just want to post the answer that we found to this issue and close it, though more comments are always welcome!&lt;/P&gt;&lt;P&gt;We are going to move forward with buffering the Z object for the range as studies have shown and all other consulting input seems to be that buffering will solve this problem.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 Sep 2014 13:29:38 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sequential-numbers-in-non-buffered-number-range-object/m-p/10396039#M1842132</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2014-09-29T13:29:38Z</dc:date>
    </item>
    <item>
      <title>Re: Sequential numbers in non-buffered number range object</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sequential-numbers-in-non-buffered-number-range-object/m-p/10396040#M1842133</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have faced the same problem in the past and what was solved to me is call the FMs&amp;nbsp; &lt;STRONG&gt;NUMBER_RANGE_ENQUEUE&lt;/STRONG&gt; and &lt;STRONG&gt;NUMBER_RANGE_DEQUEUE&lt;/STRONG&gt; before and after call the NUMBER_GET_NEXT function module respectively.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 Sep 2014 13:36:45 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sequential-numbers-in-non-buffered-number-range-object/m-p/10396040#M1842133</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2014-09-29T13:36:45Z</dc:date>
    </item>
    <item>
      <title>Re: Sequential numbers in non-buffered number range object</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/sequential-numbers-in-non-buffered-number-range-object/m-p/10396041#M1842134</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, We considered that change to all of our interfaces that use the GET_NUMBER_NEXT routine and in the short-term decided that buffering offers increased performance and less risk since there were no code changes.&amp;nbsp; Thank you.&amp;nbsp; I appreciate your feedback on this!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Sep 2014 14:06:43 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/sequential-numbers-in-non-buffered-number-range-object/m-p/10396041#M1842134</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2014-09-30T14:06:43Z</dc:date>
    </item>
  </channel>
</rss>

