We want to hear about your SAP Fiori implementation experiences, the challenges you faced and how you overcame them, the learning process you went through, and celebrate with you in your project success.  One of the goals of the Technology RIG team is to improve the implementation experience of SAP Fiori, and in order to do that we need to hear from the community.  We want you to share your story, and we are quite confident that other community members will be appreciative, and it will benefit their project efforts as well.

We will maintain this document as a landing page for implementation experience blogs, videos, and documents.  We request that after you share your experience you link it to this page.  As an outstanding example of what we’re looking for please read James Ibbotson’s blog below.

Don’t forget to use #myfioristory, and choose the ‘SAP Fiori UX’ category when creating your content, and please don’t hesitate to contact me with any questions or assistance. Thank you in advance for sharing your SAP Fiori success stories with our vibrant community!

• 2014-12-02 Implementing SAP Fiori in a Productive Environment. by James Ibbotson
• 2015-01-02 SAP Fiori – An in-house Implementation Story by Prem Prabhakaran
• 2015-04-07 myFiori App extension by Ramachandran Balakrishnan
• 2015-05-28 SAP mobility a two-phase process at CA Technologies by David Essex (TechTarget) featuring Rich Lazzara
• 2015-11-17 Lessons Learned SAP Fiori Implementation on Business Suite (TechEd Presentation) by R. Eijpe
• 2015-12-17 7 tips you need to consider to ensure your SAP Fiori implementation is a success! by Benjamin Kwong
• 2016-03-11 Real Life Experiences Extending Fiori My Inbox by Jocelyn Dart and Murali Shanmugham
• 2016-04-16 Fiori & UI5 in a Local Government Setting by Chantele Smith
• 2016-06-20 SAP Fiori - Taking the "phobe" out of Technophobe by Chantele Smith
• Who will be next?  If you are looking for inspiration or just aren't sure how to blog, you should watch the video included here (game is optional of course):  Are You a Rock Star Blogger?

Recap

In part 1 of this series, we looked at three things:

1. The origins of why an API Management solution is needed in the first place
2. How SAP has chosen to implement their solution
3. The 4 basic data object that act as the building blocks from which API is exposed to the outside world.

In this document, we will build on that knowledge and look in overview at the tools used to create and maintain these data objects.

In order to help us keep track of where we are in the big scheme of things, I will use the following diagram as a road map, in which we will start at the bottom, and work our way up.

Creating a System

At this point in the development process, we are acting as a Proxy Developer, therefore we must use the API Portal.

From the hamburger menu in the top left, select the Configure option.

In the bottom right corner, there is a Create menu.  Click here to create your new System.

All we're doing here is creating a logical name by which a backend system can be identified within the API Management framework.

Another important point to understand here is that perhaps surprisingly, the creation of System is not mandatory.

If you are wanting to access a backend system that exposes its functionality through OData services, this it is useful to create a System.

The creation of Systems is also useful for reusability.  Once you have created a System, you can access any service from that backend system using nothing more than the System name created here, and the relative path to the particular service of interest.

When creating a system, you should supply three different blocks of information:

1. The connection information to the actual server.  This includes the host name, port number and an optional path prefix.  For instance, if you are creating a System to represent an ABAP backend, then you will probably want to add the path prefix of "/sap/opu/odata" in order to restrict access to only the resources exposed from this path.
2. Authentication.  If supplied, the hard coded userid and password will be used by the API Portal's design time tools when you come to consume services from this backend system.
3. Lastly, the Catalog URL (if supplied), will allow the API Management design-time tools to invoke the special CATALOGSERVICE OData service.   This is a special OData service provided as standard with all ABAP systems, and its purpose is to list all the OData services exposed by this ABAP system.  Within this service is an OData collection called ServiceCollection that lists all the available OData services.
   As was mentioned above, this configuration is optional; however, if you do not supply it, then when we arrive at the next step of creating an API Proxy that points to an OData service, the design time tools will not be able to query the backend system and present you will a list of available services.  In this case, you will need to know the full path name to the OData service yourself.

Creating an API Proxy

We now come to the part where all the work takes place.  Creating API Proxies is the heart of API Management, and this is where you will spend the bulk of your time.

From the hamburger menu in the top left, select Manage.

A new API Proxy is created by clicking on the Create menu in the bottom right corner.

At this point, you have the option of either creating an API from scratch, or importing one.

Should you wish to import an API, you must first have exported the API from some other SAP API Management system.  (An exported API consists of a ZIP file within which the various parts of the API have been dumped as XML files).

Assuming you want to create an API Proxy from scratch, you will need to provide all the initial details yourself.

Pointing to the Backend System

As was mentioned above, when you create an API Proxy, you can specify that you want to consume a service exposed by some backend system for which you have already created a System.  The name of the System is then chosen from the drop-down list called "API Provider".  However, this is not the only way of doing it.  Alternatively, you can leave the API Provider entry set to NONE, and then enter the full URL to the service.  This second approach is sometimes used if you wish to consume something like a public Web Service (SOAP).

Either way, using the information supplied in both the API Provider and URL fields, the tool for creating the API must be able to fully identify the required service.

Also note that if you select a System from the API Provider drop-down list, then a new button will appear to the right of the drop-down called "Discover".

Remember what was mentioned above about the Catalog URL?  Well, here's where that configuration is used.  If you supplied a Catalog URL when you created the System (or API Provider), then you will now be able to click on the Discover button and see a list of all the OData services available in that System.

Alternatively, if you did not supply a Catalog URL, then the Discover button will not do anything.

It's important to understand that this "Discover" feature is designed only to work against backend systems that provide a specific CatalogService OData service.

Naming the API Proxy

Once the URL of the backend service has been defined, you can now give the API proxy a name and a description.

The API Base Path field is important to understand. This field holds the URL used when the API Proxy is consumed by the external user.

This URL must be unique across all the API Proxies you create.  That said, if you wish to create two different API Proxies that both point to the same backend service, then this is perfectly possible as long as you use two different values for the API Base Path.

The point at which we now find ourselves is that although we have created an API Proxy, this proxy is quite passive, providing no additional functionality when invoked.  Nonetheless, we will stop here in the discussion of creating API Proxies for two reasons: the first being that this current document is just an overview of the available API Management tools, and the second being that the development of an API Proxy is large and detailed topic that must be discussed individually.  Such as discussion will follow in due course.

Creating a Product

Now that we have an API Proxy (albeit one that adds no value), we can now add this Proxy to  Product in order to expose it to the outside world.

As was said in the first document, the Product is the unit of API Exposure.  In other words, if you want your Proxy to be exposed to the outside world, you must first add it to this data object called a Product.  Although there are no hard and fast rules here, it is typical to create a Product that contains all the API Proxies related to one type of business task or process.

By selecting "Product" from the tab menu in the "Manage" screen, you can add or remove API Proxies from the Product.

Remember that a Product can contain many API Proxies, and that the same API Proxy can belong to many Products.

Since we have added the API Proxy to the Product, this API Proxy is now visible to the outside world.  We have now finished all the tasks required of an API Proxy developer, and we must now change hats and look at these proxies from the perspective of a frontend app developer.

Discovering the Available API Proxies

Now that we have switched personas from an API Proxy Developer to a frontend app developer, we are no longer interested so much in the internal workings of the API Proxy, but rather being able to consume that proxy from within the larger scope of an external business application.

In addition to switching personas, we must also switch API Management tools.  Up till now, we have done all the work in the API Portal, but now we need to switch to the Dev Portal.  Return to the API Management service via your HCP account cockpit and select "SAP API Management Dev Portal".

You are now taken to a screen that looks similar to the API Portal, but here you have no ability to create or change API Proxies.

From the hamburger menu, select the Discover option and you will now see a list of all the available Products.  By selecting a Product, you can see a list of all the API Proxies it contains, which in turn, takes you to a test tool for each service exposed by the API Proxy.

Consuming API Proxies

