Development Methodology

[vidyadhar2k2]

Hi Friends and Experts,

Can any one please let me know what is Development methodology used in ABAP.

[Former Member]

Hi,

Check this PDF document.

http://hosteddocs.ittoolbox.com/CM021805.pdf

Also check this too.

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a32662d9-0b01-0010-a588-ccd23adf...

Regards,

Lalit

• Reward if useful

[Former Member]

Hi,

Some more details :

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,

Lalit

[Former Member]

hi,

ASAP metholodgy is useually recommonded for developement projects

ASAP stands for accelarated SAP. The phases of ASAP are

project preparation

business blueprint

Realization

final preparation

go-live & support

regards,

pavan

[Former Member]

Hi gopthrough the following links:

http://training.saptechies.com/category/sap-asap-documentation/

http://searchsap.techtarget.com/sDefinition/0,,sid21_gci871489,00.html

http://www.sapfans.com/sapfans/asap/be_01_e.htm

ASAP: Accelerated Systems Application and Products in Data Processing

ASAP methodoligy means nothing but standard process for implementation of SAP, It consists of 5 phases.

1. Project preperation - consists of identifying team members and developing strategy as how to go.

2. Business Blue print - consists of identifying the client current process, reqeirement and how SAP provides solution.

Consists of detailed documentaion

3. Realization -The purpose of this phase is to implement all the business and process requirements based on the

Business Blueprint.

4 Final Preparation - The purpose of this phase is to complete testing, end-user training,

5 Go Live and Support

All the functinal consultatns need good rapo with Abapers. right from uploading of legacy data, devoloping customised reports, BDC's, Forms etc, here functinal consultatns need to give guidence as to get the requried data for reports and all.. like the table name, fields etc

All implementation projects have the the following phases:

Scoping - What is to be implemented i.e. which submodules are to be implemented some clients may not require credit management for example. Look at the project scope document carefully it will tell you what SAP sub-modules in SAP you should be prepared for. Usually the sales people along with project manager do it.

As is - Here you understand the existing business processes of the client . Your BPOcollect all the ISO-documentation (if client is ISO certified), reports and forms at this stage and you analyse how and when the reports/forms are generated, where the data is coming from. You also do a Level -2 training for your BPO so he is made aware of all the required transactions in SAP.

Once this is over BPO can start learning with the consultants help more about SAP. This is crucial because if you miss out any transactions the BPO may forget about some of his Business processes which may come up later. It is a good practice to ask the BPO to make flow charts to explain business processes.

To-Be - Parallely you map these processes to SAP. Processes that you are not sure of as to whether they are present in SAP or not you try to do a configuration of those processes, and along with the BPO(Business process owner he is the clients employee who knows about the clients business processes probably a middle management guy, ther can more than one), BPO involvement is required as he may be able to tell you his requirements better. Once you do the business modelling you

will also be made aware of the gaps between as-is and to-be , here decisons have to be made as to wether a ABAP development/system modification is required or not and so on. Involve the BPO as much as possible and document everything it is good practice do not be lazy about it.

Business blueprint: Here the as-is and to-be and gap analysis is explained. This is the document that you will be using to do your configuration in the realization phase.

Realization phase: Here you do the configuration in the development server (there are three clients -development,quality, production). You also decide on the master data format, so that BPO can go collect the master data. You also gove ABAP specifications for forms, reports etc, system modifications etc. Unit testing: Your BPOs and a few key users sit down and test your configuration in your module only. It is good to test the BDCs that you need for uploading data at this stage so you have more realistic data and your BDCs are tested.

Integration testing:

Once all modules unit testing is over then the configuration is trasported to the Quality server, where testing for all the modules is done by BPOs and end user, this is to check if any problems are there in integration between various modules. Once all is okay from the QA server config is transported to the production server.

Go live preparation

Data uploading: The collected master data is checked and the uploaded into production server(sever and client I have used interchangeably). Now you are ready for go live i.e. users can now use the production server.

Reward if useful.

[Former Member]

***********Please reward points ,if found useful

Hi,

ASAP: Accelerated Systems Application and Products in Data Processing

ASAP methodoligy means nothing but standard process for implementation of SAP, It consists of 5 phases.

1. Project preperation - consists of identifying team members and developing strategy as how to go.

2. Business Blue print - consists of identifying the client current process, reqeirement and how SAP provides solution.

Consists of detailed documentaion

3. Realization -The purpose of this phase is to implement all the business and process requirements based on the

Business Blueprint.

4 Final Preparation - The purpose of this phase is to complete testing, end-user training,

5 Go Live and Support

All the functinal consultatns need good rapo with Abapers. right from uploading of legacy data, devoloping customised reports, BDC's, Forms etc, here functinal consultatns need to give guidence as to get the requried data for reports and all.. like the table name, fields etc

All implementation projects have the the following phases:

Scoping - What is to be implemented i.e. which submodules are to be implemented some clients may not require credit management for example. Look at the project scope document carefully it will tell you what SAP sub-modules in SAP you should be prepared for. Usually the sales people along with project manager do it.

As is - Here you understand the existing business processes of the client . Your BPOcollect all the ISO-documentation (if client is ISO certified), reports and forms at this stage and you analyse how and when the reports/forms are generated, where the data is coming from. You also do a Level -2 training for your BPO so he is made aware of all the required transactions in SAP.

Once this is over BPO can start learning with the consultants help more about SAP. This is crucial because if you miss out any transactions the BPO may forget about some of his Business processes which may come up later. It is a good practice to ask the BPO to make flow charts to explain business processes.

To-Be - Parallely you map these processes to SAP. Processes that you are not sure of as to whether they are present in SAP or not you try to do a configuration of those processes, and along with the BPO(Business process owner he is the clients employee who knows about the clients business processes probably a middle management guy, ther can more than one), BPO involvement is required as he may be able to tell you his requirements better. Once you do the business modelling you

will also be made aware of the gaps between as-is and to-be , here decisons have to be made as to wether a ABAP development/system modification is required or not and so on. Involve the BPO as much as possible and document everything it is good practice do not be lazy about it.

Business blueprint: Here the as-is and to-be and gap analysis is explained. This is the document that you will be using to do your configuration in the realization phase.

Realization phase: Here you do the configuration in the development server (there are three clients -development,quality, production). You also decide on the master data format, so that BPO can go collect the master data. You also gove ABAP specifications for forms, reports etc, system modifications etc. Unit testing: Your BPOs and a few key users sit down and test your configuration in your module only. It is good to test the BDCs that you need for uploading data at this stage so you have more realistic data and your BDCs are tested.

Integration testing:

Once all modules unit testing is over then the configuration is trasported to the Quality server, where testing for all the modules is done by BPOs and end user, this is to check if any problems are there in integration between various modules. Once all is okay from the QA server config is transported to the production server.

Go live preparation

Data uploading: The collected master data is checked and the uploaded into production server(sever and client I have used interchangeably). Now you are ready for go live i.e. users can now use the production server.

With Regards,

BVS

[Former Member]

SAP Development Methodology is also called as 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]

Hi,

Pls reward the helpful answers. This would encourage the ppl taking out time and helping the ppl needing help.

Just a Suggestion!!

Regards,

Lalit

[Former Member]

Hi,

Check my post from this link...It will be useful for u.

Regards,

Maha