SAP End To End

 

  SAP end to end implementation consists consists of the below steps: 1.Project Preparation 

     

   

   



Perform initiation & prepare project plans  Define the project goals, scope & objectives   Identify, on-board & train team members  Formalize strategy for implementation   Conduct Kick-off meeting   2. Business Blueprint 

· · · ·

Business Requirements aligned with the SAP business model  Business Process Design (To-Be process models)   Solution Design (including a fit gap analysis  Identified additional functional & technical requirements that need to be custom-developed  

3. Realization   ·

Configure SAP system as per the finalized BBP document.

·

Develop custom RICEFW objects

·

Define user roles & authorizations

· ·

Build a complete Business & System environment Perform rigorous testing as per Testing scope

·

Develop Training material & end-user documentation

·

Impart training to core-business users on the developed system

·

Obtain business approval – approval – User  User Acceptance Testing

4. Final Preparation  ·

Prepare the system for Production release

·

Prepare the internal & external e xternal organization for Go-Live

5.Go Live & Support  In this phase, the business owns & executes new Business Processes & systems. The purpose of Go-Live phase is · ·

Prepare the system for Production release Prepare the internal & external e xternal organization for Go-Live

Hi 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 pr oduction system for the business to use is called project go live. Cheers VJ Hi,

 

  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 pro ject manageme management nt side where they define the milestones of the project. p roject.

1. Business One  One  2. SAP Business One  One  3.

SAP Business One Accelerated Implementation Program 2.0  2.0 

Project Preparation (Phase 1)  Skip to end of metadata  metadata 

     Added by Guest, last edited by Guest on Dec 03, 2007 (view change)  change)    show comment

  

Go to start of metadata  metadata 

Project Preparation (Phase 1)  1)  In This Chapter:          



#Milestones   #Milestones



#Team members  members 



#Project tasks  tasks 



#Documentation   #Documentation



#Best-practice recommendations  recommendations 

The 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.

Milestones

 

 At the end of this phase, the following deliverables and objectives have to be completed: Milestone 1.1: 1.1: Obtain clear understanding about sales process and client from sales team Milestone 1.2: 1.2: Conduct kick-off meeting Milestone 1.3: 1.3: Deliver and install SAP Business One software Milestone 1.4: 1.4: Obtain project phase sign-off from customer for "Project Preparation"

Team members The estimated duration of this phase is 37.5 hours. During the project preparation phase, the following team members are required. Team member

Estimated 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 Committe Committeee (if applicable)

6 hours

 

SAP 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 Tasks The following lists the tasks that have to be completed during this implementation phase: Task

Description

Results

# 1

Est.

Team members

duration General project

12 hours

management

1-1

Hand-over from sales

-Obtain information about sales  process, customer, customer, sched schedule, ule,

6 hours

SAP Business One project manager, consultants, account manager consultants,

2 hours

SAP Business One project manager,

 business processes, processes, ... -Project risk assessed 1-2

1-3

Define project

-Clarify project responsibi responsibilities lities

organization

internally

Conduct internal

-Communicate project plan

consultants,, account manager consultants 4 hours

kick-off 2

SAP Business One project manager, consultants,, account manager consultants

Project kick-off

10 hours

preparation

2-1

Communicate with customer

-Confirm hardware and resource availability

2 hours

SAP Business One project manager, client project manager

8 hours

SAP Business One project manager,

-Confirm date and agenda for kickoff 2-2

Create kick-off

-Kick-Off meeting presentation with

 presentation

agenda and project plan

3

Kick-off meeting

3-1

Kick-off meeting

consultants,, account manager consultants 6 hours

-Conduct kick-off meeting -Obtain understanding of customer expectations and high-level requirements -Finalize project plan and time

6 hours

Project team (see 2.2)

 

Task

Description

Results

#

Est.

Team members

duration

schedule -Service level agreement (SLA) signed 4

Software delivery and install

4-1

Deliver software

8.5 hours

-Obtain signed delivery receipt

0.5 hours

SAP Business One project manager, client project manager

4-2

Install SAP

-SAP Business One functional and

Business One

initialized with demo database on

8 hours

SAP Business One consultants, client IT administrator

client hardware 5

Review Project

-Obtain signed project phase sign-

Phase

off

1 hour

SAP Business One project manager, client project manager, SAP Business One consultants

Documentation It 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 delivery

f)

Completion of Phase 1: Project Preparation

