SAP ASAP Methodology Tips

ASAP Methodology (Accelerated SAP) is a standard SAP project preparation and system implementation method developed and updated by consultants who are involved in implementing SAP software products. Listed below are the SAP ASAP Methodology Tips for effective project management during the different phases of implementation.

SAP ASAP Methodology Tips – Project Preparation Phase:

  1. Form an efficient Project Team – The project manager should be accountable for identifying and placing the right candidates who work together towards a common goal and share responsibility for specific outcomes of the project.
  2. Understand the Scope, TP and Contract – Ensure that the stakeholders and team members understand the scope of the project.
  3. Set Project goals – Setting proper goals will help avoid challenges which a project might face with bloating scopes and unruly requirements lists.
  4. Set the expectation of project document standards  Verify company branding and the predefined documentation from customers to incorporate the same with expected quality.
  5. Share Templates – Ensure that the templates are shared to drive the project (Risk tracker, Issues tracker, Action log.. etc)
  6. Identify Stakeholders – Identify the required stakeholders who can influence and support the project to move it to the next level.
  7. Set up the SAP solution manager – Set up the right Solution Manager (SOLMN) to drive the project and fulfill the respective tasks throughout the project lifecycle. This also helps in getting a complete single source of truth while making reporting meaningful.
  8. Set the scope of the Solution manager – Define clearly whether it’s only incident specific or whether it includes change management.
  9. Initiate the SAP project manager plan – This can be done by downloading a template ASAP solution manager.
  10. Identify Risks– Identify and register the possible risks of the scope and monitor them from the initial stage.
  11. Schedule Kick-Off Meetings – Assemble the required stakeholders and dedicated project teams from the customer for the meeting.

SAP ASAP Methodology Tips – Blueprint Phase:

  1. Get the SAP Solution Manager ready – Install the SOLMN during the project preparation phase and keep it ready to use for the blueprint phase.
  2. Set the Scope in the SOLMN – Set the preliminary scope in the SOLMN using the web page wizards so that the SAP consultants can do scope verification exercises.
  3. Verify whether Skills match with the Scope
  4. Verify that Team Selection and Mobilization is complete – Ensure that team members are mobilized on day 1 especially if it’s fixed price and rate.
  5. Complete the Project Management Plan – Try to keep it as close to the original document made on day 1.
  6. Get the IDES system ready – Ensure that the system is up and running from day one for a system walkthrough.
  7. Follow SAP best practices – Based on the Scope, identify the required business functions and activate SAP best practices.
  8. Conduct hands-on workshops –Explain the objective of the project and each ASAP phase to the customer.
  9. Make Workshop Meeting Minutes – Circulate the meeting minutes to the users at the end of each session.
  10. Make Detailed Flowchart Diagrams – Construct flowcharts with roles (who is doing what / how) of the business process so that it makes the user easily understand and sign the BBP.

SAP ASAP Methodology Tips – Realization Phase:

  1. Get the Blueprint signed off – This can be the most difficult part of any phase completion. Training, continuous buy-in and selling are key here.
  2. Have the Developments Scoped and Approved – It is best to kill as many unrealistic developments as possible.
  3. Document Functional Specifications – Have a written specification completed for later use.
  4. Configure Guide Generate vs Solution Manager – Ensure that your Basis team does a proper configuration to make the system work for you.
  5. Update the Project Management Plan – Though it seems less critical, it is important to update it from a compliance and management standpoint.
  6. Complete execution or planning of the Training – Complete the Customer Project Training cycle. If you don’t do this, it implies that you have decided to outsource support post-Go-Live.
  7. regulate Change Management Efforts – Ensure you have effectively employed all Change Management methods and techniques.
  8. Test, Test and Test Some More – It is essential to decide on the testing approach repeatedly since each project will have slightly different requirements.
  9. Review the Project Solution – SAP or other third parties will help validate your final solution and design approach.
  10. Complete the project team evaluation Process – Typically an on-going process, you should formally announce when you start and complete this task.

 SAP ASAP Methodology Tips – Final Preparation Phase: 

  1. Realization of the Phase Document Signed-Off – Similar to the blueprint signoff, training and continuous buy-in and selling are key here.
  2. Complete Developments (FRICE) – Complete all Forms, Reports, Interfaces, Conversions and Enhancements.
  3. Finish the End-User Training – Train the end user and make your life easier. Cut scope before you cut end-user training and then train some more.
  4. Revalidate the business Case  – The SOW based on your initial RFP might change during the project. Re-align your expectations with the requirement.
  5. Update the Project Management Plan –  Update the project management plan from a compliance and management standpoint of view.
  6. Deploy Change Management Globally – The scope and scale of the change management process should swing into high-gear in this phase.
  7. Conduct a Final Project Review – It is an important stage, especially if a large number of developments were necessary.
  8. Prepare a Data Migration Plan – The plan must include action items regarding purchase orders, financial issues, and human resource issues.
  9. Ensure that the Solution Manager is up to date – This should be a minor issue at this point as you would have used it for both the blueprint and realization phases along with all documentation.
  10. Decide on a Parallel Systems Approach – Always have systems which will continue to operate alongside SAP during transitions even if it is difficult to scope out from a manpower perspective.

SAP ASAP methodology Tips – Project Go-Live Phase:

  1. Formally announce that SAP is Live – Ensure that each stakeholder in the company knows about the go-live of the SAP system.
  2. Get Signoff – Get the sign off from the customer on every aspect of the project. Payment does not happen until you get the sign-off.
  3. Closeout project financials – Leave no invoice without pay off.
  4. Value management approach establishment – Continuously monitor the value management project with projected case benefits as SAP doesn’t have inbuilt prediction capabilities.
  5. Close the project management plan – For project prioritizing organizations, it’s critical that all steps of the project are closed out.
  6. Operate Change management on a goal basis – Success comes from effective change management. Post go-live, the customer should take this as part of his responsibility.
  7. Collect lessons learned from the projects – Collect all the lessons learned from the structured projects to ensure effective future projects.
  8. Conduct a final steering committee meeting – It’s important that they know about their role in the project and that the project is live. Moreover, it’s a great way to say thanks and discuss the future steps for all stakeholders.
  9. Prepare a continuous improvement plan – List out the value management approach which should be planned for future implementation phases.
  10. Verify Support from the organization –  Ensure that the SOLMN is already installed and that all support staff members are certified to handle first level support.


To learn more about the ASAP methodology or about our ERP solutions, feel free to contact us or send us an email at

Shahinsha A B

Related Posts
Leave a reply
Captcha Click on image to update the captcha .