<?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: Implementation in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/implementation/m-p/1947397#M390420</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Business blue print stage is called as is process.  Fit gap means, before implementing the SAP all the business data is in the form of documents, we cannot keep this data as is in the SAP.  There should be a gap.  So by filling this gap, we make configuration with the help of these documents.  This is called as fit gap analysis.  In this stage, we should analysis the gap between as is and is as process &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; peoplesoft-hr-l    peoplesoft-hr-lAll Groups   &lt;/P&gt;&lt;P&gt;PeopleSoft Groups &amp;gt; Technical &amp;amp; Functional &amp;gt; peoplesoft-hr-l &amp;gt; Message | About This Group &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;Join group | Manage settings |  View/Edit FAQ |  |       &lt;/P&gt;&lt;P&gt;Post reply    Post new&lt;/P&gt;&lt;P&gt;&amp;lt;&amp;lt; Prev thread  &amp;lt; Prev msg  Next msg &amp;gt;  Next thread &amp;gt;&amp;gt;  &lt;/P&gt;&lt;P&gt;Was this response helpful to you?    &lt;/P&gt;&lt;P&gt;Thank you. Your rating will be processed shortly. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; RE: Fit-Gap Analysis&lt;/P&gt;&lt;P&gt;Posted by Rachel Nicholls on 6/8/2002 9:21:00 PM  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The purpose of performing a Fit/Gap Analysis is NOT to compare the new  and&lt;/P&gt;&lt;P&gt;old systems.   Doe's that mean that you don't perform a Fit/Gap Analysis for&lt;/P&gt;&lt;P&gt;a client who has no current system?  Obviously not.   The purpose of a&lt;/P&gt;&lt;P&gt;Fit/Gap Analysis is to gather a client's requirements and current business&lt;/P&gt;&lt;P&gt;processes and compare those to the new system, creating Fits, Gaps, and&lt;/P&gt;&lt;P&gt;Partial Gaps.  This document is a starting point for determining what&lt;/P&gt;&lt;P&gt;customizations, if any, are to be performed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Amit&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward all helpful replies.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 10 Mar 2007 03:05:01 GMT</pubDate>
    <dc:creator>amit_khare</dc:creator>
    <dc:date>2007-03-10T03:05:01Z</dc:date>
    <item>
      <title>Implementation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/implementation/m-p/1947394#M390417</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi folks,&lt;/P&gt;&lt;P&gt;               what is the meaning of "&amp;lt;b&amp;gt; FIT GAP ANALYSIS &amp;lt;B&amp;gt;" in SAP implementation phases.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;can anyone plzz help me regarding this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;satish&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Feb 2007 16:41:17 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/implementation/m-p/1947394#M390417</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-02-22T16:41:17Z</dc:date>
    </item>
    <item>
      <title>Re: Implementation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/implementation/m-p/1947395#M390418</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Check this link:&lt;/P&gt;&lt;P&gt;&lt;A href="http://www.sap-img.com/sap-implementation.htm" target="test_blank"&gt;http://www.sap-img.com/sap-implementation.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Subramanian&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Feb 2007 16:42:54 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/implementation/m-p/1947395#M390418</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-02-22T16:42:54Z</dc:date>
    </item>
    <item>
      <title>Re: Implementation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/implementation/m-p/1947396#M390419</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello frnds,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;                  can anyone plzz clear my doubt.&lt;/P&gt;&lt;P&gt;                 regards,&lt;/P&gt;&lt;P&gt;                 satish&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 10 Mar 2007 02:37:45 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/implementation/m-p/1947396#M390419</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-03-10T02:37:45Z</dc:date>
    </item>
    <item>
      <title>Re: Implementation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/implementation/m-p/1947397#M390420</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Business blue print stage is called as is process.  Fit gap means, before implementing the SAP all the business data is in the form of documents, we cannot keep this data as is in the SAP.  There should be a gap.  So by filling this gap, we make configuration with the help of these documents.  This is called as fit gap analysis.  In this stage, we should analysis the gap between as is and is as process &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; peoplesoft-hr-l    peoplesoft-hr-lAll Groups   &lt;/P&gt;&lt;P&gt;PeopleSoft Groups &amp;gt; Technical &amp;amp; Functional &amp;gt; peoplesoft-hr-l &amp;gt; Message | About This Group &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;Join group | Manage settings |  View/Edit FAQ |  |       &lt;/P&gt;&lt;P&gt;Post reply    Post new&lt;/P&gt;&lt;P&gt;&amp;lt;&amp;lt; Prev thread  &amp;lt; Prev msg  Next msg &amp;gt;  Next thread &amp;gt;&amp;gt;  &lt;/P&gt;&lt;P&gt;Was this response helpful to you?    &lt;/P&gt;&lt;P&gt;Thank you. Your rating will be processed shortly. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; RE: Fit-Gap Analysis&lt;/P&gt;&lt;P&gt;Posted by Rachel Nicholls on 6/8/2002 9:21:00 PM  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The purpose of performing a Fit/Gap Analysis is NOT to compare the new  and&lt;/P&gt;&lt;P&gt;old systems.   Doe's that mean that you don't perform a Fit/Gap Analysis for&lt;/P&gt;&lt;P&gt;a client who has no current system?  Obviously not.   The purpose of a&lt;/P&gt;&lt;P&gt;Fit/Gap Analysis is to gather a client's requirements and current business&lt;/P&gt;&lt;P&gt;processes and compare those to the new system, creating Fits, Gaps, and&lt;/P&gt;&lt;P&gt;Partial Gaps.  This document is a starting point for determining what&lt;/P&gt;&lt;P&gt;customizations, if any, are to be performed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Amit&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Reward all helpful replies.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 10 Mar 2007 03:05:01 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/implementation/m-p/1947397#M390420</guid>
      <dc:creator>amit_khare</dc:creator>
      <dc:date>2007-03-10T03:05:01Z</dc:date>
    </item>
    <item>
      <title>Re: Implementation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/implementation/m-p/1947398#M390421</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;In information technology, gap analysis is the study of the differences between two different information systems or applications, often for the purpose of determining how to get from one state to a new state. A gap is sometimes spoken of as "the space between where we are and where we want to be." Gap analysis is undertaken as a means of bridging that space.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;aRs&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 10 Mar 2007 03:07:42 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/implementation/m-p/1947398#M390421</guid>
      <dc:creator>former_member194669</dc:creator>
      <dc:date>2007-03-10T03:07:42Z</dc:date>
    </item>
    <item>
      <title>Re: Implementation</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/implementation/m-p/1947399#M390422</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;tahnk u all.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;satish&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 10 Mar 2007 03:48:28 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/implementation/m-p/1947399#M390422</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2007-03-10T03:48:28Z</dc:date>
    </item>
  </channel>
</rss>

