ASAP Methodology

[Former Member]

Hello All,

Just want to know steps involved in ASAP Methodology.

I mean the sub tasks in each of the following process

1.Project preparation

2.Business blue print

3.Realization

4.Final preparation

5.Go live support

Any one can help me with good document.

Thanks,

Srihari.G

[nitin_patoliya · Accepted solution]

1.Project preparation : Defining the scope of at Project level, identification of Core team member, No. Modules to be implemented at time , No of system in scope i.e ECC, CRM SRM , SCM, PLM etc.., Project Milestone date, ( Mostly Client Top Managment has to take decesion based on service provide help .)

2.Business blue print

From here onwards real role of SAP consultants starts, Understand Current sStage Business Process ( CSBP) with the help of Core team members. Perpare AS it is Document,

Map that Current Business Process In SAP & Pepare document for the Future stage of Business Process (FSBP ) or ToBe Document & Identify the Gaps..... explain Core team the std. SAP capabilities for that Gaps and development Possibilities... Finally we have to Frezz the FSBP Document and take sign off from customer.... This Business doc. is also called as Business Blue Print Document, in future any confusion happens between Service Provider's own team or with core member this document will be taken as reference...

3.Realization

From here onwards real development starts in SAP,Creation Of Base config, Creation of Module specific Master data, As in Our case we have to start after FI/CO, PP, master data at least up to plant is available, After main config is over, checking of the same with Unit Testing , Preliminary Integration testing, If sstisfied with it release teh all Transport to Quality, Core team does Integration testing in QA Environment, Once Integration testing is over in QA, Relalisation phase is over, this dependes on project ot project.. Release Timeninngs of Transport ot QA & Prod is also vary from Projecto Project. It depends on how mcuch busines wants control on it. Here we also provides tranings to coreuser / enduser.

4.Final preparation

This real cut-over activies we can say, As in most of the time, Client don't wated to Upload his Porjects in new system, so, in PS we have least work realted to LSMW / BDC, If it is there we have to migrate Legacy projects with appropriate structure and cost in SAP PS. At this point we have to take help of FI/Co for the uploading cost, Depending upon modules this activities varies, Most of the work is on FI/ CO, SD, MM, PP side. realted ot open orders...

5.Go live support

This is very critical for the business ,as they are migrating from their legacity sys. to SAP. Based on how whole projects we have implmented we gets Issues, we have to provide at most support during this period to Clients, In this period, we come know, if we have not throughly tested application in Integration testing..

Whole process may vary from customer to customer up to some extent,

Regards

Nitin P.

[Former Member]

ASAP methodology is developed over tradiational way of implementations

Please note the subtask for SAP implementation project (end to end) which is also known as phase wise methodology

1.Project preparation

1. Project plan stating the objectives to be acheived with project start and end date

2. Availability of All infrastructre , Sowftware,adminstrative requireements

3. Basics of business which client is into and initial kick offs and communication/training

2.Business blue print

It is combination of AS is study of the client's business process and then reformed in to Standard SAP terminology , is known as the business was running like this then future it will be As per BBP as per Standard SAP practice. at this stage , no of business process client is into is defined clerly and then sample data is addressed. This phase end might be considered as start of configaration in DEV server as applicable (this may be treated as R&D/Design phase)

3.Realization

In realization the developed scenaries as per BBP are tested in co-ordination with client.

The tatality intigeration test is also conducted to see the impacts of the business processes on other

processes in the intigeration cycle. The final integration cycle is done on Quality server. (this stage can be treated as configuration and verification phase)

4.Final preparation

As the earlier phases are over the Final Basis,H/W, data preperation and cut over process is called in this phase. This phase/process is actual putting the production server into liver environement from testing environment. All master data & transition data is uploaded and system is made on for all users.

5.Go live support

Actual effectiveness of all above process depends on the list & quality of queris arised when server is in live stage.

Due to this methodology a pre defined structre of phase wise completation of project can be observed.

Regards,

Sameer