Embed Size (px)
DESCRIPTION
MIS
Citation preview
Our Journey to SAP ERP 6.0
S.RAMASAMYTeam MANTHANIndian Oil Corporation Ltd23rd July 2009
2
Our Journey to SAP ERP 6.0
Indian Oil OverviewIndian Oil Overview
ERP 6.0 UpgradeERP 6.0 Upgrade
Sequence and StepsSequence and Steps
StrategiesStrategies
Risk ManagementRisk Management
Key Take AwaysKey Take Aways
Con
tent
sC
onte
nts
Feedback from 4.6C customers who upgradedto ERP 6.0
Project duration in weeks*
Business Downtime in hours*
* 10% of outer values were cut off to provide a representative benchmark for your planning, please seedistribution of values (upper part of the grapghic) for minimum/maximum values© SAP 2008 / Transition & Upgrade to ERP 6.0 / Page 3
IOC19 weeks
IOC22:25 hrs
IndianOil Brands
Refineries
IndianOil’s Refinery at Barauni
Figures in MMTPA
Installed capacity (IOC)- 47.35
Ongoing Expansions - 4.50
Proposed Refinery - 15.00
Subsidiaries - 12.85
Along with subsidiaries, owns 60.20 MMTPA (40.4%) of domestic refining capacity
IndianOil Group owns 10 out of 19 refineries in the country
As on 1.1.2009
Haldia6.0
Panipat12.0
Paradip15.0
Koyali13.7
Mathura8.0 Barauni
6.0
CPCL/CBDU10.5
BRPL2.35
Guwahati1.0
Digboi0.65
3.0
1.5
Refineries
By the end of XI Plan, IndianOil Group’s refining capacity to reach 81.40 MMTPA
Pipelines
Single Point Mooring at Vadinar
Marketing
Reaching the icy heights of Leh
Regional Offices : 4State Offices : 17Divisional Offices : 66Indane Area Offices : 35
Patna
Delhi
Kolkata
Mumbai
Chennai
Jaipur
Bengaluru
Kochi
BhubaneswarBhopal
Ahmedabad
Guwahati
Chandigarh
Lucknow
Secunderabad
Marketing Offices
NOIDA
As on 1.1.2009
Marketing Infrastructure
Over 34,600 marketing touch points (55.4 % of Industry)
Petrol/Diesel Outlets18,005 (47.9%)(KSKs – 2,386)
Petrol/Diesel Outlets18,005 (47.9%)(KSKs – 2,386)
LPGDistributorships5,000 (53.4%)
LPGDistributorships5,000 (53.4%)
Bulk ConsumerPumps7,290 (88.5%)
Bulk ConsumerPumps7,290 (88.5%)
LPG Bottling Plants89 (49.2%)
LPG Bottling Plants89 (49.2%)
SKO/LDODealerships3,963(59.8%)
SKO/LDODealerships3,963(59.8%)
Terminals/Depots166 (48.3%)
Terminals/Depots166 (48.3%)
Aviation FuelStations101 (64.7%)
Aviation FuelStations101 (64.7%)
As on 1.1.2009(Figures in brackets indicate % share in the Industry)
Indian Oil – Total IT Map
BusinessBusiness
Business
Dem
and
Production
Supp
lSu
pply
DemandPlanning
PipelineSchedule
ShippingSchedule
CorporateIntegrated Planning
DCS + InstrumentationReal Time Database Management System (RTDBMS)
RefineryOperationsMonitoring
ProcessOptimizers
Data Reconciliationand Yield A/c
(DRYA) Advanced Process Controllers (APC)
BlendOptimizers
OM&S / InventoryOptimization
RefinerySchedule
Primary DistributionSchedule
Secondary DistributionSchedule
CrudeSelection
RefineryPlanning
DistributionPlanning
Purchase MaterialsManagement
ProductionManagement
FinancialManagement
Pricing Invoicing
Payment AccountingHumanResources
PlantMaintenance
PayrollQualityControlERP (SAP)ERP (SAP)
Supply Chain ManagementSupply Chain Management
SolutionsSolutions
Line of Business ApplicationsLine of Business Applications
IndianOil – Total IT Map
BusinessBusiness
Business
Dem
and
Dem
and
ProductionProduction
Supp
lySu
pply
DemandPlng
PLSchdl
ShippgSchdl
Corporate Int.Planning
InstrumentationReal Time Database Management System (RTDBMS)
Refy OpsMonitoring
ProcessOpt
Data Recon& Yield A/c
BlendOptmzr
OM&S / InvOpt
RefySchdl
Primary Dist.Schedule
Secondary Dist.Schedule
CrudeSelection
RefineryPlanning
DistributionPlanning
Purchase MtlsMgmt
ProdnMgmt
FinMgmt Pricing Invoicing
PaymentAccounting
HR PlantMaint InterFaces
QualityContrl
As on 31st Mar 2006
SAP Roll Out
720
As on 01-July-09
OIL – Today
Market Share - %
IOC, 49.7%
BPCL, 21.3%
Other Pvt,1.0%
RIL, 7.7%
HPCL, 19.1%
Other PSU,1.2%
INDUSTRY IndianOil
REFININGCAPACITY
178 MMTPA 60.2MMTPA
No. OFREFINERIES
20 10
Refining Capacities - MMTPA
IOC, 60.20
BPCL, 22.50
ONGC, 9.80
HPCL, 13.00RIL, 62.00
ESSAR, 10.50
INDUSTRY IndianOil +Associates
SALES, MMT 124.6 62.0
SHARE AMONGPSUs
54.7 %
Mega Masters
Type Nos.
Company codes 52Equipments 72,230Storage locations 29,479Products 8,291Users 8000Materials 7,80,728Customers 1,57,952
Vendors 2,89,585
Mega Numbers
DocumentType 2004-05 2008-09
FI Documents 2,19,28,929 3,37,78,337Controldocuments 18,97,662 37,73,034
Sales Orders 51,50,303 77,71,546BillingDocuments 50,18,896 74,13,972
Purchaseorders 1,82,052 2,25,948
MaterialDocuments 1,05,37,062 1,57,97,827
SAP HARDWARE LANDSCAPE
7513 Router
100 TX
APPL
HP StorageXP-51212 TBRawSpace
HP TapeLibrary
ESL 9595
7 noAppl.servers
3 CPU6 GB
B/UPServer4 CPU6 GB
DB/CI/SB
2XCISCO 4507 Switch
HP 1x18 CPU 875 MHz24 GB RAM
& 1x12 CPU 750 MHz 16 GB RAMSuper dome
HP StorageXP-51212 TBRaw
Space
2X64 Port McDataDirector SAN Switch
WAN(IP)
WAN(IP)
StorageXP-1024
57 TBRaw Space
Standby3 CPU6 GB
HP 1 no. 18 CPU(875 MHz)
24 GB RAM & 1x12CPU 16GB RAM
Super dome
Appl.servers
2 no. HP Rp76408 CPU 24 GB
+ 7 no RP54053 CPU 6 GB
2XCISCO 6509 switch
4 X 2 MBPS Leased Lines
New Dev/QA10 CPU
40 GB RAM
HP TapeLibrary712e
2X140 BrocadeDirector SAN Switch
DB CI
Private ClusterHeartbeat LAN
Public Network 2 – ServerPublic Network 1– User LAN
Apps
2X140 BrocadeDirector SAN Switch
2XCISCO 6509Switch
7513 Router
MMF Link over 100 FX
HP 17 CPU 1.6 GHz160 GB RAM Super dome
VirtualTape
Library
Appl. Servers8 Nos.
(3 CPU 6 GB)+ 7 Nos. Blades
(2 QC CPU 16GB)
B/UPServer
10 CPU40 GB
Test/Dev8CPU
24 GB RAM
HP StorageXP-12000
62 TBRaw Space
Upgrade12 CPU
16 GB RAM
Corporate BusinessTechnology Center, Gurgaon
Corporate Near RecoverySite, Gurgaon
Corporate BusinessContinuity Center, Jaipur
SMF Link
ERP Snapshot
1 If No. of Code Pages in old system > 1 then the Unicode Conversion MUST be done IMMEDIATELY after upgrade.
Long-term Foundation
Newly announced 5-year release cyclewith enhancement packagesMajor cornerstone in your overall ITstrategyERP upgrade decisionis important
Most Popular Processes*
New G/LEmployee Self ServicesManager Self ServicesAdministering Employee HR dataCredit Management
Upgrade Value*
87% met or exceeded ROI objectives*Performance impact company-specificMain drivers: DSO reduction, staffproductivity increase, TCO reductionStrategic value mainly perceived onflexibility and compliance
Upgrade Drivers* (in %)
6
9
19
23
23
Technical infrastructure
Process re-design
Continuous compliance
Lower system cost
Additional functionality
* ASUG survey: 55 companies* Ramp-up feedback from >200 projects
* ASUG survey: 163 companies
Our Journey……..SAP R/3 4.6C to SAP ERP 6.0 +EHP 3
Tech
nolo
gyA
pplic
atio
n
Architecture
Steps towards ECC 6.0
Pre Upgarde Scenario: SAP 4.6 C with IS Oil – Components in IOCL
Pre Upgarde Scenario: SAP 4.6 C with IS Oil – Current Landscape in IOCL
Upgrade Scope – Technical
Upgrade Scope - Functional
Upgrade Pre-requisites
Upgrade Steps – Overview
Upgrade Activity – Sequence and Steps
Upgrade Activity - Adjustment of ABAP Dictionary Objects [SPDD]
Client Strategy
Disaster Recovery Approach
Downtime Strategy
Interfaces Strategy
Risks and Risk Management
Hardware Inventory –
HCM and Solution Manager Approach
Key Differences Between R/3 and SAP ERP
Client/Server ArchitectureR/3 BasisTransactional userData-centricFunctional modulesProcess efficiency
Enterprise Services ArchitectureSAP NetWeaverBusiness UserInformation-centricAdaptable industry processesAnalysis, decisions and actions
SAP ERP 6.0
SAP NetWeaver 2004s
Java Components
XI Content
EP Content
Java WebApplications
AdditionalComponents
BILLER DIRECT 6.0
LSO (CP) 600
SAP XSS 6.0
XECO 5.0
XI Content forApplications
ELSTER 2.0
Business Packages
ABAPComponents
SAP ECC
Add Ons ABAP included in installation SAP ECCSEM 600
LSO (FE) 600
ST – PI
SAP-HR 600
SAP-APPL 600
SAP AP 7.0
IS-UT 600
IS-PS-CA 600
IS-OIL 600
IS-M 600
IS-H 600
IS-CWM 600
INSURANCE 600
FINBASIS 600
E-Recruiting 6.0
FI-CAX 600
FI-CA 600
ES-DFPS 600
ECC-DIMP 600
EA-RETAIL 600
EA-PS 600
EA-IPPE 400
EA-HR 600
EA-GLTRADE 600
EA-FINSERV 600
EA-APPL 600
Add Ons ABAP
WFMCORE 2.0
SAP CATALOG 2.0
cPROJECT SUITE 4.0
SEM 600
LSO (FE) 600
FINBASIS 600
E-Recruiting 6.0
BI Content
BI Content 7.0
SAP SRM
SAP SRM 5.5 Server
Front End
cProject ECLViewer 5.1.2
SAP Easy DocumentManagement 6.0
OpenPS for MS Project2.02
LSO (AE) 600
SEM Front-endComponents
SAP GUI 6.20/6.40
BI/BW Front-endComponents
LSO (OP) 600
SAP SolutionManagerSoftware components of
an SAP ECC 6.0 systemafter an technical upgrade
1
Industry extensions that havebeen previously used as
Add-ons in the previous SAPR/3 system are automaticallyactivated through the upgrade
by the Switch Framework.
2
2
1ECC Components
Upgrade to SAP ECC 6.0 including SAPenhancement package 3 possible from..
472471464402
SAP IS-M 4.6C4.6B4.5B4.0B
SAP R/3
3.0B
SAP IS-EC
471463461
SAP IS-U/FERC
4.6C4.6B4.5B4.1B
SAP JVA
2.2B/2.7B/4.6C2.2B/2.7B/4.6B2.2B/2.7B/4.5B
SAP EH&S
2.00
SAP LEARNING SOLUTION
4.724.714.644.614.51
FS-CD
SAP INSURANCE
4.724.714.64
FS-CM
4.724.714.64
FS-CS
4.724.63B
SAP PATIENT MANAGEMENT
4.6C12.0B1.0B
SAP IS-MP
3.0B2.0B
SAP IS-AD
4.61
SAP IS-HT
5.0
SAP ECC DIMP
4.71
SAP DIMP4.6C2
SAP DI
4.724.6C4.6B4.0B
SAP IS-OIL
4.6C4.6B
SAP IS-MINE
4.724.714.64
SAP FI-CA472471464461
SAP IS-T
2.11.0
SAP PLM RECIPE MANAGEMENT
4.634.614.03
SAP BANKING
2.0
SAP CFM
4.624.614.02
SAP IS-PS-FM3.002.05
SAP VADM
4.724.714.64
SAP PUBLIC SECTOR PSCD
4.724.714.64
SAP IS-HER-CM
Industry add-ons integrated intoSAP ECC 6.0 (see SAP Note 838003)
Non industry add-ons integrated intoSAP ECC 6.0 (see SAP Note 838002)
472471464461
SAP IS-U/CCS
4.72
SAP WASTE AND RECYCLING
4.624.614.52
SAP HR-PS
SAP ERP 6.0 + EHP 3SAP XECO
SAP XSSSAP SEM
EHP 3SAP ECC 6.0
Target
2.0
SAP IS-CWM
47X20047X110
SAP R/3 ENTERPRISE
4.6C
SAP PLM ADDON
4.6C
SAP PH-ELR
SAP ERP 2004
5.0
SAP ECC
The System Switch Upgrade Technology- ABAP
Mature Upgrade Technologysince SAP Basis 6.10!
System Switch Upgrade
Key Take Aways
Provides helpful possibilities to minimize downtime:Integration of Support Packages & Patches, Add-ons andEnhancement Packages into shadow tables during the uptime!!!Conversion of large tables with the Incremental Data Conversion(ICNV) during uptime!!!
Switch Principle
Data
GeneralCustomer Data Customizing
Domains
Reports
Tables
Views Dynpros
DocumentationModules
Function Modules
Data Elements Messages
Repository
Consistency of data& “automatic” Dataconversion
Save CustomerObjects
Allow Adjustment of“conflicting” Objects(SPDD/SPAU)
NewRepository
The Repository Switch Principle – Step byStep 1/2
46CApplication Data
Repository
1
System before Upgrade
46CApplication Data
Repository Repository ~
700
„Shadow tables“
New
tp
3System after PARMVNT_SHD
46CApplication Data
Repository Repository ~
700
tp
New
4System during DIFFEXP
46CApplication Data
Repository Repository ~
700
2
System during EU_IMPORT
R3load
The Repository Switch Principle – Step byStep 2/2
46CApplication Data
Repository Repository ~
700New
5
System during SWITCH: drop
46CApplication Data
Repository
700Application Data
7System during PARCONV:
conversion; alter table
Repository
700Application Data
8
System after PARCONV
46CApplication Data
700New
6
System during SWITCH: rename
Repository ~Repository
Up- and Downtime: The Timing DiagramU
ptim
eD
ownt
ime
Prepare Upgrade
Inst. Prod. DowntimeDowntime-minimized
Resourced-minimized
Bac
kup
NewRelease
Shad
ow In
stan
ce(o
n ta
rget
rele
ase)
Upgradepost
Imp.
Bac
kup
Stop of Production(strategy-dep.)
Bac
kup
Downtime-minimized
ICN
V
Impo
rt o
fSu
bstit
utio
n Se
tSu
ppor
t Pac
k’s
Act
ivat
ion
Dis
trib
utio
n
EhP’
s
Mod
ifica
tion
Adju
stm
ents
Add
-Ons
Upgrade
Prod. DowntimeResourced-minimized
Binding SP’s, EhP’s and Add-onsdoes not impact significantly the
downtime!
Upgrade Strategies
Downtime-minimizedTemporary SAP AS is used inparallel to central instanceMore resources are needed(CPU/ Memory)
Resourced-minimizedTemporary SAP AS is used,when central instance is downNo additional resources needed
same Upgrade with 'Ressource Minimized' method
0
5
10
15
20
0-2
4-6
8-10
12-14
16-18
20-22
24-26
28-30
32-34
36-38
40-42
44-46
48-50
52-54
Hours
Cus
tom
ers
in %
Avg.~18downtime-
minimizedresource-minimized
DOWNTIME
EU_IMPORT
ACTDIST...
EU_IMP0
START_SHDI
STOP_SHDIMODPROF_TSHD_IMP
XCNVPARCONVTABIMXPRA MODPROF_P
PRD SHD
"Downtime minimized" method
0
10
20
30
40
50
0-2
4-6
8-10
12-14
16-18
20-22
24-26
28-30
32-34
36-38
40-42
44-46
48-50
52-54
Hours
Cus
tom
ers in
%
Avg.~8
Production downtime during upgrade
What are the elements of production downtime?Upgrade technical runtime (SAPup) – not all of this is production downtime!Post-upgrade transports & manual adjustmentsBusiness validation & acceptance testingPre- and post-upgrade system backupsBusiness ramp-down & ramp-up
up
down
up
down
SAPup:PREPARE
&repository
import
ramp-down
SAPup: conversion,XPRAS, etc.
Basis
ramp-up
backup
transports& manual
tasks
businessvalidation
tests
Functional/business Operations
go/no-go decisionbackup
Overview of Factors Affecting Upgrade ToolRuntime and Downtime
Runtime /Downtimedepending
on
Hard diskconfiguration
Number ofdata structureconversions
Database
Number ofmodifications
Number ofclients
Productiveapplications/Add-Ons or
industrysolutions
Number ofinstalled
languages
Upgradestrategy andreaction time
Hardware /operatingsystem
Factors Influencing Downtime
As each system is highly individual regarding it‘s configuration and application data.A forecast of runtime and downtime is only possible when analyzing results of a testupgrade with representative set of data !
Key Take Aways
Key Decision Factors
Type StrategySystem
LandscapeLanguage
Considerations
TECHNICAL
FUNCTIONAL
STRATEGIC
DOWNTIME MIN
RESOURCE MIN
SATELLITE SYS
ALL SYS
UNICODE
NO UNICODE
Database &OS
DB ONLY
OS ONLY
DB & OS
NO DB or OS Upgrade
DECISION FACTORS
Recommended Upgrade Paths for UnicodeConversion
Yes
No
Do youcurrently
use MDMP?
SAP R/3 4.7 orhigher ?
SAP R/3 4.7 orhigher ?
SAP R/34.6b
or lower
SAP ERP 6.0unicode
Unicode conversion before or after the upgrade orCombined Upgrade & Unicode Conversion
Yes
No
Yes
No
>90%of customers
DirectUpgrade to
SAP ERP 6.0
SAP R/34.6c
SAP ERP 6.0unicodeUpgrade, directly followed by
Unicode Conversion
CombinedUpgrade &
UnicodeConversion
Unicodeconversionbeforeupgrade
SAP R/34.7 orhigher
Convert Upgrade SAP ERP 6.0unicode
SAP R/34.7 orhigher
TwinUpgrade &
UnicodeConversion
Upgrade, directly followed byUnicode Conversion
Upgrade SAP ERP 6.0non-
unicode
ConvertSAP R/34.6C orlower
SAP ERP 6.0unicode
Also possible to do a Combined Upgrade & Unicode conversion
Pre Upgrade Scenario :SAP 4.6C with IS Oil Components
Comp. ID Release Level Highest SP Short Description SP Type
SAP_BASIS 46C 44 SAPKB46C44 SAP Basis Component Basis Support Pkg.
SAP_ABA 46C 44 SAPKA46C44 Cross-Application Component Appl. Interface SP
SAP_APPL 46C 33 SAPKH46C33 Logistics and Accounting R/3 Support Package
SAP_HR 46C 56 SAPKE46C56 Human Resources R/3 HR Support Pkg.
CIN 40A 3 SAPKIPNG03 Country_Version_India Add-on Support Pkg.
IS-OIL 46C 48 SAPKI4C048 R/3_Add-On_IS-OIL_Upgrade_46C_SR2 Add-on Support Pkg.
PI 2004_1_46C 1 SAPKIPZI41 PI 2004_1_46C : Add-On Delta Upgrade Add-on Support Pkg.
ST-A/PI 01G_R3_46C 0 - Application Servicetools for R/3 46C Add-on Support Pkg.
ST-PI 2005_1_46C 3 SAPKITLQD3 SAP Solution Tools Plug-In Add-on Support Pkg.
Pre Upgrade Scenario :SAP 4.6C with IS-OIL : Landscape
Landscape Details DEV QAS PRD
Operating System HPUX IA6411.23 HPUX IA6411.23 HPUX IA6411.23Cluster DB/CI
Number of CPUs 3 3 22
RAM Size 6 GB 6 GB 24
SAP Kernel Release 46D, PL: 2364, BIT:64
46D, PL: 2364, BIT:64
46D, PL: 2364, BIT:64
SPAM Level 48 44 44
Database Software ORACLE ORACLE ORACLE
Database Version 9.2.0.5 9.2.0.5 9.2.0.5
Database size in GB 214 5 TB
Free DB storage in GB
Used DB Storage in GB
Total Application Servers None None None
MDMP (Y/N) No No No
Clients 12
System upgraded in past? (Y/N) Yes Yes Yes
JAVA Deployment required after upgrade? No No No
System accessed from multiple countries?(Y/N)
No No No
Some Key Performance Indicators
CPUProcessing times of business transactions ortasksCost factor: Number and processing power ofservers
Disk sizeDisk I/O
Data that resides on the databaseFile read and write activity to storageCost factors
– Backup/recovery depends on size of database– Storage capacity
Memory
Allocated to a user or background processGarbage collection, acceleration, planningcapabilities, buffers, cachesCost factor: Physical memory slots
Front-endNetwork
Load
Transferred amount of dataNetwork time and roundtripsCost factor: Leasing bandwidth
Monitor Current Resource Utilization …
There are numerous tools and reports available to monitor the current utilization
Available standard SAP monitorsDisk Analysis DB02, DB monitor of vendor
(DB Performance Tables & Indexes)CPU Analysis ST06, ST03N, STAD, ST03G
(Workload Analysis, Statistical Records, Global System Workload Analysis)User Analysis ST07, STAD, ST03G
(Application Monitor, Statistical Records)Memory Analysis SM04, STAD, GCLOG
(User List, Statistical Records)Front-End Network Load STAD, ST03N, ST03G, httplog
(Statistical Records, Workload Analysis)
Hardware Inventory
SIZING CALCULATION ON ACCOUNT OFUPGRADE TO ECC 6.0
SNO DETAILS CPU MEMORY DISK
A BASE(Current 4.6C) 100% 100% 100%B *Upgrade 4.6C ECC 6.0 30% 55% 25%C Sub Total=A*(1+B) 130% 155% 125%D Addl. load for BW (on C) 10% 10% 10%E Sub Total=C*(1+D) 143% 171% 138%F Growth for Year - 1 15% 15% 15%G Growth for Year - 2 15% 15% 15%H Sub Total=E*(1+F)*(1+G) 189% 259% 209%I Contingency 15% 15% 15%J Total = H*(1+I) 217% 259% 209%
* As recommended by SAP
CPU Power & Memory at CDC, DR1 & BCCPrior to Upgrade
CDC DR1 BCC
DB(SAPS) 11000 7336 6900
Application(SAPS)
27730(20825 + 6905)
6905 13670
DB Memory(GB) 24 16 16
ApplicationMemory (GB) 126 30 58
CPU Power & Memory at CDC, DR1 & BCCPost Upgrade
CDC DR1 BCC
DB(SAPS) 40000 11000 11000
Application(SAPS)
60600(41600+19000) 19000 13670
DB Memory(GB) 160 24 24
ApplicationMemory (GB) 272(176+96) 96 58
Considerations for upgrade/new procurement
OPTION – 1Upgrade the existing Hardware of R/3 by adding latest generation CPU and RAM and buynew Hardware for new applications.
OPTION – 2Procure new hardware for R/3 and new applications and use existing hardware for DRSolutions/application requirement
Hardware Platform & Vendor
SrlNo. Application OS Vendor
1. SAP ERP - DB/CI, Backupservers
HPUX HP
2. Tape Library, VTL, SANSwitch
HP
3. a) BW-EP DB/CI serversb) SAP ERP, BW, EP –
Application servers
Linux HP/IBM/DELL
4. LAN switch for new Serverroom
Partners of Cisco
Pre Upgrade Scenario :SAP 4.6C with IS-OIL : Landscape
Landscape Details DEV QAS PRD
Operating System HPUX IA6411.23 HPUX IA6411.23 HPUX IA6411.23Cluster DB/CI
Number of CPUs 3 3 22
RAM Size 6 GB 6 GB 24
SAP Kernel Release 46D, PL: 2364, BIT:64
46D, PL: 2364, BIT:64
46D, PL: 2364, BIT:64
SPAM Level 48 44 44
Database Software ORACLE ORACLE ORACLE
Database Version 9.2.0.5 9.2.0.5 9.2.0.5
Database size in GB 214 5 TB
Free DB storage in GB
Used DB Storage in GB
Total Application Servers None None None
MDMP (Y/N) No No No
Clients 12
System upgraded in past? (Y/N) Yes Yes Yes
JAVA Deployment required after upgrade? No No No
System accessed from multiple countries?(Y/N)
No No No
SAP HARDWARE LANDSCAPE
7513 Router
100 TX
APPL
HP StorageXP-51212 TBRawSpace
HP TapeLibrary
ESL 9595
7 noAppl.servers
3 CPU6 GB
B/UPServer4 CPU6 GB
DB/CI/SB
2XCISCO 4507 Switch
HP 1x18 CPU 875 MHz24 GB RAM
& 1x12 CPU 750 MHz 16 GB RAMSuper dome
HP StorageXP-51212 TBRawSpace
2X64 Port McDataDirector SAN Switch
WAN(IP)
WAN(IP)
StorageXP-1024
57 TBRaw Space
Standby3 CPU6 GB
HP 1 no. 18 CPU(875 MHz)
24 GB RAM & 1x12CPU 16GB RAM
Super dome
Appl.servers
2 no. HP Rp76408 CPU 24 GB
+ 7 no RP54053 CPU 6 GB
2XCISCO 6509 switch
4 X 2 MBPS Leased Lines
New Dev/QA10 CPU
40 GB RAM
HP TapeLibrary712e
2X140 BrocadeDirector SAN Switch
DB CI
Private ClusterHeartbeat LAN
Public Network 2 – ServerPublic Network 1– User LAN
Apps
2X140 BrocadeDirector SAN Switch
2XCISCO 6509Switch
7513 Router
MMF Link over 100 FX
HP 17 CPU 1.6 GHz160 GB RAM Super dome
VirtualTape
Library
Appl. Servers8 Nos.
(3 CPU 6 GB)+ 7 Nos. Blades
(2 QC CPU 16GB)
B/UPServer
10 CPU40 GB
Test/Dev8CPU
24 GB RAM
HP StorageXP-12000
62 TBRaw Space
Upgrade12 CPU
16 GB RAM
Corporate BusinessTechnology Center, Gurgaon
Corporate Near RecoverySite, Gurgaon
Corporate BusinessContinuity Center, Jaipur
SMF Link
Pre Upgrade Scenario in IOCLSAP 4.6C with IS Oil : Landscape
DEV4.6C(Ora 9i)
DEV4.6C(Ora 9i)
*500-Golden*500-Golden
520-ABAP520-ABAP
590-Test590-Test
*900-Gld-HR*900-Gld-HR
510-Sandbox510-Sandbox
*525- Authorizations*525- Authorizations
QAS4.6C(Ora 9i)
QAS4.6C(Ora 9i)
610Integration testing
610Integration testing
PRD4.6C(Ora 9i)
PRD4.6C(Ora 9i)
310
IOCL Production
310
IOCL Production
410
IIPL Production
410
IIPL Production
Solution Manager 3.2(Ora 9i)Solution Manager 3.2(Ora 9i)
TST4.6C(Ora 9i)
310-Test
TRN4.6C(Ora 9i)
690 -Training
*Development Client will be merged before upgrade
Client Strategy
DEV QAS PRDCONSOLIDATION ROUTE DELIVERY ROUTE
Client 510SAND Box
Client 590Test Client
Client 520Development
Client
Client 500Golden Client
Client 610QTST Client
Client 310IOCL Production
Client
Development System
Quality System Production System
Client 410IIPL Production
Client
Upgraded Landscape
DEVECC 6.0(Ora 10g)
DEVECC 6.0(Ora 10g)500-Golden
520-ABAP
590-Test
510-Sandbox
QASECC 6.0(Ora 10g)
QASECC 6.0(Ora 10g)
610
Integration testing
610
Integration testing
PRDECC 6.0(Ora 10g)
PRDECC 6.0(Ora 10g)
310
IOCL Production
310
IOCL Production
410
IIPL Production
410
IIPL Production
Solution Manager 4.0(Ora 10g)Solution Manager 4.0(Ora 10g)TST
ECC 6.0(Ora 10g)TST
ECC 6.0(Ora 10g)
310-Test
R/3 4.6C ERP 6.0
Oracle 9i
VM 3.5
Oracle 10g
VM 4.1
Application
Database
Volume Manager
Upgrade of around 40 servers
HP-UX 11 HP-UX 11.23OS
PA-RISC IA-64HW
It was not a SAP Upgrade only
Upgrade Phase – The Big Picture
PREP
ARE
R3u
p
Post
-pro
cess
ing
System is productive System is productive
Pre-upgradephase
Technical-upgradephase
Post-upgradephase
Func
tiona
l ana
lysi
sR
elea
se N
otes
Plat
form
Sup
port
Cap
acity
Pla
nnin
gSA
P U
pgra
de S
ervi
ceD
ocum
enta
tion
Tech
nica
l pre
para
tion
…..
Mod
ifica
tion
Adju
stm
ent
(SAP
U)
Test
ing
Trai
ning
& s
uppo
rtM
onito
ring
& tu
ning
….
X X + 24 hrs
Course of Upgrade – Downtime Minimized
Preparation
Preparation
Backup
Upgrade
Import substitution set
SPDD
Supp.Pkgs., add-ons
Distribution, activation
ICNV
Distribution, activation
SPDD
Supp.Pkgs., add-ons
Import substitution set
Backup
Upgrade
Post-upgrade activity
Backup BackupPost-upgrade activity
StartPREPARE
Start R3up
PhaseEU_IMPORT1
PhaseMODEPROF_TRANS
End ofR3up
Legend:
Actions by
PREPARE
Or R3up
User
Actions
Downtime
Production
operation
Downtime
Depending on
Archiving
Strategy and
database
Upgrade Project : An Opportunity To ….
Migrate to new technology framework
Re-look for scope of improvisation of quality of our development work done in last8 years and
Bring scope of new standard SAP business functionalities
20022001 20092000
R/3 Ver 3.1H R/3 Ver 4.0B R/3 Ver 4.6C SAP ECC 6.0
R/3 VER 4.6 C SAP ECC 6.0
15th Sep’ 2008 26th Jan’ 2009133 days
Key Decision Factors
Type StrategySystem
LandscapeLanguage
Considerations
TECHNICAL
FUNCTIONAL
STRATEGIC
DOWNTIME MIN
RESOURCE MIN
SATELLITE SYS
ALL SYS
UNICODE
NO UNICODE
Database &OS
DB ONLY
OS ONLY
DB & OS
NO DB or OS Upgrade
DECISION FACTORS
Upgrade Steps 1/3
System Copy and upgrade
Production Landscape 4.6CDEV
Ora 9i
4.6CQA
Ora 9i
4.6CPRD
Ora 9i
TSTECC6
Ora 10g
DEVECC6
Ora 10g
QAECC6
Ora 10g
12 3
Legend:= new release
= old release= actual project work
= transport route
= system copy
System Landscape during upgrade Project
Upgrade Steps 2/3
5W 3W5W 3W 3W
Double maintenance 1. Copy2. Upgrade
Transferchanges
QAECC6
Ora 10g
DEVECC6
Ora 10g
TSTECC6
Ora 10g
4.6CDEV
Ora 9i
4.6CQA
Ora 9i
4.6CPRD
Ora 9i
Legend:= new release
= old release
= actual project work
= transport route
= system copy
Upgrade Steps 3/3
5W 3W
System Copy and upgrade
Old ProductionLandscape
5W
4.6CDEV
Ora 9i
4.6CQA
Ora 9i
4.6CPRD
Ora 9i
3W 3W
TSTECC6
Ora 10g
DEVECC6
Ora 10g
QAECC6
Ora 10g
MOCKECC6
Ora 10g
PRDECC6
Ora 10g
Legend:= new release
= old release
= actual project work
= transport route
= system copy
Major Milestones
DEVUpgrade
TST PRDUpgrade
QAUpgrade
Dual MaintenancePre-Requisite
Oracle 10 GUpgrade MOCK 1
MOCK 2 END UserTraining
Solution ManagerDEV Upgrade GO LIVE Post GO LIVE
Support
Milestone 1 Milestone 2
Milestone 3 Milestone 4 Milestone 5
MOCK 3[ MOCK 4
PRD Upgrade
Solution ManagerPRD Upgrade
Timelines
Project Phase
Project Preparation
Upgrade Blue Print
Upgrade Realization
Final Preparation for Cutover
Production Cutover and Support
Jan - 09 Feb - 09Sept - 08 Oct - 08 Nov - 08 Dec - 08
MilestonesDevelopment System Upgrade: October 23 2008QA System Upgrade: November 15 2008PRD System Upgrade: January 05 2009Go-Live: January 26 2009
Go Live on January 26 2009On January 27 2009, the system will be released for Production Operation
High Risks Found During Upgrade
Downtime < 24 hrsHardware AvailabilityUpgrade in Cluster environmentGUI Upgrade across corporationModifications / enhancements adjustmentsComprehensive testingLarge Database SizePerformance bottlenecksHigh number of modifications @ IOCL
Oil Business Complexities
Development ( ABAP) Work Statistics
SPAU Corrections : 1658
SPDD Corrections : 210
Unicode Compliant Check : 2108
Testing & Fixing Issue Resolutions : During Mocks & After Go-live
For each object, the transactions SPDD and SPAU guides through the adjustmentprocess, offering the alternative of performing modification adjustment or returningto the SAP standard.
Transaction SPDD allows you to adjust modifications to ABAP Dictionary objectsduring an upgrade.
Transaction SPAU allows adjustment of programs, function modules, screens,interfaces, documentation, and text elements after an upgrade.
In addition, transaction SPAU allows adjustment of ABAP Dictionary objects whereno data loss can occur I.e. Views, Lock Objects, Search Help, and Data Elements(text).
SPAU and SPDD
SPDD deals with the following objects: Domains, Data Elements, and Tables.
SPDD is not required to be performed if:No changes whatsoever have been done to the SAP standard objects of the ABAPDictionaryAddition of own development work to the SAP System, such as new domains, dataelements, or table structures in the customer name range.Only changed SAP objects require further processing.
To prevent data from being lost, adjustment of the new and old versions of ABAPDictionary objects is required
The system automatically recognizes during upgrade if modification adjustment isnecessary and then prompts for performing the modification adjustment.
Adjusting ABAP Dictionary Objects (SPDD)
The adjustment of R/3 Repository Objects is carried out with transaction SPAU.Only those objects that have been modified are being redelivered by SAP in an upgrade arepresented for adjustment.
If the objects modified are not being delivered by SAP with the current upgrade, thenthey do not appear in the display.
Decision is to be taken whether the objects contained in the adjustment list shouldretain modifications or if they should revert to the standard.
Adjusting R/3 Repository Objects (SPAU)
SPDD ADJUSTMENTS –Overview
Sl.No. SPDD Object Classification Total Completed
1 Database TablesWithout
Modification 52 52
2 StructuresWithout
Modification 19 19
3 DomainsWithout
Modification 10 10
4 Data ElementsWithout
Modification 36 36
5 Data ElementsWith
Modification 74 74
6 Data Elements Deleted Objects 1 1
7 Database TablesDeletedObjects 9 9
8 StructuresDeletedObjects 8 8
9 Domains Deleted Objects 1 1Total 210 210
Percentage Completion 100%
As per denoted from the system
Key Take Aways!
Observations during SPDD , SPAU and YZ Objects Corrections:
Lack of Documentation: No Documents/Comments were maintained during standard codechange.Non Adherence to Coding Standards: No/some SAP coding standards has been followedduring the custom code written/correction.Lack of Synchronization: Some objects were present in Production but not inDevelopment server.
Key Take Aways!
Issue Diagnostics depict the followingModification to the Standard CodeActivation of User ExitsField Level Changes. Modification of Standard Field DescriptionsLack of Sync between 4.6 C DEV and 4.6 C PRDWrong SPDD and SPAU decisions in select cases
Corrective Actions TakenCorrections / Adjustments in the codesCorrective Decision on the User ExitsDelta Configuration / Complete ConfigurationRevisit SPDD and SPAU decisions. Root Cause Analysis done and correctionsimplementedDetailed documentation on actions taken
UPGRADE TESTING: Snapshot
Sl. No. System Total Number ofProcess Tested
Total Number ofIssues Resolved
1 ECC DEV SystemUpgrade
1259 284
2 TST PRD Upgrade withIntegration Testing
1325 171
3 MOCK 1 with IntegrationTesting
1320 94
4 MOCK 2 with IntegrationTesting
879 4
5 MOCK 4 with IntegrationTesting
744 19
6 After Go-live 70
Key Learning's on Testing
Comprehension of the IOCL Process in a structured manner leading to betterunderstanding
This will form the foundation for detailed integration testing in the ECC TST System
Identification of key processes which would require additional testing in TST and MOCK
scenarios
All Z and Y Programs [custom developments] were tested
Configuration checks were done in the process of testing
Identification of delta configuration areas
Identification and correction of standard code changes.
Identification and correction to user exit errors due to upgrade
Correction to custom objects to suit to upgraded system
Modification of existing test scripts to suit present day IOCL Business Process.
Fine tune of integration test scripts.Collective Approach to testing and issue resolutions, thereby ensuring cohesivenessamong teams
Interface Testing
Leave Management (Ref(HO), PL(HO), R&D)
Employee Related Payments ( Guruji & iSAP )
e-pms
HR Crystal reports
CDK. Material coding Application
XI application, Exchnage Application
i2, Optimization Applications
Terminal Automation Systems
Other Opportunities
Solution Manager Landscape Upgrade from version 3.2 to 4.0
IDES 6.0 Installation
Quality system to have latest production database for real testing.
Customer Code Impact & Analysis (CCI) tool in solution manager to make analysis at anytime for clearing unwanted development work.
Use of Code Inspector tool to optimize program code
Implementation of CHARM ( Change Request Mgmt ) after upgrade in Solution Manager
Implementation of CCI recommendations
Solution Manager (Maintenance Optimizer)& Managed Systems
Solution Manager
ABAP Java
OS-Tools + Kernel
MOPZSLD
Maintenance Optimizer (MOPZ)SLD (only required if Java systems in
the landscape)Business Blueprint & system landscape
data maintained (SOLAR01 & SMSY)Stack.XMLGenerated viaMaintenance
Optimizer
ABAP Java
OS-Tools + Kernel
SPAM JSPM
Only withSP14
OS-Tools + Kernel
Java
JSPM
Only withSP14
OS-Tools + Kernel
ABAP
SPAM
Managed Systems
Manuallypassedto the
tools, toolscalled by
admin
Check technical Prerequisites- SAP GUI options
SAP GUI
SAP GUI is still the default UI with SAP ERP
SAP Enterprise Portal is not required unless portal-specificapplications are used (e.g. Employee Self-Service)
Key Take Away
SAPGUI 7.10 is the recommended GUI for use with SAP ECC 6.0SAPGUI 6.40 also supports SAP ECC 6.0, check dependencies during planning ofSAPGUI RolloutSAP GUI for Java still offered for Macintosh, Linux, etc.SAP GUI for HTML still supported via Integrated ITS
Check the Product Availability Matrix (PAM) for technical prerequisites about your SAP GUIvia Service Marketplace Quicklink: /pam
Check technical Prerequisites- OS/DB dependencies
OS/ DB Upgrades
Check impact and dependencies early!!!
Perform your OS/ DB Upgrade in advance of the SAPupgrade
Key Take Away
Check the Product Availability Matrix (PAM) to determine if any upgrade are required to theOS/ DB via Service Marketplace Quicklink: /pamOracle customers: SAP NetWeaver 7.0 (and thus ECC 6.0) only run on Oracle 10For new installations 64bit OS-/DB releases are since SAP NetWeaver 7.0 mandatoryFor upgrades to SAP NetWeaver 7.0 64bit OS-/DB releases are recommended
Corporate Information Systems
A New Initiative Use of SolutionManager for Testing
A New InitiativeUse of Solution Manager for Testing
Change Management Issues
Windows XP SP2 or Vista on all users PCs
New SAPGUI 7.10 on all PCs across corporation
Training to users on screen changes / process changes on new version ECC 6.0
Restart Business after 24 hrs of downtime
DOWNTIME PROGRESS OVER UPGRADES
Sl.No.
DowntimeComponents
ECCDEV
Upgrade[HRS]
TSTPRD
Upgrade
[HRS]
MOCK1
[HRS]
MOCK2
[HRS]
MOCK3
[HRS]
MOCK4
[HRS]
PRDUpgrad
e[HRS]
A TechnicalDowntime
10 110 16 12 12 12 7: 25
B Post InstallationActivity
2 2 2 2 2 2 2:00
C FunctionalActivity Inclusiveof ProgramActivations andTransportsincludingFunctionalTesting
9 8 8 9 9 9 13:00
TOTALBUSINESSDOWNTIME
21 120 26 23 23 23 22:25
Progressive Reduction in Downtime
QAS Quality System - Identification of custom development extent10857 objects found in customer namespaceTop 5 development class (in terms of number of customer objects)
YV01 – 2191 (SD)Z3IE – 1706 (export / import related development)ZEX – 1545 (export / import related document)YH01 – 1093 (HR)YF01 970 (FI)
DEV ECC 6.0 Identification of custom development exposure to impacts5900 customer objects use SAP objects
8804 SAP objects are directly reference in customer objectsNot impacted “green list” – 7306 customer objects
4957 customer objects with no reference to SAP object2349 customer objects with reference to SAP objects with no change detected
Impacted : 3551 customer objects2026 customer objects severely impacted (“red list”)1525 customer objects with medium impacts (“yellow list”)
Identification of SAP changes2850 SAP objects changes
SAP Custom Code Change Impact AnalysisChange Impact Analysis – Facts
Key Take Away!
Use SAP Solution Manager to document your business processes and steps (includingcustom ones) and store centrally project documentation (blueprint).Track changes using Modification Assistant to easily revert back to standard and use SNOTE.Have a common and centralized procedure to document and centralize development
request specification.Use Code Inspector to stabilize custom development environment at dedicated Quality Gates(after adjustment completion before unit test, before transporting to Quality System).Get focused testing and mitigate trade off between risks and efforts based on:
classifying critical and core business processes affected by changes ( triggered bybusiness, Top Down approach).categorizing criticality of adjustments done (triggered by development, Bottom Upapproach).
Ensure that all changes are implemented and / or transported in relevant systems.Leverage control of custom development extent centrally and increase reusability ofexisting custom development object.
Quality and Test Management
FindingSeveral round of units tests for custom development adjustment.Focus in testing has to be finalized.
RiskRisks of endangered business processes.
RecommendationsUse Code Inspector to stabilize custom development environment at dedicated Quality Gates(after adjustment completion before unit test, before transporting to Quality System).
Get focused testing and mitigate trade off between risks and efforts based on:classifying critical and core business processes affected by changes ( triggered bybusiness, Top Down approach).categorizing criticality of adjustments done (triggered by development, Bottom Upapproach).
Change Management
FindingSeveral adjustment activities are done in copy of productive.
RiskRisks of inconsistent system landscape.
RecommendationsEnsure that all changes are implemented and / or transported in relevant systems.
Governance and Control Custom DevelopmentExtent
FindingExtensive custom development extent ( more than 10000) customer objects found incustomer namespace).Copying SAP standard reports in customer name space appeared to be preferred comparedto modifying SAP standard directly.Ratio of modifications to custom development is less than 10%.
RiskThe more you have custom development higher are the risks to be impacted by the changesof an upgrade in particular when referred SAP standard objects have changed during theupgrade.Transparency on custom developed solutions becomes a challenge.Increased gap compared to SAP standard.
Governance and Control Custom DevelopmentExtent
Recommendation:
When adopting new business requirements assess alternatives according tothe change level hierarchy type
Standard (existing or upgrade support package, down-port functionality).Work around.Standard enhancement such as Business Add-in
Sap Market Place, Release Note, Notes, use Solution Architect expertise.
Evaluate a trade-off between modification and custom development (case by case)Prefer Z report and copying to customer namespace whenever considerable deviation tostandard and integration concerns.Else prefer modifications and track changes using Modification Assistant.Encapsulate modifications and revert back to standard whenever possible(spau/spdd).
Governance and control custom developmentextent
Finding:
Development units are divided according to application core teams (FI, SD, …
RiskThere is a higher risks to create redundancies or duplicates customer objectswhich increase Total Cost of Ownership.
RecommendationLeverage control of custom development extent centrally and increase reusability ofexisting custom development object.
Promote Innovation
FindingRelease Management should be established.
RiskReactive approach of fixing issues by notes appliance which could lead in higher effortsIncreased gap with standard and efforts of future software lifecycle changes.
RecommendationGet more visibility on the changes of a support package and their impact on your customdeveloped solutions using Custom code Change Impact Analysis.Set a Release Management Strategy with releases on a regular basis.
Downtime Statistics
First Test Upgrade Run : Downtime Break-up
Major Downtime -First Test Upgrade Run
Phases Duration [hh:mm]PARCONV_UPG (Index creation, Table Conversion, Nametab) 64:25TABIM_UPG (Import of Data into control tables) 14:40XPRAS_UPG (Executes XPRAs – application data conversion) 29:16TOTAL DOWNTIME 110 Hrs
Result AnalysisUnusual long runtime for all the three major phases listed above which are themajor constituents of downtime phases during ‘Downtime-Minimized’ Upgradestrategy
PARCONV_UPG
Major contributors for Long runtime of PARCONV_UPG:Table APQD (~2days):
An ICNV Candidate, but ICNV didn’t finish before the start of downtime phase(MODPROF_TRANS) due to large number of entries. Incremental Conversioncontinued in the PARCONV_PHASE for over two days. Hence used workaround toclear the temporary QCM* table to proceed as APQD entries were not thatimportant
Table BKPF (~1 Hr)Field added in the new release required for index (BKPF~BUT) creationTables USH* (~4 Hrs)
USH* Tables are being converted from pool to transparent table in new release.Conversion of USH* tables were done in this phase. As there are large number ofentries in these tables it took around 4 hours
Index Creation (~6 Hrs)::Some of the indexes on very large tables like MSEG, BSAD,BSIS were created in this phase increasing the runtimeTable space PSAPTEMP full:
Oracle error (ORA-01652) occurred during the PARCONV_UPG phase causingtermination
TABIM_UPG
Major contributors for Long runtime of TABIM_UPG:
Less number of R3trans and Batch processesOracle 10g parameters not optimalMissing statistics
XPRAS_UPG
Major contributors for Long runtime of XPRAS_UPG:
Missing statistics (mainly for D010INC): Due to missing statistics, XPRAS was running forover a dayLess number of Batch processesOracle 10g parameters not optimal
DTA Recommendations in Mock 1
Following Recommendations from DTA were Implemented:
Oracle Parameters were fine tunedData Buffer Cache size was increased by 2 GBPSAPTEMP tablespace increased by 2 GBR3trans processes increased to 12Batch processes increased to 12APQD cleared till 30th March 2008USH10 and USH12 Tables converted to transparent before handMSEG~M Index adjusted at the database level before hand
Mock1 Upgrade Run : Downtime Break-up
Major Downtime Consumers of Mock1 Upgrade Run
Phases Duration [hh:mm]PARCONV_UPG (Index creation, Table Conversion, Nametab)09:45TABIM_UPG (Import of Data into control tables) 00:45XPRAS_UPG (Executes XPRAs – application data conversion)04:30TOTAL DOWNTIME 16 Hrs
Result AnalysisThere is a potential of reducing the runtime of PARCONV_UPG bybuilding the indexes in the uptime or after the upgrade downtime.It was observed that indexes BSIS~Y4 and BSAS~Y4 were included inthe SPAU request and it took 03:40 and 01:40 Hrs respectively to buildthese indexes in the PARCONV_UPG downtime phaseThere is no much potential in reducing the runtime of TABIM_UPG andXPRAS_UPG phase on this hardware
Downtime Comparison: Test vs Mock1
Phases TestMoc
k1PARCONV_U
PG 64:25 9:45
TABIM_UPG 14:40 0:45
XPRAS_UPG 29:16 4:30REM 01:40 1:10
Time Comparison
64.25
14.4
29.16
1.49.45
0.454.3 1.1
PARCONV_UPG TABIM_UPG XPRAS_UPG REM
Downtime Phases
Run
tim
e in
Hrs Test
Mock1
DTA Recommendations in Mock 2
Following Recommendations from DTA1 were Implemented:
Oracle Parameters were kept as in Mock 1Data Buffer Cache size was kept at 6 GBR3trans processes increased to 14Batch processes increased to 14APQD cleared till 30th March 2008USH10 and USH12 Tables converted to transparent before handIndex MSEG~M adjusted at the database level before handIndexes BSIS~Y4 and BSAS~Y4 were removed from the SPAU requestIndexes BSAD~4, FMIFIIT~6, BSIS~1 were adjusted before handIndex BKPF~BUT on BKPF Table was not adjusted as it required structure change inBKPF
Mock 2 Upgrade Run : Downtime Break-up
Major Downtime Consumers of Mock2 Upgrade Run
Phases Duration [hh:mm]PARCONV_UPG (Index creation, Table Conversion, Nametab) 02:15TABIM_UPG (Import of Data into control tables) 00:50XPRAS_UPG (Executes XPRAs – application data conversion) 07:45TOTAL DOWNTIME ~11 Hrs
Downtime Comparison: Mock1 vs Mock2
Phases Mock1Moc
k2PARCONV_
UPG 09:4502:1
5
TABIM_UPG 00:4500:5
0
XPRAS_UPG 04:3007:4
5
REM 01:1001:1
0
Time Comparison
64.25
14.4
29.16
1.49.45
0.45 4.3 1.1
PARCONV_UPG TABIM_UPG XPRAS_UPG REM
Downtime Phases
Run
tim
e in
Hrs Test
Mock1
0:00
2:24
4:48
7:12
9:36
12:00
PARCONV XPRAS
Mock1Mock2
DTA Recommendations in Final Mock Run
Following Recommendations from DTA1&2 were Implemented:Oracle Parameters were kept as in Mock 1Data Buffer Cache size set to 4 GBR3trans processes increased to 14Batch processes increased to 14APQD cleared till 30th March 2008USH10 and USH12 pool tables converted to transparent tableIndex MSEG~M adjusted at the database level before handIndexes BSAD~4, FMIFIIT~6, BSIS~1 were adjusted before handIndex BKPF~BUT on BKPF Table was not modified as it required structure change inBKPF
Final Mock Run : Downtime Break-up
Major Downtime Consumers of Final Mock Upgrade Run
Phases Duration [hh:mm]PARCONV_UPG (Index creation, Table Conversion, Nametab) 02:18TABIM_UPG (Import of Data into control tables) 00:53XPRAS_UPG (Executes XPRAs – application data conversion) 09:15TOTAL DOWNTIME ~12 Hrs
Downtime Comparison: Mock2 vs. Final Mock
Phases Mock2
FinalMock
PARCONV_UPG 02:15
02:18
TABIM_UPG 00:5000:5
3
XPRAS_UPG 07:4509:1
5
REM 01:1001:1
0
Time Comparison
64.25
14.4
29.16
1.49.45
0.454.3 1.1
PARCONV_UPG TABIM_UPG XPRAS_UPG REM
Downtime Phases
Run
time
in H
rs Test
Mock1
0:00
2:24
4:48
7:12
9:36
12:00
PARCO XPRAS
Mock1Mock2
00:0001:1202:2403:3604:4806:0007:1208:2409:36
PARCO TABIM XPRAS REM
Mock2FinalMock
DTA Recommendations in Production System
Following Recommendations from previous experiences were Implemented:
Oracle Parameters were tuned during Oracle 10g Upgrade for productive runData Buffer Cache size was set to 24GBDB and CI were shifted to one cluster node as insisted by IOCL basis teamR3trans processes increased to 16Batch processes increased to 16APQD cleared till 30th March 2008
DTA Recommendations in Production System
Following Recommendations from previous experiences were Implemented:
USH10 and USH12 Tables converted to transparent before PREPARE to avoidconversion during downtime phase PARCONV_UPGIndex MSEG~M adjusted at the database level before PREPAREIndexes FMIFIIT~6, BSIS~1 were adjusted before handIt was agreed to leave index BSAD~4 as build time was not significant from productionsystem perspectiveIndex BKPF~BUT on BKPF Table was not adjusted as it required structure change inBKPF which could have effected the production system activity
Productive Upgrade Run : Downtime Break-up
Major Downtime Consumers
Phases Duration [hh:mm]PARCONV_UPG (Index creation, Table Conversion, Nametab) 01:25TABIM_UPG (Import of Data into control tables) 00:57XPRAS_UPG (Executes XPRAs – application data conversion) 04:00REM 01:00TOTAL DOWNTIME ~ 07:30 Hrs
BASIS Problems & Resolutions
Re-alignment/re-deployment of the existing hardware.
Prior planning in identifying common platform for current (4.6c/oracle9i) and future (ECC 6.0/ oracle 10g) applications
Operating system platform Upgrade to 11.23
ORACLE Database upgrade to 10g
SAP Upgrade to ERP 6.0
Technical Activities
Common platform for existing 4.6C & futureECC 6.0
OS platform for existing 4.6C & ECC 6.0
Oracle Upgrade to 10g
BR Tools for DR1 & BCC, Jaipur
SAP Extended Kernel Selection
DB Upgrade in Three Site setup
Large Volume of Data
Implementation of DTA recommendations inProduction
MC/SG cluster
Application servers
Upgrade phase
Upgrade Phase
Upgrade Phase
Go-Live Phase
ABAP Problems & Resolutions
Activities of ABAP Team
Compiling Inventory of all DevelopmentsAction on Open Change RequestsReplication of 4.6C Changes to ECC 6.0SPDD/SPAU AdjustmentsSyntax CorrectionRemoval of obsolete function modulesImplementation of Note/Execution of other programsIssue Log ResolutionInterface Testing/Issue ResolutionsUnicode Correction
Compiling Inventory of All Developments
ABAP team compiled all the Y/Z developmentsFunctional people assigned priority to the above developments as thesedevelopments to be addressed on priority by ABAP team.
Above step also ensured critical developments were not missed out intesting
ChallengesLack of DocumentationRedundant Developments for eg unused programs and empty tablesLack of Development dictionaryHerculean task for Functional team to categorize the developments due toabove reasons
Compiling Inventory of All Developmentscontd…
Lessons Learnt
CCI Workshop should be held well in advance to obtain following benefits -Usage analysis of one-two months gives true picture of critical transactions/programsCode impact due to upgrade also helps in better preparedness for Upgrade.Impacted programs can be studied/modified in suitable timeframeDocumentation of all the developments must be strictly enforced
Action on Open Change Requests
As per Best Practice, minimum number of Open requests in Customer Namespaceshould be present during Upgrade
Approximately 750 Open Change Requests existed in DEVABAP team asked to advise action for Hold/Delete against each open DEV Request
Subsequently objects under open change requests were brought in sync withProduction so that undesirable / untested code is not moved to Production
ChallengesNumber of open change requests were very largeVery old open change requests were existing on which decision making was difficultOwners of many open change requests were not available in Manthan team
Action on Open Change Requests contd…
Mistakes
Open change requests were deleted/released without reverting the PRD version of theobjects contained in the change requests. This led to undesirable results since the aboveprograms/objects were further transported in ECC landscape due to syntax errorcorrection/issue log resolution etc.
Open change requests were existing in PRD , DEV testing clients
Action on Open Change Requests contd…
Lessons Learnt
Change requests should not be left open
For testing purposes, create local change requests
Frequent audit of Change Requests
In case the developer is leaving, all the open requests should be closed and changesreverted to PRD version or the open change requests should be handed over
Replication of 4.6C Changes to ECC 6.0
When Dual landscapes were present ABAP Team was required to replicate thechanges which had gone to Production since the date ECC Dev came intoexistence
MistakesIn this period also, ABAP Team was doing developments without documentation
Communication stating the criticality/gravity for documenting the changes in duallandscape was ineffective
As replication was manual so in few cases the changes were not replicated properly
Lessons LearntEfforts of replication could have been avoided if code freeze would have been strictlyfollowed
SPDD/SPAU Adjustments
SPDD/SPAU
During upgrade, existing SAP standard objects areoverwritten with the objects redelivered. To help thecustomer retain the objects modified in a previous release,SAP provides all modified objects which are redelivered (inan upgrade or Support Package) in the upgrade adjustmentof transactions SPAU and SPDD
SPDD deals with the adjustment of the dictionary objectslike tables, structures, domains & data elements
SPDD/SPAU Adjustments contd…
Example of SPDD Adjustment
SPDD/SPAU contd…
There were total of 240 objects in DEV
Following actions are proposed for all objects presented for adjustment in SPDD:Retain modification:Either confirm that you want to adopt the modification or maintain the changes with theappropriate maintenance transactionCancel modification:Choose Reset to original.
Judgement has to be made very carefully as it might result in loss of data.
Lessons Learnt
Data elements Text/Documentation should not be modified by taking access key, instead weshould use text enhancement using CMOD.
Use CI or Append Structure as far as possible instead of changing standard SAP table
SPDD/SPAU contd…
SPAUThe adjustment of R/3 Repository Objects is carried out with transaction SPAUThose objects that have been modified by customer and are being redelivered bySAP in an upgrade are presented for adjustmentIf the objects modified are not being delivered by SAP with the current upgrade,then they do not appear in the displayDecision was taken whether the objects contained in the adjustment list shouldretain modifications or if they should be reverted to the standardTransaction SPAU allows to adjust standard SAP programs, function modules,screens, interfaces, documentation, and text elements after an upgrade.
SPDD/SPAU contd…
Following two actions appear in SPAU adjustment:Reset To Original
Keep the standard ECC version as activeNo custom changes have been carried out in the previous releaseOss notes have been applied in previous release , but the notes are not applicable tothe new release
Adopt ModificationModifications have been done to standard objects in the previous releaseAdopt the custom modifications, that have been done in previous release, in the newupgraded releaseOSS notes have been applied in previous release and the notes are also applicable tothe new release
SPDD/SPAU contd…
Almost 1700 Objects - Out of which some which were changed throughsnote/modification assistant were adjusted automatically.
MistakesDEV SPAU upgrade was not done properly hence lot of problems were faced duringUnit/Integration testing and changes had to be redone
Lessons LearntAs DEV and PRD were not in sync, adjustments of SPDD/SPAU was done separately forDEV and PRDThere was little/no documentation for standard program changes hence it was really toughto find out the functionality of the changes.Modifications in standard SAP to be avoided as far as possible.However, if required, say application of note, note should be necessarily applied throughSNOTE and modification to be made only from modification assistant with properdocumentation.In future new enhancement framework should be explored instead of changes throughaccess key.SAP standard indexes to be modified only after proper study by functional/Technical groupincluding basis
Syntax Correction
Syntax correction was carried out in Y/Z programsExample
Literals that take up to more than one line are not permittedError ( Statement is not Accessible)
There were Y/Z objects which were copy of Standard SAP; with upgrade theseobjects got changed and many includes were changed/removed. It was difficult tomodify these programs to make them syntax free with retention of its functionality.
We have asked SAP to give detailed syntax error which might come in ECC6.0 andwere correct in 46C , which they are yet to give
Lessons LearntExtended syntax/Code Inspector to be used as far possible.Few programs having syntax-error were existing in PRD. Regular audit should be done todrop/correct themPractice of making copy standard SAP objects should be avoided to the maximum extentpossibleIt should be mandatory to check request before it is released Request- Complete check
Removal of obsolete function modules
Some Obsolete FunctionsWS_UPLOADWS_DOWNLOADUPLOADDOWNLOADWS_FILENAME_GETPOPUP_TO_CONFIRM_STEPPOPUP_TO_CONFIRM_LOSS_OF_DATAPOPUP_TO_DECIDECONVERT_TO_LOCAL_CURRENCY_N
Some function modules were giving dump like MS_EXCEL_OLE_STANDRD_DATwhich was used in many of the programs for Excel Download. This was replaced byother function.
Lessons LearntReplacement of obsolete function modules should be done as a regular practice
Unicode Corrections
Unicode corrections of Programs and Function Modules were doneSome Examples
Non Unicode UnicodeCALL FUNCTION'WS_DOWNLOAD'EXPORTINGFILENAME = p_pcfileFILETYPE = 'ASC'TABLESDATA_TAB = itabEXCEPTIONSOTHERS = 1.
CALL METHODcl_gui_frontend_services=>gui_downloadEXPORTINGfilename = p_pcfilefiletype = 'ASC‘CHANGINGdata_tab = itab[]EXCEPTIONSOTHERS = 1.
OPEN DATASET f_name IN TEXT MODE. OPEN DATASET f_name FOR OUTPUTIN TEXT MODE ENCODING DEFAULT.
DESCRIBE FIELD itab LENGTH len. *THE DESCRIBE LENGTH can only be usedwith *the IN BYTE or IN CHARACTER MODEDescribe field itab length len in character mode*OrDescribe field itab length len in character mode
Issue Log Resolution
Lot of issues were reported during testing of DEV/MOCK server by functional teamwere resolved. Some of the common problems
BDC ProblemsField Exit ActivationProblem in SAPSCript/SMARTFORMSearch HelpPurely ECC 6.0 code logic related issuesF4 Help
Interfaces were also tested and issues were resolved
Corporate Information Systems
FS & TS Uploaded in SOLMAN
Upgrade Phase: Best Practices Followed
SPDD & SPAU Phase:
Utilization of Modification Assistant wherever possible. By taking this approach, it isensured that in the subsequent upgrades the changes are copied automatically.Some objects will not appear as part of “Modification Assistance” in the absence ofversion management. Here manual intervention becomes essentialSome objects will not appear in “Modification Assistance” where version management ispossible, but they have been changed in earlier release without Modification Assistantsupport. As per SAP Best Practice, for all those objects, we have used ModificationAssistant support.
Upgrade Phase: Best Practices Followed
SPDD & SPAU Phase:
Fine tuned the methodology for taking Actions (Reset to Original / Adopt Modification).Designed the Template WHEREIN all actions proposed and action taken based on thedefined methodology are recorded with inputs [where applicable] from IOCL Team.Effectively corrected 1658 SPAU and 210 SPDD objects
Upgrade Phase: Best Practices Followed
Custom Objects:
Compiled the list of all Y & Z objects from the Production Server. This ensured that noobject used directly / indirectly by the end user of IOCL was missed outPerformed Syntax check and UCCHECK on 2208 custom objects and corrected allAfter the CCI Tool Workshop, a list was generated by the SAP Team using CCI Tool onReporting Production Server. Comparison of CCI list with Production List (1856 + 352 )ensured all custom objects are correctedReplacement of all obsolete Function Module with new Function Module wherever it isused in Custom Developments.
Upgrade Phase: Best Practices Followed
Documentation:
Prepared SAP Standard FS & TS for all new developments in ECC 6.0.During dual maintenance, ensured that proper documentation for all developments /changes in ECC 6.0Reviewed all FS, TS and Code written and provided by IOCL and uploaded the same inthe Solution Manager.
Upgrade Phase: Best Practices Followed
Transport Request:
Closely coordinated with Basis Team for transporting the requests.Designed and implemented the Transport Request FormSet the process for moving transport requests. Without signed hard copy of TR formBasis team has not moved the request from Development to TST-PRD or any Mockserver.Maintained list of Transport Request with the CORRECT sequence
Upgrade Phase: Best Practices Followed
Enhancement Points:
During Upgrade, guided IOCL team about Enhancement Points. This functionality allowsenhancement of standard SAP code without taking the Access Key at specific pointsThis functionality is very useful in Customer Exit where without taking access keymodification was not possible in 4.6 C
Key Take Away!
Good housekeeping (archiving, cleansing) drives efficiency of Upgrade
“Downtime minimized” method should be used - In order to get a realistic forecast aboutto be expected downtime a Test Upgrade with representative configuration and data set isnecessary
Distribution of new SAPGUI version should be started early
Check the Product Availability Matrix to determine if any upgrades are required to the OSor RDBMS
Verify Sizing - Request SAP Going Live - Functional Upgrade Check
Major key success factor: Early involvement of User Community
Install Solution Manager (generate Upgrade Key, download SPs)
The better the documentation about modifications, the easier the modificationsadjustments can be performed!
Customers with Industry Add-Ons should review the Industry Add-On specific upgradeguides
Fond Remembrances 4.6C….
Corporate Information Systems
The Journey Begins …to Next Upgrade !
© SAP 2008 / Page 147
Thank you!
Copyright 2009 SAP AGAll Rights Reserved
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained hereinmay be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x, System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer,z/VM, z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM, Power Architecture, POWER6+, POWER6, POWER5+, POWER5,POWER, OpenPower, PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2 Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX,Intelligent Miner, WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or othercountries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, and other SAP products and services mentioned herein as well as their respective logos aretrademarks or registered trademarks of SAP AG in Germany and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal Decisions, Web Intelligence, Xcelsius, and other Business Objects products andservices mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects S.A. in the United States and in other countries.Business Objects is an SAP company.
All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only.National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only,without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Groupproducts and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed asconstituting an additional warrant.
