ABS-CBN SAP Upgrade Plan v4 - ABS

advertisement
SAP ECC Upgrade
Project Team
Pre-Planning
September 26, 2008
Scope – Upgrade Scenario Evaluation
The Quick Upgrade Analysis evaluates two different scenarios - Technical Upgrade
and Retrofit Upgrade.
New
functionalities
3
Standard
functionalities
2
Limited number
of modifications
1
Start release
SAP ERP 6.0
SAP Releases
As-is
Target
Strategic Business Improvement

Focus on functionality extension and
improvement

Enablement of new and optimized business
processes and scenarios based on new ERP
core functionality
2
Highly modified
environment
SAP Standardization
3
retro-fit Upgrade

Focus on reduction of system complexity

Maximization of SAP standard functionality by
replacing modified objects by standard
functionality
1
Technical Upgrade

Focus on pure technology upgrade

No changes to used standard functionality

Elimination of unused modified objects
Milestone Planning – Upgrade
Month1
Month2
Month3
Month4
Month5
Month6
Month7
week 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
Upgrade
1
Upgrade Assessment
2
Upgrade Planning
3
Hardware Set-up
4
Realization
5
Cut-Over / PRD Migration
6
Go Live and Support
Development Freeze in 4.6c
4w
2 w.
4 w.
Note :
 Hardware set-up can be shortened since HW is ready
4 months
4 w.
Strategy
Prepara
tion
Plannin
g
Realizatio
n
Scope
Final prep.
for
Cutover
Go-Live &
Support
Legend
= new release
= old release
= actual project work
System landscape
= transport route
Detailed Planning for the Upgrade
Process (phases, work packages etc.)
Test Planning, Planning of Training and
Documentation
Perform upgrade for three-tiered
landscape
ECC project
landscape
DB
AS
Unicode ready ECC 6
ABAP Adjustments on Custom objects
and documentation
Functional Testing and documentation
Delta Training
DEV’
ECC
QAS’
4.6C
PRD’
4.6C
PRD
4.6C
PRD
4.6c
Double
maintenance
productive
landscape
DEV
4.6C
Timeline
Z object count
CUSTOM OBJECT COUNT IN SAP PRODUCTION SYSTEM
(z* objects)
Statistics of ABAP Objects
with BDC
ABAP Queries
372
Reports/BDCs/Scripts
645
Function Groups
89
Function Modules
147
Field Exits
7
User Exits
10
IDOC types
45
Function Pools
44
Subroutine Pools
379
Message Classes
16
Rep.Writers/Painters
CATT Procedures
133
2
151
Data Elements
88
Search Helps
13
Tables
Views
Structures
112
7
18
9
69
111
LSMW Projects/Objects
49
Layout Sets (SAPscripts)
31
Smartforms
0
Smart Styles
0
Transactions
357
Includes
147
TOTAL ABAP OBJECTS
Domains
0
Module Pools
Report Groups
Statistics of DDIC Objects
2527
135
TOTAL DDIC OBJECTS
389
Internal count
Strategy – Realization
Preparatio
nPlanning
Realizati
on
Final prep.
for
Cutover
Go-Live &
Support
Legend
= new release
= old release
= actual project work
Project work
System landscape
= transport route
 Adjustments (custom
programs/interfaces/forms..)& functional
tests
Upgrade QAS’
Transport Changes to QAS‘
Integration test (4 weeks)
mySAP ERP
project
landscape
DEV
ECC
QAS
ECC
SAP ROLL OUT
 Config and Customize in DEV ECC?
Double
maintenance
 Simultaneous go-live with cut-over?
Start Blueprinting once DEV-ECC
stabilizes
DEV
4.6C
PRD
4.6C
PRD
4.6c
Strategy – Final Preparation
Preparatio
nPlanning
Realizatio
n
Final
prep.
for
cutover
Go-Live &
Support
Legend
= new release
= old release
= actual project work
Project work
System landscape
= transport route
 2nd Integration test with key
users (2 weeks incl. correction)
 End-user Training
 Preparation of the Production
System Landscape for Upgrade
 Dry Run of Cut-over
 Go/No-Go decision
mySAP ERP
project
landscape
DEV
ECC
QAS
ECC
Double
maintenance
DEV
4.6C
PRD
4.6C
PRD
4.6C
Strategy – Cut-over
Preparatio
nPlanning
Realizatio
n
EXAMPLE
Final prep.
for
Cutover
Go-Live &
Support
Legend
= new release
= old release
= actual project work
Project work
System landscape
= transport route
Upgrade of the Production
System PRD (Downtime)
Support for the Live Date
and the week afterwards
Project Closure
mySAP ERP
project
landscape
DEV
ECC
QAS
ECC
PRD
ECC
DEV
4.6C
QAS
4.6C
PRD
4.6C
Tasks and Responsibilities
Task
Responsible-Primary
ResponsibleSecondary
Basis
Vendor
ABS-CBN Basis Team
(includes Oracle
Migration)
Functional –
adjustment
System Testing
Update OLQR,
Config Rationale
ABAP adjustment
Lead: Angel De Luna
2 weeks (DEV and
QAS)
Estimated No. of Resources
1 Senior Basis
1 Junior Basis
1 week (PROD)
ABS-CBN IT-SAP
Vendor Consultant (Lead 1
month with knowledge
transfer and actual
deliverable)
ABS-CBN IT-SAP
(Lead 1 month with
knowledge transfer and
actual deliverable)
User training
Estimated No. of
Weeks
??
Vendor (staff
augmentation)
3 months
2 FI-CO
2 MM/SD
1 lead (vendor)
Vendor (staff
augmentation)
2 months
??
1 month
7 ABAP
1 lead (vendor)
AR
AP
GL
User Acceptance
Testing
CO
Treasury
Procurement
AMWD
c/o SMOM
PM
Vendor
ABS-CBN IT
Arlan/Bessie
Finance/SMOM
Vendor Selection
Activity
Responsible
Timeline
Preliminary discussion
with vendor including
scope
IT-CSS;IT-SAP; ITBasis;SMOM
Oct 2008
Confidentiality agreement
IT-SAP
ASAP
Vendor Selection Criteria
IT-CSS;IT-SAP; ITBasis;SMOM
2nd week October 2008
Preliminary Proposals
IT-CSS;IT-SAP; ITBasis;SMOM
4th week of October 2008
Review and evaluation of
proposals
IT-CSS;IT-SAP; ITBasis;SMOM
2nd week November 2008
Final recommendation on
selected vendor
IT-CSS;IT-SAP; ITBasis;SMOM
4th week November 2008
Final negotiation
IT-CSS;IT-SAP; ITBasis;SMOM
1st week December 2008
Contract Preparation
IT-CSS;IT-SAP; ITBasis;SMOM
2nd week December 2008
(with NDA – HP; NGL; Kaisa;
Questronix)
Target kick-off: January 2009
End of Presentation
Download