Archives 2020

SAP Hana XSA enables different deployments in one single Hana database. However, companies have to consider various security guidelines to ensure diligent access management

Hana XSA makes different deployments (separated development environments) in one single Hana database possible. Every application operates in a separate container and in its own environment, meaning that problems in one application do not affect the others.

Companies have to consider various security guidelines to ensure diligent access management. SAP Hana XSA Cockpit orchestrates the solution, managing users, access and security configurations (e.g. tenants or SAML identity providers).

In user management, admins can create new accounts or convert existing Hana users to XSA users. Access is granted by so-called role collections. For example, for user management the role collection XS User Admin is necessary, and for role management users need the role collection XS Authorization Admin. For viewing only, standard role collections XS Authorization Display and XS User Display are available. Accountability is guaranteed by Hana’s auditing. It is a Total new thing in the SAP HANA method.

How SAP Hana XSA works

The basic structure of SAP Hana

XSA consists of organizations and spaces. In spaces, users can develop applications. Organizations are containers meant to structure the spaces. Developers operate in spaces. After the user master data have been created, developers are assigned spaces and access rights. There are three types of roles: Space Manager (space management as wells as evaluating applications); Space Developer (implementing, activating and deactivating of applications, matching applications to services); and Space Auditor (evaluation of applications and role management).

Regarding organizations, the role Organization Manager enables user management and maintaining the spaces in an organization. Protection Rule in SAP Education

The central development platform for SAPUI5 applications is SAP WebIDE (integrated development environment). It supports various programming languages like Java, Java Script, SAPUI5 HTML5, Node.js and more. WebIDE can be used for on-prem applications (Hana XSA) and as central development application for SAP Cloud Platform (Cloud Foundry).

To leverage WebIDE, developers have to be assigned corresponding access rights in SAP Hana XSA. Two standard templates already exist for this purpose: WebIDE Developer and WebIDE Administrator. To authorize users for application development, a role has to be created from the template WebIDE Developer. Here is Protection Rule in SAP Education

To implement access rights in customized solutions, companies have to define their own rules. They can also integrate actions into customized solutions that can be recorded using Hana’s auditing (category application auditing).

Using the new SAP MaxAttention Analytics and Data Management portfolio, SAP Premium Engagement customers can now experience X+O Analytics Consulting services to further enhance their organisation’s business improvement process. The brand new offering aims to empower customers to drive innovation by providing authoritative guidance in leveraging the combined power of X-data (experience data) and O-data (operational data) with SAP analytics technology.

Ever since the acquisition of leading experience management company by SAP in 2018, the global solutions provider has been encouraging and educating customers and prospects all over the world on the importance of bringing O-data together with X-data in transforming customer engagement and driving business goals. Combining these two sets of data eliminates what Qualtrics calls an “experience gap”—the disconnect between how a company perceives its product and/or service performance and how customers actually feel about it.

X+O Analytics: An Integral Part of Business Improvement Process

SAP has been the leader in helping companies gather O-data from enterprise applications in managing their businesses. O-data is data a type of strategic data collected from day-to-day operations that include internal control and operational environment information such as:

• customer information (the number of new or lost customers, the number of website visitors)
• workforce information (employee attrition, employee promotion history, and employee performance rating)
• financial information (sales figures, profitability)
• inventory turnover
• information on direct competitors

Obtaining these data is the first step to understanding the experiences of customers. The second step is gathering X-data which is the customer’s “side” of the story. In a blog post, Karthik Thirumalai, Vice President of Analytics and Insight Services at SAP Customer Success, explains the importance of this next step in designing a company’s business improvement process.

With the latest X+O Analytics Consulting service from the SAP MaxAttention team, SAP Premium Engagement customers will be able to successfully develop an X+O Analytics capability that seamlessly integrates into their existing SAP analytics landscape. SAP MaxAttention experts will help in efficiently gathering O-data from SAP information systems to compare against and combine with the outcomes of X-data tracking. 

The standardised specialist service will be delivered in a phased manner across SAP MaxAttention’s Prepare, Discover, Design and Deliver phases, according to Thirumalai. Furthermore, the X+O Analytics service also has touchpoints with other SAP services like the Quick Start Service for Experience Management Solutions that help develop and validate an Experience Management (XM) program strategy.

