Scribd
Upload
52 views1 page

ASAP Methodology: Business Blueprint: Here The As-Is and To-Be and Gap Analysis Is Explained. This Is The Document That

The ASAP methodology has four phases: 1) The business blueprint phase outlines the current and desired future states and identifies gaps. This document is used to guide configuration. 2) In the realization phase, configuration is done on a development server and master data formats are decided. ABAP specifications are also developed. 3) Unit testing involves key users testing the configuration in individual modules. 4) Integration testing transports the full configuration to a quality server where all modules are tested together before going live on the production server.

Uploaded by

amitkele
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
52 views1 page

ASAP Methodology: Business Blueprint: Here The As-Is and To-Be and Gap Analysis Is Explained. This Is The Document That

The ASAP methodology has four phases: 1) The business blueprint phase outlines the current and desired future states and identifies gaps. This document is used to guide configuration. 2) In the realization phase, configuration is done on a development server and master data formats are decided. ABAP specifications are also developed. 3) Unit testing involves key users testing the configuration in individual modules. 4) Integration testing transports the full configuration to a quality server where all modules are tested together before going live on the production server.

Uploaded by

amitkele
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 1

ASAP Methodology

ASAP: Accelerated Systems Application and Products in Data Processing


All implementation projects have the following phases:
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.

You might also like