Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Development Methodology: urgent

Former Member
0 Likes
588

what is development methodology in sap development.

4 REPLIES 4
Read only

Former Member
Read only

Former Member
0 Likes
535

Thank you Mahalakshmi. But I think my question is not answered completely.I want an answer to the quetion " what development methodology u follow ". Will the be any name for the methodologies we follow.

Read only

0 Likes
535

ASAP methodology

AcceleratedSAP (i.e. ASAP) methodology/roadmap is a proven, repeatable and successful approach to implement SAP solutions across industries and customer environments. ASAP is widely used for SAP Business Suite (SAP ERP, SAP CRM, SAP SCM, SAP PLM, SAP SRM), SAP xApps, SAP NetWeaver and SAP Solutions for Mobile Business among many other solutions. The methodology covers the necessary project management, the configuration of business processes, testing and training aspects as well as technical implementation activities.

In order to ensure central data access, the ASAP roadmap and tools have become a standard component in SAP Solution Manager (service.sap.com/solutionmanager) - the implementation and operations platform. In addition, ASAP is available for browsing and offline use on Service Market Place. From tool perspective, the SAP Solution Manager implementation function is the successor to the ASAP tools, hence some tools such as the Implementation Assistant, Q&Adb, and the Master Lists are replaced by Solution Manager Implementation Function.

ASAP Roadmap

Use

The ASAP Roadmap provides the methodology for implementing and continuously optimizing

your SAP software. It divides the implementation process into five phases and offers detailed

Project Plans to assist you (in Microsoft Project format). The documentation stored at each level

of the Roadmap tree structure contains recommendations on implementing your SAP software

and links to helpful tools and accelerators.

Purpose

When you install the Implementation Assistant you can choose from several Roadmap types and

flavors. You can select one of the following flavors:

• R/3 - Implementation and Continuous Improvement

• APO - Advanced Planner & Optimizer

• BW - Business Information Warehouse

• B2B - Business to Business

• CRM - Customer Relationship Management

Features

Implementation of SAP software covers the following phases:

1. Project Preparation

In this phase you plan your project and lay the foundations for successful implementation. It

is at this stage that you make the strategic decisions crucial to your project:

− Define your project goals and objectives

− Clarify the scope of your implementation

− Define your project schedule, budget plan, and implementation sequence

− Establish the project organization and relevant committees and assign resources

2. Business Blueprint

In this phase you create a blueprint, which documents your enterprise’s requirements and

establishes how your business processes and organizational structure are to be represented

in SAP software. You also refine the original project goals and objectives and revise the

overall project schedule in this phase.

3. Realization

In this phase, you configure the requirements contained in the Business Blueprint. Baseline

configuration (major scope) is followed by final configuration (remaining scope), which can

consist of up to four cycles. Other key focal areas of this phase are conducting integration

tests and drawing up end user documentation.

4. Final Preparation

In this phase you complete your preparations, including testing, end user training, system

management, and cutover activities. You also need to resolve all open issues in this phase.

At this stage you need to ensure that all the prerequisites for your system to go live have

been fulfilled.

5. Go Live & Support

In this phase you move from a pre-production environment to the live system. The most

important elements include setting up production support, monitoring system transactions,

and optimizing overall system performance.

After your system has gone live, you can use a separate Roadmap with six work

packages, in order to optimize your R/3 System continuously.

These phases are the main milestones for implementing SAP software. Each phase has:

• Work packages, which consist of activities, for which project teams are responsible.

• Activities, which consist of tasks, which are processed by one or more team members.

• Tasks, which are carried out by a project team member. You can also access the How-to

sections and accelerators at this level.

Also check this AcceleratedSAP document.

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

Regards,

Maha

Read only

Former Member
0 Likes
535

Development Methodology in SAP is called as ASAP Methodology:

It has the following procedure:

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.

Reward points if useful.