<?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: ERP Implementation Transition in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/erp-implementation-transition/m-p/3330803#M798000</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Your question about ensuring a smooth ERP migration is a very complex one. There are a number of factors to be considered, including the number of sites that you are going live with, how many legacy systems are being replaced, and how many users are affected. In general, though, the variables that are most likely to reduce the risk of your migration causing interruptions include:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) Phased vs. "big bang" approach to migration - cutting over your systems all at once generally increases your risk, particularly on large projects across multiple geographies/countries.&lt;/P&gt;&lt;P&gt;2) Training - the better training you provide users, the less problems you will see.&lt;/P&gt;&lt;P&gt;3) Legacy system planning - what are you going to do with your systems after go-live? Will you run them in parallel for a short-period until you know the new ERP system is functional? If so, have you budgeted these costs in your ROI?&lt;/P&gt;&lt;P&gt;4) Testing - Unit and integration testing is very important; you significantly reduce your implementation risk if you have thoroughly tested the solution with real data and real user profiles before go-live.&lt;/P&gt;&lt;P&gt;5) IT support - expect more support center call volume and staff accordingly during go-live. You will also want to make sure you have clearly defined escalation procedures in place for ERP issues that your support staff isn't able to handle.&lt;/P&gt;&lt;P&gt;6) Contingency planning - what will you do if your system does go down? Do you have manual processes you can revert to if needed? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It all boils down to ERP risk mitigation. You want to make your project plan, budget, and staffing all address the above variables. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Reward points if found helpfull...&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Cheers,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Siva.&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 27 Jan 2008 10:29:27 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-01-27T10:29:27Z</dc:date>
    <item>
      <title>ERP Implementation Transition</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/erp-implementation-transition/m-p/3330802#M797999</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What are the steps that you should take for a smooth ERP implementation?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Rachita.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 26 Jan 2008 13:30:05 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/erp-implementation-transition/m-p/3330802#M797999</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-26T13:30:05Z</dc:date>
    </item>
    <item>
      <title>Re: ERP Implementation Transition</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/erp-implementation-transition/m-p/3330803#M798000</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Your question about ensuring a smooth ERP migration is a very complex one. There are a number of factors to be considered, including the number of sites that you are going live with, how many legacy systems are being replaced, and how many users are affected. In general, though, the variables that are most likely to reduce the risk of your migration causing interruptions include:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) Phased vs. "big bang" approach to migration - cutting over your systems all at once generally increases your risk, particularly on large projects across multiple geographies/countries.&lt;/P&gt;&lt;P&gt;2) Training - the better training you provide users, the less problems you will see.&lt;/P&gt;&lt;P&gt;3) Legacy system planning - what are you going to do with your systems after go-live? Will you run them in parallel for a short-period until you know the new ERP system is functional? If so, have you budgeted these costs in your ROI?&lt;/P&gt;&lt;P&gt;4) Testing - Unit and integration testing is very important; you significantly reduce your implementation risk if you have thoroughly tested the solution with real data and real user profiles before go-live.&lt;/P&gt;&lt;P&gt;5) IT support - expect more support center call volume and staff accordingly during go-live. You will also want to make sure you have clearly defined escalation procedures in place for ERP issues that your support staff isn't able to handle.&lt;/P&gt;&lt;P&gt;6) Contingency planning - what will you do if your system does go down? Do you have manual processes you can revert to if needed? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It all boils down to ERP risk mitigation. You want to make your project plan, budget, and staffing all address the above variables. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Reward points if found helpfull...&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Cheers,&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Siva.&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 27 Jan 2008 10:29:27 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/erp-implementation-transition/m-p/3330803#M798000</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-27T10:29:27Z</dc:date>
    </item>
    <item>
      <title>Re: ERP Implementation Transition</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/erp-implementation-transition/m-p/3330804#M798001</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Rachita,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check the below links.U can get more information about SAP project implementation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.erpgenie.com/sapgenie/docs/TheSecretsToSuccessfulSAPproject.doc" target="test_blank"&gt;http://www.erpgenie.com/sapgenie/docs/TheSecretsToSuccessfulSAPproject.doc&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_thread" href="https://community.sap.com/" __jive_macro_name="thread" modifiedtitle="true" __default_attr="260514"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://help.sap.com/saphelp_47x200/helpdata/en/48/623972d55a11d2bbf700105a5e5b3c/content.htm" target="test_blank"&gt;http://help.sap.com/saphelp_47x200/helpdata/en/48/623972d55a11d2bbf700105a5e5b3c/content.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;kindly reward if found helpful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;cheers,&lt;/P&gt;&lt;P&gt;Hema.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 27 Jan 2008 10:33:07 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/erp-implementation-transition/m-p/3330804#M798001</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-01-27T10:33:07Z</dc:date>
    </item>
  </channel>
</rss>