When you have found the Product or Products you want, select the Consume option from the hamburger menu.  Now by clicking on the Create option in the bottom right of the screen, you can create your own Application.

Remember that the term "Application" is not being used in the normal sense of a unit of software with which a user interacts in order to perform some business task.  Instead here, the term Application means the set of Products to which you have subscribed for the purposes of building some client application.  So, in one sense the API Management term "Application" does potentially refer to the unit of business software more traditionally referred to as an application, but even if this is true, the reference is only indirect.

Once you have added as many products to your Application as you require and saved it, you will be given an Application Key.  This is a randomly generated string that serves to uniquely identify your specific usage of the selected Products.

When you create an Application, you are creating a unit of API Subscription.  This unit of subscription is then identified by its Application Key, and this very must typically be supplied each time a call to an API Proxy is made.

In the next document, we will take a look at creating the necessary HCP Destinations in order for you to be able to consume API MAnagement Proxies using the SAP Web IDE.

Chris W

This side is dedicated to German speaking customers. If you are interested English Webinars please check out the North America (EN) Product Road Map Webinars here.

Die Lines of Business (LoB) Road Maps Webinar Serie bietet interaktive Präsentationen für die verschiedenen Lines of Businesses an. Die Road Maps beschreiben die geplanten Änderungen und die künftige Ausrichtung von SAP Produkten in den verschiedenen Bereichen. Die Webinar-Serie wird durch das SAP P&I PMCS-Team in Zusammenarbeit mit den entsprechenden Road Map-Verantwortlichen organisiert. Die Webinare einschließlich der Aufzeichnungen und Präsentationen sind für alle DSAG Mitglieder im DSAG-Net zugänglich.

Die Anmeldung und Registrierung erfolgt über die DSAG direkt. Ansprechpartner ist Herr Günter Haack (Guenter.Haack@dsag.de).

Die vollständige Liste aller veröffentlichten Lösungen und Product Road Map Präsentationen finden Sie auf unserem SAP Service Market Place hier: http://service.sap.com/saproadmaps.

Für weitere Informationen kontaktieren Sie bitte: Tanja Russow (Tanja.Russow@sap.com).

Folgende LoB Road Map Webinare finden in 2016 statt:

Die Aufzeichnungen hierzu werden zeitnah im DSAG Net für DSAG Mitglieder bereitgestellt.

Informationen und Recordings zu den Webinarserien der vergangenen Jahre finden Sie hier:

LoB Road Map Webinar Series for DSAG 2015

LoB Road Map Webinar Series for DSAG 2014

Ich bin Bachelorand der Wirtschaftsinformatik an der Hochschule Kaiserslautern und werde im Rahmen meiner Bachelorarbeit eine Marktstudie zum Thema Mobile IT Security Infrastruktur im SAP Umfeld in Kooperation mit der mindsquare durchführen.

Ich suche Unternehmen, die bereit sind, sich 5-10 Minuten Zeit zu nehmen, um die dazugehörige Umfrage zu beantworten. Dabei werden Ihre Daten selbstverständlich anonymisiert.

Und welchen Nutzen haben Sie durch die Teilnahme?

Als Teilnehmer der Marktstudie erhalten Sie die Ergebnisse gratis. Anderenfalls wird sich der Preis auf 1500€ belaufen.

Mit Hilfe der Ergebnisse können Sie unter anderem die Fragen beantworten, ob die von Ihnen gewählte Lösung die beste bzw. kosteneffizienteste Möglichkeit ist. Außerdem sehen Sie, welche Alternativen andere Unternehmen gewählt haben, wie zufrieden sie damit sind und welche Kosten dabei entstehen.

Noch keine mobilen Anwendungen im Einsatz?
Eine Teilnahme lohnt sich dennoch für Sie. Durch die Ergebnisse der Marktstudie können Sie, wenn Sie mobile Anwendungen in Ihrem Unternehmen einsetzen möchten, auf diese Informationen zurückgreifen. Diese werden Ihnen bei der Einführung behilflich sein.

Folgende Fragen sind unter anderem Bestandteil der Marktstudie:

• Nutzen Sie Single Sign On zur Authentifizierung und wie setzen Sie dieses Konzept um?
• Welche Möglichkeiten nutzen Sie, um Unbefugten den Zugriff auf Ihr internes Netzwerk zu verwehren?
• Nutzen Sie Mobile Device Management und wie setzen Sie dieses Konzept um?
• Welche Kosten kommen für Ihre Infrastruktur auf Sie zu?

Hier finden Sie weitere Informationen und den Onlinefragebogen.

Beste Grüße

Sören Lübben

SAP Fiori Launchpad - Simplification of Target Mapping Configuration without LPD_CUST

With SAP UI Add-On 2.0 for SAP Netweaver navigation targets for the application types SAPUI5 Fiori apps, transactions, Web Dynpro applications and URLs can be defined completely within the SAP Fiori launchpad designerwithout using transaction LPD_CUST. Carola Steinmaier, June 9, 2016

Top 220 Apps Created from the SAP Fiori Develop Challenge – Now on SCN

More than 30,000 learners enrolled and thousands upon thousands submitted app prototypes, each including a story, persona, user experience journey, mock-up, app prototype, and sometimes more! Bob Caswell, June 2, 2016

UX for Optimal User Performance – Accessibility & Fiori

While user research and role-based design are essential to a good user experience, accessibility gives us a range of simple and effective ways we can lift user experience from good to great. Jocelyn Dart,April 26, 2016

Get Involved: Impact SAP’s Solution for UI Adaptation by Sharing Your Needs

Help us to understand how you’re currently dealing with UI adaptation. What do your processes look like? What challenges do you face? And how should it work for you ideally? Whether you’re a key user, a partner, or a rapid developer: share your views with us and be part of shaping Runtime Adaptation. Thomas Niederbuehl, December 10, 2015

SAP Investigative Case Management (SAP ICM) is streamlined for end-to-end processes of any investigation in public security and beyond. This is not the end of the story though. For complex investigations, which are not following a straight and simple path but are forking and winding, many supportive tools and features could be helpful and necessary. Such tools could support the digital agenda for policing and organizations that conduct investigations. Here are some trends and outlooks that will dominate our thinking and development considerations over the coming years.

1. Eye-opener: Visualize your data

Data in tables are nice for sorting and filtering but you cannot see easily how they belong together. Specifically in ICM the relations between persons, objects, locations, and events are of utter importance. How much simpler is it to look at a picture that shows how everything is connected! We believe that customers will embrace graphs, maps, timelines, and more eye-catching features that could be added. An ideal tool would be designed for visualizing not only ICM data but data from different sources and systems.

2. Needle in the haystack: Quick (re)searches with SAP HANA

SAP ICM runs smoothly on HANA, SAP’s platform for in-memory computing. However, the full power of HANA is yet to be unleashed for ICM. This especially valid for the requirements on searches and researches. Combining search criteria of different objects connected by relations, mixing searches on structured and unstructured data, using features like fuzzy or phonetic search can slow down the performance significantly. Possible future HANA-based enhancements to ICM could conceivably improve search efficiency and capabilities.

3. On the road again: Mobile processes

One would assume that public security organizations are natural customers for mobile processes because few incidents happen directly in their offices. Reality is a bit more complicated, and a mobilized ICM has to be designed carefully. Police officers in action must be attentive and alert, they don’t have the time to fumble around with mobile devices usually. Therefore they will only use them if there is a clear advantage. Mobility is thus a major focus for us as we consider the future of ICM.

4. It’s one world: National and international data exchange

Crime does not stop at borders, neither of states nor of countries. On the other hand public security organizations are often bound to these borders. The only way to overcome this is exchanging and sharing data in a way that ensures the very high data safety requirements in this area. SAP is evaluating how national and international standards for interfaces for public security data can be supported and integrated with ICM to ensure that crime can be fought globally.

5. Beyond vanilla: ICM flavors for special purposes

Investigations in different organizations and areas are similar but not the same. Processes in border management, justice management, fraud management etc. can already run with ICM currently. However, their particular needs could be supported even better with specific solution considerations that we are evaluating. This might also include further integration with solutions like SAP hybris for multichannel demands.

