methodology

to end implementation consists of the below steps:1.2.Business Blueprint Business Requirements aligned with the SAP business modelBusiness Process Design (To-Be process models)Solution Design (including a fit gap analysisIdentified additional functional & technical requirements that need to be custom-developed3.RealizationConfigure SAP system as per the finalized BBP document.Develop custom RICEFW objectsDefine user roles & authorizationsBuild a complete Business & System environmentPerform rigorous testing as per Testing scopeDevelop Trair documentationImpart training to core-business users on the developed systemObtain business approval User Acceptance Testing4.Final PreparationPrepare the system for Production releasePrepare the internal & external organization for Go-Live5.Go Live & SupportIn this phase, the business owns & executes new Business Processes & systems. The purpose of Go-Live phase is -Prepare the system for Production releasePrepare the internal & external organization for Go-LiveHi Sunil,When the project is started then it is called as PROJECT KICK-OFF after which the project phases like desigining, analysinzg and development starts.PROJECT GO LIVE means once the project is complete and its moved to the live production system for the business to use is called project go live.CheersVJHi,Project Kick-off is the time when the plan is finalised, approved and the project work starts.Post go-live usually refers to teh activities and production support involved once the project goes to Production system.For Kick off meeting, you just introduce yourself and read user mindset and ask project implementation related questions.I mean to say that dont go in deep while kick off meeting with pondering many questions so that client will get a 100% pros and cons of the implemented project. Go ahead with mild questions about business operations and how client handling current processes.If you can go through this below link:Just convert these questions into your EWM area.You will get an idea.Kick Off Meeting is the official announcement of the start of the project. Most of the time, Consultants will not play an role in it. It is more from the project management side where they define the milestones of the project.Business OneSAP Business OneSAP Business One Accelerated Implementation Program 2.0Project Preparation (Phase 1)Skip to end of metadataAdded by Guest, last edited by Guest on Dec 03, 2007(view change)show commentGo to start of metadataProject Preparation (Phase 1)In This Chapter:#Milestones#Team members#Project tasks#Documentation#Best-practice recommendationsThe purpose of this phase is to provide initial planning and preparation for the SAP Business One implementation project. Although each SAP Business One project has its own unique objectives, scope, and priorities; the steps in the preparation phase help identify and plan the primary focus areas that need to be considered. This does include technical issues as well as project management topics. In addition, the SAP Business One software is delivered during this phase and a preliminary installation of a sandbox or test system is completed.MilestonesAt the end of this phase, the following deliverables and objectives have to be completed:Milestone 1.1: Obtain clear understanding about sales process and client from sales teamMilestone 1.2: Conduct kick-off meetingMilestone 1.3: Deliver and install SAP Business One softwareMilestone 1.4: Obtain project phase sign-off from customer for "Project Preparation"Team membersThe estimated duration of this phase is 37.5 hours. During the project preparation phase, the following team members are required.Team memberEstimated Time Commitment

SAP Business One Project Manager

29.5 hours

SAP Business One Consultant

35 hours

SAP Business One Account Manager

26 hours

Client Project Manager

9.5 hours

Client IT Administrator

14 hours

Client Lead - Accounting

6 hours

Client Lead - Sales

6 hours

Client Lead - Operations

6 hours

Client Lead - Purchasing

6 hours

Client Lead - Logistics

6 hours

Client Lead - HR

6 hours

Client Executive Steering Committee (if applicable)

6 hoursSAP Business One project manager, consultant(s), and account manager are involved in the initial steps of this phase, i.e. the project handover from sales to consulting. They should also all attend the kick-off meeting in order to assure that no miscommunication and misunderstandings impact the project early on.The client project manager needs to be involved early on in the process, as he is responsible for client-internal communication with the client team. He is to be involved in the planning and execution of the kick-off workshop and guides the project (together with the SAP Business One project manager) from that point on.Client IT administrator and functional leads should be prepared by the client project manager as soon as possible to make sure that they can attend the kick-off meeting and are available subsequently for questions. The client IT administrator also needs to assist in the installation of the SAP Business One software and database.Project TasksThe following lists the tasks that have to be completed during this implementation phase:Task #DescriptionResultsEst. durationTeam members1General project management12 hours1-1Hand-over from sales-Obtain information about sales process, customer, schedule, business processes, ...-Project risk assessed6 hoursSAP Business One project manager, consultants, account manager1-2Define project organization-Clarify project responsibilities internally2 hoursSAP Business One project manager, consultants, account manager1-3Conduct internal kick-off-Communicate project plan4 hoursSAP Business One project manager, consultants, account manager2Project kick-off preparation10 hours2-1Communicate with customer-Confirm hardware and resource availability-Confirm date and agenda for kick-off2 hoursSAP Business One project manager, client project manager2-2Create kick-off presentation-Kick-Off meeting presentation with agenda and project plan8 hoursSAP Business One project manager, consultants, account manager3Kick-off meeting6 hours3-1Kick-off meeting-Conduct kick-off meeting-Obtain understanding of customer expectations and high-level requirements-Finalize project plan and time schedule-Service level agreement (SLA) signed6 hoursProject team (see 2.2)4Software delivery and install8.5 hours4-1Deliver software-Obtain signed delivery receipt0.5 hoursSAP Business One project manager, client project manager4-2Install SAP Business One-SAP Business One functional and initialized with demo database on client hardware8 hoursSAP Business One consultants, client IT administrator5Review Project Phase-Obtain signed project phase sign-off1 hourSAP Business One project manager, client project manager, SAP Business One consultantsDocumentationIt is important that the following steps and results of this phase be documented. a) Handover from sales b)Project scope and organization c) Kick-off meeting result d) Service level agreement (SLA) e) SAP Business One software deliveryf) Completion of Phase 1: Project PreparationPlease use the following templates as guidelines for corresponding project tasks and to create the necessary documentation:Handover from Sales Checklist(DOC, 155Kb)Project Risk Assessment(XLS, 99 Kb)Project Plan(MPP, 223 Kb)SAP Business One Guides(ZIP, 2,925 Kb)Kick-Off Meeting Presentation Template(PPT, 552 Kb)Meeting Agenda Template(DOC, 78 Kb)Meeting Minutes Template(DOC, 72 Kb)Service Level Agreement(DOC, 86 Kb)Software Delivery Receipt(DOC, 135 Kb)Project Phase Signoff(DOC, 130 Kb)Best-practice recommendationsPlease find below a list of frequently asked questions and know issues for the implementation phase.Include sales team in kick-off meetingto assure that customer expectations set during the sales process are feasible and that product capabilities have not been miscommunicatedExplicity confirm hardware, software, and resource availibilityfor kick-off meeting with client project manager and/or IT administratorPerforma high levelSAP Business One product demonstration as part of the kick-off meetingin order to give all team members a visual understanding of the product and to address early questionsClearlycommunicate time requirements for client resources, i.e. when and how long they have to be availableClient shouldcreate an executive steering committeein order to assure executive management support of the implementation projectAt the completion of the "Project Preparation Phase", obtain a copy of the "Project Phase Signoff"document signed by the client project manager

usiness OneSAP Business OneSAP Business One Accelerated Implementation Program 2.0Business Blueprint (Phase 2)Skip to end of metadataAdded by Guest, last edited by Guest on Dec 03, 2007(view change)show commentGo to start of metadataBusiness Blueprint (Phase 2)In This Chapter#Milestones#Team members#Project Tasks#Documentation#Best-practice recommendationsThe purpose of this phase is to achieve a common understanding of how the client intends to run SAP Business One to support their business. One or more requirements gathering workshops are conducted during which business processes and individual functional requirements of the client are defined and analyzed. In addition, the workshops serve to refine the original project goals and objectives as well as to revise the overall project schedule, if necessary. The result is the Business Blueprint, which is a detailed documentation of the results gathered during requirements workshops. The Business Blueprint serves as a technical and functional guide during the subsequent phases of the SAP Business One implementation project.MilestonesAt the end of this phase, the following deliverables and objectives have to be completed:Milestone 2.1: Schedule and conduct business requirement gathering workshops with client functional leadsMilestone 2.2: Create Business BlueprintMilestone 2.3: Determine changes to project scope and time schedule (if applicable)Milestone 2.4: Obtain project phase sign-off from customer for "Business Blueprint"Team membersThe estimated duration of this phase is 26.5 hours. During the business blueprint phase, the following team members are required.Team memberEstimated Time Commitment


7.5 hours


24 hours


7.5 hours


6 hours


3 hours

Client Lead - Sales

3 hours


3 hours


3 hours


3 hours

Client Lead - HR

3 hoursThe SAP Business One project manager is responsible for scheduling the business requirements gathering workshops together with the client project manager. The SAP Business One consultants conduct the business requirements gathering workshops together with the client functional leads. The client IT administrator should attend the workshops. If this is not possible, he should be briefed on the outcome of each workshop to ensure that requirements defined are feasible in the client's IT environment.During the business requirements workshops, client functional leads should be prepared to discuss details of each business process they oversee and to walk the consultant through their operations.Project TasksThe following lists the tasks that have to be completed during this implementation phase:Task #DescriptionResultsEst. durationTeam members1General project management1.5 hours1-1Review project plan-Review minutes from kick-off meeting-Project plan is updated based on outcome of kick-off meeting1 hourSAP Business One project manager, client project manager1-2Schedule business requirements gathering workshops-Business requirements gathering workshops are scheduled0.5 hoursSAP Business One project manager, client project manager2Business requirements gathering19 hours2-1Conduct business requirements gathering workshopsBusiness needs defined in detail in the areas ofsales,purchasing,inventory management,production and MRP,financials and accounting,service managementbankingreportingbusiness partner and item master datachart-of-accountsRequirements defined forauthorizations and data ownershipdata migrationinterfaces and integration pointssystem performance15 hours (5 workshops at 3 hours each)SAP Business One consultant, client functional leads, client IT administrator2-2Create Business Blueprint-All relevant data (requirements, solutions, limitations, and gaps) are documented in Business Blueprint document4 hoursSAP Business One consultant3Review Blueprint5 hours3-1Review and discuss Business Blueprint-Feasibility of business and technical requirements is determined-Limitations and gaps are established and solutions are agreed upon4 hoursSAP Business One consultants, SAP Business One project manager, client project manager3-2Review project plan-Project plan is up-to-date based on Business Blueprint review1 hourSAP Business One project manager, client project manager4Review Project Phase-Obtain signed project phase sign-off1 hourSAP Business One project manager, client project manager, SAP Business One consultantsDocumentationIt is important that the following steps and results of this phase be documented. a) Review meeting results b) Business process and technical requirements c) Completion of Phase 2: Business Blueprint Please use the following templates as guidelines for corresponding project tasks and to create the necessary documentation:Meeting Agenda Template(DOC, 78 Kb)Meeting MinutesTemplate(DOC, 72 KbSAP Business One Business Blueprint(DOC, 450 Kb)SAP Business One Guides(ZIP, 2,925 Kb)Project Plan(MPP, 223 Kb)Project Phase Signoff(DOC, 130 Kb)Best-practice recommendationsPlease find below a list of frequently asked questions and know issues for the implementation phase.Conduct both one-on-one and group workshopsbe able to discuss individual requirements as well as overlaps and dependencies between departmentsHave aSAP Business One system available during the workshopsin order to be able to demonstrate how business requirements can be addressed by the system*Use client's chart-of-accounts* instead of creating a new chart-of-accounts as this will significantly reduce efforts for data migration and open balance reconciliationCommunicate and document thatdata migration includes only master data from legacy system to SAP Business One;if client wishes to migrate historical transaction data, defer to a separate project following the initial implementationAssure detailed documentation of requirementsin Business Blueprint andemphasize to clientthat even seemingly smallchanges to scope and/or requirements can have a significant impacton cost, resources, and timeline of the projectMake sure toobtain client sign-off on Business Blueprint

Project Realization (Phase 3)In This Chapter#Milestones#Team members#Project tasks#Documentation#Best-practice recommendationsThis phase represents the most significant of the implementation phases. The purpose of Project Realization is to implement all the business process and technical requirements defined during the previous phases and documented in the Business Blueprint. During this phase, the consultants validate and update configuration and demonstrate processes while the customer updates the work instructions (business process procedures: BPP) and performs unit and integration tests.MilestonesAt the end of this phase, the following deliverables and objectives have to be completed:Milestone 3.1: SAP Business One production system installed and customized based on Business BlueprintMilestone 3.2: Data migration complete (if applicable)Milestone 3.3: System setup validatedMilestone 3.4: System testing completeMilestone 3.5: Training and cut-over plan definedMilestone 3.6: Obtain project phase sign-off from customer for "Project Realization"Team membersThe estimated duration of this phase is 86 hours. During the project realization phase, the following team members are required.Team memberEstimated Time Commitment


17 hours


86 hours


17 hours


40 hours


20 hours

Client Lead - Sales

20 hours


20 hours


20 hours


20 hours

Client Lead - HR

20 hoursThe SAP Business One project manager is responsible for scheduling system configuration, as well as oversee and possibly execute any planning steps in cooperation with the client project manager. SAP Business One consultants perform the install of all SAP Business One components (operating system, database, SAP Business One, patches) on client hardware.The client IT administrator is responsible for supporting the installation of the SAP Business One components. Client leads mainly need to be available for the creation of validation and test scripts as well as system testing and validation itself. Client leads are responsible to confirm that the configurations in SAP Business One correspond to the business requirements defined and provide the solution expectedProject tasksThe following lists the tasks that have to be completet during this implementation phase:Task #DescriptionResultsEst. durationTeam members1General project management18 hours1-1Plan organizational change management-User roles are defined and assigned to business processes-Communication strategy for end users is defined2 hoursSAP Business One project manager, client project manager, SAP Business One consultants1-2Plan end-user and administrator training-Training strategy defined-Preliminary training schedule created-Training material is created8 hoursSAP Business One project manager, client project manager, SAP Business One consultants1-3Define and prepare data migration-Relevant item, BP, and balance data from legacy system is cleaned and filtered8 hoursSAP Business One consultants, client IT administrator2Production system setup28 hours2-1Install SAP Business One production system-SAP Business One with database installed on client hardware for intended production use2 hoursSAP Business One consultants, client IT administrator2-2Complete system initialization-SAP Business One system initialized based on Business Blueprint and SAP system initialization guide2 hoursSAP Business One consultants, client IT administrator2-2Complete system initialization-SAP Business One system initialized based on Business Blueprint and SAP system initialization guide2 hoursSAP Business One consultants, client IT administrator2-3Complete system configuration based on Business Blueprint-SAP Business One system configured for production use based on Business Blueprint8 hoursSAP Business One consultants, client IT administrator2-4Complete data migration-All relevant item, business partner, and accounting data imported into SAP Business One8 hours(depending on data volume and quality, this number varies greatly)SAP Business One consultants, client IT administrator2-5Configure applicable interfaces-Standard interfaces to print, fax, email, etc. configured and functional4 hoursSAP Business One consultants, client IT administrator2-6SAP Business One consultants, client IT administrator-User list with authorizations is completed and users have been created in the SAP Business One system4 hoursSAP Business One consultants, client IT administrator3Organizational Change Management2 hours3-1Conduct change management communication(if applicable)-Roles, tasks, and training schedule have been communicated to end users-Vendors and customers have been informed about schedule and upcoming changes2 hoursSAP Business One project manager, client project manager, client functional leads4System validation/acceptance testing8 hours4-1Maintain Business Process Master List-List of all relevant core business processes relevant for the SAP Business One implementation is created6 hoursSAP Business One consultants, client functional leads4-2Conduct business process and data validation/acceptance testing workshops-All processes from the business process master list have been walked through in the system and have been reviewed-Data imported via data migration has been verified-Changes to setup or scope are documented2 hoursSAP Business One consultants, client functional leads5System Testing26 hours5-1Define test cases and scope-Test plan and cases created8 hoursSAP Business One consultants, client functional leads5-2Prepare test environment-Copy of production SAP Business One database created and initialized in SAP Business One test system1 hourSAP Business One consultants, client IT administrator5-3Execute test plan-All test cases have been completed successfully16 hoursSAP Business One consultants, client functional leads5-4Review test results and necessary changes-Results and necessary changes are reviewed-Project plan is updated1 hourSAP Business One project manager, client project manager, SAP Business One consultants6Cut-Over and Support Planning3 hours6-1Define cut-over plan-Cut-over plan defined1 hourSAP Business One project manager, client project manager, client functional leads, client IT administrator, SAP Business One consultants6-2Plan support strategy-All support procedures and contacts are defined1 hourSAP Business One project manager, client project manager, client functional leads, client IT administrator, SAP Business One consultants6-3Plan system administration-System administrator is appointed; tasks and responsibilities are defined1 hourSAP Business One project manager, SAP Business One consultants, client project manager, client IT administrator7Review Project Phase-Obtain signed project phase sign-off1 hourSAP Business One project manager, client project manager, SAP Business One consultantsDocumentationIt is important that the following steps and results of this phase be documented. a) General project management tasks b) User and administrator training plan c) System validation d) System testing e) Changes required or desired after validation and testing f) Cut-over and support g) Completion of Phase 3: Project Realization

Please use the following templates as guidelines for corresponding project tasks and to create the necessary documentation:Meeting Agenda Template(DOC, 78 Kb)Meeting Minutes Template(DOC, 72 Kb)Change Management Communication Guide(DOC, 585 Kb)SAP Business One Guides(ZIP, 2,925 Kb)Business Process Master List(XLS, 98 Kb)Training Plan(DOC, 174 Kb)Test Strategy Guide(DOC, 219 Kb)Test Case Template(DOC, 78 Kb)Test Plans(ZIP, 343 Kb)Issue Log(XLS, 119 Kb)Change Request Form(DOC, 141 Kb)Change Log(XLS, 99 kb)Project Plan(MPP, 223 Kb)Project Phase Signoff(DOC, 130 Kb)Best-practice recommendationsPlease find below a list of frequently asked questions and know issues for the implementation phase.Involve client functional leadsconstantly during the entire phase in order to make them feel considered and comfortable with the changes the new system will bringClearly communicate to the client thatdata quality and integrity for data migration is client responsibilityUse Configuration Express Wizard (CEW)to initialize the SAP Business One system.Conduct all or large parts of system validation/acceptance testing together with client in aformal "Conference Room Pilot"End-users should log into system with their user ID and simulate relevant business processesfrom start to finishPrint a copy of all output documentsi.e. invoices, purchase orders, reports, etc., and financial statements andhave client sign off upon acceptancePlan to initially train key-users and implement a formaltraining conceptMinimize the number of changesto setup and scope you implement as testing and training are significantly affected;document changes and reason for changes consistentlywith change request formswith change request formsin order to have the weekend for production preparation activities; complete business activities that Friday by noon

Re: Role of MM consultant in Full Life Cycle Implementation?

Jrgen LJan 11, 2013 4:55 PM(in response to Vasu Bhatt)this can vary from project to project depending on the project size, the budget, the stuffing,if you have no have no knowledge in IM and LIV, then a second consultant has to take care about that. If the project layout does not allow a second consultant in this area then the project lead may have to look for an alternative.if you have the knowledge but the project is huge and you cannot do it alone, then you will have several consultants for this part, and you maybe be free to arrange yourself who is doing what part.it is even possible that FI guys take over the LIV part and you just do MM and IM.I am doing project for 15 years already and there was never a project equal to another.The more skills you have the more flexible you can be used in a project. I am doing purchasing in in project in Saudi Arabia and master data in huge project in Germany, and only IM in a China rollout, while I never do LIV.

Re: Role of MM consultant in Full Life Cycle Implementation?

Bijay Kumar BarikJan 12, 2013 2:11 PM(in response to Vasu Bhatt)Hi,At present world with speedy and modern management system wheretime and material billingconcerned- its really very difficult to find a consultant working in a project with full life cycle implementation! But you can find project manager; team leads are working on full life cycle implementation project for project successful go-live and hang on till stabilizationwhere an expertise consultant in each specialization enter into project and leave the project after specific assigned work completion.In a quick summery a Full life cycle implementation where Project Team involved (1) Initial preparation where involves Project Kick off with preparation of project plan with SAP overview,(2) Blue Print involves AS-IS Study with IS-TO BE presented with GAP Analysis with BBP preparation with SAP Installation with Training to Core users,(3) Realization involves Configuration & customization, master data design, testing with own master data (4)Final preparation involves All TR transportations with later Testing with Customer Master data with later Training to end users and finally Cut over phase,(5) Go-live and Stabilization- Customer run his business on a specific date in SAP with followed by stabilization.Coming back to Role of MM consultant is vital in each stage where involvement of 2 phase in critical where designing business process starts with decision of MM organization units with how many material types are needed, valuation classes for material type keeping in mind at the end you should have report - after goods receipt,invoice verification or payment to vendor. Also procurement process need to be designed with approval process and later goods receipt followed by invoice verification where setting of tolerance keys required.Refer details which discussed in a thread for a plant creation.http://scn.sap.com/SAP Implementation is the whole of processes that defines a complete method to implement SAP software in an organization. The SAP implementation method described in this entry is a generic method and not a specific implementation method as such. It is based on best practices and case studies from various literature sources and presents a collection of processes and products that make up a complete implementation method to allow any organization to plan and execute the implementation of SAP (ERP) software.The implementation of SAP software, such as SAP R/3 is almost always a massive operation that brings a lot of changes in the organization. The whole process can take up to several years. Virtually every person in the organization is involved, whether they are part of the SAP technical support organization (TSO) or the actual end-users of the SAP software. The resulting changes that the implementation of SAP generates are intended to reach high level goals, such as improved communication and increased return on information (as people will work with the same information). It is therefore very important that the implementation process is planned and executed with the usage of a solid method. There are various SAP implementation methods, such as IBMs Ascendant. An example of how one company, Robert Bosch GmbH, implemented SAP R/3 over 10 years is available. This study shows that designing IT architecture is very critical in SAP implementation practices.The SAP implementation process is made up out of four main phases, i.e. the project preparation where a vision of the future-state of the SAP solution is being created, a sizing and blueprinting phase where the solution stack is created and training is being performed, a functional development phase and finally a final preparation phase, when the last tests are being performed before the actual go live. For each phase, the vital activities are addressed and the deliverables/products are explained.The process-data diagram that is depicted at the right, gives an overview of all of these activities/processes and deliverables. The four gray boxes depict the four main implementation phases, which each contain several processes that are in this case all sequential. The boxes at the right show all the deliverables/concepts that result from the processes. Boxes without a shadow have no further sub-concepts. Boxes with a black shadow depict complex closed concepts, so concepts that have sub-concepts, which however will not be described in any more detail. Boxes with a white shadow (a box behind it) depict open closed concepts, where the sub-concepts are expanded in greater detail. The lines with diamonds show a has-a relationship between concepts.Duration of the project:Re: What is the total life cycle involved in any projectIt actually depends on various factors, such as :1. how many modules they want to implement.2. Team Size.3. Organizational Structure (Volume of data)4. Legacy System5. Business Complexity etc.There is no hard and fast rule that every project should be completed in a particular duration of time. Depending on the above factors, it may vary any where from 6 months to 18 months or so. (Approximately, it may be less than 6 months or more than 18 months in some exceptional cases).Usually it is divided into phases:1. Project Preparation : Project team, infrastructure, Software, Steering committe etc will be identified in this phase.2. Business Blue Print : Re-engineering of Business process and BBP sign off.3. Realization : Analysing Gap and Realization of possible customization and development effort4. Final Preparation : Development and Configuration5. Go Live and Post Go Live support : Going Live and Support after go liveYou would allot specific time periods for each of these phases and will set milestones accordingly.or it could even be like :Project StartAnalysisDesignDesign Freeze / Client Sign-offConstructionTestingImplementationProject EndProject Management FrameworkPost Close ReviewTrainingChange ManagementRegards,Naveen.

Hello,Implementation steps:1. AS IS process2. To be process mapping3. customizaiton in SAP + devepment4. Unit testing5. Full testing6. End-user training7. Go-live8. Support for initial month-ends.9. Ongoing support....1. AS IS process - Study of the existing process.2. To be process mapping - What will be the new process.3. customizaiton in SAP + devepment - Customization like company codes, plants etc based on the To be process. And master data upload.4. Unit testing - Testing of each and every module separatly5. Full testing - Full system testing. In this step all steps are integrated so, it is also known as Integration testing.6. End-user training - Training for the Power user (first line users) by the SAP Consultants. They will in turn train to other users.7. Go-live - Creation of first PO or Invoice8. Support for initial month-ends. - First month-end closing, this is very much critical as FI/CO point of view.9. Ongoing support....

methodology

Documents