implementation and support

[Former Member]

hi

what is the diff between implementation project and support?

haaaaaappy pongal

kanny

[Former Member]

hi....

iam waiting......

haappy pongal

kanny

[Former Member]

ABAP Development, Implementation, and Support

The ABAP Developer will be responsible for the design, coding, testing, implementation, and support of SAP ABAP programming. This person will provide a solid understanding of the ABAP Workbench, including design, coding, testing, implementation, and support of ABAP-related tools. The Lead ABAP Developer will also provide strong expertise in the following ABAP tool sets: ABAP List Processing, including reporting, query tools, logical databases, list design, and control level processing; ABAP transaction processing, including screen objects and controls; SAPscript / SmartForms / Form Design; ABAP user exits; IDOC technology; and ABAP interface programming to and from other systems, including support and maintenance of the IM/3 tool.

The Lead ABAP Developer will work in conjunction with Business Analysts and Project Leaders to define needs, and to write technical and functional specifications. This person will guide and mentor other ABAP Developers, provide level 2 support, participate in unit and integration testing, act as a technical liaison, and coordinate ABAP-related issues during SAP release / version upgrades

http://help.sap.com/saphelp_sm40/helpdata/en/ba/38c93a37c59122e10000000a114084/content.htm

Regards.

[Former Member]

We can divide the SAP projects into three categories. They are

1) SAP Implementation Projects

2) SAP Support Projects

3) SAP Migration Projects

1) SAP Implementation Projects

In this type of projects, Customers are moving towards SAP software. Previously they might be using some

other software.

2) SAP Support Projects

Once SAP project is implemented, it should be supported by the consultants in day-to-day business. In

Support projects, the support team helps the customer in day-to-day business.

3) SAP Migration Projects

As we see, SAP is continuously upgrading the R/3 software. Customers are moving from the older versions

to new versions. When the customer decides to new version, it is called SAP Migration Projects.

Now-a-days many customers are migrating from older versions like 4.5 or 4.6b, 4.6c to ECC 5.0 or ECC 6.0

versions.

Reward points if useful.

[Former Member]

hi sravan,

thanks for reply....

can you tell me what are the diff stages while releasing an object , if we fail to release it then what happens and what may be the reasons may cause for it?

haaaappy pongal

kanny

[Former Member]

diff stages while releasing an object

ASAP Methodology:

Project Preparation:

The first step in ASAP is Project Preparation. In this step the Functional Consultant will analyse the business process and define the system for SAP and will give the time line for the project. The Manpower required and the budgets are also considered in this step.

Blue Print Preparation:

This is second step in ASAP Methodology. In this step the Project Preparation scenarios are finalised. A out line of the Project is given in this step.

Realisation:

In this step actual development is taken place. The ABAPer is responsible for this step.

Testing:

In this step the development done by the abaper is being tested. This is the area where the Unit Test Document is prepared (i.e. Positive Testing and Negative Testing).

GO live and Support:

This is the final stage where the project is running in the live environment. In this step the bugs if any that are found in the go live procedure are fixed and the project will be considered as support project.

Rewards if useful.

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

refer this for end to end implementation in SAP

reward point if helpful.