What do you think?

Do you feel that I missed a general topic that must be mentioned in this list of current trends for ICM? Is there anything else you would like to see addressed by SAP to push ICM to the next level? Pease let me know directly or post a comment below. Your feedback is much appreciated!

[new] SAP hybris Marketing and SAP CRM RDS V3 - fully-activated Landscape

More Information(last update: 17 May, 2016)

[new] SAP NetWeaver AS ABAP and SAP BW 7.50 SP02 on SAP ASE 16.0

(last update: 16 May, 2016)

[new] SAP HANA, Platform Edition 1.0 SPS 11 revision 112

More Information(last update: 10 May, 2016)

[new] SAP ERP 6.0 EHP8, version for SAP HANA SP11

(last update: 27 April, 2016)

[new] SAP SCM 7.0 EHP4, version for SAP HANA SP11

(last update: 27 April, 2016)

[new] SAP SRM 7.0 EHP4, version for SAP HANA SP11

(last update: 21 April, 2016)

[new] SAP CRM 7.0 EHP4, version for SAP HANA SP11

(last update: 21 April, 2016)

[new] SAP BusinessObjects Business Intelligence Platform 4.2 SP2

(last update: 13 April, 2016)

[new] SAP S/4HANA, on premise edition 1511 FPS01 Fully-Activated

More Information(last update: 1 April, 2016)

SAP IT Operations Analytics 2.0

More Information(last update: 11 March, 2016)

SAP enhancement package 8 for SAP ERP 6.0, version for SAP Adaptive Server Enterprise

(last update: 4 February, 2016)

SAP enhancement package 4 for SAP SRM 7.0, version for SAP Adaptive Server Enterprise

(last update: 3 February, 2016)

SAP enhancement package 4 for SAP SCM 7.0, version for SAP Adaptive Server Enterprise

(last update: 3 February, 2016)

SAP enhancement package 4 for SAP CRM 7.0, version for SAP Adaptive Server Enterprise

(last update: 3 February, 2016)

SAP NetWeaver AS Java 7.5 on SAP ASE 16.0

(last update: 1 February, 2016)

SAP NetWeaver AS ABAP and SAP BW 7.5 on SAP HANA SP10

(last update: 27 January, 2016)

SAP Solution Manager 7.2: Test drive Content Activation of Customer's Own Documentation

More Information(last update: 27 January, 2016)

SAP Screen Personas pre-configured environment based on IDES ERP 6.0 EhP7

More Information(last update: 21 December, 2015)

SAP NetWeaver AS ABAP 7.5 on SAP ASE 16.0

(last update: 2 December, 2015)

SAP NetWeaver AS ABAP 7.5 on SAP HANA SP10

(last update: 17 November, 2015)

SAP BusinessObjects Business Intelligence Platform 4.1 SP6

(last update: 22 October, 2015)

Intelligent Business Operations: SAP Process Orchestration 7.4 SPS 11 and SAP Operational Process Intelligence 1.0 SPS 09

More Information(last update: 22 October, 2015)

SAP Access Control Rapid Deployment Solution - semi-activated - Appliance

More Information(last update: 8 October, 2015)

SAP enhancement package 7 for SAP ERP 6.0 on SAP ASE

(last update: 14 September, 2015)

SAP enhancement package 3 for SAP CRM 7.0 on SAP ASE

(last update: 14 September, 2015)

SAP NetWeaver 7.4 SP10 Enterprise Portal on SAP ASE

(last update: 14 August, 2015)

SAP End-to-End Lending and Deposits rapid-deployment solution – Fully-Activated Appliance Landscape

More Information(last update: 03 July, 2015)

SAP hybris Marketing and SAP CRM RDS V2 - fully-activated Landscape

More Information(last update: 10 June, 2015)

SAP NetWeaver AS ABAP and SAP BW 7.4 SP08 on SAP ASE 15.7

More Information(last update: 03 June, 2015)

SAP enhancement package 7 for SAP ERP 6.0 on SAP HANA 1.0 SP9

More Information(last update: 12 May, 2015)

IDES ERP 6.0 Including Enhancement Package 7 on SAP HANA

More Information(last update: 28 April, 2015)

IDES ERP 6.0 Including Enhancement Package 7 on SAP ASE 15.7

More Information(last update: 26 February, 2015)

SAP Supply Chain Management 7.0

More Information

SAP Enterprise Portal 7.4 SP8 on SAP ASE

SAP Business Warehouse 7.4 SP5 incl. SAP Business Objects BI 4.1 SP2 on SAP HANA 1.0 SP7

SAP enhancement package 3 for SAP Supplier Relationship Management 7.0 on SAP MaxDB 7.9 SP8

More Information

SAP CRM rapid-deployment solution Appliance Landscape

More Information

Didn't find what you were looking for? Beyond the standard configurable package, SAP Cloud Appliance Library offers access to a free of charge Trial and Developer versions of SAP software. Check out our additional offerings here.

Recap of Part 3

In part 3 of this document series, we looked at how to set up a pair of HCP Destinations that allow Web IDE to access the API Proxy objects created SAP API Management.  Two destinations were required: one for design time and the other for runtime.

We also saw that when Web IDE starts, your browser receives a file called listDestinations.  This file contains a JSON array in which is defined all the HCP Destinations for which the WebIDEEnabled flag is set to true.  The fact that this file is static explains the need to restart Web IDE after changes are made to any HCP Destinations used by Web IDE.

Next, we will take a look at how the security token known as the "Application Key" or "API Key" can be supplied at runtime.  This token is a 32 byte, randomly generated string that uniquely identifies the specific set of Products subscribed to by an Application.

Supplying the API Key at Runtime

Recall from Part 2 that when an you create an Application, you are creating a subscription to one or more Products; then within each Product, is/are the API proxy object/s you wish to invoke.

Unless you are offering a free, public service such as sunset and sunrise times for a given GPS location, you will want to manage, monitor and control the usage of this API Proxy.  The the highest level, way this is done is to configure the API Proxy such that it will reject all incoming requests that do not carry a valid API Key.  Therefore, the very first action that is usually performed by an API Proxy is to check for this API Key.

But before we can describe how an API Proxy would check for the presence of such a value, we first need to supply that value as part of the incoming request.

Logon on to your API Portal and select Manage from the hamburger menu in the top left.  Then from the tab menu, select Application.  Here you see a list of all the Applications people have created when they subscribed to your Products.

Select any one of the available applications and look at the overview screen.  Here you will see something like the screen shot shown below: notice the Application Key value.  This is the value that must be supplied when making any request to an API Proxy contained within this Application.

The API Key - To supply, or not to supply?  That is the question

It is important to understand that each API Proxy object is configured to make its own check for the presence of the API Key in the incoming request.  There is no system wide flag you can switch on called "Check for API Key in all incoming requests".  Such a check must be made on a "per API Proxy" basis.

Remember also that one Application can contain multiple Products, and that each Product can contain multiple API Proxies.  Since each API Proxy makes its own check for the API Key, it is therefore entirely possible that within the scope of a single Application, you could could have a mixture of API Proxies as shown in the diagram below:

• Some check for an API Key
• Some do not check for an API Key

Generally speaking, it is better to supply the API Key in all requests, even if it is not needed.  Supplying an un-needed API Key will not do any harm and increases the request size only by a few tens of bytes.

If, as the consumer of an API Proxy however, you would like to be more precise and send the API Key only when needed, it becomes necessary to identify not only when it should be sent, but also how.

Remember, in this scenario we are acting as the developer of a frontend application that consumes an API Proxy, not the developer of the API Proxy; therefore, we are now working in the Dev Portal, not the API Portal.

From your Dev Portal, select Test from the hamburger menu.

Here you will see a screen in which all the available APIs are listed.  Select the one in which you are interested and then simply press Send in the bottom right corner.

Check to see if you get 2 specific error messages:

