Dr Pepper Snapple Group: Reduces SAP Database by 40% for Faster Move to HANA

Industry
Beverage

Revenue
$14B+

Employees
21,000+

Headquarters
Plano, TX, USA

40%
of database archived and deleted
8TB
of free space within the HANA environment for optimal performance
25 Hours
to complete HANA migration

Dr Pepper Snapple Group was migrating to an SAP HANA instance. Their SAP ECC database was not compatible with their plan to migrate to the suite. Even after archiving 4 TB of technical tables, Dr Pepper’s Oracle database was 22TB and growing by 400 Gb every month.

The projected timeline of total HANA migration was 86 hours. They needed a partner to help consolidate and streamline their complex system database to enable a 72-hour HANA migration window, including EHP upgrade, the actual data migration, IT validation, and business validation. They also needed to be able to quickly access their archived data to ensure they can meet audit and compliance regulations.

They needed to achieve the following within a six-month timeline:

  • Archive 40% of data to reduce HANA migration time
  • Increase available space for secure and fast HANA operation
  • No impact to the Stack XML used by HANA migration team

  • Reduce size of SAP ECC and Oracle Database prior to HANA migration
  • 72-hour max migration window to SAP HANA
  • No changes to Stack XML
  • Transparent access to all SAP ECC archived information

Dr Pepper Snapple Group worked with Serrala to complete this project in three phases. 1. Rapidly reduce database size using accelerated archiving tool, focusing on large cluster tables.  2. Provide business users with seamless access to archived data using archiving retrieval modules. 3. Enable faster reporting on archived data with nearline storage.

The first month was devoted to proof of concept to gain business buy-in. Once completed, we created more than 700 Write jobs and 19,800 Delete jobs.

Archiving happened in four steps:

  • WRITE: Write the data to be archived to .ADK files.
  • STORE: Move archived data to long-term storage
  • DELETE: Delete the data from the database
  • INDEX: For objects that are BPS enabled, run the indexing procedu

Serrala met the goal in only four months.

Here’s a breakdown of the top results and what we learned:

  • 40% (>8.7 TB) of database archived and deleted
  • 25 Hours to complete HANA migration
  • 8TB of free space within the HANA environment for optimal performance

The big takeaways from the project:

  • Start archiving early and obtain business approval by involving them in the decision making and testing.
  • Start with technical objects while you are getting business object approvals
  • SAP Data Archiving is a unique skillset, get the right resources.
  • Tight timelines require periodic intense focus by client stakeholders
  • Don’t forget to test.
  • Automated archiving SIGNIFICANTLY reduces time and effort required to reduce footprint
  • Data management should be considered early in the lifecycle of every system

The company continues to monitor its data growth and implement new archiving objects as needed to continuously improve system performance.

Business Need

Dr Pepper Snapple Group was migrating to an SAP HANA instance. Their SAP ECC database was not compatible with their plan to migrate to the suite. Even after archiving 4 TB of technical tables, Dr Pepper’s Oracle database was 22TB and growing by 400 Gb every month.

The projected timeline of total HANA migration was 86 hours. They needed a partner to help consolidate and streamline their complex system database to enable a 72-hour HANA migration window, including EHP upgrade, the actual data migration, IT validation, and business validation. They also needed to be able to quickly access their archived data to ensure they can meet audit and compliance regulations.

They needed to achieve the following within a six-month timeline:

  • Archive 40% of data to reduce HANA migration time
  • Increase available space for secure and fast HANA operation
  • No impact to the Stack XML used by HANA migration team

  • Reduce size of SAP ECC and Oracle Database prior to HANA migration
  • 72-hour max migration window to SAP HANA
  • No changes to Stack XML
  • Transparent access to all SAP ECC archived information

Solution Implemented

Dr Pepper Snapple Group worked with Serrala to complete this project in three phases. 1. Rapidly reduce database size using accelerated archiving tool, focusing on large cluster tables.  2. Provide business users with seamless access to archived data using archiving retrieval modules. 3. Enable faster reporting on archived data with nearline storage.

The first month was devoted to proof of concept to gain business buy-in. Once completed, we created more than 700 Write jobs and 19,800 Delete jobs.

Archiving happened in four steps:

  • WRITE: Write the data to be archived to .ADK files.
  • STORE: Move archived data to long-term storage
  • DELETE: Delete the data from the database
  • INDEX: For objects that are BPS enabled, run the indexing procedu

Results Achieved

Serrala met the goal in only four months.

Here’s a breakdown of the top results and what we learned:

  • 40% (>8.7 TB) of database archived and deleted
  • 25 Hours to complete HANA migration
  • 8TB of free space within the HANA environment for optimal performance

The big takeaways from the project:

  • Start archiving early and obtain business approval by involving them in the decision making and testing.
  • Start with technical objects while you are getting business object approvals
  • SAP Data Archiving is a unique skillset, get the right resources.
  • Tight timelines require periodic intense focus by client stakeholders
  • Don’t forget to test.
  • Automated archiving SIGNIFICANTLY reduces time and effort required to reduce footprint
  • Data management should be considered early in the lifecycle of every system

The company continues to monitor its data growth and implement new archiving objects as needed to continuously improve system performance.

Scroll to Top