end 2 end implementation

[Former Member]

hi,

What r the stages in end 2 end implementation ? what is the process v do at that stages

[Nkrish]

hi,

In an end to end implementation , these are the various phases in short...

1) Project Preparation : Start of the project

2) Business blueprint : what has to be, developments required etc, requirements are frozen.

3) Realization : Implementation ( usuallly this is the phase where the ABAP developers are required, development etc happens in this stage) , integration testing

4) Final Preparation( pre go live)

5) Go live :

6) maintenance.

Each stage is documented.

If you want know further details :

http://en.wikipedia.org/wiki/SAP_Implementation

Regards,

Narayani

[Former Member]

Hi,

In any impl you have following phases....

1.project prep---here the staffing model project scope and all the req system details etc are gathered with date and time.

2 busines blueprint--here BPD are being created by analysing the current scenario and how sap is to be implemented.In these doc the overall strategy is disclosed(the whole lifecycle for any module)

3.realization and testing--Depending upon the FS the real developements goes here with unit and integration testing.

4.go live -once develop and testing is finished the system goes live or the end user starts working after UAT.

5 support:- post go live and support.

Now a days all the implementation/support/maintenance projects are being monitored and implemented using SAP Solution manager aNW comp.It supports all the five phases of implementation.You can get track of all the information in ur proj using the same and it's mandatory after 2007 onwards.

Check the link,

http://www.sap-img.com/sap-implementation.htm

http://www.thespot4sap.com/Articles/SAPImplementationRisks.asp

You can view ASAP methodology also to understand better.

Please check this links.

http://www.geocities.com/rmtiwari/main.html?http://www.geocities.com/rmtiwari/Resources/Management/A...

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/SVASAP/SVASAP.pdf

Please reward points for the same.

Message was edited by:

Prakhar Saxena

[Former Member]

Implementing a package can be a traumatic affair for both the customer and the vendor. Get it wrong and the vendor may get paid late or have to resort to lawyers to get paid and tarnish their reputation. For the company the new package may not work the way they expected, be late or cost a more than budgeted for and take management will take their eye off running their business.

Recently a client asked me what I would consider to be the five most important things one should consider before embarking on an implementation. This isn't a simple question, although there are many factors to think about after some consideration for me the top five are way ahead of the others.

My top five factors to consider would be:

1. Set up a Project Board,

2. Secure the resources,

3. Complete the GAP Analysis,

4. Have detailed Cut Over Plans,

5. Train the users.

Taking each one in turn:

The Project Board

The correct set up and operation of the Project Board in my view is major factor in the success failure of the project. The Project Board will consist of the stakeholders, key users and the vendor. The Project Board is part of the governance of the project. The Project Board will meet regularly to ensure that the project plans are created and being executed as planned, moves from stage to stage with all the deliverables being signed off is resourced properly.

The Resources

Three types of resources are absolutely necessary -- end users, change team and technicians.

Early involvement by the end users is absolutely necessary, as they will be the ones living with the system for hopefully many years to come. They will want to feel involved in its implementation. Buy in from the end users of the system is absolutely essential if the system is to have a long and stable life in any organisation.

The Change Team will identify the gaps between the package and the business requirements, re-engineer some of the businesses process to cope with the package, train the users to ensure implementation is smooth as possible into the business.

The Technical Team will prepare the systems environment for the package, apply any software fixes from the vendor, implement the software in the best way possible for the organisation set up and tune the software for the particular technical environment.

GAP Analysis

A through gap analysis will identify the gaps between how the business operates ad its needs against what the package can can't do. For each gap there will be one of three outcomes which must be recorded and actioned, GAP must be closed and customised software can be developed close the gap, GAP must be closed but software cannot be written therefore a workaround is required, GAP does not need to be closed.

In simple terms: Gap means small cracks. In SAP world. In information technology, gap analysis is the study of the differences between two different information systems or applications( ex; existing system or legacy system with Client and new is SAP), 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.

Actual gap analysis is time consuming and it plays vital role in blue print stage.

Cut Over Plans

Detailed plans need to be developed for cutting over from the old system(s) to the new. Parallel runs of what will happen over the conversion period using test data, convert and watch for a period after wards to ensure nothing unexpected happens.

Train Users

Well trained users will support and defend the system on site. Unsupportive users will continually undermine the system and eventually it will be replaced. Therefore the more effort you put into helping the users master the system early the better.

<a href="http://en.wikipedia.org/wiki/SAP_Implementation">refer this for end to end implementation in SAP</a>

regards,

srinivas

<b>*reward for useful answers*</b>