1. A JSON response that contains the error message "Failed to resolve API Key"
2. An HTTP 401 Unauthorised status code.

If the request fails due to the absence of the API Key, you should see something like this:

IMPORTANT: The HTTP 401 Unauthorised status code is the default status code response from API Management in the event that the API Key is missing.  However, it is possible that the Proxy developer could decide to issue a different status code in the event of a missing API Key.  Although this is possible, it  is also unusual.

So we have now established that if this particular API Proxy does not receive an API Key, it will just make rude binary noises at us.  The next question then is to ask: How should the API Key be supplied - in the Query String or as an HTTP Header?

To answer this question, we must take a closer look at the details of the error message:

Look at the text above highlighted in red.  In this case, the error message indicates that the API Proxy is looking for the API Key as query string parameter called apikey; hence request.querystring.apikey.

Alternatively, you might see an error message like this:

In this case, the error message indicates that the API Proxy is looking for the API Key as an HTTP header field called APIKey.

It's very important to notice the subtle differences here.  In the first case, the API Proxy expects to find the API Key value in a query string parameter called exactly "apikey" (all lowercase), and in the second case, the API Proxy expects to find the API Key value in an HTTP Header field called exactly "APIKey" (mixed case).

The point here is that the variable name carrying the API Key can be called anything the proxy developer likes!

For consistency however, SAP is standardising on the sending this value as an HTTP header in a field called "APIKey".  Nonetheless, always check this error message to see exactly which variable name should be used to pass the API Key value.

So we now know:

1. Whether a particular API Proxy will fail if the API Key is missing
2. Whether the API Key should be passed as a query string parameter or as an HTTP header field
3. The name of the variable that should contain the API Key value

Now we can move on to looking at how to consume an API Proxy in Web IDE

Chris W

Recap of Part 2

In Part 2 of this Introduction to SAP API Management, we looked in overview at the sequence of steps needed to:

1. Create a System
2. Expose backend services from that system as API Proxies
3. Group one or more API Proxies together into a Product (remember, the Product represents the unit of API Exposure)
4. Subscribe one or more Products by creating an Application (remember, an Application represents the unit of API Consumption)

Now we will take something of a sideways steps and do some preparatory work in order to allow API Proxies to be consumed through the SAP Web IDE.  The steps described here are one-off configuration steps and once completed, do not need to be repeated.

Meanwhile, back in the HCP Cockpit...

In order for the Web IDE to be able to consume API Proxies created in API Management, we must set up two HCP Destinations.  One destination will be used by Web IDE at design time, and the other will be used at runtime.

So log on to your HCP Account and select Destinations from the menu on the left.

The first destination that needs to be created will be the one used by Web IDE at design time, and will connect to your API Management Dev Portal.  In other words, the Web IDE design time tools need to be able to connect to the same Portal used when consume an API Proxy.

Alternatively, this destination could connect Web IDE to some public API service such as the SAP API Hub.  In this example however, we will concentrate on connecting Web IDE to your own API Management Dev Portal through which your API Proxies are exposed for consumption.

The name you give to this Destination is not particularly important, but whatever name you choose should reflect the fact that it connects Web IDE's design time tools with your API Management (APIM) Dev Portal.

In this example, I'll call the destination Web_IDE_to_APIM_Designtime; however you are free to choose any name you consider suitable.

At this point, you might be thinking "if the actual name of the Destination is not important, then how is Web IDE able to identify the correct destination?"

This identification is done by means of the additional properties assigned to the Destination; but before we get to that detail, we must obtain the other property values needed for this destination.

HCP Destination for use by Web IDE at design time

The design time HCP destination needs the following property values:

If we were to stop at this point, we would have a perfectly valid HCP Destination, but it would be of no use whatsoever, because we have not added the vital Additional Properties:

Now add the following two properties:

As you have probably worked out, the first parameter makes this HCP destination visible to Web IDE, and the second tells Web IDE that this particular system is a source of API Proxies that can be used by the template wizards.

HCP Destination for use by Web IDE Applications at runtime

As with the design time portal, you are free to choose any name you like for this destination.  In this case, we will use the name APIM_Endpoint_Trial since this the communication endpoint for external apps when connection API Management running on an HCP Trial account.  Again, choose whatever name make sense for you situation.

To find the URL of this particular destination requires a little explanation.  In this case, we are not creating an HCP destination dedicated to invoking a single API Proxy; instead, we want the URL that gives us access to all our published API Proxies.  In our case, this is simply the hostname prefix used to access any one of our API Proxies.

To find this value, connect to your API Management API Portal and select Test from the hamburger menu in the top left.  Select any Proxy name from the left side menu and then copy the protocol, hostname and port number from URL shown near the top of the screen.

Exactly as described for the design time HCP destination, if we were to stop at this point, this HCP Destination would be valid, but useless as far as Web IDE is concerned.

We need to add the following additional properties:

Some Interesting Background

When Web IDE is started, one of the configuration files your browser receives is simply called listDestinations.  This is a JSON file that contains the names of all HCP destination where the WebIDEEnabled property is set to true.  For example, it might look something like this:

So based on the contents of this static file, we can understand how Web IDE knows which destinations it can look at in order to find API Management proxies.

However, we must also understand that this file is static!  This means that if you create a new HCP destination whilst Web IDE is running, you must restart Web IDE in order for it to receive a new copy of this listDestinations file.

Now that this preparatory configuration has been done, in the next document, we can look at how to consume an API Proxy using the template wizard in Web IDE.  As was mentioned in Part 2, whenever you create an Application, you are subscribing to one or more Products.  Every Application is assigned a randomly generated security token known as an "Application Key" or "API Key".

Whenever you wish to call a backend service exposed as an API Proxy, you must (almost) always provide this security token as part of the HTTP request.  I say almost always have to supply it because API Management imposes no technical requirement for an API Proxy to check for the presence of the API Key in the request.  However, it is usual for such a check to be made.  One situation in which a check for an API Key is not needed, is if you were to offer a free service to the public such as sunset and sunrise times for a given GPS location etc.

So next, let's now look at how this API Key value can be supplied when invoking an API Proxy.

Part 4 - Supplying the API Key at Runtime

Chris W

Introduction

In this series of documents, I will introduce you to the concepts and ideas that sit behind SAP's API Management offering.  We'll start by looking at the "the big picture", and then as we progress through the documents, we'll dive deeper into the details so you can see how all the pieces fit together.

By the end of this series of documents, you will be able to build a real-life API Proxy that exposes a Web Service from a backend system.

So, let's start with the 30,000 feet overview...

Where We've Come From

It has long been known that lots of powerful business functionality lies buried deep inside every SAP system.  However, the challenge has always been how to get at that functionality in a consistent and easy-to-consume manner?

Back in the mid-nineties, the Remote Function Call (RFC) interface arrived on the scene (1994 if my memory serves me correctly).  Originally, the RFC interface was accessed from outside the SAP system via a set of C libraries that allowed an external C program to call any ABAP function module that had the "Remote Enabled" flag switched on.

This was certainly a good start, but it was fairly restricted in its adoption for the simple reason that first, in order to make use of this interface you had to be a C programmer, and second, you had to have some internal knowledge of the SAP system in order to understand the data being sent and received.  Needless to say, adoption was limited.

Then, the libraries for accessing the RFC interface were expanded to include Visual Basic and this new fangled language from Sun Microsystems called "Java".  For a while, it looked like everyone was happy.  Visual Basic and its MS Office counterpart "VB for Applications" was widely used and Java was growing in popularity.  But the whole use of RFC based access to SAP imposed a barrier to adoption.  RFC was a proprietary protocol and required the external developer to have at least some knowledge of how an ABAP function modules works.

But the mid-nineties saw the invention of another technology that has now totally transformed the face of both the retail and business computing world - the World Wide Web (now often referred to by non-technical people as "The Interwebs").  Quite soon, businesses began to see the benefits of giving customers access to their systems through these new bits of (not very compatible) software called browsers.

