My Inbox App: Tile Error

Introduction
This blog is especially for configuring My Inbox App. These details are about to setup the configuration for My Inbox App.

Problem:
After configuring My Inbox App from Launchpad Designer, have faced this issue in our Fiori Launchpad.

To resolve this issue, have to implement SAP Note 2348671 and perform following steps;

1. Execute transaction code SPRO

2. Click on SAP Reference IMG or Press F5

3. Navigate to the structure and Execute Manage SAP System Aliases as shown below by clicking on the time/green check icon:

4. Click on Create System Alias icon

5. Now define a new system alias and change the Software version from DEFAULT to /IWPGW/BWF as shown below:

6. Then Go to TCode Activate and maintain services.

7. Click on Find option and search the TASKPROCESSING.

8. Click on ZTASKPROCESSING version 2.0

9. Check System Alias and click on Remove System Alias.

10. Click on Add System Alias.

11. Fill the properties as shown below, give SAP System Alias as you have defied in your 5^th step and save it.

12. Execute Cache Clearing Programs.

13. Then go to Launchpad, load My Inbox App.

Conclusion:

See the tile error has gone now.


Should you have any further query, please let me know how I can help.
Thanks for reading my post.
Regards,
Muhammad Hassan Alam Khan


Source: https://blogs.sap.com/2019/01/29/my-inbox-app-tile-error/

Extending Fiori Apps in S/4HANA using the Adaption Transport Organizer

During one of my recent S/4HANA implementations I had to extend a standard SAP Fiori App (Manage Supplier Quotations) with an additional input field. Never ever had I thought this could be so easy!
During this blog I’ll walk you through:

• Setting up the Adaption Transport Organizer (ATO)
• Extending a standard Fiori App (Manage Supplier Quotations)

Setting up the Adaption Transport Organizer

To setup the Adaption Transport Organizer I followed the official documentation which can be found here.
First we have to create 2 local packages in our system (I chose to stick with the ones proposed in the official documentation):

• $YATO_KEY_USER_LOCAL
• $YATO_KEY_USER_SANDBOX

Next launch transaction S_ATO_SETUP to start the actual configuration. Enter following details:

• Local and sandbox package
• Prefix and sandbox prefix

After entering the details, start the configuration using button “Setup with specific data”.

Afterwards the red light should turn green:

This concludes the configuration of the Adaption Transport Organizer.

Extending a standard Fiori App

To be able to continue, you first need to make sure that you’ve activated following Fiori Apps in the system:

• Custom Fields and Logic (documentation)
• Configure Software Packages (documentation)
• Register Extensions for Transport (documentation)

All these apps are only available in a technical catalog, so you’ll have to create a custom business catalog and group to gain access to these tiles.

Adding a custom field to the data model

In our example we’d like to add a custom field in the item section of the Supplier Quotation to enter the supplier material number.
Open the Custom Fields and Logic app to add a custom field to the data model.

In the popup enter details for the custom field you’d like to add (in our case the supplier material number) and click the Create and Edit button.

In the next screen, switch to tab UIs and Reports and enable usage in following components:

• Manage Quota Extensibility Model
• Supplier Quotation Item
• Supplier Quotation Item Enhanced
• Supplier Quotation Item Enhanced Consumption View

To find out what you need to extend for your app, you need to review the section App Extensibility of official app documentation. (For the Manage Supplier Quotation app, the documentation can be found here)


Next, save the custom field data using the Save button in the bottom of the screen

After everything is saved, the Publish button will be available. Click this button to actually activate the extension.

Now you’ll have to wait until publishing is finished, this can take a while. (In the background the system is now extending tables, CDS views, structures, …)

The custom field is now availble in the app and is automatically input ready / display only based on the mode the app is in (display / change). It might be possible that you need to add the field to the screen using the configure button in top of the item table.

Configuring a Software Package

As you might have noticed, our extension is now created in the local package we assigned to the Adaption Transport Organizer and not yet registered to a transport. To be able to register our extension to a transport we first need to configure a software package.
Open up the Configure Software Packages tile and click the Add Registration button.

Search for your desired package to hold the extension(s), to add it to the list of registered packages.

