You are here
Monday, 7 Mar, 2016
SAP HANA - Impact on SAP Development Teams
Ray Prasad - Architect, Technologies Team
After attending SAP TechEd in October 2015, and presenting a session at the New Zealand SAP User Group (NZSUG) later in the year on this topic, I had requests from both partners and customers for more discussion around the impact of SAP HANA on the future of SAP development teams.
With SAP HANA now taking off as the new ‘digital core’ for the SAP juggernaut, there is no doubt that the impact on existing SAP development teams, who implement and support SAP solutions, will be significant. With the rise of SAP HANA, the ways in which SAP technical teams deliver services to their SAP customers (in-house or external), will need a rethink. Teams and their managers should consider how they can prepare themselves to ensure they remain effective in delivering this new breed of SAP HANA-based solutions.
Looking ahead, SAP development teams will have many questions, such as:
- What new skills and training do we need?
- What development tools should we use and how do we set them up?
- What is our role going to be and what should we focus on?
- How will our team deliver and support HANA-based solutions?
- What happens to traditional SAP development? Is it still relevant?
- How will this align with our organisational goals?
- How will we structure our teams in the future?
- What strategies and methodologies will we introduce or modify to adapt to HANA?
Impact on SAP Development Teams
SAP HANA introduces new technologies and platforms, challenging the status quo. Consequently, existing SAP technical teams will need to look at how they adapt to these new challenges.
The impact on development teams could include:
- The need to acquire new skill sets
- The use of new development & platform tools
- The requirement to establish new strategies and methodologies
- The need to revise team roles and structures.
This article discusses these areas of impact, and highlights the key action-points required for SAP practitioners and their managers to be better prepared and remain effective in delivering new SAP HANA-based solutions to their customers.
The context of this discussion is specific to an SAP technical team and the focus is on a few key areas only. However, the introduction of SAP HANA has a far wider impact on all kinds of organisations (both partners and customers), and deserves its own scrutiny in a broader sense.
Developers Need New Skillsets
In addition to traditional ABAP skills (as in ABAP programming e.g. Workflow, Reports, Interfaces, Conversions, Enhancements, Forms), new HANA development skills are now required in areas such as HANA Modelling and Development, Development Tools, Programming Languages and User Experience (UX) Strategy and Design.
With HANA Modelling and Development capabilities, new ABAP CDS Views and HANA Views can be created for consumption by applications and reports. This provides the ability to push the heavy lifting to the HANA database, rather than using the traditional application layer.
SAP UI5 Applications and HANA Views require new toolsets, such as the SAP Web IDE and Eclipse-based HANA Studio.
More importantly, in order to create an engaging User Experience (UX), greater focus and design effort is now required in creating new applications. This increased focus on the user requires new skills not universally known by current ABAP practitioners. To assist, SAP is providing prototyping tools such as BUILD to improve the quality of newly created applications, as well as facilitate them being created in an intuitive and responsive manner.
In order to achieve the above, and shift into the new development world of SAP HANA, team members need to re-assess their current skill levels and acquire new ones. In turn, managers should review their strategies and make sure they are investing in the necessary training to ensure their teams are prepared for SAP HANA.
New Roles and Team Structures
Traditionally, when creating ABAP applications, a single developer covered multiple skill areas. With this shift in the developer skill set required to better meet the demands of HANA enriched solutions, new roles and team structures may be required to collaborate on projects and support responsibilities. For example, it might make sense to separate the design and development elements of HANA applications, based on specific individual and team strengths.
Traditional ABAP skills are still required, with the addition to new capabilities such as Personas and ABAP CDS Views. These could be responsibilities of the ERP backend developer.
The HANA Modelling and native HANA development could be completed by a HANA Data Modeller or HANA Developer.
Integration Architects now require added cloud-based integration capabilities, in addition to traditional process orchestration skills. This is leading to new roles being created, such as ‘Cloud Integration Architect’.
Other areas that may require new team roles include Business Intelligence and Cloud Technologies. Of course, this analysis only mentions a few areas, and managers will need to consider the broader impact the ever-changing world of SAP Technology is likely to make to their teams.
In summary, we recommend that managers review their teams and skills, both established and latent, and look to match these against the SAP roadmap, in order to effectively deliver and support HANA-based SAP Solutions in the future. This may include splitting responsibilities within teams across ERP backend, HANA specific development and UX, in order to better plan and deliver such solutions. Organisational size, existing structures and strategies and customer demand will impact on both what is feasible and when the optimal time to introduce change is.
New Strategies and Methodologies
SAP Project and Support Teams establish strategies and methodologies to deliver services and solutions to their customers. This ensures standards and protocols are followed, in order to deliver consistent and quality solutions in an organised and measurable fashion.
With the new SAP HANA development capabilities, and deployment options (On-Premise, Hybrid or Cloud Platform), every aspect of these strategies and methodologies needs to be reviewed to consider whether they are still effectively delivering services and solutions to customers.
The architectural and deployment changes with migration from On-Premise to Hybrid or the HANA Cloud Platform (HCP) require new governance, roles, responsibilities and security strategies.
Creating solutions via the HCP requires an assessment of existing strategies around Change and Lifecycle Management, Testing, Training, Hardware, Security and Integration.
With new developer skills and team structures, updates to operational guidelines are needed to establish clear reporting, delivery roles and responsibilities. Documentation that covers development standards and naming conventions for the developers needs to include new HANA development objects. New UX strategies and design methodologies need to be established to cover the development of SAP Fiori/SAPUI5 applications.
It must be noted that strategies and methodologies should align with organisational strategies and methodologies. Organisations that deliver SAP HANA solutions need to be clear on how they approach projects and how they measure whether they have been successful or not. Apart from these technically focused strategies, wider organisational strategies need to be reviewed, by both SAP Partners and Customers, to consider the organisational impacts of SAP HANA.
This article has covered how SAP HANA impacts on the key focus areas for SAP Technical teams. The impact is, of course, far greater than this and is relevant across any organisation that implements or interacts with SAP.
SAP HANA is a catalyst for organisational change, and must be evaluated as a platform enabling organisations to gain a competitive advantage in the ever changing world of digital technology.
As Partners, the better prepared we are, the better we can prepare our customers and deliver better quality HANA-based solutions.