<?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: LSMW: Batch Input for modified XD01? in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/lsmw-batch-input-for-modified-xd01/m-p/3289583#M787067</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Guess you need an end of record marker in field SENDE (BKNA1):&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;End of record marker:                                                                                &lt;/P&gt;&lt;P&gt;If a batch input structure is later extended, the new end of the structure is indicated by a special field (SENDE). If you are already    &lt;/P&gt;&lt;P&gt;working with the new, extended structure, you must also supply this      &lt;/P&gt;&lt;P&gt;field with the NODATA indicator when "initializing" the structure. As a  &lt;/P&gt;&lt;P&gt;result, the system can recognize whether the data is based on the old or &lt;/P&gt;&lt;P&gt;the new structure when the structure is imported.                                                                                &lt;/P&gt;&lt;P&gt;Old structures can no longer be processed and the system terminates with &lt;/P&gt;&lt;P&gt;an error message if the following prerequisites are fulfilled:                                                                                &lt;/P&gt;&lt;P&gt;o   You are using the modification-free enhancement of the customer/vendor master either directly or indirectly via an SAP solution.                                                                                &lt;/P&gt;&lt;P&gt;o   Either you or an SAP solution extends the structure.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 16 Jan 2008 14:46:46 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-01-16T14:46:46Z</dc:date>
    <item>
      <title>LSMW: Batch Input for modified XD01?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/lsmw-batch-input-for-modified-xd01/m-p/3289582#M787066</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I want to import some customers data via LSMW, however we are using an add-on in our R3. For this reason I recieved the message: 'Old data BKNA1 cannot be processed, ADD-ON exists', when I tried to create the batch input session. All the steps before were fine. The modification of xd01 is just one button to add some additional information. Do I have to record the whole batch input session on my own again or does anyone knows an other opportunity?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;kind regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Jan 2008 13:47:41 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/lsmw-batch-input-for-modified-xd01/m-p/3289582#M787066</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-16T13:47:41Z</dc:date>
    </item>
    <item>
      <title>Re: LSMW: Batch Input for modified XD01?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/lsmw-batch-input-for-modified-xd01/m-p/3289583#M787067</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Guess you need an end of record marker in field SENDE (BKNA1):&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;End of record marker:                                                                                &lt;/P&gt;&lt;P&gt;If a batch input structure is later extended, the new end of the structure is indicated by a special field (SENDE). If you are already    &lt;/P&gt;&lt;P&gt;working with the new, extended structure, you must also supply this      &lt;/P&gt;&lt;P&gt;field with the NODATA indicator when "initializing" the structure. As a  &lt;/P&gt;&lt;P&gt;result, the system can recognize whether the data is based on the old or &lt;/P&gt;&lt;P&gt;the new structure when the structure is imported.                                                                                &lt;/P&gt;&lt;P&gt;Old structures can no longer be processed and the system terminates with &lt;/P&gt;&lt;P&gt;an error message if the following prerequisites are fulfilled:                                                                                &lt;/P&gt;&lt;P&gt;o   You are using the modification-free enhancement of the customer/vendor master either directly or indirectly via an SAP solution.                                                                                &lt;/P&gt;&lt;P&gt;o   Either you or an SAP solution extends the structure.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 16 Jan 2008 14:46:46 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/lsmw-batch-input-for-modified-xd01/m-p/3289583#M787067</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-16T14:46:46Z</dc:date>
    </item>
    <item>
      <title>Re: LSMW: Batch Input for modified XD01?</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/lsmw-batch-input-for-modified-xd01/m-p/3289584#M787068</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks! You're right! &lt;/P&gt;&lt;P&gt;I solved the problem!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 17 Jan 2008 12:37:19 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/lsmw-batch-input-for-modified-xd01/m-p/3289584#M787068</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-17T12:37:19Z</dc:date>
    </item>
  </channel>
</rss>