Next, assign a transport to the package (or enable automatic request / task handling).

The package can now be used to hold the extension we created.

Register the extension for transport

Now we can finally register our extension to the package and transport, to move it through the landscape.
To do this, open up the Register Extensions for Transport app, select the extension and click the Reassign to Package button in the bottom of the screen.

Select the package we registered earlier and wait for the process to complete.

Once the assignment is finished you should see that the extension is now transportable, you can now release the transport to move the extenion(s) through the system landscape.

This concludes the walkthrough on extending standard Fiori Apps using the Adaption Transport Organizer, which was quite easy once you get a hang of it. Hope this saved you quite some time. As always I’m open to your feedback!



Source: https://blogs.sap.com/2019/01/29/extending-fiori-apps-in-s4hana-using-the-adaption-transport-organizer/

Fiori for S/4HANA – Calling GUI & Web Dynpro ABAP without opening a new tab

Latest Update: Addendum added on how to open a specific app in explace as a user 
It can be a lot of fun to get your hands on a new release of software and try out new possibilities!  Some of the happy additions to SAP S/4HANA 1809 (SAPUI5 1.56) include a much easier way to configure Fiori Launchpad, and some new options for smoothing the user experience, such as a way to avoid opening a new tab whenever you call a classic app (i.e. a SAP GUI transaction or Web Dynpro for ABAP application).  In this blog you will learn how to take advantage of both of these new options.
Prior to SAP S/4HANA 1809 , one of the less agreeable parts of the SAP S/4HANA User Experience for some users was the proliferation of web browser tabs and windows whenever you used classic apps, i.e. SAP GUI for HTML transactions and Web Dynpro for ABAP applications, alongside SAP Fiori apps and the Fiori launchpad.  This was due to a navigation technique known as explace navigation. In SAP S/4HANA 1709 you could avoid this behaviour for Web Dynpro for ABAP applications only. Starting with SAP S/4HANA 1809, you can avoid this behaviour altogether, by configuring certain Fiori launchpad parameters to swap to inplace navigation – i.e. opening the classic app in the Fiori content area, just like a SAP Fiori app.
Learning how to do this will also give you the opportunity to explore the new way of setting Fiori launchpad parameters in an ABAP configuration table provided as of SAP S/4HANA 1809.
To do this you will need to understand:

1. Explace vs inplace navigation
2. Where to find Fiori launchpad parameters and their values
3. How to use the new Fiori launchpad configuration approach
4. What to watch when testing the new approach

The good news is it’s quite easy to do this. It will probably take you longer to read this blog than to make the change.
IMPORTANT:
Some of the previously available options for setting Fiori launchpad parameters have now been deprecated as of SAP S/4HANA 1809 and should not be used anymore.

• Setting parameters in a Launchpad Configuration File – deprecated
• Setting parameters in the FioriLaunchpad.html file – deprecated

You will find the deprecation confirmed in the Fiori Launchpad Administration Guide in section Configuring the Launchpad subsection Alternative Ways of Setting Parameters.

Explace vs inplace navigation

Explace navigation simply means that whenever you navigate to a classic app it opens in a new browser window or tab.  Classic apps include SAP GUI for HTML transactions and Web Dynpro for ABAP applications. This includes navigation from a tile or from within a Fiori app.
You can see how this works in this brief example. Here you see a screenshot from a SAP S/4HANA 1809 Fully Activated Appliance trial system.  You are logged on with a provided demo user (any demo user will do). When you select a tile, button, or link that launches a classic app, a new tab is opened.
TIP: If you need to confirm whether an app is a GUI transaction or Web Dynpro for ABAP application just use the About Icon in the Me Area as explained in Fiori for S/4HANA – Finding the technical Name of an app Or you can also read the launchpad url parameters once you open the app – the keyword sap-ui-tech-hint should tell you if its WDA or GUI.

In the new tab you see the GUI transaction displayed within the Fiori shell and with the Fiori Visual Theme applied.

Once you finish what you are doing with this transaction, you might press the Home icon to return to the launchpad. This will close the transaction normally.  Here you might see a standard data loss protection warning if you have entered some data before pressing Home.