In the UK, ISG’s research found that the majority of service providers have been able to support their clients during the coronavirus pandemic by enforcing business continuity plans and finding ways to deliver essential services. But ISG said there was minimal or negative growth in the UK for SAP S/4 Hana, specifically among large accounts. It predicted that more organisations will be looking to implement S/4 Hana Cloud.

Given that cost reduction will be a primary enterprise focus, ISG said it expected the service providers that offer competitive pricing (at less cost) or an innovative pricing model (such as consumption-based) will have an extra edge over their competitors. According to the ISG report, managed services will increase for SAP applications because the client enterprises will want to optimise their cost model and service delivery efficiency for managing their SAP architecture.

Negotiate outcome-based pricing

In the report, ISG predicted that as enterprises navigate through the uncertainty of the pandemic and brace for alignment across regulations defined for Brexit completion, they will demand different types of outcome-based pricing and services from their service providers. Some of the pricing models explored are consumption-based, gain-sharing, risk-sharing and shared fixed reward, where a fixed fee amount is decided by both the provider and the client. Any delay in execution results in a reduced fee, while any increase in execution cost will add to it.

According to ISG, service providers will continue to focus on meeting their employees’ remote working needs to ensure business continuity, which will mean the use of data analytics for faster and efficient decision-making.

Improve productivity with service provider AI

Assessing the SAP S/4 Hana service providers’ market, ISG found that service providers were relying on tools that use bots, automation, artificial intelligence (AI) and machine learning (ML) to deliver application management services. These bots are generally used for managing repetitive tasks and repeatable business processes, as well as fixing the more straightforward user support queries.

ISG found that the AI and ML deployed by SAP service providers was being used to resolve tickets automatically, learn from tasks in the IT landscape, predict application failures and perform fixes as required. The report’s authors found that most providers have holistic application management frameworks that enable better productivity, throughput, quality and reliability. 

Wait for improved integration

SAP has recognised that customers will face challenges and costs when they upgrade to S/4 Hana. It has set out a roadmap to simplify integration, in a bid to lower the transition cost of moving from ECC to the S/4 platform.

Until 2025, SAP customers have to migrate to S/4 Hana. There’s an easy way to integrate customer and vendor master data, saving time and money.

S/4 Hana is SAP’s new business software suite with real-time ERP based on in-memory database Hana. The ‘S’ stands for simple; simple pertaining both to a simpler data model and better usability, but not pertaining to the implementation!

Simple or not, customers have to implement S/4 Hana sooner or later. SAP announced sunset support for ECC 6.0, and if customers want to stay competitive after 2025, they will have to migrate to the new software generation.

There are different answers to when and how, but everyone can agree on one thing: The implementation of S/4 Hana is not going to be simple. It will take a lot of time and effort to make it work. Switching to S/4 Hana is more than an upgrade or a database migration – it affects the entire corporate IT landscape.

How to get to S/4 Hana

It’s nothing new that two main roads lead to S/4 Hana, better known as greenfield and brownfield.

Greenfield means starting from scratch – planning entirely new business processes and only keeping the data. Brownfield means optimizing existing processes and data to retrofit them for S/4 Hana.

Whether companies decide on greenfield or brownfield, the quality of master data is important. Ideally, the standardization and harmonization of master data is part of the new process design.

Opting for a brownfield approach usually means arriving at S/4 Hana faster, since existing processes are transferred to the new system. However, brownfield migrations require high master data quality. There are also some typical pitfalls regarding customer-vendor integration or customized analysis.

Master data management in S/4 Hana

For example, Company Y is both customer and vendor to Company X. Up until now, Company X had to create two different data sets for Company Y. In S/4 Hana, however, Company Y is simply a business partner but with two roles: customer and vendor. While assigning different roles, companies only have to manage one set of master data.

Consequently, the two different data sets in the legacy SAP systems have to become one in S/4 Hana. Technologically speaking, this is an effort not to be underestimated. However, there are already solutions on the market (like ZetVisions SPoT) that can reduce that effort significantly.

These solutions have one major benefit: customers can enjoy the best of both worlds. Customers can create one master data set for their business partner with the solution while still being able to work with the traditional classifications of the ERP system. Companies therefore optimize their master data before migrating to S/4 Hana, saving time and money in the process.

Quite apart from the wider world itself going continuously 24×7 in the face of globalisation and ubiquitous interconnectivity, the software world has adopted more defined approaches to continuous methodologies over the last decade.