But as with any emerging technology, there's always a scramble for market domination and whoever wins this scrap tends to be able to set the technical standards for how that software should behave.

All of these changes provided SAP with a significant challenge because at that time, the ABAP kernel had no way to communicate using any protocol other than DIAG (used by SAPGUI) and CPIC (used for Remote Function Calls).  Back then, this new fangled protocol called HTTP was completely incompatible with ABAP systems.

So to get the ball rolling, SAP implemented a protocol translation layer called the Internet Transaction Server.  The main job of this software was to translate HTTP messages arriving from browsers into either the DIAG protocol used by SAPGUI or the RFC protocol, then to translate the outbound response from the SAP system back into HTML for the browser.

Shortly after the ITS was released, and In parallel to its development, a project started to allow an ABAP kernel to send and receive XML based messages using the HTTP protocol.  This then became the foundation of what is now the Internet Connectivity Framework

Step forward now to the Millenium Year and a researcher at the University of California, Irvine by the name of Roy Fielding was granted a doctorate for his thesis called Architectural Styles and the Design of Network-based Software Architectures (available here https://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm if you're curious).  From this paper, the widely popular concept of Representational State Transfer, or REST has been acquired.

The architectural principles of REST are now taken to be the de facto design philosophy behind all well designed Web software.  Unfortunately, the term "RESTful service" has been bandied around so much nowadays, that some people talk of REST as if it is an alternative protocol to HTTP.  "Yes, we have two types of service, HTTP and REST".

Which reminds me of a scene from the Blues Brothers: Classic Movie Line #5 - YouTube

But anyway, I digress...

All through the browser wars of the late nineties and early naughties, people were experimenting with different protocols.  During this time, SOAP based Web Services started to become widely used (in spite of their dubious grasp of the principles of REST)

All this to say that everyone knew that backend business systems contained lots of useful information and functionality - its just that nobody could agree on a single, unified protocol through which these backend systems could be accessed.

And even today, people still can't agree...

Leveling The Playing Field

In all of this technical maelstrom of conflicting or ambiguous interface standards, and with the petty squabbles over my-interface-is-better-than-your-interface, various companies have decided to sidestep the whole issue and provide software from which anyone can create their own standardisation layer.  One such company was Apigee.

What SAP has done is to implement the Apigee Edge software as a cloud-based service and then provide all HCP users with access to it via a service called "SAP API Management".

Using the functionality of API Management, you can develop your own proxies to almost any backend service you like - and there's no restriction here to access only SAP backend systems.  You can access any system that is visible to the public internet and supports HTTP based communication.

APIs Are The Fuel That Drives Innovation

Any backend business system (such as an SAP ERP system) is known as a "System of Record".  These systems need to be rock-solid stable simply because large businesses are entirely dependent both on the data they contain, and the functionality they provide.  If such a system goes down, its quite possible that part (or even all) of the business could stop working!

Consequently, reliability is the number one issue here.  Systems of record do not change either very often or very quickly - and for good reason.

However, in the brave new world of Agile software development and the accelerating pace of change, the systems with which the end users interact are expected to stay up to date with the latest technological developments.  This means new layers of software must be built on top of the Systems of Record that can accommodate the expectation of a more rapid pace of change.

Hence we now see the emergence of Systems of Engagement that sit on top of the Systems of Record.  Systems of Engagement change faster than the underlying Systems of Record, but still not fast enough to keep up with the pace of change that occurs with technology innovation.  Therefore, we see a third layer of software known as Systems of Innovation.

Systems of Innovation are where the latest technological advances are implemented.  The apps in this layer of software are known for their generally short lifespan and high turnover; yet at the same time, these apps still need to access the same old business functionality exposed by the Systems of Records.

Therefore, to provide a standardised interface, SAP API Management sits in between the systems of Engagement and the Systems of Innovation.

Enabling Innovation and Bimodal IT

In the world of API Management, the term "Bimodal IT" refers to the practice of managing two separate, yet coherent modes of IT delivery: one focused on stability and the other on agility.

Mode 1 is traditional and sequential, emphasizing safety and accuracy. (Systems of Record)

Mode 2 is exploratory and nonlinear, emphasizing agility and speed. (Systems of Innovation)

Starting Your API Management Service

To gain access to this API Management service, you must at least have a Trial Account on the SAP HANA Cloud Platform.  If you don't have one of these, please go and set one up now...

From your HCP account, from the menu on the left, select Services, then scroll down to the section titled "Integration" and click on the "SAP API Management" tile.  If this is the first time you've access SAP API Management, you will first need to enable this service before proceeding.

When the API Management service screen appears, you will see that there are several different links you could select:

1. The API Portal.  This is used by a proxy developer for creating API Proxies and Products
2. The Dev Portal.  This is used by the developer of a frontend application when they wish to consume an API Proxy developed by the proxy developer
3. Service Configuration.  Here there are two further links that allow you to configure the roles and destinations used by API Management

Click on the link to access the API Portal (not the Dev Portal!) and you will see a screen similar to the following.  If this is the first time you've accessed your API Management tool, then all the counters on these analytic tiles will be zero.

Before we dive into the details of how to build an API Proxy, it is very important that we first understand two things:

1. The data objects with which we will be working
2. How these data objects are related to each other

Overview of API Management Data Objects

In API Management, you will be working with 4 different data objects.

Systems

The first type of data object is a "System".  A system is simply a logical name for some backend system of record.  Each system you define will act as the provider of backend functionality such as Web Services or OData Services.

API Proxies

An API Proxy is the data object that contains all the functionality to be executed when an external user wants to access the backend service.  Within the API Proxy you can implement all manner of functionality such as checking that the user has not called this API more times that are permitted by their quota, or preventing a denial of service attack with a tool known as a "Spike Arrest", or translating the incoming request into a SOAP XML payload, or performing your own custom written functionality, etc etc etc...

To be honest, the development of an API Proxy is where 99% of your development effort will go.  You can think of the API Proxy as the heart of API Management.

Each API Proxy represents the interface to a single backend service,  You cannot create an API Proxy that is a mashup of data received from different backend services.  If you want to do that, then you should look at HCP's OData Provisioning service and not here in API Management - this is the wrong tool for that particular job.

Products

Now this is where the fun starts (as if we aren't having fun already...)

It is not possible for an external user to consume an API Proxy directly.  In order for your API Proxy to be visible to the outside world, you must first add it to a data object known as a "Product".  The purpose of a Product is to group proxies together into units that represent all the services needed to perform some larger unit of business functionality.

You should think of a Product as The unit of API exposure

The important thing to understand here is that in addition to an Product being able to contain multiple API Proxies, one API Proxy can be added to multiple Products.  This results in the formation of something called a many-to-many hierarchy, like this:

So remember: one API Proxy can be added to multiple Products, and one Product can contain multiple API Proxies.

Either way, if you do not add an API Proxy to a Product, then no external user will be able to consume that API Proxy - it will remain completely hidden from view.

Applications

Finally, we come to the last data object known as an Application.

We must be very careful to understand what is meant here by the use of the term "application", because in the context of API management, the term "application" does not carry the conventional meaning.

The conventional meaning for the term "application" is a unit of software with which a user interacts in order to perform some business task.

In the context of API Management, an "application" is the unit of API consumption.  In other words, if you, as the developer of some external business application wish to consume the API Proxies exposed through the various Products, you must declare your usage of those Products by the creation of this data object known as an "application".

In other words, in API Management, an "application" represents one user's subscription to a specific set of Products.  If a different user wishes to subscribe to the same set of Products, then they must create their own application.  This is how API Management is then able to manage the usage of APIs and keep track of things like quotas.

As we've already seen with API Proxies and Products, there is a many-to-many relationship between Products and Applications.  One Application can contain multiple Products, and one Product can be consumed through multiple Applications.

Two Different Perspectives: Development and Consumption

As was described above, there are two different tools used for the development and consumption of API Proxies.

If you are the developer of an API Proxy, then you use the API Portal and are concerned with creating the data objects outlined below.

However, if you are the developer of some front end application such as an iPad app, then you will be looking at the API Proxies from the perspective of a consumer, not a developer; therefore, you will use the Dev Portal and be concerned with the data objects outlined below.

In the next document, we will look in overview at the development of each of these data objects: Systems, API Proxies, Products and Applications

Part 2 - Overview of SAP API Management Tools

Chris W

Definición

En los documentos anteriores hemos revisado los siguientes temas:

En este documento veremos como completar valores en variantes dinámicas a partir de variables de usuario.

Para esto utilizaremos como ejemplo el siguiente reporte:

Supongamos que necesitamos que los parámetros Sociedad, Material, Lote y Centro se llenen automáticamente con unos valores prefijados para cada usuario.  Una opción podría ser que todos esos datos estén  en una tabla Z de modo que los datos se traigan mediante un SELECT a dicha tabla. Esto implicaría tener una transacción que actualice esos datos  y una política de administración de la misma. Ademas, es posible que algunos de estos datos estén cambiando con cierta regularidad y sea el usuario mismo quien deba definir el valor que van a tener, lo que podría causar que nos llenemos de un montón de solicitudes de cambios y transportes de los valores de esa tabla.   Podríamos entonces permitir que el usuario sea quien haga los cambios pero tendríamos asegurarnos de que solo pueda afectar sus propios valores

Una alternativa estándar con la que podemos darle ese control al usuario sin afectar la seguridad es mediante variables de usuario.

Definición de parametros en el programa ABAP

En primer lugar, debemos asegurarnos de que los parámetros que queremos enlazar con la variable de usuario tengan asociado un parámetro SET/GET de memoria SAP mediante la cláusula MEMORY ID.

Definición de valores para las variables de usuario

El paso siguiente es asignar el valor de la variable.   Para ello ejecutamos nuestro reporte y seleccionamos las siguientes opciones del menú :  Pasar a -> Variables Usuario

A continuación se nos presentaran las dos variables que hemos asociado a nuestros parámetros.  Primero seleccionaremos la opción MAT que corresponde al material.

Seleccionamos la opción variable:

En la ventana siguiente ingresamos el valor que vamos a asignar a la variable:

Confirmamos la grabación en las siguientes ventanas de diálogo:

Una vez hecho esto habremos asociado nuestro valor personalizado para la variable MAT.  Procedemos de igual forma con la variable CHA correspondiente al parámetro Lote.

Creación de la variante dinámica

Una vez hecho todo esto podemos crear la variante de la siguiente forma:

• Invocamos el programa y llenamos los campos que van a tener valores fijos, dejando vacíos los que van a calcularse dinámicamente.  Para este caso vamos a dejar en blanco los campos Material y Lote, luego de esto presionamos el botón de guardar.

• Como en los casos anteriores, en el dialogo siguiente escribimos el nombre y descripción de la orden.  Luego de esto nos ubicamos en el campo Material.

• Hacemos doble clic sobre el campo correspondiente a la columna "Variable Selección".  En el diálogo resultante seleccionamos la opción "B - Variable especifica de usuario.

Veremos entonces que campo correspondiente a la columna "Nombre de Variables" se debe llenar automáticamente con la descripción asociada a la variable MAT.

Repetimos los mismos pasos para el parámetro de selección LOTE obteniendo el siguiente resultado:

• Una vez lista nuestra variante presionamos el botón de guardar y regresamos a nuestro reporte.

Utilización de variables de usuario en la variante dinámica

• Como paso final ejecutamos el reporte y seleccionamos la variante "VAR_TEST" que acabamos de crear.

Al seleccionar la variante veremos que los parámetros Material y Lote se han completado con los valores que ingresamos para las variables.

Creación de variables de usuario

Para el caso descrito en este documento hemos utilizado 2 variables de usuario definidas en el estándar, lo que implica que si esta misma variable es utilizada en otros programas los valores que hemos almacenado se llenen de forma automática en esos programas.  En el siguiente documento revisaremos como se crean nuevas variables de usuario que podemos también utilizar en nuestros desarrollos.

Having trouble? Want to share feedback and suggestions? Just post in our CAL discussion forum.

All planned or unplanned maintenance windows of SAP Cloud Appliance Library will be announced on this page.

To receive e-mail notifications for maintenance activities, you have to log on to SCN and from the Actions box choose the Receive email notifications option.

SAP Cloud Appliance Library runs on SAP HANA Cloud platform. The maintenance activities and the infrastructure downtimes of SAP HANA Cloud platform might cause a temporary unavailability of SAP Cloud Appliance Library. For more information about the downtime activities of SAP HANA Cloud, see the following links:

• General Terms and Conditions for Cloud Services
• SAP HANA Cloud Supplemental Terms and Conditions
• Terms of Use Agreement for the SAP HANA Cloud Site
• SCN maintenance page of SAP HANA Cloud

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system from June 27th 2016 between 09:00 – 10:00 CETS.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Completed System Maintenance

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system maintenance has been completed. The system is up and running.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system from May 30th 2016 between 12:00 – 13:00 CETS.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Increased AWS API Error rates

Dear Customers,

Please be informed that SAP Cloud Appliance Library Operators detected increased rate of failed instance create operations in the last hour.

AWS confirmed increased API errors. For more information see AWS Service Health Dashboard - May 18, 2016 PDT

SAP Cloud Appliance Library Operators

Completed System Maintenance

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system maintenance has been completed. The system is up and running.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system from May 3rd 2016 between 09:00 – 10:00 CETS.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Completed System Maintenance

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system maintenance has been completed. The system is up and running.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system from February 25th 2016 between 09:00 – 10:00 CET.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Completed System Maintenance

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system maintenance has been completed. The system is up and running.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system on 10thFebruary  2016 between 09:00 – 11:00 CET.   due to activities connected with the database maintenance.

Impact

During the maintenance window SAP Cloud Appliance Library landscape will not be accessible.

There will be a notification on this page once the update is completed.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Completed System Maintenance

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system maintenance has been completed. The system is up and running.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system from February 5th 2016 between 09:00 – 10:00 CET.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Completed System Maintenance

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system maintenance has been completed. The system is up and running.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system from December 11th 2015 between 09:00 – 10:00 CET.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Completed System Maintenance

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system maintenance has been completed. The system is up and running.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system from November 16th 2015 between 09:00 – 10:00 CET.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Completed System Maintenance

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system maintenance has been completed. The system is up and running.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system from October 15th 2015 between 13:00 -14:00 CEST.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Completed System Maintenance

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system maintenance has been completed. The system is up and running.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system from October 7th 2015 between 08:00 – 09:00 CET.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Completed System Maintenance

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system maintenance has been completed. The system is up and running.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system from September 25th 2015 between 08:00 – 09:00 CET.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Completed System Maintenance

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system maintenance has been completed. The system is up and running.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system from August 21th 2015 between 08:00 – 09:00 CET.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Completed System Maintenance

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system maintenance has been completed. The system is up and running.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned downtime for SAP Cloud Appliance Library system from August 6th 2015 between 9:00 – 10:00 CET.

Impact

SAP Cloud Appliance Library landscape will not be available for any operations and access during the maintenance period.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Completed System Maintenance

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system maintenance has been completed. The system is up and running.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system from July  24th 2015 between 9:30 – 10:30 CET.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Completed System Maintenance

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system maintenance has been completed. The system is up and running.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system from June  26th 2015 between 8:30 – 9:30 UTC.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Completed System Maintenance

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system maintenance has been completed. The system is up and running.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system from June  1st 2015 between 7:00 – 8:00 UTC.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Completed System Maintenance

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system maintenance has been completed. The system is up and running.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system from April  30th 2015 between 7:00 – 8:00 UTC.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Completed System Maintenance

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system maintenance has been completed. The system is up and running.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system from April  3rd 2015 between 7:00 – 8:00 UTC.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Completed System Maintenance

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system maintenance has been completed. The system is up and running.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system from March 17th 2015 between 8:00 – 9:00 UTC.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators 

Completed System Maintenance

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system maintenance has been completed. The system is up and running.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system from March 16th 2015 between 10:00 – 11:00 UTC.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Completed System Maintenance

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system maintenance has been completed. The system is up and running.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system from March 10th 2015 between 7:00 – 8:00 UTC.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Completed System Maintenance

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system maintenance has been completed. The system is up and running.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system from February 17th 2015 between 12:00 – 13:00 UTC.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Completed System Maintenance

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system maintenance has been completed. The system is up and running.

SAP Cloud Appliance Library Operators 

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system from February 11th 2015 between 08:00 – 09:00 UTC.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Completed System Maintenance

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system maintenance has been completed. The system is up and running.

SAP Cloud Appliance Library Operators 

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system from January 12th 2015 between 09:00 – 09:30 UTC.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system on January 10th 2015 between 06:00 - 12:00 UTC.

SAP Cloud Appliance Library will be down for approximately 40 minutes.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Completed System Maintenance

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system maintenance has been completed. The system is up and running.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system from November 27th 2014 between 09:00– 09:30 UTC.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Completed System Maintenance

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system maintenance has been completed. The system is up and running.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system from October 17th 2014 between 09:00– 09:30 UTC.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Completed System Maintenance

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system maintenance has been completed. The system is up and running.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system from September 25th 2014 between 09:00– 11:00 CET due to activities connected with the database maintenance.

Impact

SAP Cloud Appliance Library landscape will not be available for any operations and access during the maintenance period.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Completed System Update

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system update has been completed. The system is up and running.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system from September 10th 2014 between 08:00– 08:30 UTC.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Completed System Update

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system update has been completed. The system is up and running.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system from August 12th 2014 between 07:00– 07:30 UTC due to activities connected with the database maintenance.

Impact

SAP Cloud Appliance Library landscape will not be available for any operations and access during the maintenance period.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Completed System Update

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system update has been completed. The system is up and running.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system from June 26th 2014 between 10:00– 12:00 UTC due to activities connected with the database maintenance.

Impact

SAP Cloud Appliance Library landscape will not be available for any operations and access during the maintenance period.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Completed System Update

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system update has been completed. The system is up and running.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system on Tuesday, April 22th 2014 between 14:00 – 15:00 UTC.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Completed System Update

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system update has been completed. The system is up and running.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system on Friday, February 14th 2014 between 10:00 – 11:00 UTC.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Completed System Update

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system update has been completed. The system is up and running.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system on Monday, September 9th 2013 between 08:00 – 09:00 UTC.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Completed System Update

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system update has been completed. The system is up and running.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system on Monday, August 5th 2013 between 08:00 – 09:00 UTC.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Completed System Update

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system update has been completed. The system is up and running.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system on Monday, July 1st 2013 between 08:00 – 09:00 UTC.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system on Wednesday, June 05th 2013 between 08:00 – 09:00 UTC.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Completed System Update

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system update has been completed. The system is up and running.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system on Thursday, May 16th 2013 between 13:00 – 14:00 UTC.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Completed System Update

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system update has been completed. The system is up and running.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system on Monday, April 15th 2013 between 07:00 – 08:00 UTC.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Service Health Dashboard

Dear Customers,

Please be informed that Amazon reported issues in US-EAST-1 region on March 20th 2013, 5:34PM PDT, related with degraded performance for some EBS Volumes which can affect starting new instances in the SAP Cloud Appliance Library system. The issue is now resolved, but if you experience any problems with the system, please let us know.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Completed System Update

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system update has been completed. The system is up and running.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system on

Wednesday, 13 March 2013 between 07:00 – 08:00 UTC.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Completed System Update

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system update has been completed. The system is up and running.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system on

Wednesday, 13 February 2013 between 07:00 – 08:00 UTC.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Completed System Maintenance

Dear Customers,

Please be informed that the SAP Cloud Appliance Library system maintenance has been completed. The system is up and running.

SAP Cloud Appliance Library Operators

Planned Maintenance

Dear Customers,

Please be informed that there will be a planned maintenance for SAP Cloud Appliance Library system on

Friday, 14 December 2012 between 07:00 – 08:00 UTC.

There will be a notification on this page once the new product version is successfully applied.

Thank you in advance for your understanding.

SAP Cloud Appliance Library Operators

Erschließen Sie neue Möglichkeiten in der digitalen Wirtschaft und vereinfachen Sie Ihre Geschäftsabläufe mit SAP S/4HANA.
Die neue Suite basiert vollständig auf der zukunftsweisenden In-Memory-Plattform SAP HANA und bietet mit SAP Fiori eine personalisierte Benutzeroberfläche. Ob in der Cloud oder als On-Premise-Lösung – SAP S/4HANA ebnet den Weg für eine schnelle Wertschöpfung in allen Geschäftsbereichen und Branchen.

• Überblickstraining – von der Business Suite zu S/4HANA
• SAP S/4HANA Analytics
• SAP S/4HANA Finance: Informationen zu unserem Gesamtcurriculum
• SAP S/4HANA Finance: Kompaktseminar (Release 1511) inklusive Zertifizierung
• SAP S/4HANA Finance: SAP Fiori for Finance and Controlling - lernen Sie die SAP Financials Fiori Apps kennen
• SAP S/4HANA Materials Management and Operations ("Logistik" im klassischen ERP)
• SAP S/4HANA Administration

Unser Schulungsangebot wird regelmäßig aktualisiert und erweitert. Sämtliche aktuellen Informationen über unser komplettes Schulungsangebot (Inhalte, Termine, Preise usw.) finden Sie stets aktuell im Online Trainingskatalog und unter den nachfolgenden Links:

1. How do I schedule a migration?
   • 4.x and 5.x customers
     1. Please complete the 6.x Migration Planning Checklist (Provided by john.lopus@sap.com)
     2. Email john.lopus@sap.com with scheduling requests.
     3. Please include desired timeframe for migration and planned migration type. ie. Manual vs. Assisted (details below).
2. When will migrations take place?
   • Early Adopter – April through June
   • Scheduling 4.x and 5.x – Starting with July timeslots
3. How do I learn more about 6.x?
   • What’s New help.sap.com
   • What’s New Webinar: Recording | Slides
   • IBP Customer Group: 6.1 Webinar Series
   • 6.x Customer Onboarding Guide
   • User Management - SAP Cloud Integration | Help |Webinar Recording | Slides | FAQ
   • 6.x Migration Guide
4. What kinds of “migrations” are there and what are the differences?

5.  By when do I need to complete the migration?

• Goal is to have all customers on 6.x by end of 2016.

6. License or cost implications?

• No license implications for Test and Production licenses

Administratoren, die SAP-Anwendungen in VMware virtualisierten Systemlandschaften betreiben möchten, benötigen umfassendes und plattformübergreifendes Know-how.
In der Schulung AD310 - VMware vSphere – Install, Configure & Manage for SAP System Administration erwerben sie schnell und praxisorientiert das für die SAP-Virtualisierung benötigte Wissen. Komplett überarbeitet basiert der Kurs auf VMware vSphere 6.
Dieses Seminar richtet sich speziell an Systemadministratoren, System Engineers und Operators, die den Einsatz von SAP Systemen unter VMware vSphere 6.X planen. Sie lernen, wie virtuelle Maschinen optimal für SAP-Systeme konfiguriert, installiert und administriert werden. Die Schulungsinhalte werden anhand zahlreicher Beispiele praxisnah vermittelt. So wird sichergestellt, dass Teilnehmer nach dem Kurs in der Lage sind, erworbenes Wissen schnell und zielführend einzusetzen.
Weitere Informationen finden Sie hier:

Unser Schulungsangebot wird regelmäßig aktualisiert und erweitert. Sämtliche aktuellen Informationen über unser komplettes Schulungsangebot (Inhalte, Termine, Preise usw.) finden Sie stets aktuell im Online Trainingskatalog und unter den nachfolgenden Links:

In der neuen 5-tägigen Schulung WDE390 (Entwickeln von SAP Fiori Oberflächen) erlernen Sie, wie SAP Fiori Oberflächen mit Hilfe von SAPUI5 erstellt werden können.
Nach einem Überblick über die Grundlagen von SAP Fiori und die Konzepte des Design Thinkings und Visual Design führt Sie die neue 5-tägige Schulung WDE390 (Entwickeln von SAP Fiori Oberflächen) in die SAP Fiori Design Guidelines ein. Anhand zahlreicher Beispiele und Übungen wird demonstriert, wie diese Guidelines praktisch angewendet werden.

Ferner erlernen Sie die Entwicklung der konzeptionellen SAP Fiori Anwendungen Master-Detail und Working List sowie die Implementierung analytischer Anwendung mit dem sap.viz-Framework. Gezeigt wird auch, wie das SAP Fiori Launchpad technisch aufgebaut ist, wie SAP Fiori Anwendungen in das SAP Fiori Launchpad integriert werden können und welche Möglichkeiten gegeben sind, das Launchpad an eigene, unternehmensspezifische Anforderungen anzupassen.

In der Schulung erfahren Sie auch, wie UI2-Dienste wie Personalisierung oder Navigation in eigenen SAP Fiori ähnlichen Anwendungen verwendet und integriert werden können. Schließlich steht auch auf der Agenda, wie eine typische Infrastruktur für die Entwicklung von SAP Fiori Apps aussieht.

Beginnen Sie heute noch damit, Ihr Expertenwissen für die Zukunft aufzubauen.

Unser Schulungsangebot wird regelmäßig aktualisiert und erweitert. Sämtliche aktuellen Informationen über unser komplettes Schulungsangebot (Inhalte, Termine, Preise usw.) finden Sie stets aktuell im Online Trainingskatalog und unter den nachfolgenden Links:

Password Self Service Configuration in SAP GRC AC 10.0 allows users to reset their passwords. This helps users to perform self service password reset and also employee can self-update  personal details.

Please find few common issues that are faced during configuration of PSS.

After submitting the PSS action, the error " Password reset failed: no valid Email-id maintained for user id" appears and nothing happens.

• Go to SPRO > SAP Reference IMG > Governance, Risk and Compliance > Access Control > Maintain Data Sources Configuration and make sure you have Connectors setup for each of the Data Sources.

• Execute the synch. Job GRAC_REPOSITORY_OBJECT_SYNC program again for the Connector you are using as your User Source and then attempt it again.

• GRACUSER is the right table to get the user's email if it is being populated correctly. Setting up this should fix it.

After using "Reset Password" option and Clicking on the Next button the following error is displayed "user is locked"

• In the PSS global configuration settings, you can define after how many failed attempts the user gets locked out from PSS. This setting can be configured in SPRO > SAP Reference IMG > Governance, Risk and Compliance > Access Control> User Provisioning > Maintain Password Self Service.

• Please see SAP Note: 2018010

When the end users access the "End User Logon Page" link in a new browser for resetting the passwords for their ids in the backend systems, freshly, it is asking for user id and password but not prompting for user ID and Password when the same is accessed through NWBC. How to troubleshoot this?

• Make sure that the guest user in configured in each of the 10 services in SICF for the EU Logon Pages to work.

Admin Registered Questions are not visible in PSS.

• Please make sure all the PSS questions are maintained in all the languages which are used by End Users including user default languages.

• PSS questions are visible with user default language from SP9 with configuration in IMG to maintain support language as in steps below: Go to SPRO > IMG > GRC > Access Control > General Settings->Maintain Supported Languages.

• Default language is maintained at first in the sequence. If no questions of default language are available then the next language in the sequence becomes the default language.  

While trying to Register Security Questions for Admin Registered Questions the following error message is displayed.

• The Field 'Number of Questions' is not maintained in the SPRO configuration. To Resolve this:

• Execute transaction code SPRO > IMG > Governance Risk and Compliance->Access Control->User Provisioning->Maintain Password Self Service

• Maintain the required value in field 'Number Of Questions’.

While trying to reset password, the user is receiving the error message 'You can change your password only once a day'

• Password parameter is not set in RZ11 on the system the user is attempting to change the password.

• On the plugin system please set the RZ11 password parameter in system as the password has to be changed for system where user actually exists.

• The parameter which needs to be checked is as below:
  login/password_max_reset_valid

The error message "User is not registered. Please register the user first"  is displayed in PSS after registering the security questions.

• Prior to SP10 of GRC 10.0 If the PSS authentication source is set to "challenge Response" then Questions were getting registered against user maintained in SICF web service grac_gaf_pwd_selfservice_eu", not against logged in user.

• Upgrade to SP 10 or above or Implement the note 1747265 to resolve the issue.

IMPORTANT TAKEAWAY ABOUT PSS

• Following password status are supported by GRC - Password Self Service (PSS) functionality.
  • Normal User having productive password
  • Productive password expired
  • Initial password expired
  • Incorrect Logon lock

• Password Self Service (PSS) functionality is not supported for
  • Deactivated passwords
  • Admin Lock(User is locked by Admin)

• Standard delivered PSS notification is delivered under document 'GRAC_CUP_PSS_NOTIFY'.

• The NWBC Authorization used for managing Password Self Service are as follows:

• During the password reset phases, only those Plug-in systems would be shown in the list of systems for which the User Sync has been done and the logged-in user exists in GRC Box repository for that Plug-in system.

• The following parameters can be considered to control the system generated password:

       GEN_PSW_MAX_DIGITS

       GEN_PSW_MAX_LENGTH

       GEN_PSW_MAX_LETTERS

       GEN_PSW_MAX_SPECIALS

Any Subtractions or additions to the document is most welcome.

Regards,

Rakesh Ram M

Dear Partner,

Update since January 2016:

The Certified SAP HANA Directory was enriched with all the SAP Business One for SAP HANA server configurations.

To access the list of the certified servers, please follow this link. Then, you will need to select the 'Appliance Type' --> SAP Business One.

For full BoM, please check the attached document from this blog.

New updates available since 30.11.2015.

• Lenovo certified their Haswell offer (ThinkServer) from 64GB up to 512GB.
  • The RD550 and RD650 (Haswell 2x E5-2670v3) are complementing the existing x-series.

New updates available since 08.10.2015

• Huawei certified in August their servers HW RH2288H V3, running on Haswell E5-2670v3, with memories from 64GB up to 512GB.
  They can now be ordered following the BoM attached to this blog.

New updates available since 01.09.2015

• HP certified in August their servers ProLiant ML350 Gen9, ProLiant DL360 Gen9 and ProLiant DL380 Gen9, running on Haswell E5-2670v3, with memories from 64GB up to 512GB.
  There are available chassis for rack deployment and tower and can now be ordered also following the BoM attached to this blog.

Note: All sizes have now been updated!

New updates available since 07.07.2015

• Fujitsu certified in May their servers PRIMERGY RX2540 M1, RX2560 M1, TX2560 M1, running on Haswell E5-2670v3, with memories from 64GB up to 512GB.
  The chassis are available in rack and tower versions and can now be ordered also following the BoM attached to this blog.

New updates avaialble since 03.07.2015

• Dell changed the storage setup (reduction of the # of disks) of their offer T630/730 R630/730.

New updates available since 01.06.2015.

• Lenovo certified their Haswell offer (system x) from 64GB up to 512GB.
  • The x3500 M5, x3550 M5 and x3650 M5 (Haswell 2x E5-2670v3) are complementing the exisiting x3850/ X6 (IvyBridge 2xE7-4880v2 or 4xE7-4880v2)

New updates available since 19.02.2015.

• Dell just certified the first Haswell configurations, which are available from 64GB up to 512GB.

This document contains all Bill of Materials for SAP Business One for SAP HANA certified servers.

This file is to be updated often, and depending of HW vendors capacity to recertify new configurations.

Please open the attached file with MS Excel.