SAP Commissions Oracle to HANA Migration: Considerations and Best Practices
Following on from the SAP acquisition of Callidus, many organizations have remained on the CallidusCloud Oracle platform instance of Incentive Management (formerly SAP Commissions). However, with the Oracle architecture being deprecated by SAP there is a need for organizations to move forward onto the SAP HANA platform. This move should be seen in a positive light and provides a great opportunity for organizations to gain the benefits of the new platform, integrate more closely with their other SAP products, and take advantage of the chance to put into place plans to fully utilize and optimize their commissions strategy.
The SAP Incentive Management tool has been optimised for SAP HANA and will provide faster runtimes, data loading, and validations. We understand, however, that every installation is different and has its own challenges and complexities. There are several considerations, which we will illustrate below, when undertaking a conversion to maximize the benefit and limit the conversion time, but with thought, planning, and experience the conversion will provide real benefit to your compensation administration processes and sales teams.
- Increase performance
- Additional capabilities
- Better user experience
The challenge of migrating a complex SQL application to another database is not to be underestimated, but with the right planning and process it becomes possible.
Want to discuss the SAP Commissions Oracle to HANA transition with your peers and our team of experts? If so, let us know and we’ll be in touch with event details soon!
DATA MIGRATION
A strategy around data migration will need to be developed to speed up the migration process.
- Does all historical data need to be migrated?
- Do you want to start with a clean slate or bring over all data?
The migration of data and custom stored procedures used in Stagehooks may present a challenge, however automated tools such as the SAP Advanced SQL Migration Tool can be deployed to automate much of the process of conversion between DBMS syntax. Once this is done, the team can look in depth at the code and make any corrections necessary. Resources will need to be allocated to optimize and correct any complex Stagehook and reporting code manually.
WORKFLOW
Migration between workflow environments will need to assess for any changes in related SQL procedures and API calls. Items such as parameters and references to databases may need to be updated if they are used in workflow groovy scripting. Consider if you will need to retain any history
of old cases and approvals and if there is any reference data in the database that impacts workflow. The workflow tool itself provides for easy migrations of code between platforms but as with any changes testing is key to understanding the impact.
DATA INTEGRATIONS
SAP Commissions Implementations typically have multiple integration points. Customers using stock ODI templates may find the migration pathway relatively straightforward as equivalent templates exist for the Express Data Loader. Customers with more complex integration requirements such as
Landing Pad will need their old processes transformed and transferred to the new tools such as SDI, Express Data Loader, SAP Datasphere or Cloud Integration tools. There will be additional complexities and analysis for these more complex integrations, but generally the new Express Data Loaders and API endpoints in SAP HANA make for a smoother and more transparent data loading process. Operations that previously required complex Informatica mappings or scripts can be moved to easier-to-maintain database processes. We can assess current infrastructure and recommend the best alternatives in the new tools.
REPORTING CONSIDERATIONS
Reporting is a key area in any commission system. Reports are often the only thing seen by the field users and are the face of the commissions system. The SAP HANA platform offers more advanced reporting tools than previous generations of SAP Commissions. The Embedded Analytics
tool offers an easy way to develop no-code reports and advanced analytics and self-service capabilities. Current reports should be evaluated for suitability and consolidated onto the new platform. Organizations will also need to determine a strategy for dealing with existing reports.
- How far back are reports kept for compliance purposes?
- Will old reports need to be archived to PDF and stored?
- Where can this take place?
- Is assistance needed with the storage and conversion?
Experienced consultants can help guide migrations of SQL based reporting code from old to new systems.
This is a good chance to also evaluate:
- Does the current reporting strategy work?
- Does the field appreciate and use the reports to enable them to optimize their selling?
- What is the current usage of reports?
- Are all reports viewed and needed, or are some redundant?
- Do the reports convey the required information or would other technologies like dashboards fit better?
TESTING STRATEGY
A solid testing strategy is critical to any migration. Testing will need to cover many of the following areas. A migration of this type will need comprehensive testing across all areas, Incentive logic, reports, data integrations, and workflows.
Regression Testing
- Does the new system output the same results as the old? Automation of regression testing results helps here and good preparation of your test cases. A good set of real-world test data should be used to compare old and new systems.
Performance Testing
- Does the new system perform at least as well as, or better than, the old?
SIT Testing
- Do all the old integration points interface with the new systems such as Express Data Loader?
- Do any new integrations that take advantages of the new features, such as API calls, work?
UAT Testing
- While the UI of the HANA and Oracle versions of Incentive Management are very similar there can be a few key differences that users should be trained on and test.
- UAT testing will be particularly important as well for reports.
TRAINING
Ensuring that teams are up to speed with any new functionality and tools such as Embedded Analytics and the Express Data Loader will be essential. If the IT support teams help manage database queries for reporting and Stagehooks, ensure they can adapt to the new architecture.
Also, think about end user and admin level training requirements for the new system. It is important to have a communication strategy for payees when the old system is cut over to the new system.
PLANNING & ASSESSMENT
The first step in any migration will be to assess the current commissions landscape. Undertake a planning exercise and identify what systems you use and any specific customizations that are in place, how they work and how they can be mapped into the new world.
A high-level framework for this could be as follows:
Integration Tools
- Callidus Connect Enterprise
- Custom ODI processes
- Informatica / Landing Pad
- Shell Scripts
Custom SQL Code
- Stagehooks
Reporting
- Crystal Reports
- Dashboards
- Webi Reports
- SQL Code for Reports
- Data Extracts
- Payroll Files
Each system can then be assessed for complexity. Organizations should also be prepared to benchmark their current processes and document this. This gives a real understanding of the positive impact the migration can have to daily timelines.
SUMMARY
While the process of conversion may initially be a daunting project, it should be seen as a positive opportunity to take advantage of the new features and optimizations available in the SAP HANA architecture. In particular, the benefits of moving to cloud native HyperScaler technology will help
to future-proof the system for years to come. Partnering with SAP implementation experts such as OpenSymmetry will help make the transition smooth and provide the most benefits to end users.
Want to discuss the SAP Commissions Oracle to HANA transition with your peers and our team of experts? If so, let us know and we’ll be in touch with event details soon!
Want The PDF Version?
About Us
OpenSymmetry enables clients to achieve greater operational efficiency and get better sales results. We are a global consulting company specializing in the planning, implementation, and optimization of industry leading technology suppliers of sales performance management solutions.
CONSIDERATIONS WHEN REPLACING YOUR SPM TECHNOLOGY SOLUTION
Understanding the challenges companies face when migrating Sales Performance Management (SPM) technology solutions can be a significant undertaking. This paper is designed to provide high-level guidance to stakeholders who carry this responsibility. As OpenSymmetry has helped many companies evaluate and effectively migrate to new technology solutions, we are sharing seven key areas that we find critical to completing this kind of effort.
1. CURRENT STATE ASSESSMENT & FUTURE STATE PLANNING
A critical initial step before migrating to a new SPM solution is understanding how well your current program is performing across people, processes, and technology. From there you can devise a future state vision for how your SPM program should operate. By understanding both current state gaps and what your future state needs look like, you can effectively begin defining requirements while also clearly articulating success criteria. It’s important to recognize that your previous or initial SPM implementation may not have gathered all necessary processes/requirements, so it’s vital to take a fresh, holistic view in this first step.
2. DATA INTEGRATION
One of the most complex and time-consuming requirements is determining how to best leverage current source data feeds to support the new platform. Within the context of your current state assessment and future state planning, the team should review what their reporting, analytics, and any future state compensation elements needs are to ensure a meaningful inventory of data requirements are defined. SPM solutions vary in terms of how data is gathered, translated, and uploaded into the system. Some solution applications may have a standardized format requiring additional configuration, whereas others may have the ability of data field mapping, which provides additional flexibility. The ability to own the data translation from your source systems to the SPM platform is key. Another focus point is to ensure that you evaluate all manual feeds to incorporate automation, as well as any additional error validation processes.
3. HISTORICAL DATA
Migrating historical data is an often-overlooked requirement when moving from one SPM platform to another. To keep costs down and minimize complexity, clients may want to ID only the data that is needed to ensure ongoing management of comp (e.g. payment history) and then transfer detail-level data into data storage to be referenced at a future date. It is important to consider what historical data is needed for the new system for reference on future payments
4. PROCESS IMPROVEMENT
Each SPM solution may require users to interact with the system in different ways. This area may need additional attention, especially as it has the potential to improve processes currently employed to manage sales compensation. Understanding the impact a new system will have on current processes, as well as those who manage the processes, is critical to ensuring a successful launch and ongoing management of core processes. As an example, two of the leading solutions in the market have very different expectations regarding the skills users need to possess to effectively maintain compensation plans and reports and, in some cases, execute the day-to-day activities. Defining expectations of your staff related to the new technology, prior to the project, will ideally give your organization the necessary time to introduce training that ensures effective ongoing management of the program.
5. WORKFLOW
SPM solutions vary widely in their ability to support automated workflow. As a result, there are significant challenges for sales compensation teams related to an SPM migration. Capabilities can range from templates to existing documentation, levels of routing, and even implementation of a stopgap for a payee to accept plan documentation prior to payout. Within the context of your future state definition, capturing and defining areas where automated workflows can be leveraged is a necessary part of the core requirements. Before a new system is deployed, it is important to map these processes out to drive user adoption, leverage the SPM system as an auditable repository, and minimize email management.
6. REPORTING & ANALYTICS
It is critical to develop a holistic vision of information distribution to the various stakeholders and tools used to deliver this content (i.e. static pages vs. dashboards). Similar to workflows, different vendors have various capabilities related to reporting for the end users. Assessing these capabilities against your business requirements is imperative to the success of the roll-out. For example, some vendors require more robust configurations in the system (e.g. crediting logic) to enable specific analytics capabilities, while some solutions, architected specifically for reporting and analytics, have much more robust capabilities. Another area for consideration is the use of the vendor’s reporting solution against your in-house technology stack. Some solutions make it easy to port data into new environments, which could be a consideration in helping to keep the number of reporting tools requiring management to a minimum.
7. DEPLOYMENT
The implementation of a new solution should be designed to minimize the impact on payees and managers. One of the most critical aspects of your effort is assessing how all stakeholders will be impacted and how to mitigate any disruption. It is important to identify upcoming changes for your sales organization, administrators, and other internal partners with a plan in place to offer the steps needed to ensure the best chances for solution adoption.
The first step when considering a new SPM platform is an assessment of your current program and the development of a future state vision. OpenSymmetry offers a no-cost workshop to help you gain an understanding of how your current SPM program performs against your needs and industry best practices, as well as a readout on current solutions in the market.
Leveraging the OpenSymmetry assessment methodology and knowledge of the leading SPM providers, you will be equipped with:
• A current state analysis scorecard
• The framework for a business case to support change
• Contemporary intel on the SPM market and SPM vendor capabilities
• High-level deployment and license cost estimates