Key among the continuous continuum is Continuous Deployment (CD), Continuous Integration (CI) and Continuous Testing (CT). 

Continuous Testing (CT) aka ‘shift-left testing’ is the practice of post-production testing carried out by developers and operations teams in order to uncover performance issues associated with applications (and data systems) that may arise due to a) unplanned user behaviours b) unplanned data-flows and system demands c) other unplanned (unforeseen would be a better term) elements of software performance.

With its fairly meaty total software stack, SAP has of course been using various continuous approaches for some years.

This year sees the German softwarehaus up its continuous play by forming a stronger integration with Tricentis, a Continuous Testing (and, crucially, an Automated Testing) specialist.

SAP will re-sell Tricentis testing solutions as SAP Solution Extensions. 

The partnership also includes an OEM agreement in which Tricentis’ core model-based test automation capability will be embedded in SAP Enterprise Support  to offer automated testing in SAP Solution Manager and SAP Cloud ALM.

As the volume and velocity of SAP updates have increased in recent years, customers are finding their traditional testing methods require significant manual effort and can be a challenge to deploy in a timely manner. 

With a next-generation continuous testing platform, businesses using SAP solutions can unleash the full power of the intelligent enterprise,” said Sandeep Johri, Tricentis CEO. “Tricentis is partnering with SAP to help customers keep up with the rapidly increasing pace of SAP releases. With this partnership, customers can turbocharge their SAP releases with a modern, continuous testing platform that helps to eliminate testing approaches that are not only slow and costly, but ultimately ineffective.

SAP plans to introduce the following new software elements:

• SAP Change Impact Analysis by Tricentis – For AI-powered impact analysis that identifies potential risk to business processes after an SAP software update. 
• SAP Enterprise Continuous Testing by Tricentis – Automates around 90% of a customer’s end-to-end business process tests – spanning SAP and third party tests.
• SAP Load Testing by Tricentis – To optimise the SAP user experience with scalable, on-demand performance testing for SAP Fiori® and modern cloud applications.

SAP’s next generation Service Parts Management

SAP has a long and strong journey into the automotive aftermarket industry showing that it is an important market segment. Innovation within the SAP service parts planning (SPP) solution has been ongoing for decades and product development was tightly done in cooperation and collaboratively with several of the larger automotive OEMs companies in the Automotive Aftermarket.  In 2018 it was decided to bring  Service Parts Planning Solution into S/4HANA as part of the core Digital Supply Chain solutions to enable the Intelligent Enterprise Suite based on S/4HANA

Now, we are happy to announce that SAP S/4HANA Supply Chain for extended Service Parts Planning – one major pillar for service parts management solutions – will be launched as part of SAP S/4HANA 2020. The availability of the Service Parts Planning in S/4HANA means a supply chain planning offer for companies that distribute large volumes of aftermarket service parts to numerous stocking locations, and, at the same time, it natively integrates with demand captured, order management and execution processes making Service Parts Management an end to end solution.

The core areas of Service Parts Management sit on the intelligent suite, interoperating with SAP’s Industry Cloud access to vertical solutions that leverage SAP Cloud Platform supporting customers to accelerate business operations while balancing cost efficiencies with advanced technologies. Additionally SAP Service Parts Management has the possibility to leverage access to the Unified Business Network extending business processes beyond the core business, facilitating the seamless exchange of data and insights across businesses and geographies to drive greater levels of collaboration and agility with suppliers.

Finally, being in SAP S4/HANA allows Service Parts Management to benefit from SAP S/4HANA business technology platform main path of innovation with a simpler architecture and eliminating master data redundancy.

Therefore, SAP’s next generation Service Parts Management leverages business processes applications and technology making available to the aftermarket players an enterprise-wide functionality covering end to end processes in an innovative platform.

The SAP solution portfolio evolved immensely from the introduction of financial accounting (RF) and inventory verification and management (RM) in 1975. From R/2 evolving into R/4, Business Suite and now SAP S/4HANA, the software evolved to fit different business models supported by end-to-end processes and best practices.

Specific Portfolios are offered already to different industries – see the automotive example – covering end-to-end processes with cross-digital integrated capabilities.  SAP announced one more step supporting industries by announcing the Industry Cloud. This is an innovation space for SAP, partners and customers to provide both industry cloud solutions and applications that complement the intelligent suite using the Business Technology Platform.