If you answer Ok to get past the warning, you now have 2 web browser tabs with 2 home pages and need to manually close the 2^nd tab.

In most previous versions of SAP S/4HANA explace was the only option available for classic apps. This was due to some technical restrictions around use of the SAP Fiori shell with these classic technologies.
The user experience problem with the explace approach is the user has to be careful to close windows/tabs when they have finished using the app.   If you open a few different apps you can end up with a confusingly large number of tabs.  Since each tab gives access to the Fiori shell you can also use the Home icon to return to the home page which opens in that same browser window/tab. This can quickly result in multiple tabs showing the Fiori launchpad in multiple states.  If you have too many users with lots of tabs and apps open at the same time can contribute to performance degradation, and other side effects.
Explace navigation can also give users the impression of a slow system. With explace navigation,  everytime a new tab is opened for a GUI transaction the browser needs to reload the NWBC runtime libraries required by SAP GUI for HTML. With inplace navigation runtime libraries are loaded only once.
Inplace navigation simply means that when you navigate to an app it opens in the current browser window and tab. This is always the behaviour for Fiori apps.
With SAP S/4HANA 1809, all classic apps can use the inplace option as well. For older releases, it is possible to use inplace navigation for Web Dynpro for ABAP applications only in SAP S/4HANA 1709.  Inplace navigation for classic apps is not available at all for SAP S/4HANA 1610 or earlier.
NOTE: There are a few exception scenarios that still use explace navigation even when inplace navigation is in place.  When users navigate to Web Dynpro ABAP applications or SAP GUI transactions through:

• links in Notifications,
• in the Me Area, or
• via intent-based navigation triggered by Web Dynpro ABAP applications

Where to find Fiori launchpad parameters and their values

You can find the Fiori launchpad parameters relevant to your SAP S/4HANA release in the SAP Fiori Launchpad Administration Guide in the SAP Help Portal.

You will find a table listing all the parameters in the section Configuring the Launchpad and subsection Launchpad Configuration Parameters.
There are quite a lot of parameters now available so you will either need to scroll to each page or use the Show <x> entries option to adjust the number of entries shown. You can also search for a specific parameter if you know it already.  You will find all of these options just above the table.

The simplest option is to search on keyword INPLACE (or inplace – the search is not case sensitive) and you will find the parameters with short key NAVIGATION_GUI_INPLACE and NAVIGATION_WDA_INPLACE.  It’s this short key you will need to use the new Fiori launchpad configuration approach.

How to use the new Fiori launchpad configuration approach

The new Fiori launchpad configuration approach uses an ABAP configuration maintenance view to set the parameters. This change is intended to be made by an administrator.  The change is accessed via 2 transactions depending on your scope of change:

• Use transaction /UI2/FLP_CUS_CONF to change FLP Configuration parameters in current client only
• Use transaction /UI2/FLP_SYS_CONF to change the FLP Configuration parameters system-wide

Changes to the tables can be transported to other clients/systems using ABAP customizing request or workbench request respectively.
One of the advantages of using this new approach is the ease of changing these settings so you can:  try out the new navigation temporarily; test it out to understand the difference; and change it back again until you have a decision on which way forward.  This can give you the time to discuss the pros and cons for of changing the navigation with your business stakeholders & other interested parties.  Your organizational change management and support teams might also need to prepare some communications to explain the change to users before you implement it in your productive system.
TIP: One possible disadvantage of this new configuration approach is that the settings apply to all users.  If you want to apply Fiori launchpad configuration parameters to only selected users, then use the alternate option for Setting Parameters in a Target Mapping.  You can then assign the target mappings to the user’s security roles.  Most customers use a mix of setting parameters for all users and setting parameters for selected users only.
You can experience the new Fiori launchpad configuration approach by logging on to SAP GUI as an administrator (e.g. using SAP Logon) and going to transaction /UI2/FLP_CUS_CONF.  By default the table is empty, i.e. SAP default values are applied to all launchpad parameters.  You only need to maintain parameters you want to override.

Toggle the Change/Display icon to go into Change mode.  You will see the title changes from Display View “FLP Configuration”: Overview to Change View “FLP Configuration”: Overview.  Then press New Entries to add a parameter.

