<?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: internal batch number assignment in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-batch-number-assignment/m-p/1371890#M182930</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi, Manti&lt;/P&gt;&lt;P&gt;This problem is not due to your programming.&lt;/P&gt;&lt;P&gt;It determined by the GR strategy configurated on your SAP server. Your symptom show that when do GR always need to generate a new batch for the material, not combine the stock into exists batch.&lt;/P&gt;&lt;P&gt;In my test server, this action is permitted, and two same item material in a PO can be receipt into a exist batch though this batch already has stock on a quality inspection storloc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So the problem due to the SPRO configuration. Talk with your consultant, and to confirm if the proper setting has been done in server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 25 May 2006 02:17:15 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2006-05-25T02:17:15Z</dc:date>
    <item>
      <title>internal batch number assignment</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-batch-number-assignment/m-p/1371889#M182929</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi developers, I need to use user exits to force the batch number I want during goods movement '101'.&lt;/P&gt;&lt;P&gt;The exits I am using are ZXVBZU01 and ZXVBZU02.&lt;/P&gt;&lt;P&gt;The problem is that if the system recognizes that the values MATNR WERKS and CHARG already are in MCHA it stops the registration with an error message. It is a problem beacuse I want to force the same CHARG number several times...&lt;/P&gt;&lt;P&gt;Does anybody knows the answer?&lt;/P&gt;&lt;P&gt;Thanks to everyone&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 May 2006 16:08:54 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-batch-number-assignment/m-p/1371889#M182929</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-05-24T16:08:54Z</dc:date>
    </item>
    <item>
      <title>Re: internal batch number assignment</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/internal-batch-number-assignment/m-p/1371890#M182930</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi, Manti&lt;/P&gt;&lt;P&gt;This problem is not due to your programming.&lt;/P&gt;&lt;P&gt;It determined by the GR strategy configurated on your SAP server. Your symptom show that when do GR always need to generate a new batch for the material, not combine the stock into exists batch.&lt;/P&gt;&lt;P&gt;In my test server, this action is permitted, and two same item material in a PO can be receipt into a exist batch though this batch already has stock on a quality inspection storloc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So the problem due to the SPRO configuration. Talk with your consultant, and to confirm if the proper setting has been done in server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 May 2006 02:17:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/internal-batch-number-assignment/m-p/1371890#M182930</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2006-05-25T02:17:15Z</dc:date>
    </item>
  </channel>
</rss>

