<?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: Query on Data Conversion in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/query-on-data-conversion/m-p/5516499#M1261155</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The easiest would be to create a mapping table which holds the legacy value and the SAP value&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;e.g. Legacy AB =&amp;gt; SAP SQ&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then you write a function module which accepts the legacy string AB6790 (changing parameter) and based on the mapping table converts it into SQ6790.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can extend your mapping table with field lengths (e.g. first 4 char or first 5 char) or other conditions which you would need to read and evaluate in your FM. You can get as complex as the requirements ask for. &lt;/P&gt;&lt;P&gt;You also need to think about error handling, what happens if no mapping value can be found, how would it be reported back to the user, etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In terms of performance you might want to think about buffering the mapping table .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps,&lt;/P&gt;&lt;P&gt;Michael&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 13 Apr 2009 12:28:15 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2009-04-13T12:28:15Z</dc:date>
    <item>
      <title>Query on Data Conversion</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/query-on-data-conversion/m-p/5516498#M1261154</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are trying to build a generic tool which could help the conversion process in data migration.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For eg, If the material name in legacy starts with AB (AB6790), the same has to be referred in SAP as SQ6790.&lt;/P&gt;&lt;P&gt;So its replacing initial few characters during the conversion process.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Like this, I am expected to collect possible scenarios and &lt;/P&gt;&lt;P&gt;develop a generic tool, which can cover some possible conversion conditions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you please help me with such scenarios, which you may have come across in project needs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;P&gt;Meenakshi&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Apr 2009 03:55:10 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/query-on-data-conversion/m-p/5516498#M1261154</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-04-13T03:55:10Z</dc:date>
    </item>
    <item>
      <title>Re: Query on Data Conversion</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/query-on-data-conversion/m-p/5516499#M1261155</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The easiest would be to create a mapping table which holds the legacy value and the SAP value&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;e.g. Legacy AB =&amp;gt; SAP SQ&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then you write a function module which accepts the legacy string AB6790 (changing parameter) and based on the mapping table converts it into SQ6790.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can extend your mapping table with field lengths (e.g. first 4 char or first 5 char) or other conditions which you would need to read and evaluate in your FM. You can get as complex as the requirements ask for. &lt;/P&gt;&lt;P&gt;You also need to think about error handling, what happens if no mapping value can be found, how would it be reported back to the user, etc.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In terms of performance you might want to think about buffering the mapping table .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope that helps,&lt;/P&gt;&lt;P&gt;Michael&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 13 Apr 2009 12:28:15 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/query-on-data-conversion/m-p/5516499#M1261155</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-04-13T12:28:15Z</dc:date>
    </item>
    <item>
      <title>Re: Query on Data Conversion</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/query-on-data-conversion/m-p/5516500#M1261156</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You can maintain Ztable for this purpose that will contain your old material number and new material number .&lt;/P&gt;&lt;P&gt;write conversion program that will read this material number conversion table .&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 20 Apr 2009 09:27:57 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/query-on-data-conversion/m-p/5516500#M1261156</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2009-04-20T09:27:57Z</dc:date>
    </item>
  </channel>
</rss>

