sap fico implementation project phase pd
- 2. 1 | P a g e CONTENTS Introduction……………………………………………………………………………………………………………2 PHASE 1: Project Preparation…………………………………………………………………………………3 PHASE 2: Business Blueprint (BBP)…………………………………………………………………………4 PHASE 3: Realization Phase…………………………………………………………………………………….6 PHASE 4: Final Preparation……………………………………………………………………………………..8 PHASE 5: GO-Live & Support………………………………………………………………………………….10
- 3. 2 | P a g e III
- 4. 3 | P a g e BUSINESS CLIENT ERP SOLN. PROVIDER PHASE 1: PROJECT PREPERATION List of activities to be carried out to make Implementation Sucessful High level Whitepaper statement of the project The ERP Solution provider must carry out the implementation in Phases based on Delivery to Cost Delivery to Time Delivery to Quality ACTIVITIES Scope of Project Convey the vision of the program which should satisfy all the stakeholders STAKEHOHER BUSINESS CLIENT ERP TEAM Each phase activities / deliverables with its review process Start date and end date for each activity Resources to be assigned to each activity Roles and responsibilities of teams from Client and ERP Team Each phase progress (Planned, Actual, Delay, Deviation %) Activities during the period Activities planned for the next week Risk status with owner who is responsible to mitigate these risks Team deployed at site (Role with no. of resources in each role) ECC ENVIRONMENT SAP R/3 Business Navigator SAP S/4 HANA Auditing Partners Training Partner Testing Partner Accelerated SAP (ASAP) Victory ASAP SUCCESS ASAP Standalone module testing System Integration testing (SIT) User Acceptance Test (UAT) Performance testing Train the Trainer mode. Training hand outs / manuals how to use concepts for all modules Deliverables of each module( MM,PFI,PP etc) Specifying, developing and testing of reports enhancements, forms and workflows SAP technical cutover plan. SAP Project Management Develop a program resource plan based on resource requirements to complete program activities Finalization of negotiation Signing of the Agreement by both parties Duly signed on all pages Z / Y Configuration start 1. Project Name and Description 2. Project Vision & Mission 3. Project Logo 4. Project Management Structure 5. Project Plan 6. Budget and completion acceptance 7. Project Success Indicators 8. Project Scope 13. Training Methodology 12. Testing Standard & Strategy 15. Resource planning & Allocating 14. Project Deliverables 10. Project Implementation Strategy 16. Sign Off Charter 11. SAP Configuration Standard 9. Partners Scope of Work
- 5. 4 | P a g e BUSINESS CLIENT ERP SOLN. PROVIDER PHASE 2 : Business Blueprint (BBP) KICK-OFF Meeting: Core users of Business, SAP Consultants, Project Managers from both team will be present Company will describe, give presentation their current business process Linking current processes to the organization s strategy Analyzing the effectiveness of each process Understanding existing automated solutions No Laptops yet, all paper work RICEFW FS Documents Enhancements & developments * Analyze As-Is and To-Be Processes * Organization Structure Definition * GAP Analysis * Create Blueprint documents * FS documents Purpose: BBP provides a common strategy of how your business processes are to be mapped into one or more SAP systems. ACTIVITIES Current business processes defined for the daily activities. * Translate into SAP Terminology * Optimizing the existent flows within the organization. DOCS IN BBP Below docs are prepared by taking into consideration Current business processes , any pain points etc Business Process Doc (BPD) : Ref for process, e.g.: P2P cycle of business, flowchart etc. Key Structure Doc (KDS) : Ref for Configuration, e.g.: Configurations that need to performed for the business WHAT is FIT/GAP Analysis? 1. Prior to GAP, available SAP best fit method in-built enhancement option, such as: exit, function modules, etc.is recommended 2. The difference between AS-IS and TO-BE processes is called GAP. 3. Whatever the standard system does not support but can be customized through ABAP development (RICEFW) . 4. Certain functionalities not available in standard and can't be customized (FS Docs). 5. For future requirements are filled in the forms of enhancement for key additional dependent processes. 6. In BBP for respective SAP solution we maintain the GAP list and list of ABAP development activities. 7. Interface to third party system if required. BILLVARAJ G BILLVARAJ G BILLVARAJ G
- 6. 5 | P a g e Functional Cousultants will gather desired functionality of a particulate area i.e. to be precise, a transaction in SAP terminology Functional Cousultants explains, The purpose of this report Logic required to achieve end result Tables & fields to be considered Inputs & Outputs to be displayed ABAPer will acess & implements accordingly Contains customised solution details along with screenshots Functional Specification (FS) Docs: Doccument to Technical consultant so that he understands business requirement since he is not aware of what the business looking for. Situations which calls for FS to be written : 1. Enhancements /modifications. If business requires some special procedure. 2. Reports, Client's customized reports. 3. Interface, EDI interface involves ALE/IDOC. When you hear the term RICEFW - you should think: customization / changes to std SAP. It is applicable to all modules R – Reports includes classic and interactive reports, customized reports in ABAP I-Interfaces to other SAP and Third Part Tools – EDI, ALE-Idocs , developed to automate the postings in SAP for external activities C – Conversion, BDC Extraction of legacy data from legacy systems, Transformation of data into loadable LSMW format and Loading the data into SAP. This activity is important and need accuracy. E – Enhancement – Use Exits, Customer Exits, BADI s etc. are written in order to enhance SAP system functionality F – Forms (Output) includes Smart Forms, Development of layouts for Invoices, Account statements, Delivery notes etc. W-workflow, Development of specific approval flow logic in SAP RICEFW Functional Consultants FS Docs Technical Consultants (ABAPer s) TTD Doc BILLVARAJ G BILLVARAJ G BILLVARAJ G
- 7. 6 | P a g e BUSINESS CLIENT ERP SOLN. PROVIDER PHASE 3 : Realization Phase Transport request (TR) : Acts as carrier of configuration settings from one system to another or one client under the same Landscape Before moving the data from Development server to Quality server every TR must be released using T-code SE09 , once released it cannot be changed TR from one landscape to another for example: Development to Quality server, as a functional consultant we should request BASIS team consultant to release TR, (source system, source client, transport number) To release TR tasks under TR should be released first T-code: STMS, to move from one server system another * Server configuration is carried out by the BASIS security team. * BASIS team moves all configurations from one server to another for testing purposes. * Testing is carried out by the core team. In this phase, consultants start configuring as per BBP business scenario. IMPORTANT ACTIVITIES PROCESS FLOW 1. Configuration by Functional Consultants 2. ABAP Customization by Technical Consultants 3. Different types of testing by both consultants 4. THREE servers are created basically one server for the Functional Consultants one for the Technical Consultants and the last server is used for the Testing 5. Customization TR s created by Functional Consultants 6. Workbench bench TR s created by Technical Consultants For e.g. 500 & 510 server of consultants are tested in 520 server Configuring Plant in 500 server all data should be moved into 520 server for test. Before that we should log in to 520 client import(500, source client) to destination through TR s. 7. Log into destination client server, pull using T-code : SCC1 SANDBOX SERVER DEVELOPMENT SERVER QUALITY SERVER PRODUCTION SERVER TR TR Transport Request (TR) Configuring the object in application layer & saving in respective TR number . Prepare confirmation document along with screenshot. Perform testing on configured objects. Preparation of documents for testing along with screenshot. Arrange demo session for end users or core users for approval of configured object. After approval they are eligible to transfer from Development server to Quality server. BILLVARAJ G BILLVARAJ G
- 8. 7 | P a g e SANDBOX SERVER Practice IDES server used to configure & test all business scenario before moving into Development server . Any Transport request (TR) created will not be done from Sandbox to Development server . DEVELOPMENT SERVER All Functional Consultants get involved. Consultants perform configuration & customization settings for the defined business scenarios . Unit Testing (T-code based testing) Positive testing and negative testing TR must be released from Unit testing before moving onto Qualty server. Before releasing any corrections can be made in same TR s/. Once released we cannot change TR. We should create new TR or use existing TR no. to make changes. Each TR contains tasks which contains the details of complete . QUALITY SERVER Both Functional Consultant & Core Users are involved 1. System integration testing (Module based testing) Scenarios based on testing integration of modules MM-FI,MM- ,MM-SD etc. Testing is done by the testing team (some companies will have in house testing team consultants, need to provide data templates to them, testing team reports to functional consultants) Will perform positive and negative testing with documentation. Core users will review & provide approval for scenarios. Any changes needed, again need for Development server TR construction changes and testing approval. For system integration testing reference document is the BBP document . 2. User Acceptance Test (UAT) Critical testing phase, UAT will be performed by business users in their respective modules under support of functional consultants . UAT also contains positive and negative testing if you it is successful that particular tier will be eligible to move from Quality to Production server. Here IDES system is provided initially to core users . In UAT stage core user receives system will be trained under Trainer A trainer (TAT) method. On successful user approval, TR to the basis consultant in order to move from quality to production server in sequential order. PRODUCTION SERVER Live server in which business is running i.e. core users are working in SAP system. here again BASIS team consultants are responsible for TRs No configuration changes will be allowed in production server as functional consultants will havr only display access. No creation and No change access for business transactions If functional consultants require access to production server they need to take Firefighting access (FFID) from business owners. Once all TRs and moved into production server then only configuration data is ready for business . Master data & open transaction data are loaded in Final Preparation phase i.e. cut over activities. BILLVARAJ G BILLVARAJ G
- 9. 8 | P a g e * Mock Go-Live and end-user training * Data migration and cut over strategy * Documentation clearly specifying the details of location wise business process owners with primary contacts. * A decision and date for GO-Live is agreed with the client * Serves to resolve all critical open issues * The actual switch to GO-Live happens at the end of this phase. BUSINESS CLIENT ERP SOLN. PROVIDER PHASE 4 : Final Preperation Purpose: To finalize the readiness to go-live. The key change happening with respect to the traditional procedure is to go for Mock Go-Live plan. Final Preparation Activities 1. Uploading Master Data & Open Transaction data into SAP system Upload using standard tools of SAP: LSMW(for ECC 6.0) BAPI (for S/4 HANA) etc. LSMW : Define the mapping and rules for the changeover and LSMW then uses this definition to generate an ABAP data transfer program. BAPI uses exel data format to upload data Data Migration team is responsible to upload data BILLVARAJ G BILLVARAJ G 2. Cutover Planning & Strategies Accounting balances and final transactions from legacy system are transferred to the production system The transfer of balances takes place before GO-Live , in what is called as cut over period 3. Authorization matrix In SAP systems, users are typically assigned the appropriate roles / profiles by the BASIS Security team Transactions SU01: Creates and maintains users SU02: Creates and maintains profiles PFCG: Profile Generator SU53: Displays LAST authorization failure ST01: Traces keystrokes SU03: Lists objects and classes SM04: Monitors user activity SE16: can be used to download SAP security tables. SU10: Adds or deletes a profile to all users General Program Management End User Training Cutover Management Business Simulation End User Practice in the Sysytem Infrastructure Finalization Data Migration Pre-GO-Live Operations Authorization Matrix Final Cutover and Controlled Process GO-Live Completion Check & Prepare for next Step
- 10. 9 | P a g e BILLVARAJ G BILLVARAJ G 4. End User Training Consultants are responsible for document preparation & end user training. Train-a-Trainer (TAT), a popular method for conducting training. Success of SAP implementation depends upon the end user successful training and acceptance. The training program comprises of business process flow details, various integration points and their dependency, etc. The end-user documentation should consist all the details such as: integration points, validation of details and types of errors with root cause analysis report. 5. Audit Closure SAP has provided a very powerful framework in the standard ERP package for conducting Audits, evaluating them and taking corrective actions. In Audit there are NO Primary or Secondary Books of Account – only data stored in Tables Opening and Closing Trial Balances As per SAP need to match up with audited figures The audit plan consists of all audits planned for a particular period of time. Performed by audit partner companies such as PwC, Delloite etc. There are many critical activities that must be completed in a short period of time to transfer operations from the legacy system to the new SAP Business system including Import of open transactions from the legacy system Entering opening balances from the legacy balance sheet Reconciliation of accounting between the legacy system and the new system Closing down legacy system and starting production on SAP Business system. BILLVARAJ G
- 11. 10 | P a g e * Monitoring of new system in production * Design and publication of war room strategy as per business requirement. * Resolution of outstanding issues * Handover to customer, partner support organization and to SAP support * Evaluation of support team performance and plan corrective action on bi-weekly basis. BUSINESS CLIENT ERP SOLN. PROVIDER PHASE 5 : GO-Live & Support Purpose: Purpose: To move from a project-oriented, pre-production environment to live production operation. Project Closing Activities BILLVARAJ G BILLVARAJ G General Program Management Organizational Alignment System Support Business Support Project Closing Once the new susyem has been running with no critical issues for a designated period of time you should hand over the system to the Business owners. Post Go-Live – every user looks upon the implementation team to avail some extra support and guidance which further leads to delay in response. All the bugs that are raised in the tool, should be primarily evaluated by the location process owners, if they fail to resolve, then it should be re directed to the support team. In any case, it is mandatory for the support team to have correct information with them, which comprises of process owner details tagged up with their evaluation remarks. Closure of the Project: In this sign-off, the business owners will acknowledge & accept the system in production. The final milestone is met when a Review & Optimization conference takes place to review how the project went. This meeting also provides an opportunity to plan further phase or additional enhancements.