SAP upgrade - Hexawarehexaware.com/casestudies/sa-hr-cs-7.pdf · additional functionalities...
1
Leading International mining company, USA Client Overview Case Study © Hexaware Technologies. All rights reserved. www.hexaware.com SAP Upgrade Client Requirements Landscape Before Upgrade Landscape After Upgrade The client is the world’s leading provider of market intelligence to the pharmaceutical and healthcare industries. The client has operations in more than 90 countries & has 7600 employees. A technical upgrade was required because of the compatibility issue with SRM 7.0 landscape. Client is implementing SAPSRM for its global requirement and this demands an upgrade of ECC and BIW landscape to be in the minimal level of EHP4. ECC 6.0 BIW 7.0 Database Size: 420 GB Modules/Components: FI, CO, SD, MM and PS 1000+ Custom Development objects across the above modules. ECC 6.0 EHP4 BIW 7.0 EHP1 Benefits This upgrade allowed the customer to choose the functional requirements by switch framework method where customer can activate or deactivate the required functionality. This helped the customer to select additional functionalities provided in SAP in some of the modules SAP Upgrade Execution Model The project was executed in offshore model for the Test iterations, Sand box, DEV and Test. The final production upgrade was done Onsite at client US location Resources - Onsite: 1 , Offshore: 2 Solution EHP4 upgrade differs from other enhancement upgrades in terms of methodology. The upgrade required procedure of the conventional application upgrades but using a new tool Enhancement Package installer (EHPI) from SAP. This tool drives the whole upgrade and also uses solution manager in order to allow the customer to choose the components for upgrade during the planning phase. This required skill of experienced Basis team with experience in installation and configuration of SAP ECC 6.0 systems on latest Ep4. Since EP4 brings lot of new business scenarios it comes with many repositorychanges like support package or stack upgrade. Hence implementing SPAD and SPAU changes during the process of the upgrade is essential. Since it is a technical upgrade, no other functionality were activated (except related to SRM) after the upgrade in IMS.
Transcript of SAP upgrade - Hexawarehexaware.com/casestudies/sa-hr-cs-7.pdf · additional functionalities...
Leading International mining company, USA
Client Overview
Case Study
© Hexaware Technologies. All rights reserved. www.hexaware.com
SAP Upgrade
Client
Requirements
Landscape Before Upgrade
Landscape After Upgrade
The client is the world’s leading provider of market intelligence to the pharmaceutical and healthcare industries. The client has operations in more than 90 countries & has 7600 employees.
A technical upgrade was required because of the compatibility issue with SRM 7.0 landscape. Client is implementing SAPSRM for its global requirement and this demands an upgrade of ECC and BIW landscape to be in the minimal level of EHP4.
ECC 6.0 BIW 7.0Database Size: 420 GBModules/Components: FI, CO, SD, MM and PS1000+ Custom Development objects across the above modules.
ECC 6.0 EHP4BIW 7.0 EHP1
Benefits
This upgrade allowed the customer to choose the functional requirements by switch framework method where customer can activate or deactivate the required functionality.
This helped the customer to select additional functionalities provided in SAP in some of the modules
SAP Upgrade
Execution Model
The project was executed in offshore model for the Test iterations, Sand box, DEV and Test. The final production upgrade was done Onsite at client US locationResources - Onsite: 1 , Offshore: 2
SolutionEHP4 upgrade differs from other enhancement upgrades in terms of methodology. The upgrade required procedure of the conventional application upgrades but using a new tool Enhancement Package installer (EHPI) from SAP.This tool drives the whole upgrade and also uses solution manager in order to allow the customer to choose the components for upgrade during the planning phase. This required skill of experienced Basis team with experience in installation and configuration of SAP ECC 6.0 systems on latest Ep4.Since EP4 brings lot of new business scenarios it comes with many repositorychanges like support package or stack upgrade. Hence implementing SPAD and SPAU changes during the process of the upgrade is essential.Since it is a technical upgrade, no other functionality were activated (except related to SRM) after the upgrade in IMS.