Use the dropdown on the FLP Property ID field to find the short keys NAVIGATION_GUI_INPLACE and NAVIGATION_WDA_INPLACE. Create an entry for each short key.

Press ENTER to get the Description, type and current Property Value defaulted into the table.


Now you can change the Property Value to any other value supported for this parameter, as previously advised in the Fiori Launchpad Parameters.

For these inplace parameters the only values are true or false.  You can set both to true. Finally press the Save icon to save your values.

You can find out more about the new approach in the SAP Fiori Launchpad Administration Guide in the SAP Help Portal. Look for the section Configuring the Launchpad and subsection Setting Parameters in SAP Fiori Customizing
There are also a few related SAP Notes worth reading:
2730956 – Configuring SAP Fiori Launchpad in ABAP Customizing
2403527 – Force WebGUI/WebDynpro apps to open in same window when launching from Fiori Launchpad

Testing inplace navigation

Once you have saved your changes in the table, simply refresh your Web Browser and your changes are immediately applied.
Go back to your Fiori launchpad home page, and reselect the relevant tile or link to launch the classic app.  The SAP GUI transaction now opens in place so there is only one tab – no additional browser window/tab is opened.

You should also find the Fiori launchpad features Me Area, Notifications, Back and Home are all available.

For support reasons, if you need to confirm the technical id of the transaction just use the About Icon in the Me Area as explained in Fiori for S/4HANA – Finding the technical Name of an app

Easy!
Watchpoints:

• If you are having problems with empty mandatory fields in a GUI transaction locking up the Fiori shell, then check your kernel version is up to date.
• The support component for the inplace navigation is CA-FLP-ABA
• For other Fiori launchpad configuration parameters, use CA-FLP-FE-COR

Addendum: How to explicitly open a specific app explace

Well there is an easy answer for this too.  And it comes with your device’s web browser.
When you are on a tile or link, just use your usual web browser context menu commands to “Open Link in New Tab” or “Open Link in New Window”.
And you should find that approach generally works regardless of app type.

Becoming a SAP Fiori for SAP S/4HANA guru

You’ll find much more on our SAP Fiori for SAP S/4HANA wiki
Brought to you by the S/4HANA RIG





Source: https://blogs.sap.com/2019/01/29/fiori-for-s4hana-calling-gui-web-dynpro-abap-without-opening-a-new-tab/

Process Analytics with SAP Master Data Governance on S/4HANA 1809

Quality is key when it comes to master data management. This of course holds true when it comes to controlling the data quality itself, as thoroughly described by Andreas Seifried, and it also applies when it comes to reveal the quality of processing activities in SAP MDG.

The current SAP Master Data Governance on SAP S/4HANA 1809, offers FIORI-based process analytics to control the process quality in master data. Process analytics features, Overview Pages and Analytical List Pages that visualize relevant process information at a glance.

• Overview Pages provide you with one-stop information on work due and the work done for the individual user, including for example direct navigation to Analytical List pages for further analysis and drill down.
• Analytical List Pages are a highly flexible deep-dive analysis tool for processes in the area of consolidation, mass processing and central governance.

Overview Pages

Overview Pages are summary dashboards displaying relevant process information with intuitive navigation and drill down for detailed analysis of process-quality issues related to the following master data objects

• Business Partner, Customer, Supplier
• Product
• Financial Accounting and Financial Controlling data.

The cards on an Overview Page (OVP) provide you with one-stop information on work due and work done for the individual user plus the following process features:

• Users are able to hide and unhide cards on the OVP depending on working needs
• Display of Change Request related information as trigger to work on change requests requiring the user’s attention (open change requests, long running change requests, rejected change requests)
• Display of average processing times of change requests to improve processing times
• Display of completed change requests and upcoming workload (i.e. open change requests)
• Display of consolidation processes and their status (not for financial data)
• Visualization of quality in Mass Processing (not for financial data)

For process analytics related to central governance, you can find the following change request-related cards on the Overview Page for Products and Business Partners:

• Total Change Requests
• Open Change Requests
• Overdue Change Requests
• Rejected Change Requests
• Change Requests with my Involvement
• Longest Running Open Change Requests
• Change Requests older than 48 hours
• Processing Duration of Finalized Change Requests

From every change request related card of the Master Data Process Overview you can navigate to the Change Request Analysis app for further drill-down analysis.
For process analytics related to consolidation and mass processing, you can find the following cards for Business Partners and Products:

• Open Consolidation and Mass Processes
• Finished Consolidation and Mass Processes
• Duration of Consolidation and Mass Processes
• Number of Processes Business Partners / Products
• Consolidation Validation Results
• Changed Business Partner / Product Attributes

From these cards you can navigate the Change Process Analysis app for further drill-down and analysis.

Analytical List Pages – Change Request Analysis and Change Process Analysis

Analytical List Pages are used for Change Request Analysis apps and Change Process Analysis apps. These apps offer a one-stop information and highly flexible analysis tool for change request and change process analysis monitoring process quality issues related to change requests and change processes using various drill-down dimensions. The apps are available as stand-alone apps as well as navigation target coming from the Overview Pages for further drill-down.
With the Analytical List Pages you can

• Analyze change request, consolidation and mass processes using different drill-downs on dimensions, such as status, priority, and business object type.
• Use graphical or compact filters for selecting your change requests, time-frame, status… to analyze the process data
• Keep track of the average change request processing time
• Navigate to the selected change request or change process

Benefits

Process Analytics with SAP Master Data Governance on S/4HANA 1809 provides you with unique benefits:

• One-stop information on prevailing process quality in central governance, consolidation, and mass processing
• Intuitive navigation and drill down for detailed analysis of process-quality issues
• Navigation to change request or change process for triggering further actions

I hope this is beneficial in helping to control you process quality in your master data governance activities.


Source: https://blogs.sap.com/2019/01/11/process-analytics-with-sap-master-data-governance-on-s4hana-1809/

SAP HANA licensing models explained

SAP’s column-oriented, in-memory database, that combines OLAP and OLTP operations into a single system, or in other words, SAP HANA originated from a research started in 2006 by SAP’s co-founder Hasso Plattner while he was a computer science professor at the Hasso Platner Institute in Postdam, Germany.
After several years of development at SAP, a prerelease version of SAP HANA was given to selected customers in October 2010. SAP released the first official version, SAP HANA 1.0, on June 18, 2011. After a few years of development and major architectural changes, SAP HANA 2.0 was released in 2017, with a variety of updated and new features. Below you can check a timeline with the major SAP HANA events:

SAP HANA is an enterprise platform designed to handle a huge amount of data and a large number of applications in support of mission-critical business. By platform, we mean that it is not only a database anymore. Application developers can build applications and data scientists can run advanced analytics and machine learning directly on SAP HANA, and database administrators can integrate their landscape within the SAP HANA database management tools. SAP HANA provides features for multi tenancy, high availability, disaster recovery, and dynamic tiering to help ensure 24×7 access and smooth horizontal and vertical scaling. SAP HANA also lets you access a wide variety of data sources and support Big Data and the Internet of Things.
Since its release, SAP HANA has had multiple versions and editions. The objective of this blog post is to clarify what is the most suited licensing option for you to leverage the full potential of SAP’s highest profile product – SAP HANA. The following options are going to be covered:

• SAP HANA Runtime Edition
• SAP HANA Full Use Edition
• SAP HANA Active/Active (Read Enabled)
• SAP HANA Express Edition
• SAP Cloud Platform, SAP HANA Service

---

SAP HANA Runtime Edition
SAP HANA Runtime Edition is limited to a runtime environment for SAP Applications. An SAP Application is any application that includes a NetWeaver Application Server, e.g. SAP Business Warehouse (BW), SAP BW/4HANA, SAP Business Suite, SAP S/4HANA and other related products.

SAP offers two options with SAP HANA Runtime Edition:

• SAP HANA Runtime Edition for SAP BW (HANA REB)
• SAP HANA Runtime Edition for Apps and SAP BW (HANA REAB), which includes all capabilities from REB, plus other SAP Apps.

The picture below shows the available features of both for these options.

