<?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 conversion tool with rules in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/conversion-tool-with-rules/m-p/4937802#M1151714</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi guys!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are moving our old SAP system to another (also old and running) system. I have a task to create a MM conversion tool which should not just collect all data. Main purpose is to prepare and export data in form ready for direct input to the new system.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Idea is to create a several Z tables with conversion rules structured like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;FIELD&lt;/STRONG&gt;  |  &lt;STRONG&gt;MAT TYPE&lt;/STRONG&gt;  |  OPER     | VAL&lt;/P&gt;&lt;P&gt;MTART |  FERT         |  convertto  | MAT&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so ... in this simple example system should check material type and if it is FERT it should use method convertto and set value of field MTART to MAT (rule in new system is to use MAT instead of FERT). I planed to create "rules table" for every master data table (MARA, MARD, MARC....) and use same keys + some additional (like MTART  for ZMARA_RULES).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With this conversion rules in database tables I'm more flexible to define rules, but I'm not sure if this is a really good idea? what do you think? Any experience with this? How to organize this rules? Anything!? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;T.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 17 Dec 2008 11:42:28 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-12-17T11:42:28Z</dc:date>
    <item>
      <title>conversion tool with rules</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/conversion-tool-with-rules/m-p/4937802#M1151714</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi guys!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are moving our old SAP system to another (also old and running) system. I have a task to create a MM conversion tool which should not just collect all data. Main purpose is to prepare and export data in form ready for direct input to the new system.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Idea is to create a several Z tables with conversion rules structured like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;FIELD&lt;/STRONG&gt;  |  &lt;STRONG&gt;MAT TYPE&lt;/STRONG&gt;  |  OPER     | VAL&lt;/P&gt;&lt;P&gt;MTART |  FERT         |  convertto  | MAT&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so ... in this simple example system should check material type and if it is FERT it should use method convertto and set value of field MTART to MAT (rule in new system is to use MAT instead of FERT). I planed to create "rules table" for every master data table (MARA, MARD, MARC....) and use same keys + some additional (like MTART  for ZMARA_RULES).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;With this conversion rules in database tables I'm more flexible to define rules, but I'm not sure if this is a really good idea? what do you think? Any experience with this? How to organize this rules? Anything!? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;T.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Dec 2008 11:42:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/conversion-tool-with-rules/m-p/4937802#M1151714</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-12-17T11:42:28Z</dc:date>
    </item>
    <item>
      <title>Re: conversion tool with rules</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/conversion-tool-with-rules/m-p/4937803#M1151715</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi &lt;/P&gt;&lt;P&gt;Welcome to SCN.&lt;/P&gt;&lt;P&gt;This is not the right procedure to do so.&lt;/P&gt;&lt;P&gt;You need to extract the data from source system,cleanse it(may be using your excel sheet), transform it(by writing conversion rules in LSMW or may be in your ABAP Program) then load it using direct input or whatever method you prefer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Hakim&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Dec 2008 12:24:02 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/conversion-tool-with-rules/m-p/4937803#M1151715</guid>
      <dc:creator>abdul_hakim</dc:creator>
      <dc:date>2008-12-17T12:24:02Z</dc:date>
    </item>
    <item>
      <title>Re: conversion tool with rules</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/conversion-tool-with-rules/m-p/4937804#M1151716</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Hakim,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;what you wrote ...  that was my plan &lt;SPAN __jive_emoticon_name="happy"&gt;&lt;/SPAN&gt; actually.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All data will be cleaned in old system before transfer. ABAP written tool should be used on source system to download all necessary data to excel file ... Only question is now how to organize writing conversion rules so that this data is suitable (in right structure and form) for upload to destination system. Reason why we want to have it that way is because we have both (source and destination) systems alive. Conversion from one to another system should be done in period of one or two days max. &lt;SPAN __jive_emoticon_name="happy"&gt;&lt;/SPAN&gt; thats why we don't want have any "editable" excel files. Our excel file will be used only for upload not for maintaining data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i hope you understand now.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;t.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Dec 2008 12:46:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/conversion-tool-with-rules/m-p/4937804#M1151716</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-12-17T12:46:25Z</dc:date>
    </item>
  </channel>
</rss>

