QAG SAP Internal Document

1Operation process flow for SAP projects

Legend Sample docs and path to see is attached in Sample Docs worksheet
Bold Letters - Added wrt SAP Implementation process handbook 2.0 Roles and Responsibility
Blue indicates the work items T TCS
C Client Time frame in each phase is mentioned in case of Medium complexity SAP E2E implementation
SAP Implementation process using ASAP J Joint
Phases

or g
ks 1 4 o n

(P ind ject
(1 B) pri ss

pp oin
an
e e ( ti

U p
ks 2 ion

ks 8 ion
(B lue ine

t
w Z) liza

W u
nt

W ro

su ng
w P) par t

im os Live

ks S) ti
(P re jec
e e ( at

e e ( at

)
P
ee P t a
B us

(F rep l

O
(R ea

P ina
w ) ar
)

w L en
P ro

ks
B

)
R

p o
P

F
ee

(4 (G em
G

on pl t
)

)
0w

)
P
Input 1.Contract 1. Project plan 1. business blueprint docs 1. Data migration plan 1. Support doc 1. Final 1. support plan ( SLA details if
- During contract finalisation type of implementation SAP Vanilla/IS/others
- Type of project (E2E/Upgrade/Rollout/Support
1.Project Plan (UPP) 2. cutover plan for after go live signoff from they are defined)
- Warranty /Support details after go live phase 7. Strategy document for ( Training, Testing, Stds, 3. BPML 3. TMS plan (T) customer 2. Any market regulation details
2. high level System architecture plan Quality, Standards, Risk ) 4. Data Migration plan 4. After go live strategy 3. Support Model required ( n
3. Statement of work (SOW) - 11. Architecture document ( technical and solution 5. UAT plan Tier architecture)
4. Common entry criteria fulfilled (project initiated, env set up, H/w, S/w set up, DDL
cycle)
Management) 6. Master Data 4. Support plan
12. Detail Plan for Business blueprint phase requirement plan
7. Configuration
document
8. Functional and
Technical specification

Key Onetime Onetime Onetime Onetime One time One time One time
1. Conduct Project Startup meeting -Project Charter (T) 1. Prepare detailed plan for current phase - Plan for Blueprint 1. Baseline configuration and 1. Conduct Volume & stress 1. Finalise the support model -Support
Activity 2. Create project Profile - Profile (T) phase Level 2 (T) confirmation (T) test - Test logs (T)
1.Go live (J) 1. Obtain plan document
3. Sign of NDA for Information security with customer - NDA (J) 2. Define business process -Blueprint document -(J) 2. Final configuration and 2. Deliver end user training - Iterative customer 2. Establish help desk operating
6. Customer engagement for project readiness (using checklist) Checklist (C) - conduct 'As-IS' and 'To -be' business process workshop, confirmation - Configuration Training Register (T) 2. Review and feedback - procedure
- Project Go ahead from customer, Infrastructure availability, SAP and other use sandbox client for demo document (T) 3. Set up production system close the open CSS (J) 3. Prepare SPOC for each business
license availability - Identify Fits and Gaps 2.Set up production and QA (J) process - list of SPOC
3. Define Environment (J) - Key data element and key data structure environment (J) 4. Integration testing - test
items - Problem 2. Prepare the 4. Get Client SPOC for each business
Define software, hardware Tools, any third party tool, 3. Define enterprise organization structure (J) - 3. Develop system test cases logs (T) Register (T) project process - Client list of SPOC
4. Conduct Kick off meeting (T) - Plan Org structure workshop, Conduct workshop (use ( inclusive Information 5. Defects resolution - 3. Implement completion Repetitive
5. Build Team (T) Questionnaire), security testing)- System test Defects logs (T) support system report - 5. Accept the problem Ticket and change
7. Establish project procedures - Project procedure and strategy document (J) 4.. Define the user Roles and Responsibility structure - Roles plan (T) 6. Transport from QA to request -Problem / Change register (T)
- identify coding, modeling, data and document standards, define strategy for and authorisation doc (J) 4.Coding and testing of FRICE Production system
(T) Project 6. Prepare Impact analysis and
Testing, Training, Migration, Quality, Transport management system (TMS), 5. Finalise architecture - Architecture document (J) (T) 7. Support user acceptance 4. causal completion recommendation - Impact analysis (T)
Templates needed for documentation -Entities involved, identify core and support process, identify 5. Finalise functional testing - User acceptance sign analysis - report (T) 7. Update / addition of new test scripts -
- Define the data/Scenarios required, Define the guideline, the interfaces specification - Functinal Specs off (J) Causal analysis 3. Release Test scripts (T)
8. Prepare the communication management plan - Communication Management 6.. Design Training plan for end users - training plan for core (T) 8. Data migration - update 8. Causal analysis of the issue - Causal
plan (J) users (L1/L2/L3) (J) 6. Finalse technical Data migration doc (T) (T) resource to analysis (T)
- Steering committee R&R, Project governance, inter group coordination, crisis 7. Identify test scenarios for - Integration, volume and test specification - Technical 9. Go live readiness check - 5. Change MATC 9. Plan the testing plan ( UAT/integration
management testing(VST) , BCP (T) - Test Scenarions specification (T) Checklist (J) management - /Practice - testing/negative testing) -Test plan (T)
9. Receive client supplied products - List of client supplied products (J) 8.. Freezing business scope at L3 level - Business process 7. Establish user role and - Client readiness wrt change register Released 10. Configuration / FRICE changes done
10. Plan for blue print Phase (J) - Plan for blueprint phase ( L1 level plan) (J) Master List (BPML) (J) authorisation (C) Technical/people/process, (T)
- Plan the workshops/orientation required with the users in blueprint phase 9. Finalise BCP plan - BCP Planning document (J) 8. Transport from Golden risk assessment (T) Resource 11.customisation changes done -
11. Install IPMS - IPMS PP1012 (T) 10. Prepare planning for - Planning doc for Training, UAT, client to QA (T) 10. Finalise cutover plan (T) 6. Update project names (T) configuration doc (T)
Iterative Migration, Quality, TMS (T) 9. Final integration test in QA 11 Execute data migration plan -UPP (T) 4. Update 12.Update Functional and technical
13. Prepare project plan - UPP (T) Iterative environment- Test logs (T) 12.Cutover to Production 7. Obtain final quality specs - Func and Tech specs (T)
14. Prepare architechture doc- Technical and solution architechture (T) 11. Prepare high level functional specification and 10.Identify and develop data system 13. Testing (T)
- Define landscape, define the network requirement, define the high level solution technical specification for FRICE migration programs - Data 13. Prepare plan for after go sign off for records (T) 14. Follow change (T)
architecture 12.Define Master data requirements (J) - Master Data Migration document (J) live - Support plan (T) implementation - 5. Complete 15. Customer verification (C)
15. Establish the project estimates - high level schedule (L1 level) and resource requirement doc 11.Prepare UAT training Iterative Final Sign off project wind 16. transport movement ( Data upload
loading (J) 13. update project plan -UPP (T) material - UAT training doc (C) 1. Update Project plan (UPP) (C) up activities done if needed) (T)
16. Prepare high level support strategy for after go live - Support strategy after go 14. Knowledge sharing for TCS team ( inclusive IS training) Iterative
live (J) (T) Finalise test cases of integration (T)
16. Prepare Induction Manual - Induction Manual (T) 15.update the project estimates ( at L1, L2, L3 level)- Project test, VST tests 6. Handover
17. Set up quality Records (T) estimates doc (T) 12.One round of Data upload Q documents
18. Build Risk register and mitigation strategy - Risk Register (T) 16. Identify UAT test scenarios - UAT test cases(C) test (T) (T)
19. Prepare Asset Register for Information Security Management (ISM) -AR (T) 17. Prepare the configuration document - config doc (T) 13.Define cutover strategy and
20. Build ISM Risk Management - RM (J) plan (J)
14.Update the AR and RM
document - AR & RM(T)
15. Update project plan -UPP
(T)
16. Update the Project schedule
(T)
keno
Output 1.Project Plan (UPP) 1. Blueprint doc ( with key data element and key 1. Configuration doc 1. Acceptance sign off 1. Final sign off 1. CSS 1. Support plan doc
2. Project Charter and WON created data scenarios) 2. Data Migration plan 2. Updated project plan 2. Updated 2. PAL 2. SPOC for TCS
3. Project Profile 2. Functional Specification 3. Updated Blueprint 3. User training project plan updated 3. SPOC from Client
4.. Project start up checklist updated 3. Technical specification 4. System test plan attendance list 3. Causal 3. List of 4. Change Register
5.. Project Estimates ( L1 plan and resource loading) 4. BPML ( business process master list) 5. Updated project plan 4. Support doc for after analysis released 5. Problem register
6. Induction Manual 5.. Architecture doc 6. Updated AR and RM go live resources 6. Impact analysis
7. Project Procedure and Strategy document for ( Training, Testing, 6. test scenarios ( integration, BCP, VST) 7. Cutover plan 7. Test plan
Stds, Quality, Standards, Risk ) 7. UAT training plan 8. Tech specs for FRICE 8. Test scripts
8. Plan for Business blueprint phase 8. UAT test cases 9. updated project 9. Configuration doc
9..Communication Management plan 9. Update project charter estimates 10. Func and Tech specs
10.. Support strategy after go live 10. Update project plan 10. UAT training material 11. Help desk
11..NDA ( if applicable) 11.Master Data requirement document 11.Detail Plan for 12. Regular Status report to
12. Architecture document ( technical and solution Management) 12.Training Plan for end users Testing,User acceptance customer
13.Risk Register 13. Updated project estimates Training,Data 13. customer confirmation of the
14.AR 14. Planning document for (Testing,User Migration,Quality,TMS change
15. ISM RM acceptance Training,Data
Migration,Quality,Transport management system
(TMS),
Client Sign QAG SAP Internal Document
Mandatory Mandatory Mandatory Mandatory Mandatory Mandatory Mandatory
offs 1.NDA ( if applicable) 1. Blueprint doc ( with key data element and key 1. Cutover plan 1. UAT 1. Final sign off 1.none 1. Support plan doc
2. Project Charter data scenarios) 2. Data Migration plan Optional Optional Optional 2. Customer confirmation of the
Optional 2. Functional specification 3. Updated Blueprint 1. Cutover planning none CSS change
3. Strategy document for ( Training, Testing, Standards ( data and Optional Optional 2. Support doc for after 3. Help desk OPD
code), Quality, Risk ) 2. Architecture doc 4. Configuration doc go live Optional
4. Architecture document ( technical and solution Management) 3. BPML ( business process master list) 5. Updated AR and RM 4. Change Register
5. Project plan ( L1, L2, L3) 4. Project schedule 6.System test plan 5. Problem register
6. Plan for Business blueprint phase 4. Master Data requirement document 7. updated project 6. Impact analysis
7. Support strategy after go live 5. Technical specification estimates 7. Test plan
Not required Not required 8.Plan for Testing,User 8. Test scripts
8..Project Plan (UPP) 5. Training Plan for end users acceptance Training,Data 9. Configuration doc
9. Project Profile 6.Test scenarios Migration,Quality,TMS 10. Func and Tech specs
10. Work Order 7. Update project charter Not required Not required
11 Project start up checklist updated 8. Update project plan 9. Tech specs for FRICE 12. Regular Status report to
12.Induction Manual 9. UAT test cases ( review to be done by project 10. Updated project plan customer
13.RARM team) (UPP) 2. SPOC for TCS
10. Prepare planning for (Training, UAT, Migration, 11.UAT Training material 3. SPOC from Client
Quality, TMS

Reviews SAP Practice review Internal quality Audit 1. IQA & EQA of 1. SAP Practice review 1.IQA IQA and EQA SAP Practice review
Needed Internal quality Audit SAP Practice review Baseline and final config of cutover plan 2. PMR Related business IP review
Related business IP review 2. IQA & EQA of FRICE 2. SAP practice Review Internal Quality Audit
code of Data Migration plan IQA & EQA Changes
3. TCS review of UAT
specs

Q 1. Architecture document 1. Blueprint doc 1. customised 1.Cut over plan 1. Final sign off 1. Support plan
Document 2. Strategy documents for transport management, UAT, Quality 2. BPML doc configuration details ( cutover strategy is 2. Impact analysis
template 3. Master Data requirement 2. Data Migration and available)
not strategy developed
available 3. UAT Training material

List of Abbreviations
FRICE Forms, Reports, Interface, conversion and Enhancement BPML Business process Master list
QADB Question and answer database ISM Information security Manager
IQA Internal Quality Assurance NDA Non disclosure agreement
EQA External Quality Assurance IMG Implementation manual guide
IS Industry Specific VST Volume and stress testing
TMS Transport management system

Deleted items wrt to SAP process handbook

Identify and integrate dependencies on work items - This is part of . Develop Information Model - Information Model Detail plan of the current Go live is deleted from
Solution architecture document (J) document (J) - Because this is part of phase is replaced by here and added in Go
communication management plan Project estimates update live phase
where Schedule and
estimates are updated

Ensure inter group coordination (T) - This is part of the 8. Conduct PMR EQA (T)
communication management
Conduct training- replaced by Knowledge sharing
in the team
Detail plan of the current phase is replaced by
Project estimates update where Schedule and
estimates are updated