The options marked with * have some restrictions regarding data processing. All SAP HANA functions description can be found here.
SAP HANA Runtime Edition is considered an integral part of the application itself, so that any kind of data processing (modeling, administration, creation of data structures and use of advanced analytics) must be done by this application, via the application layer (where the interface can be either from SAP or a 3rd party provider). With SAP HANA Runtime Edition, the data from the application can only be displayed or graphically processed at the front-end application and any direct connection to the database bypassing the application is a license violation.
The picture below shows not only the available SAP HANA capabilities, but also the restricted (Δ) and not included (X) ones when SAP HANA Runtime Edition is licensed.

---

SAP HANA Full Use Edition
SAP HANA Full Use Edition offers an unrestricted platform for any combination of SAP, non-SAP, custom, third-party, and hybrid applications.

With SAP HANA Full Use Edition there are no limitations on data modeling, administration, creation of custom structures, and use of advanced engines via HANA Web IDE, HANA Studio (IDEs used to develop artifacts on a HANA server) or other applications. There are no limitations on loading and exporting of SAP & non-SAP data directly into and out of SAP HANA.
With the Full Use Edition it is possible to read data both from the application and database layers. You can consume the data of the SAP HANA system whichever way you need it.
SAP offers two versions of the SAP HANA Full Use Edition:

• SAP HANA Standard Edition
• SAP HANA Enterprise Edition (includes all capabilities from the Standard Edition). The picture below shows the available features for both editions.

It is also possible to acquire the Standard Edition and just add the services you need for your business. Here are the available options:

• Data Privacy Option, for enhanced protection of sensitive and confidential data (e.g. Data Masking);
• Information Management Option, for data integration, data quality management, and information stewardship;
• Predictive Option, for Predictive Analytics Library access, R engine, and TensorFlow integration for advanced analytics;
• Replication Option, for replicating data from any supported source system to the SAP HANA database;
• Search/Text Option, for search, text analysis, and text-mining functionality for you to gain real insights from unstructured textual data;
• Spatial/Graph Option, for advanced spatial and graph analytics capabilities;
• Streaming Analytics Option, for processing streams of events and messages in real time, allowing some or all of the data to be captured in the SAP HANA database and/or Hadoop.

Basically, if you license all available options on top of your SAP HANA Standard Edition, your SAP HANA system will have the same capabilities as the SAP HANA Enterprise Edition.

SAP HANA Enterprise Edition includes the full range of functions and features from SAP HANA, being the foundation of SAP’s data management solutions and the Intelligent Enterprise. An exhaustive description of all SAP HANA functions can be found here.

SAP HANA Full Use allows you to use widespread skills (such as JavaScript, Python, SQL, ABAP). ABAP developers have unrestricted code push-down possibilities.
The HANA platform allows for a development with no data transfers, no data duplication and no data latency, because the processing is done within the database itself; and the powerful technical capabilities of SAP HANA can be utilized. With this, we can have faster time to value and we can have lower development and maintenance costs.

---

SAP HANA Runtime Edition vs Full Use Edition
Conceptually speaking SAP HANA Runtime Edition offers a limited platform, centralized only for SAP applications and SAP HANA Full Use Edition offers an unrestricted platform for all systems and distributed data in modern, hybrid environments.
The picture below provides an overview of the biggest technical differences between these two editions. For SAP HANA Runtime Edition we’ve included restricted (Δ) and not available (X) capabilities.

In terms of functions and features, the picture below compares the difference between the two available editions.

To sum up, the decision of choosing which edition is best for you depends on whether you want to leverage SAP Applications, or you want to use the full power of the SAP HANA platform.
If you are just looking for a faster database that supports your SAP applications SAP HANA Runtime Edition is the right choice, but if you are looking for a long-term and strategic solution, you need SAP HANA Full Use Edition. Making the right choice here will depend on your company’s needs. Even if you license SAP HANA Runtime Edition based on your current requirements, but your long-term roadmap calls for SAP HANA Full Use Edition, SAP supports this transition both commercially and technically.

---

