01_31-05-2025_FICO_Activate methology, BBP, Types of Projects and different roles

Summary

FICO Team Introduction and Goals

The meeting began with introductions from participants, including Abidunnisa, who leads the FICO team, and others like Priyanka, a CA finalist working as a SAP consultant, and Venkatesh, with 7 years of finance experience pursuing CMA. The group discussed their reasons for attending the FICO sessions, with Priyanka aiming for career growth and Venkatesh seeking to enhance skills. Abidunnisa shared her background, highlighting her 15 years of experience in SAP and her current role as a team lead. The session concluded with a request for additional introductions from other participants.

SAP ERP System Overview

The meeting focused on an introductory session about SAP (System Applications and Products), an enterprise resource planning (ERP) system developed by five former IBM employees in 1972 and released in 2006. Abidunnisa explained that SAP processes business data for enterprises, including financial information, human capital management, material data (from raw materials to finished products), and machinery details. The system, which requires no coding or programming, is used for data processing across various modules such as FI (finance), HR, PP (production planning), and others, and is available on mobile platforms.

SAP Module Integration Overview

The discussion focused on the integration features of SAP modules, where Abidunnisa explained that 20+ modules are interconnected to enable data flow between different functional areas. Venkatesh clarified that integration means linking between modules like FO with CO and material management, while Priyanka demonstrated how automatic posting of entries works through integration, showing how invoices can be processed across different modules. The conversation concluded with an example of how material receipt data flows through different departments, with Chandra confirming that the accounting entry would be handled by the P2 department.

SAP Workflow and Integration Overview

Abidunnisa explained the workflow between the material team and the finance team in SAP, highlighting that journal entries are now posted automatically due to system integration, unlike the previous manual process. She discussed the different types of SAP roles, including consultants, end-users, and support consultants, and used Toyota as an example to illustrate how large companies manage their operations across various sectors using SAP. The session concluded with a discussion on preparing for future opportunities in SAP, emphasizing the importance of understanding different types of projects and roles.

Toyota SAP Implementation Planning

Toyota is planning to implement SAP server to manage their growing data needs, but the system will require extensive configuration and settings specific to their operations. The company lacks an in-house SAP team, so they will need to hire external consultants from companies like IBM, Infosys, or TCS. The implementation process will begin with a kickoff meeting between Toyota's management and the consultant team, followed by gathering business information from various department heads and end users across the Toyota group of companies.

SAP Configuration Documentation Best Practices

The team discussed the importance of documentation in SAP system configurations, emphasizing that it serves as a single source of truth and proof of understanding between end users and consultants. They agreed that documentation should be prepared after gathering business requirements and conducting as-is process analysis, with the understanding that system configurations should initially be tested in a lower environment before moving to production. The team concluded that before making any system changes, they must obtain client approval, as this involves configuring a client's SAP system rather than an IBM internal system.

SAP System Implementation Testing Overview

Abidunnisa explained the testing process for a new SAP system implementation, which includes unit testing by consultants followed by User Acceptance Testing (UAT) or Quality Assurance Testing (QAS) by end users. She described how data migration from existing systems like Tally or Excel would be handled using SAP tools like LDMC and LSMW, and explained the concept of a system landscape with development, quality, and production environments. The process concludes with go-live, where end users begin using the SAP system for daily operations after successful testing and data migration.

Post-Project Support Consultant Roles

The meeting discussed the roles and responsibilities of support consultants after a project goes live. Abidunnisa explained that support consultants provide assistance to end users by troubleshooting issues and handling configuration errors. She clarified that Toyota has an agreement with IBM for consulting services, and after the project completion, they may extend the agreement for support services or hire a new team. The discussion also covered the concept of knowledge transfer from the consultant team to the support consultant team during the hyper care period.

SAP Project Implementation Overview

Abidunnisa explained the different types of SAP projects, focusing on implementation and rollout projects. She outlined the steps involved in these projects, including project preparation, gathering information, configuration, testing, and go-live activities. Abidunnisa emphasized the importance of understanding the SAP Activate methodology and the differences between ECC and S/4HANA systems. She also discussed the role of consultants and end-users in these projects, highlighting the need for clear communication and timely information exchange to ensure project success.

SAP Implementation Project Types Overview

The meeting discussed different types of SAP implementation projects, including implementation, rollout, and upgrade projects. Abidunnisa explained that a rollout involves implementing SAP for additional company codes after an initial implementation, while an upgrade involves updating to a new SAP version. They also covered the concept of support projects, which are ongoing to address issues and provide assistance. The group discussed the importance of understanding the role and project type when working on SAP projects. Abidunnisa outlined the agenda for the next session, which will cover ECC to S/4 system differences, landscape, GUI tutorials, and hands-on practical exercises.

Complete and Continue