‘ea, 741 PM ASAP METHODOLOGY IN SAP ASAP METHODOLOGY IN SAP. 26 September 2020 | ASAP Methodology, SAP Basic Concepts ASAP methodology is a standard SAP project preparation and system implementation method. In simple words we can say ASAP methodology is used in implementing SAP for client. ASAP stands for accelerated SAP. ASAP methodology consists of guidelines to implement SAP, that is step by step implementing of SAP. ASAP Methodology consists 5 Phases 1. Project Preparation 2. Business Blue Print (BBP) 3. Realization 4. Final Preparation 5. GorLive & Support 2. Business x) Care 5, Go-Live & Blue Print Cenietl erie) Rien ey as eerie 1. Project Preparation Phase:- In project preparation phase the management from the company responsible for implementing SAP and management from client will have meetings to finalize the scope of project and set ASAP goals. There are multiple activities falls under Project Preparation Phase: a. User Licenses: - Any client if they want to implement SAP they need to purchase user licenses from SAP. Based on number of end user's client need to decide on how many user licenses to be purchased from SAP. b. Landscape: A landscape is an arrangement of servers. Any client if they want to implement SAP they need to purchase servers. SAP Suggest to go for 3 Servers: i, Development Server => Development Server are used to configure the client business process into SAP. Development server are mainly used by consultants. Quality Server => Quality Server are used mainly for testing. Quality server will be used by consultant and core user. il, Production Server => Its live server where end user will do day to day transaction in SAP. Production server is mainly used by end users, Consultant does not have access to production server. Note: Core User here we are referring to the employee of the company who has good experience & exposure in client business process. c. Infrastructure:- Infrastructure include below aspects: i. No of system required ii, Server Environment: - ili VPN connectivity (Virtual private Network) 2. Business Blue Print Phase SAP has defined this business blueprint phase to help extract all the necessary information about your client business that is necessary for implementation. tips:ifsapfundamentals.com/sap-basic-conceptstiasap-metnodology-n-sap 18118123, 7:41 PM [ASAP METHODOLOGY IN SAP Below activities falls under blueprint phase: a. Requirement Gathering: Understanding the client business process and their requirements. b. Prepare BBP document and sign-off: - After completion of requirement gathering, we need to prepare BBP document. c. Prepare GAP analysis document: While preparing the BBP document whenever we find GAP i. for client business process, if there is no solution in standard SAP then we call it as a GAP. We will prepare GAP analysis document. Gap analysis document consist of Clear description of client process, which is a GAP in SAP. GAP. analysis document also contain alternate/custom solutions and details of the solution ‘As mentioned above in BBP phase we prepare two documents: - i, BBP document. ii. GAP analysis document. Note: SAP consultant will be involved from business blue print phase. 3. Realization Phase Realization: - Configuring the client business process into SAP. In this phase SAP consultants login into development server, to configure the client business process into SAP. We have two types of configurations:- a. Base Line configuration => It is the configuration for which, we don't depend on other module consultant (itis a configuration which is specific to one module). b. Final configuration (Integration between Modules) => itis the configuration for which we need to depend on other module consultants (MM, PP, Fl). Post configuration testing comes into picture, Testing is classified into two categories i. Unit testing => It is the testing which is specific to one module and no need to depend on other module consultants, ii, Integration testing => Its the testing for which we need to depend on other module consultants. Note: Before testing we need to prepare test case document or test scenario document. Based on this test case we will do unit and integration testing After completion of testing, we prepare user manual document. User Manual document: -Itis a guideline to end users, this document consist of step by step process of creating master data and transaction data along with the screen shots. After preparing user manual document, we will give it to core user. Configuration document: - This document consists of the entire configurations made for that particular client along with the screenshots. Configuration document will be used for KT (knowledge Transfer) purpose. This document will be given to core users. Functional Specification document (FS):- We prepare FS whenever we require the help of ABAPER. 4, Final Preparation Phase The final preparation includes below list of activities: i) Training to core users: - We give training to core user. After that core user will give training to their end User. ii) UAT Sign-off:- After training we will ask core user to test the scenarios and confirm, Core user has to test all the scenarios; if everything is fine, he will give UAT sign-off (User acceptance test). Throughout the implementation project we take two sign-off "s from core user. {1st is BBP sign-off 2nd is UAT sign-off ii) Quality to production: - After getting UAT sign-off we transport all the requests(configurations) from quality to production Server. iv) Cutover activities: - Uploading of master data and open transactions data from legacy to SAP(Legacy means Non-SAP) Consultant role in cutover activities: tips:ifsapfundamentals.comfsap-basic-conceptsitiasap-methodology-n-sap 28118123, 7:41 PM [ASAP METHODOLOGY IN SAP a) Consultants will ist out what master data and what open transaction data should be uploaded from legacy to SAP Master data consist:- Customer master, Material master, Pricing master, Open transaction data: - Open Order (The order which created but yet not delivered or pending) v) Culover Strategy: - Its the planning for uploading data from legacy to SAP. During this strategy we decide when exactly to upload the data from legacy to SAP, Whenever we plan to upload the data from legacy to SAP, ‘we request the client to stop the business transactions, The reason is to avoid data inconsistency. vi) Cutover Period: - Generally we take 2 days to upload the data from legacy to SAP. The 2 days period is called cutover period. After cutover period we go to the next phase of ASAP methodology that is GO-LIVE & Support. 5. GO-LIVE & SUPPORT PHASE Go-Live: - Handing over SAP to client, from that date onwards users will start entering day to day transaction in SAP. After implementation we provide 3 months of post-production support. tips:ifsapfundamentals.com/sap-basic-conceptstiasap-metnodology-n-sap