Sap Sdlc

SAP Development Life Cycle The Typical SAP Module development has to be maintaining a sequential development formation. For any of the module development someone has to follow the following steps to make the module functional: [pic] †¢ Business Process Blue Printing: This function documents the business processes in the company that we want to implement in the system. In a Business Blueprint for Projects, the manager has to create a project structure in which relevant business scenarios, business processes and process steps are organized in a hierarchical structure. The Manager can also create project documentation and assign it to individual scenarios, processes or process steps. Then assign transactions to each process step, to specify how your business processes should run in the company’s SAP systems. The Business Blueprint is a detailed description of the company business processes and systems requirements. Use The Business Blueprint provides a common strategy of how your business processes are to be mapped into one or more SAP systems. The Business Blueprint documents in detail the scope of business scenarios, business processes, process steps, and the requirements of an SAP solution implementation. Structure A Business Blueprint comprises the following structure elements in a hierarchy: ? Organizational Units ?  Ã‚  Ã‚  Ã‚  Ã‚   Master data ?  Ã‚  Ã‚  Ã‚  Ã‚   Business scenarios ?  Ã‚  Ã‚  Ã‚  Ã‚   Business processes ?  Ã‚  Ã‚  Ã‚  Ã‚   Process steps †¢ GAP Analysis A through gap analysis will identify the gaps between how the business operates its needs against what the package can/can't do. For each gap there will be one of three outcomes which must be recorded and action has taken, 1. GAP must be closed and customized software can be developed 2. GAP must be closed but software cannot be written therefore a workaround is required 3. GAP does not need to be closed. GAP must be closed and customized software can be developed close the gap, GAP must be closed but software cannot be written therefore a workaround is required; GAP does not need to be closed. In simple terms: Gap means small cracks. In SAP world. In information technology, gap analysis is the study of the differences between two different information systems or applications (ex; existing system or legacy system with Client and new is SAP), often for the purpose of determining how to get from one state to a new state. A gap is sometimes spoken of as â€Å"the space between where we are and where we want to be. † Gap analysis is undertaken as a means of bridging that space. Actual gap analysis is time consuming and it plays vital role in blue print stage. †¢ Integration Testing: The purpose of integration testing is to confirm that the company business processes work according to the requirement established in the business blue print phase and the system is ready to go live. To accomplish this we must test every aspect of business. Integration Testing a process, development or configuration within the context of any other functions that the process, development or functionality will touch or integrated. The test should examine all data involved across all modules and any data indirectly affected. A successful test indicates that the processes work as designed and integrate with other functions without causing any problems in any integrated areas. †¢ UAT (User Acceptance Testing): The purpose of this document is to provide a detailed explanation of the concept and approach that will be used for User Acceptance Testing. This document does not include the performance testing approach. The objective of the User Acceptance Test is to ensure that the SAP solution has met our business requirements and to provide users with confidence that the system works correctly and is manageable by them to run our business. User Acceptance Testing is accomplished through the execution of real life scenarios with a representative subsection of end users. To that end, â€Å"Day In the Life Of† scenarios (DILOs) will be performed in a multifaceted computing environment comprised of SAP software, third-party software, legacy applications and various hardware and software components. It is this environment that builds the necessary level of confidence that the solution is complete and will perform in our business. User Acceptance Testing is a role-based dress rehearsal of SAP production including security, change management, and production support. Burning Hand Exercise: It is the practice period where the user to practicing the operation more and more to prepare themselves in live uses. By practicing the operation the user could able to know the difficulties, possible solutions of the difficulties and make themselves furnished for future. †¢ SAP End User Training: SAP User training is the proces s of formally introducing the user community to the business processes as implemented in SAP along with acclimatizing them to the SAP environment. In general this involves identifying the key stakeholders, documenting the business processes and interactively training them. Many projects fail or face serious hiccups in spite of excellent resources from a technical standpoint and superior project management. While the entire team is racing against time to complete the implementation, they forget to ramp-up the major stakeholder in the entire project. Users often come from other ERP backgrounds and are often very ignorant of the SAP environment. Often there is subtle resistance as well. Go Live All of the previously described phases all lead towards this final moment: the go-live. Go-live means to turn on the SAP system for the end-users and to obtain feedback on the solution and to monitor the solution. It is also the moment where product software adoption comes into play. The go live strategy comprises of the following: a) Cut of procedure b) Pre go live check Cut of Procedures: SAP system is configured as per the requirement of the company. The system is read for the client to use. The client now needs to migrate from the old systems to the new SAP System. The migration from the old system to the new system is known as the cut of date. The old system is switched of and the new system is on. The data will be migrated from old system to SAP. The data will henceforth be entered in new system. To have a smooth switch over from the legacy system to the new SAP systems are devised the cut of procedures. Pre go live check: It is ensuring that SAP production system is ready to go live smoothly.