SAP HANA Active/Active (Read Enabled)
SAP HANA Active/Active (Read Enabled) is a solution that targets resiliency and better performance of your SAP HANA productive environment. With this option you can offload intensive read operations to the secondary system, freeing up more computational power to be used on the primary system for read and write operations.
As data is continuously being replicated from the primary to the secondary system using either synchronous or asynchronous communication protocols, you can leverage the secondary system to offset read-intensive workloads from the primary system. With SAP HANA Active/Active (Read Enabled) you can gain usage rights to access secondary system for productive read-enabled operation, the utilization of the underlying hardware can be increased because the workloads can be much more balanced, which also improves the performance of the operations on the primary system. Latency can also be reduced as read intensive users can now be located next to the secondary data center and there is no impact on your Recovery Time Objective (RTO) and Recovery Point Objective (RPO).
Without SAP HANA Active/Active (Read Enabled), the secondary system can’t be used for any operation, which means it’s only idle capacity for High Availability and Disaster Recovery purposes.
This option can either be used by SAP HANA Runtime and Full Use Editions as you can check below. Only SAP HANA 2.0 works with this option.

---

SAP HANA Express Edition
All the different versions of SAP HANA that we have introduced are enterprise-ready, meant to be run in productive environments. What if you are a programmer who wants to run SAP HANA on a local PC, or on a cloud service offered by a Hyperscaler (AWS, GCP, Azure, …) ?
SAP HANA, express edition is the best way to test out and get hands on with SAP HANA, being available to install on your local laptop or desktop computer, a local server, or in the cloud. This means you can now use the express edition of SAP HANA on devices other than existing, SAP-certified, hardware appliances, or access it from the SAP Cloud Appliance Library tool on either Amazon Web Services, Microsoft Azure or Google Cloud Platform.
This edition allows you to jump-start application development on top of SAP HANA today and move to other editions of SAP HANA (i.e. SAP HANA Runtime or Full Use Edition) as your needs to grow tomorrow. Developers and independent software vendors (ISVs) can start using the express edition of SAP HANA at no cost to build and deploy applications that use up to 32 GB of memory. You can expand the use of your existing SAP HANA Express Edition for a fee, paying incrementally for up to 128 GB of memory use.
To support application development on your personal computer, where data size and scalability are limited, we have streamlined the SAP HANA platform to fit within the constraints of PCs. Because of this, the following features are not available with the express edition of SAP HANA:

• Data warehousing foundation
• Disaster recovery
• Dynamic tiering
• High availability
• Multihosting
• Outward scaling for multiple hosts
• Remote data synchronization
• SAP Solution Manager
• Smart data integration
• Smart data quality
• Smart data streaming
• System replication

You can download SAP HANA, Express edition here. Or you can get it as a Virtual Machine on the marketplace of any cloud Hyperscaler (GCP, AWS, Azure, etc.).

---

SAP Cloud Platform, SAP HANA Service
The SAP HANA service (officially called SAP Cloud Platform, SAP HANA service) allows you to leverage the in-memory data processing capabilities of SAP HANA in the cloud. As a managed database service, backups are fully automated and service availability guaranteed. Using the SAP HANA service, you can set up and manage SAP HANA databases and bind them to applications running on SAP Cloud Platform. You can access SAP HANA databases using a variety of languages and interfaces, as well as build applications and models using tools provided with SAP HANA.
There are multiple cloud deployment options available for SAP HANA service: it can be deployed in the Cloud Foundry environment or in the Neo Environment from SAP Cloud Platform. The Cloud Foundry environment is based on Amazon Web Services, Google Cloud Platform or Microsoft Azure while the Neo environment is hosted by SAP.
SAP HANA service is available in two editions: Standard and Enterprise (similar to the editions available for SAP HANA Full Use). Standard Edition only includes core database services with in-memory capabilities as well as smart data access. Enterprise Edition includes all SAP HANA Service Standard Edition capabilities including advanced analytics options and smart data integration.


Jorge Mendes, SAP Portugal
Maxime Simon, SAP Japan


Source: https://blogs.sap.com/2019/01/21/sap-hana-licensing-models-explained/?source=social-Global-SAP+Developers-LINKEDIN_COMPANY-AudienceEngagement-Developers-SAPHANA&campaigncode=CRM-XB19-MKT-DGEALL