SAP Hana XSA enables different deployments in one single Hana database. However, companies have to consider various security guidelines to ensure diligent access management.

With Hana 1.0 SPS11, SAP Hana Extended Application Services, Advanced Model (SAP Hana XSA) was introduced. This model is based on a microservices approach and enables the modulization of software development.

Hana XSA makes different deployments (separated development environments) in one single Hana database possible. Every application operates in a separate container and in its own environment, meaning that problems in one application do not affect the others.

Companies have to consider various security guidelines to ensure diligent access management. SAP Hana XSA Cockpit orchestrates the solution, managing users, access and security configurations (e.g. tenants or SAML identity providers).

How SAP Hana XSA works

The basic structure of SAP Hana XSA consists of organizations and spaces. In spaces, users can develop applications. Organizations are containers meant to structure the spaces. Developers operate in spaces. After the user master data have been created, developers are assigned spaces and access rights. There are three types of roles: Space Manager (space management as wells as evaluating applications); Space Developer (implementing, activating and deactivating of applications, matching applications to services); and Space Auditor (evaluation of applications and role management).

Regarding organizations, the role Organization Manager enables user management and maintaining the spaces in an organization.

Any changes of organizations or spaces are recorded in trace files on the operating system that can be analyzed with e.g. Hana Database Explorer.

The central development platform for SAPUI5 applications is SAP WebIDE (integrated development environment). It supports various programming languages like Java, Java Script, SAPUI5 HTML5, Node.js and more. WebIDE can be used for on-prem applications (Hana XSA) and as central development application for SAP Cloud Platform (Cloud Foundry).

To leverage WebIDE, developers have to be assigned corresponding access rights in SAP Hana XSA. Two standard templates already exist for this purpose: WebIDE Developer and WebIDE Administrator. To authorize users for application development, a role has to be created from the template WebIDE Developer.

The US government is urging SAP customers to patch a critical vulnerability published earlier this week, which could affect as many as 40,000 customers. 

Released as part of the software giant’s July patch update round,it affects the SAP NetWeaver Application Server (AS) Java component LM Configuration Wizard.

According to an alert from the Department of Homeland Security’s Cybersecurity and Infrastructure Security Agency (CISA), the bug is introduced thanks to a lack of authentication in the component.

“If successfully exploited, a remote, unauthenticated attacker can obtain unrestricted access to SAP systems through the creation of high-privileged users and the execution of arbitrary operating system commands with the privileges of the SAP service user account (adm), which has unrestricted access to the SAP database and is able to perform application maintenance activities, such as shutting down federated SAP applications,” it explained.

“The confidentiality, integrity, and availability of the data and processes hosted by the SAP application are at risk by this vulnerability.”

As SAP NetWeaver AS Java supports a large range of SAP applications, the potential impact is severe. These include: SAP Enterprise Resource Planning, Product Lifecycle Management, Customer Relationship Management, Supply Chain Management, Supplier Relationship Management, NetWeaver Business Warehouse, Business Intelligence, NetWeaver Mobile Infrastructure, Enterprise Portal, Process Orchestration/Process Integration, Solution Manager, NetWeaver Development Infrastructure, Central Process Scheduling, NetWeaver Composition Environment, and Landscape Manager.

Onapsis Research Labs, which discovered the vulnerability, named it RECON and warned that the CVSS 10.0 bug could affect more than 40,000 global SAP customers. It could allow remote attackers to steal PII from employees, customers and suppliers, delete or modify financial records, change banking details, disrupt operations and much more, the vendor claimed. “The business impact of a potential exploit targeting RECON could be financial loss, compliance violations and reputation damage for the organization experiencing a cyber-attack,” it added.

The buzz around SAP Data Hub has quieted down significantly since it was first announced. Why is that?

Some time ago, someone advised me to stop focusing so much on SAP Data Hub. When former SAP executive Franz Faerber first presented the idea during a Sapphire Now Conference in Orlando,  for the possibilities that Data Hub promised. The core idea: Customers wouldn’t have to move their data anymore, ever. The data itself is not moved but stays in silos. If an app needs to access the data stored in a different app, there’s no copy and paste, but a reference to the other app instead. Meanwhile, the app requesting the data ‘feels’ like it has stored it itself.

For this system to work, the app storing the data has to take care of data processing and structuring for the app requesting the data, since the information itself cannot be moved. The requesting app will suffer no consequences, but the storing app could. If users request too much data, workload increases drastically, and the app’s server uses its resources solely on requests.

No luck with SAP Data Hub

SAP Data Hub has a great underlying concept, but SAP missed by a mile on its execution. A server that does nothing all day but fielding and complying with data access requests from apps and systems soon becomes worthless. Nobody knows how many resources the core concept of SAP Data Hub would require in practice. On paper, the concept is brilliant, but in reality, it becomes unmanageable.

SAP therefore still has a lot of work to do before it will have completely harmonized and consolidated the data complexity in ERP systems, in the cloud and on prem.

SAP Data Hub is a data sharing, pipelining, and orchestration solution that helps companies accelerate and expand the flow of data across their modern, diverse data landscapes.

SAP Data Hub provides visibility and access to a broad range of data systems and assets; allows the easy and fast creation of powerful, organization-spanning data pipelines; and optimizes data pipeline execution speed with a “push-down” distributed processing approach at each step.

SAP Data Hub meets the governance and security needs of the enterprise, ensuring that appropriate policy measures are in place to meet regulatory and corporate requirements.

SAP Data Hub accelerates and expands your data projects by easily and quickly creating powerful data pipelines in a single, visual design environment

In a single design environment, data stewards can easily and quickly create powerful data pipelines that access, harmonize, transform, process, and move information from a variety of sources across the organization. Pipeline creators can easily activate powerful libraries for computation or machine learning, for example; rapidly connect data of a wide variety of types, such as social media, customer, and product information; and leverage existing processing investments, such as capabilities in SAP HANA, Apache Hadoop, SAP Vora, or Apache Spark. Pipeline models can be easily copied, modified, and re-used to accelerate pipeline deployment and leverage best practices.

The Harvard Business Review ran an article in 1990 by management consultant and former Massachusetts Institute of Technology computer science professor Michael Hammer titled “Reengineering Work: Don’t Automate, Obliterate.” Hammer, recognized as the seminal theorist of reengineering, the consultant-driven discipline of streamlining work processes, encouraged businesses to radically restructure rather than rely on information technology to automate work.

This proved impossible. While the 1990s is now viewed as an epoch of business reengineering, the revamp of work processes advanced hand in hand with the rise of centralized corporate IT, enabled by enterprise resource planning (ERP) software.

The 2020s, on the other hand, appear poised for the final takedown of monolithic business IT in response to a new revolution in work processes spurred and enabled by digitization. IT managers in the chemical industry, among the first industries to opt for ERP systems, are preparing for a new wave of change in business management software.

To understand the likely changes ahead, it helps to look back at the provenance and evolution of IT systems currently in operation at most chemical companies.

The computing infrastructures that emerged some 30 years ago supported efficiency gains, the kind also targeted by business reengineering. But ERP software installations also caused years-long headaches for many companies as they converted from hodgepodge mixes of software to monolithic IT systems covering most financial aspects of business and plant operations.

During this period, SAP, a German software firm started by former IBM engineers, rose to prominence in ERP. Starting with its first customer, the UK’s Imperial Chemical Industries, SAP swept the chemical sector. By the early 2000s, many major companies had lashed their operations to the firm’s R/3 software.

By today’s standards, the IT platforms of the early 21st century are museum pieces. Cloud computing, artificial intelligence, and big data have fundamentally changed IT and the workplace.

SAP and other major vendors of ERP software, including Oracle and JD Edwards, have introduced successive generations of their products over the years that chip away at the monolithic, comparatively lethargic control of early IT architectures. In the process, a modular approach to IT has emerged in which specialized software for specific work functions can be added to a centralized, often multivendor network of business management software with an ERP system at the core.

“Enterprise resource planning has evolved far beyond its original purpose and scope,” the consulting firm Gartner writes in a report issued last year. “It now represents different things to different organizations, but in all cases is no longer focused on ‘resources’ or ‘planning.’ ” The view is echoed by Forrester, another consulting firm, in a recent report: “Today, we see the beginning of a new era of operational systems that are so different that calling them ERP no longer makes sense.”

Guay notes that ERP vendors have partnered with and acquired specialized software providers to offer hybrid networks. SAP, for example, acquired SuccessFactors, a cloud-based human resources management services provider, and now offers the service as an adjunct to its core software.