Topic Covered -

1. AP Training Course Kickoff and Expectations

2. Introduction to SAP S/4HANA System and ERP Overview

3. HANA Database: Performance and Architecture Explained

4. Types of SAP Projects and Typical Timelines

5. SAP Project Methodology and Planning Phases

6. Detailed Phases of an SAP Implementation Project

7. Activate vs Waterfall: SAP Implementation Methodologies Compared

8. Deployment and Agile Feedback in SAP Projects

9. SAP Testing Types and Real-Time Feedback Strategies

Summary

SAP Training Course Introduction

Agastya led an introductory session for a SAP training class, discussing the structure and expectations for the course. He emphasized the importance of practical experience and understanding of business scenarios, suggesting that participants spend 1-2 hours daily on practice and self-study. Agastya also addressed questions from Dimple about her approach as a non-SAP background participant, advising her to focus on understanding theoretical concepts and applying them in practical scenarios. The session concluded with a brief overview of SAP as an enterprise resource planning system, and Agastya encouraged active participation and note-taking during future classes.

SAP S/4hana System Overview

Agastya explained the concept of SAP as an ERP (Enterprise Resource Planning) system, highlighting its comprehensive solutions for various company departments through integrated modules. He discussed SAP's market leadership and its evolution from earlier versions to S/4HANA, which was introduced in March 2015 as a fourth-generation system built on SAP's own HANA database. Agastya emphasized that S/4HANA offers simplified processes and high-level analytics, with updates released annually since 2019, and recommended using versions that are at least one year old for stability.

SAP HANA Database Performance Overview

Agastya explained the differences between traditional SAP database systems and the new HANA database, focusing on performance improvements. He described how HANA stores data column-wise in RAM rather than sequentially on hard drives, allowing for faster data retrieval. Agastya used simple analogies with Excel and laptop memory to illustrate these concepts, while Atanu asked clarifying questions about the columnar storage structure.

SAP Project Types and Timelines

Agastya explained the different types of SAP projects, including Greenfield (new implementation from scratch), Brownfield (technical upgrade with minimal configuration changes), and Bluefield (technical upgrade with new configurations). He clarified that while Greenfield projects typically involve 8-9 months of work, migration projects usually take 4-5 months, though these timelines can vary. Agastya emphasized that companies don't have to be on non-SAP systems to choose a Greenfield implementation, as some SAP customers also opt for this approach when upgrading from older versions or when they want to redesign their processes and organization structure.

SAP Project Methodology Overview

Agastya led a discussion on SAP project methodologies, explaining key concepts like project preparation, business blueprint, and the different phases of implementation. Participants discussed the importance of understanding business requirements and organizational SOPs during project planning. Agastya emphasized the need for arranging resources, defining project scope, and setting objectives during the preparation phase.

SAP Implementation Project Phases Overview

Agastya explained the phases of an SAP implementation project, starting with business blueprint where current processes are understood and documented for new system design. He then described the realization phase where consultants configure the SAP system and perform custom development based on the business blueprint, followed by final preparation which includes UAT testing, training, and data migration. The project concludes with go-live, typically in the first week of April in India, followed by a three-month hyper care support period.

SAP Implementation Methodology Comparison

Agastya explained the differences between the waterfall model and the Activate methodology in SAP implementation projects. He described how the Activate methodology, with its six phases (Discover, Prepare, Explore, Realize, Deploy, and Run), allows for faster issue resolution compared to the rigid waterfall model. Agastya provided an example from a past project at a FMCG company where a scanning process issue caused a complete transaction blackout for several days, emphasizing the importance of careful documentation and understanding of requirements in the discovery phase.

SAP Deployment and Agile Feedback

Agastya explained the deployment process in SAP, emphasizing the importance of final preparation, testing, and user acceptance. He discussed the differences between the traditional waterfall model and the agile approach, highlighting that in agile, feedback is continuous and issues can be addressed early. Agastya also shared his experience implementing SAP, noting that while the agile approach is not directly applicable to SAP, continuous feedback with business stakeholders can still be incorporated to improve the process.

SAP Testing and Feedback Strategies

Agastya explained the different types of testing used in SAP projects, including unit testing, system integration testing, and UAT. He emphasized the importance of continuous feedback and involving business stakeholders early in the testing process. Agastya also addressed a question from Dimple about handling feedback that may not be applicable, explaining that such cases are rare but can be managed through mutual agreement and proper documentation during the fit-gap analysis phase. The class concluded with Agastya agreeing to provide more specific examples of custom developments using SAP's RICEF (Reports, Interfaces, Conversions, Enhancements, and Forms) framework in future sessions.