Please use the following templates as guidelines for corresponding project tasks and to create the necessary documentation: Handover from Sales Checklist  (DOC,  (DOC, 155Kb) Project Risk Assessment  (XLS,  (XLS, 99 Kb) Project Plan (MPP, Plan (MPP, 223 Kb) SAP Business One Guides (ZIP, Guides (ZIP, 2,925 Kb) Kick-Off Meeting Presentation Template (PPT, Template (PPT, 552 Kb) Meeting Agenda Template (DOC, Template (DOC, 78 Kb) Meeting Minutes Template (DOC, Template (DOC, 72 Kb) Service Level Agreement  (DOC,  (DOC, 86 Kb)

 

Software Delivery Receipt  (DOC,  (DOC, 135 Kb) Project Phase Signoff  (DOC,  (DOC, 130 Kb)

Best-practice recommendations Please find below a list of frequently asked questions and know issues for the implementation phase.

 



Include sales team in kick-off meeting to meeting to assure that customer expectations set during the sales process are feasible and that product capabilities have not been miscommunicated

 



Explicity confirm hardware, software, and resource availibility for availibility for kick-off meeting with client project manager and/or IT administrator

 



Perform a Perform  a high level SAP Business One product demonstration as part of the kick-off meeting  in order to give all team members a visual understanding of the product and to address early questions

 

Clearly communicate time requirements for client resources, resources , i.e. when and how long they have to be available

 

Client should create an executive steering committee in committee  in order to assure executive management support of the





implementation project

   At the completion of the "Project Preparation Phase", obtain a copy of the "Project " Project Phase Signoff " document



signed by the client project manager  

1. usiness One  One  2. SAP Business One  One  3. SAP Business One Accelerated Implementation Program 2.0  2.0 

Business Blueprint (Phase 2)  Skip to end of metadata  metadata 

     Added by Guest, last edited by Guest on Dec 03, 2007 (view change)  change)    show comment

  

Go to start of metadata  metadata 

Business Blueprint (Phase 2)  2)  In This Chapter      



#Milestones   #Milestones



#Team members  members 



#Project Tasks  Tasks 



#Documentation  #Documentation  #Best-practice recommendations  recommendations 

   



 

The 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.

Milestones  At the end of this phase, the following deliverables and objectives have to be completed: Milestone 2.1: 2.1: Schedule and conduct business requirement gathering workshops with client functional leads Milestone 2.2: 2.2: Create Business Blueprint Milestone 2.3: 2.3: Determine changes to project scope and time schedule (if applicable) Milestone 2.4: 2.4: Obtain project phase sign-off from customer for "Business Blueprint"

Team members The estimated duration of this phase is 26.5 hours. During the business blueprint phase, the following team members are required. Team member

Estimated Time Commitment

SAP Business One Project Manager

7.5 hours

SAP Business One Consultant

24 hours

Client Project Manager

7.5 hours

Client IT Administrator

6 hours

Client Lead - Accounting

3 hours

Client Lead - Sales

3 hours

Client Lead - Operations

3 hours

Client Lead - Purchasing

3 hours

 

Team member

Estimated Time Commitm Commitment ent

Client Lead - Logistics

3 hours

Client Lead - HR

3 hours

The 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 t he outcome of each workshop works hop 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 Tasks The following lists the tasks that have to be completed during this implementation phase: Task #

Description

1

General project

Results

Est. duration

Team members

1.5 hours

management

1-1

Review project plan

-Review minutes from kick-off

1 hour

SAP Business One project

meeting

manager, client project

-Project plan is updated based on

manager

outcome of kick-off meeting 1-2

Schedule business

-Business requirements gathering

requirements

workshops are scheduled

0.5 hours

manager, client project manager

gathering workshops 2

SAP Business One project

Business

19 hours

requirements gathering

2-1

Conduct business

Business needs defined in detail in

15 hours (5

SAP Business One consultant,

requirements

the areas of

workshops at 3

client functional leads, client

gathering workshops

sales,

hours each)

IT administrator

 purchasing, inventory management,  production and MRP, financials and accounting, accounting, service management  banking reporting

 

Task

Description

Results

Est. duration

Team members

4 hours

SAP Business One consultant

#

 business partner partner and ite item m master data chart-of-accounts Requirements Requiremen ts defined for authorizationss and data ownership authorization data migration interfaces and integration points system performance

2-2

Create Business

-All relevant data (requirements, (requirements,

Blueprint

solutions, limitations, and gaps) are documented in Business Blueprint document

3

Review Blueprint

5 hours

3-1

Review and discuss

-Feasibility of business and

Business Blueprint

technical requirements is

SAP Business One project

determined

manager, client project

-Limitationss and gaps are -Limitation

manager

4 hours

SAP Business One consultants,

established and solutions are agreed upon 3-2

Review project plan

-Project plan is up-to-date based on

1 hour

Business Blueprint review

SAP Business One project manager, client project manager

4

Review Project

-Obtain signed project phase sign-

Phase

off

1 hour

SAP Business One project manager, client project manager, SAP Business One consultants

Documentation It 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, Template (DOC, 78 Kb)

 

Minutes Template Meeting Minutes  Template (DOC,  (DOC, 72 Kb SAP Business One Business Blueprint  (DOC,  (DOC, 450 Kb) SAP Business One Guides (ZIP, Guides (ZIP, 2,925 Kb) Project Plan (MPP, Plan (MPP, 223 Kb) Project Phase Signoff  (DOC,  (DOC, 130 Kb)

Best-practice recommendations Please find below a list of frequently asked questions and know issues for the implementation phase.

 



Conduct both one-on-one and group workshops be workshops  be able to discuss individual requirements as well as overlaps and dependencies between departments

 



Have a SAP Business One system available during the workshops  in 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 reconciliation

 



Communicate and document that data migration includes only master data from legacy system to SAP Business One; if One;  if client wishes to migrate historical transaction data, defer to a separate project following the initial implementation

 



Assure detailed documentation of requirements in requirements in Business Blueprint and emphasize to client that client  that even seemingly small changes to scope and/or requirements can have a significant impact  on cost, resources, and timeline of the project

 



Make sure to obtain client sign-off on Business Blueprint  Blueprint  

Project Realization (Phase 3)  3)  In This Chapter          



#Milestones   #Milestones



#Team members  members 



#Project tasks  tasks 



#Documentation   #Documentation



#Best-practice recommendations  recommendations  This 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.

Milestones  At the end of this phase, the following deliverables and objectives have to be completed: Milestone 3.1: 3.1: SAP Business One production system installed and customized based on Business Blueprint

 

3.2: Data migration complete (if applicable) Milestone 3.2: Milestone 3.3: 3.3: System setup validated Milestone 3.4: 3.4: System testing complete Milestone 3.5: 3.5: Training and cut-over plan defined Milestone 3.6: 3.6: Obtain project phase sign-off from customer for "Project Realization"

Team members The estimated duration of this phase is 86 hours. During the project realization phase, the following team members are required. Team member

Estimated Time Commitment

SAP Business One Project Manager

17 hours

SAP Business One Consultant

86 hours

Client Project Manager

17 hours

Client IT Administrator Administrator

40 hours

Client Lead - Accountin Accounting g

20 hours

Client Lead - Sales

20 hours

Client Lead - Operations

20 hours

Client Lead - Purchasing

20 hours

Client Lead - Logistics

20 hours

Client Lead - HR

20 hours

The 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 syst em 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 expected

Project tasks The following lists the tasks that have to be completet during this implementation phase: Task #

Description

1

General project

Results

Est. duration

Team members

18 hours

management

1-1

Plan organizational organizationa l change

-User roles are defined and

2 hours

SAP Business One project

management

assigned to business

manager, client project

 processes

manager, SAP Business One

-Communication strategy for

consultants

end users is defined 1-2

1-3

Plan end-user and

-Training strategy defined

administrator training

-Preliminary training

manager, client project

schedule created -Training material is created

manager, SAP Business One consultants

8 hours

SAP Business One project

Define and prepare data

-Relevant item, BP, and

migration

 balance data from from legacy

consultants, client IT

system is cleaned and filtered

administrator

8 hours

SAP Business One

2

Production system setup

28 hours

2-1

Install SAP Business One

-SAP Business One with

 production system system

database installed on client

consultants, client IT

hardware for intended

administrator

2 hours

SAP Business One

 production use 2-2

Complete system initialization

-SAP Business One system initialized based on Business

2 hours

Blueprint and SAP system

SAP Business One consultants, client IT administrator

initialization guide 2-2

Complete system

-SAP Business One system

2 hours

SAP Business One

initialization

initialized based on Business

consultants, client IT

Blueprint and SAP system

administrator

initialization guide 2-3

Complete system

-SAP Business One system

configuration based on

configured for production

consultants, client IT

Business Blueprint

use based on Business

administrator

Blueprint

8 hours

SAP Business One

 

Task

Description

Results

Est. duration

Team members

Complete data migration

-All relevant item, business

8 hours

SAP Business One

 partner, and accounting data

(depending on

consultants, client IT

imported into SAP Business

data volume and

administrator

One

quality, this

#

2-4

number varies greatly) 2-5

2-6

Configure applicable

-Standard interfaces to print,

4 hours

SAP Business One

interfaces

fax, email, etc. configured

consultants, client IT

and functional

administrator

SAP Business One

-User list with authorizations

consultants, client IT

is completed and users have

consultants, client IT

administrator

 been created in the SAP

administrator

4 hours

SAP Business One

Business One system 3

Organizational Organizat ional Change

2 hours

Management

3-1

Conduct change management

-Roles, tasks, and training

communication(if applicable)

schedule have been

manager, client project

communicated to end users

manager, client functional

-Vendors and customers

leads

2 hours

SAP Business One project

have been informed about schedule and upcoming changes 4

System

8 hours

validation/acceptance testing

4-1

Maintain Business Process

-List of all relevant core

6 hours

SAP Business One

Master List

 business processes relev relevant ant

consultants, client functional

for the SAP Business One

leads

implementation is created 4-2

Conduct business process and

-All processes from the

data validation validation/acceptance /acceptance

 business process maste masterr list

consultants, client functional

testing workshops

have been walked through in

leads

2 hours

the system and have been reviewed -Data imported via data migration has been verified -Changes to setup or scope are documented documented 5

System Testing

26 hours

SAP Business One

 

Task

Description

Results

Est. duration

Team members

Define test cases and scope

-Test plan and cases created

8 hours

SAP Business One

#

5-1

consultants, client functional leads 5-2

Prepare test environm environment ent

-Copy of production SAP Business One database

1 hour

SAP Business One consultants, client IT administrator

created and initialized in SAP Business One test system 5-3

Execute test plan

-All test cases have been

16 hours

completed successfully

SAP Business One consultants,, client functional consultants leads

5-4

1 hour

SAP Business One project

Review test results and

-Results and necessary

necessary changes

changes are reviewed

manager, client project

-Project plan is updated

manager, SAP Business One consultants

6

Cut-Over and Support

3 hours

Planning

6-1

Define cut-over plan

-Cut-over plan defined

1 hour

SAP Business One project manager, client project manager, client functional leads, client IT administrator, administrator, SAP Business One consultants

6-2

Plan support strategy

-All support procedures and

1 hour

contacts are defined

SAP Business One project manager, client project manager, client functional leads, client IT administrator, administrator, SAP Business One consultants

6-3

Plan system administrat administration ion

-System administrat administrator or is

1 hour

SAP Business One project

appointed; tasks and

manager, SAP Business One

responsibilities responsibil ities are defined

consultants, client project manager, client IT administrator

7

Review Project Phase

-Obtain signed project phase sign-off

1 hour

SAP Business One project manager, client project manager, SAP Business One consultants

 

Documentation It 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, Template (DOC, 78 Kb) Meeting Minutes Template (DOC, Template (DOC, 72 Kb) Change Management Communication Guide (DOC, Guide  (DOC, 585 Kb) SAP Business One Guides (ZIP, Guides (ZIP, 2,925 Kb) Business Process Master List  (XLS,  (XLS, 98 Kb) Training Plan (DOC, Plan (DOC, 174 Kb) Test Strategy Guide (DOC, Guide (DOC, 219 Kb) Test Case Template (DOC, Template (DOC, 78 Kb) Test Plans (ZIP, Plans (ZIP, 343 Kb) Issue Log  (XLS,  (XLS, 119 Kb) Change Request Form (DOC, Form (DOC, 141 Kb) Change Log  (XLS,  (XLS, 99 kb) Project Plan (MPP, Plan (MPP, 223 Kb) Project Phase Signoff  (DOC,  (DOC, 130 Kb)

Best-practice recommendations Please find below a list of frequently asked questions and know issues for the implementation phase.

 



Involve client functional leads constantly leads  constantly during the entire phase in order to make them feel considered and comfortable with the changes the new system will bring

 

 

Clearly communicate to the client that data quality and integrity for data migration is client responsibility  responsibility  

 

Use Configuration Express Wizard (CEW) to (CEW)  to initialize the SAP Business One system.

 

Conduct all or large parts of system validation/acceptance testing together with client in a formal "Conference Room Pilot"  Pilot"  

 

End-users should log into system with their user ID and simulate relevant business processes  from start to finish

 

Print a copy of all output documents i.e. documents  i.e. invoices, purchase orders, reports, etc., and financial statements and have











client sign off upon acceptance  acceptance  

 

Plan to initially train key-users and implement a formal training concept  concept 

 

Minimize the number of changes to changes  to setup and scope you implement as testing and training are significantly





affected; document changes and reason for changes consistently with consistently  with change request forms

 



with change request forms in forms  in 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? 

Jürgen L Jan 11, 2013 4:55 PM (in response to Vasu Bhatt)  this can vary from project to project depending on the project size, 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 kno wledge 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 o ver the LIV part and you just do MM and IM. I am doing project for 15 1 5 years already and there was never a project equal to another. The more skills youproject have the flexible can in a rollout, project. while project. I am doing master data in huge inmore Germany, andyou only IMbeinused a China I neverpurchasing do LIV. in in project in Saudi Arabia and Re: Role of MM consultant in Full Life Cycle Implementation? 

Bijay Kumar Barik  Jan 12, 2013 2:11 PM (in response to Vasu Bhatt)  Hi, At present world with speedy and modern management system where time and material billingconcerned- it’s really very difficult to find a consultant working in a project with full life cycle implementation! 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 stabiliz stabilization ation where an expertise consultant in each specialization specialization enter into project and leave the project after specific assigned work completion. In a quick summery a Full life cycle implementation 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 IS -TO BE presented with GAP Analysis with BBP p reparation preparation with with SAP own Installation Trainingpreparation to Core users,(3) Realization involves Configuration customization, maste master r data design, testing master with data (4)Final involves All TR transportations with later&

 

Testing with Customer Master Master data with later Trai Training ning to end users and finally Cut over phase,(5) Go-live and StabilizationCustomer 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 ph ase in critical wher e designing  business process starts with decision of MM organization units w with ith how many materi material al types are needed, va valuation luation classes for material type keeping in mind at tthe he end you should have report - afte afterr goods receipt,invoice veri verification fication or payment to vendor. Also procurement process need to be designed with approval process pro cess and later goods receipt followed by invoice verification where setting of tolerance keys required. Refer details which discussed in a threa thread d for a plant creation. http://scn.sap.com/  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 n ot a specific implementati implementation on 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 o f 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 executed with the usag usagee of a solid method. The There re are various SAP imple implementation mentation methods, suc such h as IBM’s Ascendant. An example of how one company, Robert Bosch GmbH, implemented SAP R/3 over 10 years is available. This study shows that th at 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 b lueprinting phase where the solution stack is created and training is being  performed, a functional development development phase and final finally ly a final prepara preparation tion phase, when the llast ast 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 d epicted at the right, gives an overview of all of these activities/process activities/processes es and deliverables. The four gray boxes depict the four main implementation phases, which each contain several processe processess that are in t his 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 d epict complex closed concepts, so concepts that have sub-concepts, which however will not be described in any more detail. d etail. Boxes with a white shadow (a box behind it) d depict epict open closed concepts, where the sub-concepts are expanded in greater detail. The lines with diamonds show a has-a has -a relationship between concepts. Duration of the project: project   Re: What is the total life cycle involved in any project It 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 System 5. 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 wi ll be identified in this phase. 2. Business Blue Print : Re-engineering of Business process and BBP sign off. 3. Realization : Analysing Gap and Realizati Realization on of possible customization and development effort 4. Final Preparation : Development and Configuration 5. Go Live and Post Go Live support : Going Live and Support after go live You would allot specific time periods for each of these phases and will set milestones accordingly. or it could even be like : Project Start

 

Analysis Design Design Freeze / Client Sign-off Construction Testing Implementation Project End Project Management Framework Post Close Review Training Change Management Regards,  Naveen.

Hello, Implementation steps: 1. AS IS process 2. To be process mapping 3. customizaiton in SAP + devepment 4. Unit testing 5. Full testing 6. End-user training 7. Go-live 8. 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. upload. 4. Unit testing - Testing of each and every module separatly 5. 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 Invoice 8. Support for initial month-ends. - First month-end closing, this is very much critical as FI/CO point of view. 9. Ongoing support....