<?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 how to prepare blue prints in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-prepare-blue-prints/m-p/3550683#M854268</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi all,&lt;/P&gt;&lt;P&gt;please send me the documents of blueprints. how we prepare it.&lt;/P&gt;&lt;P&gt;sharma82.puneet@gmail.com&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks n regards&lt;/P&gt;&lt;P&gt;puneet&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 27 Mar 2008 04:04:34 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-03-27T04:04:34Z</dc:date>
    <item>
      <title>how to prepare blue prints</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-prepare-blue-prints/m-p/3550683#M854268</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi all,&lt;/P&gt;&lt;P&gt;please send me the documents of blueprints. how we prepare it.&lt;/P&gt;&lt;P&gt;sharma82.puneet@gmail.com&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks n regards&lt;/P&gt;&lt;P&gt;puneet&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Mar 2008 04:04:34 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-prepare-blue-prints/m-p/3550683#M854268</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-03-27T04:04:34Z</dc:date>
    </item>
    <item>
      <title>Re: how to prepare blue prints</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-prepare-blue-prints/m-p/3550684#M854269</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello puneet,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;in these threads might be some helpful links: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;[sample of blueprint doc |/thread/220997 &lt;B&gt;[original link is broken]&lt;/B&gt;;&lt;/P&gt;&lt;P&gt;[business blueprints   |/thread/148912 &lt;B&gt;[original link is broken]&lt;/B&gt;;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;M.L.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Mar 2008 15:51:57 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-prepare-blue-prints/m-p/3550684#M854269</guid>
      <dc:creator>martin_lehmann4</dc:creator>
      <dc:date>2008-03-27T15:51:57Z</dc:date>
    </item>
    <item>
      <title>Re: how to prepare blue prints</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-prepare-blue-prints/m-p/3550685#M854270</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi puneet,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is a very valuable blueprint document from a big real-life SAP implementation project implemented very successfully in the year 2005. Blue print is the single most important document in a SAP implementation project. It contains all the requirements captured from the users and how it is analyzed and mapped into respective SAP functions. This document will last till the last drop of the project and will serve as a guide for both the users and consultants to track the user requirements and the correctness of its configuration to SAP functions. Hence as a SAP consultant it is very important to prepare this document in a very professional format and as accurate as possible. The success of any SAP implementation lies in the hand of these blueprints because it determines how the user requirements will be translated into SAP functions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Using this document you can get a clear picture of how to prepare and format a SAP blueprint document professionally. Knowing SAP configuration alone will not guarantee you to prepare a good blueprint document. You must also know the proper format of a blueprint. &lt;/P&gt;&lt;P&gt;   &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;   &lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt;ORGANIZATIONAL HIERARCHY DATA &lt;/P&gt;&lt;P&gt;ORGANIZATION ELEMENTS AND STRUCTURE &lt;/P&gt;&lt;P&gt;Business Requirement &lt;/P&gt;&lt;P&gt;Blueprint &lt;/P&gt;&lt;P&gt;Factory Calendar &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MASTER DATA&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MATERIAL MASTER &lt;/P&gt;&lt;P&gt;Business Requirement &lt;/P&gt;&lt;P&gt;Blueprint &lt;/P&gt;&lt;P&gt;PURCHASING MASTER DATA &lt;/P&gt;&lt;P&gt;Business Requirement &lt;/P&gt;&lt;P&gt;Business Blueprint &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PROCUREMENT PROCESS &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BUSINESS REQUIREMENT &lt;/P&gt;&lt;P&gt;Finished Goods, Semi- Finished Goods &amp;amp; Wrapping Materials &lt;/P&gt;&lt;P&gt;Non-Stock Items, M&amp;amp;P Items, Fixed Assets, And Services &lt;/P&gt;&lt;P&gt;Procurement Approval Authorities &lt;/P&gt;&lt;P&gt;BLUEPRINT &lt;/P&gt;&lt;P&gt;Direct Purchases &lt;/P&gt;&lt;P&gt;Indirect Purchases &lt;/P&gt;&lt;P&gt;Conceptual Design &lt;/P&gt;&lt;P&gt;Purchasing Pricing &lt;/P&gt;&lt;P&gt;Procurement Approval Authorities &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;INVENTORY MANAGEMENT &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BUSINESS REQUIREMENT &lt;/P&gt;&lt;P&gt;FOC Issue for Staff Allowanve &lt;/P&gt;&lt;P&gt;Material to Material Transfer for Rothmans &lt;/P&gt;&lt;P&gt;Write-Off Process &lt;/P&gt;&lt;P&gt;Issue and Receipts in Eastern Corporation &lt;/P&gt;&lt;P&gt;BLUEPRINT &lt;/P&gt;&lt;P&gt;Stock Status &lt;/P&gt;&lt;P&gt;Goods Movement &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;INVOICE VERIFICATION &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BUSINESS REQUIREMENT &lt;/P&gt;&lt;P&gt;BLUEPRINT &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PHYSICAL INVENTORY &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BUSINESS REQUIREMENT &lt;/P&gt;&lt;P&gt;BLUEPRINT &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ACCOUNTING POSTINGS &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BLUEPRINT &lt;/P&gt;&lt;P&gt;GL Account Mapping &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;INTERFACE &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FORMS, PROGRAMS AND REPORTS &lt;/P&gt;&lt;P&gt;FORMS &lt;/P&gt;&lt;P&gt;PROGRAMS &lt;/P&gt;&lt;P&gt;REPORTS &lt;/P&gt;&lt;P&gt;APPENDIX &lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;for seeing the blue print document go to this url...&lt;/P&gt;&lt;P&gt;&lt;A href="http://cgi.ebay.com.sg/SAP-MM-Blue-Print_W0QQitemZ200193026883QQcmdZViewItem" target="test_blank"&gt;http://cgi.ebay.com.sg/SAP-MM-Blue-Print_W0QQitemZ200193026883QQcmdZViewItem&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Business Blue print is a detailed documentation of the &lt;/P&gt;&lt;P&gt;requirements gathered from client.it represents the &lt;/P&gt;&lt;P&gt;business process requirements of the company.  It is an &lt;/P&gt;&lt;P&gt;agreed statement of how the company intends to run its &lt;/P&gt;&lt;P&gt;business within SAP system.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Business blue print is the conversion of the legacy system &lt;/P&gt;&lt;P&gt;data into sap compliant - i.e. what ever the companies &lt;/P&gt;&lt;P&gt;processes are there are converted and put into SAP &lt;/P&gt;&lt;P&gt;Compliant configuration documentation so as to enable us to &lt;/P&gt;&lt;P&gt;carryout the realization according to the blueprint &lt;/P&gt;&lt;P&gt;prepared in a methodical way which saves time in &lt;/P&gt;&lt;P&gt;realization.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In blue print  stage the following things will be done&lt;/P&gt;&lt;P&gt;1. Business process walk through&lt;/P&gt;&lt;P&gt;2. Determining freeze organization Strature&lt;/P&gt;&lt;P&gt;3. Prepare and Review Buz Blue Print&lt;/P&gt;&lt;P&gt;4.Sign off blue Print&lt;/P&gt;&lt;P&gt;5.Setup Development Enviornment&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;blue prints are very important for implementing projects. &lt;/P&gt;&lt;P&gt;blue prints contains client business process and legacy &lt;/P&gt;&lt;P&gt;system details. in this we want to know the client business &lt;/P&gt;&lt;P&gt;process according to that we are customising and &lt;/P&gt;&lt;P&gt;configuring the things&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if the above is usefull to you&lt;/P&gt;&lt;P&gt;please reward me some points&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thanks &lt;/P&gt;&lt;P&gt;karthik&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Mar 2008 16:00:29 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/how-to-prepare-blue-prints/m-p/3550685#M854270</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-03-27T16:00:29Z</dc:date>
    </item>
  </channel>
</rss>

