Project Preparation: We conducted training on SAP & Module overview We installed IDES server & Solution Manager We prepared system Landscape We prepared Training Strategy i.e. Duration of the Project We decided the overall Teams & their Roles We decided the Project Scope i.e. how many Modules shall be used in SAP R/3 system We identified the Tools for Testing & Data Migration We conducted Project Kick-off meeting AS-IS documentation (plan for BBP) Business Blue Print (BBP): We defined TO-BE process We identified GAP’s We mapped Organization Structure We documented BBP & uploaded in Solution Manager We conducted Steering Committee meeting on Project Status We established Development Environment We prepared Functional Specification Template i.e. RICEFW objects AS-IS Study: Documentation of Client Business Requirements TO-BE Process: Client Business Requirements can be Configured in SAP or Not GAP: Client Business Requirements can’t be Configured or Customized in SAP (Permanent GAP) Client Business Requirements can’t be Configured But it can be Customized (Standard GAP) Business Blue Print: Comparison study between AS-IS & TO-BE Process Realization: We configured SAP system based on TO-BE process
Project Preparation: We conducted training on SAP & Module
overview We installed IDES server & Solution Manager We
prepared system Landscape We prepared Training Strategy i.e.
Duration of the Project We decided the overall Teams & their
Roles We decided the Project Scope i.e. how many Modules shall be
used in SAP R/3 system We identified the Tools for Testing &
Data Migration We conducted Project Kick-off meeting AS-IS
documentation (plan for BBP)Business Blue Print (BBP): We defined
TO-BE process We identified GAPs We mapped Organization Structure
We documented BBP & uploaded in Solution Manager We conducted
Steering Committee meeting on Project Status We established
Development Environment We prepared Functional Specification
Template i.e. RICEFW objectsAS-IS Study: Documentation of Client
Business RequirementsTO-BE Process: Client Business Requirements
can be Configured in SAP or NotGAP: Client Business Requirements
cant be Configured or Customized in SAP (Permanent GAP) Client
Business Requirements cant be Configured But it can be Customized
(Standard GAP)Business Blue Print: Comparison study between AS-IS
& TO-BE ProcessRealization: We configured SAP system based on
TO-BE process We prepared Configuration & Customization
documents and maintained in Solman We connected Development &
Quality servers with Solman We configured Base Line Configuration
i.e. without Enhancements We prepared ABAP Development objects
(RICEFW) Identified & Developed Data Migration programmes We
Configured Final Configuration i.e. set up all Client Business
Requirements and Confirm that are properly met in SAP system We set
up User Roles & Authorization We developed documentation for
End-User TrainingFinal Preparation: We transported the completed
Configuration & Customization to the Production Environment We
migrated the Master Data & Open Transactional Data into SAP
system We Delivered End-User Training We done Integration Testing
We done UAT We set up Production Environment We done Data Migration
We done Cut-Over activities GO-Live readinessData Migration: Master
Data is migrated from Legacy system to QA EnvironmentCut-Over
Activities: Activities can be stopped for time beingGO-Live:
Perform transactions in the Production systemPost Implementation
Support: We provided Support for Locking-Period We reviewed Open
Issues & ResolvedProject Wind-Up:
