SAP Integrated Report: 2020 Targets Met Early

Despite growing four-fold since 2000, SAP emits less carbon dioxide today than it did 18 years ago – and still has advanced ambitions.

Released this week, the latest SAP Integrated Report sets it all out in black and white: In 2017, SAP cut its CO2 emissions by 55,000 tons year over year. That’s a whopping 14%. But even more important: At 325 kilotons, the company’s carbon footprint is once again below year-2000 levels. Back in 2009, SAP had set itself the goal of reducing its global greenhouse gas emissions to the year 2000 level by 2020 – despite strong company growth in the interim. A closer look at the per capita values reveals just how impressive that reduction is: In 2000, SAP recorded 13.9 tons CO2 emissions per employee. Today it’s only around 3.8 tons.

But this improvement doesn’t come by chance. It is the result of a dedicated climate policy that SAP adopted in 2009 and has been following ever since, and it underscores SAP’s commitment to the United Nations Sustainable Development Goal (SDG) 13: “Climate Action.” The policy is part of a holistic management approach that is aimed at harmonizing the economic, social, and environmental performance of a company instead of focusing exclusively on optimizing profit.

The SAP Integrated Report, the company’s “online first” financial report, showcases just how SAP is making that happen. Among other things, the report provides key figures on the financial and non-financial value add of the company and explains the key connections between SAP’s economic, social, and environmental performance.

Where to Invest Efforts?

“SAP’s key lever for a sustainable future is our product portfolio, with which we enable customers to create positive economic, environmental, and social impact. Leading by example and being a trustworthy role model has always been very important to SAP. Our transparent results in the report show that we continue to make great progress in all areas and are turning SAP’s vision and purpose into reality. I’d like to thank all employees for helping the world run better and improving peoples’ lives,” says SAP Chief Sustainability Officer Daniel Schmid.

While the focus is on innovations that help customers become more sustainable, SAP is just as committed to reducing its own greenhouse gas emissions, and has implemented a number of measures in order to achieve this. Currently, SAP’s sustainability strategy is based on the three pillars of avoid, reduce, and compensate:

* Avoid: Emissions are avoided wherever and whenever possible. Substituting business flights with video conferencing is just one example.
* Reduce: SAP has programs in place to increase efficiency in data centers, for example, that scale significantly and not least benefit our customers in the cloud.
* Compensate: SAP compensates for remaining emissions by investing in certified climate projects with high quality standards.

Cornerstone No. 1: The Green Cloud

Switching to electricity from renewable energy sources was a key milestone. Between 2010 and the end of 2013, SAP converted all of its data centers and office buildings to green energy, and at the same time increased the energy efficiency in its buildings, above all in the data centers, by leveraging innovations in server virtualization and air-flow management.

A clear indicator of just how successful that approach was is the power usage effectiveness (PUE) value of its global data center in St. Leon-Rot, which is currently 1.36. As such, the energy required to maintain the SAP facilities is now just one-third of the energy consumed by the servers. This is an ideal value for a data center operating in the highest availability class.

Cornerstone No. 2: Intelligent Mobility

Following the successful establishment of a green cloud, SAP’s climate management is now focusing on reducing the remaining sources of emissions. More than four-fifths of its current emissions are generated in the mobility sector. Among the culprits is commuter traffic, which produced 49 kilotons of CO2 in 2017. That being said, according to SAP’s most recent internal commuting survey, carbon emissions per SAP employee went down by 6.6% compared to the previous year.

SAP supports this development through a number of measures ranging from promoting bicycle use, rail transport, and e-mobility, to the operation of its TwoGo ride-sharing solution, which is open to employees and external drivers alike. Employees are also taking an increasing number of home office days — up 16% in 2017 — which is expected to have further reduction effects.

Air travel currently accounts for more than half of all mobility-related CO2 emissions. To reduce its carbon footprint in this area, SAP encourages the use of telepresence, video conferencing systems, video telephony, and other virtual collaboration technologies. Thanks to such measures, the number of flights remained constant in 2017 despite continued business growth. A reduction in the absolute number of business flights is not expected; as the world’s biggest provider of business software, SAP relies heavily on close contact with its customers and partners, and will therefore continue to depend on a certain minimum level of flights going forward.

Carbon Neutral as of 2025

Notwithstanding the above, SAP has set itself the goal of being fully carbon neutral as of 2025. Again, avoidance and reduction will be key factors in achieving this ambition. Whenever SAP is unable to reduce emissions on its own, it turns to the third pillar in its operating strategy: compensation. This fallback option means investing in CO2 offsets, such as the Livelihoods Fund’s forest restoration program. In return, SAP receives carbon credits from the sponsored offset projects. In 2017, SAP’s offset efforts resulted in total compensation of 160 kilotons of CO2.

SAP primarily uses the renowned World Wide Fund for Nature (WWF) GOLD Standard to select its offset projects. The advantage of the WWF “seal of approval” is that it not only discloses the carbon footprint of the projects, but also makes clear how the projects impact the social environment and the neighboring ecosystems.

By 2050: 85% Less CO2 Along the Entire Value Chain

SAP’s goal to be carbon-neutral by 2025 addresses the company’s internal operational processes. What customers do with SAP products is another matter. In 2017, these so-called product-in-use emissions totaled 9.7 megatons CO2. Thus, looking at the downstream emissions, climate management will be a much longer-term undertaking than minimizing SAP’s internal carbon footprint.

And SAP is tackling the problem head on. In June 2017, it committed itself to reducing all CO2 emissions of the reference year 2016 by 85% by 2050 as part of the Science Based Targets initiative. The first major interim stage is 2025, by which time a minimum 40% reduction is expected.

“Given our cloud strategy, this roadmap is definitely feasible,” says Schmid. “If all goes to plan and we really are cloud-only in 2050, the entire operation of our solutions will take place in SAP’s carbon-neutral data centers. And that in turn will mean less product-in-use emissions.”

The journey continues. http://bit.ly/2G4PRjn #SAP #SAPCloud #AI

SAP FIORI Launchpad Architecture

What Fiori is

SAP Fiori is basically designed to focus on the most common and critical activities such as:

Role-based – what does this mean? It means explicitly designed to break down complex applications into a task-based experience with one central entry point for each user.

Responsive: It adapts to all sizes, devices, versions, and channels to provide a common user experience across all channels.

 Simple: SAP Fiori apps follow what we call the 1-1-3 rule – 1 user, 1 scenario, 3 screens.

Coherent: a user experience with apps that speak the same design language.

Delightful, or instant value – what do we mean by that?

It makes an emotional connection. It allows you to access the most recent version of your backend data via OData services.

All UIs are built using HTML5 and SAPUI5. Now that we have an idea about what is behind Fiori launchpad, we’ll go to the architecture.

The most important thing for us when we look at or want to try to troubleshoot any Fiori issues is we want to understand what kind of architecture we are dealing with.

For example, in Fiori you would have a client that is running on a mobile device or laptop, and you will get a Web-based application that is served from a back-end server, you will have a front-end server that is running SAP Gateway, and you may possibly have a mobile platform in the front as a reverse proxy to deal with mobile devices.

And in your back end, where your data is located, you may have S/4HANA. But in our architecture, in the front, we also have something called the SAP Web dispatcher.

Why do we need the Web dispatcher? Because we need to connect to a different back end that is not the original host of the server.

What does this mean? Imagine you are talking to domain 1 and you want to access data from domain 2.

That is not allowed by the browser – we call this CORS, Cross-Origin Resource Sharing. So to overcome this issue, we use the Web dispatcher.

Deployment Options:

Gateway Central Hub Deployment:

For example, we have the Gateway central hub deployment. What does this mean?

It means that in the front you will have an SAP gateway running the UI5 library, and you have a back-end S/4HANA.

The front end talks to the back end by using an RFC connection, and that way, if there is a product issue, for example, in the library, in the UI5, you will upgrade the library on the front-end server, and you don’t need to touch the back-end server. That’s the beauty of that.

Embedded System Deployment:

With that system, you will have one node, one host – everything running on that node. We call that the embedded system.

Development Central Hub System Deployment:

It offers the same advantages as the central hub. The only difference here is that the services are developed on the front end.

Components Required for Central Hub System:

components needs to be deploy on the front end and the back end :

For example, the components that are required for the central hub deployment on the front end…

* if you are running less than SAP Gateway 7.40, then you need to have what we call GW_CORE and IW_FND
* And on the back end, you need to have IW_BEP. And the SAPUI5 library that you’ll have is 1.28 or higher.
* Now, if you’re running 7.40 or higher, we made it simpler for you. We put everything in one component and that is called SAP_GWFND, and that resides on the front end and on the back end as well.

Components Required for Embedded System:

In the embedded system, they’re constant – they all run on one node. And in that case, you will have the same thing as we said.

If you’re running less than 7.40, then you need all three components running on the same node. But if you’re running higher than or equal to 7.40, then you need SAP_GWFND.

Now that we’ve understood what Fiori and the architecture are, and we know the deployment options that we have.

SAP FIORI Launchpad Building Blocks:

SAP Fiori launchpad is based on the unified shell architecture.

The guiding principle of the unified shell is to have a single platform-independent client-side runtime environment which can be hosted on different server platforms – for example, SAP Gateway or SAP Cloud Platform.

This means that the shell offers unified services with platform-independent interfaces to the hosted apps and shell components. The implementation of these services can utilize different service adapters for the respective platform if they need platform-specific behavior. The visualization of this shell is independent of the shell services.

This is achieved by using a shell renderer that can be replaced by a different implementation. Now, we’ll continue with the building blocks

The apps are embedded in an “application container“. As this is an independent re-use component, the embedding aspect is decoupled from the renderer. The application container can host SAPUI5 components, Web Dynpro ABAP applications, and SAP GUI for HTML transactions.

The shell services and renderers are managed by the central shell container.

It utilizes a runtime configuration which defines the concrete implementations for services, adapters, and shell renderers, as well as global settings like theme, language, system and user data.

The runtime configuration is fed by the following settings:

static configuration settings in the hosting HTML page; dynamic configuration data read from the front-end server during startup and dynamic settings passed as query parameters in the URL. Finally, all described JavaScript components are embedded into a single HTML page.

The SAP Fiori launchpad implementation of the SAP Gateway front-end server contains a standard page called FioriLaunchpad.html. http://bit.ly/2pDolPS #SAP #SAPCloud #AI

Building hybris suite from console-facing the major.minor version 52.0 error

Hi Everyone,

Am very new to SAP Hybris.

While am taking the initial step to extract the hybris commerce suite 6.1 and  setup the environment, I faced the unsupported version error.

While setting up the hybris suite from console, you may face the following error.

Error:

java.lang.UnsupportedClassVersionError: de/hybris/ant/taskdefs/DbDriverValidator : Unsupported major.minor version 52.0

Reason:

This will happen because of Java version Compatibility, which means in your system if your using more than one jdk. This error will occur.

Solution:

Go to your

ControlPanel->Advanced system settings->Environment variables

In the Edit system variable, if your find the text as  path, then click on edit and check if you have more than one jdk exists.

If you found any, then remove those jdks and put only one jdk which is used for building Hybris suite.
Then click on ok.

And Restart your system once.

After completion of Restart, Follow the below steps.

1.Run your hybris suite from console.

2.By setting ant environment by the command in the below path

hybrissuitefolder/hybris/bin/platform: setantenv.bat

3.Now, check the javaversion by giving a command like java -version

4.Once check if the java version is related to your hybris suite for running.

5.If not change your jdk version.

6.If you found that java version is related to run your hybris suite then, do an ant all.

7.And start the hybris server by giving the command as hybrisserver.bat http://bit.ly/2pENB7u #SAP #SAPCloud #AI