Skip to Content
Author's profile photo Martin Herrmann

Extensibility highlights of S/4HANA Cloud 1708

With S/4HANA Cloud you get innovations on regular basis delivered by SAP. But custom specific business extensions or even new functionality is still an important part of your overall business solution. It is important that your custom adaptions and extensions are easily created and managed and that you keep an overview of the extensions. Finally, the time an effort for maintenance and testing should be keep to a minimum.

The SAP S/4HANA concept supports your business needs via

  • an easy to use extensibility apps in S/4HANA Cloud (in-app extensibility)
  • a seamless integration to SAP Cloud Platform to extend your business without impacting the digital core (side-by-side extensibility)

What is new with S/4HANA Cloud in 1708?

This release is the first shipment of the new  “extensibility cockpit” and “inventory app”.. With the two new apps you easily receive answers  regarding the extension capabilities of each scope item and what are the objects implemented for extensions and how are they used.

Info Center

  • Extensibility cockpit (currently only available in beta mode)
  • Inventory app

The extensibility cockpit provides full information regarding extension options in S/4HANA Cloud. You begin with a business perspective. You select the best practice content you need to extend

  • edition,
  • solution scope,
  • scope item(s)

You filter the relevant business contexts. Business contexts are SAP entities that can be extended by custom fields and/or custom logic (ABAP code). “Billing document” or “Business Partner Core View” are examples of business contexts.

For each business context, you see the overview of the available extension objects. Extension objects are OData, CDS views, Business Logic, UIs and reports or Forms. You get a list of Fiori screens that can be extended or you get a list of business logic, e.g. BADIs or you get a list of whitelisted APIs.

The extensibility cockpit app is currently in beta mode and it is planned with 1711 to have this available for a broader roll out.

With the Extensibility Inventory app detailed information about your custom created in-app extension objects is provided

  • Type and name of the extension object
  • Status
  • Last changed from and when
  • Usage
  • Transport info

On selecting a particular object, the details page displays the usage of this object. Further navigation is possible to respective objects listed in the Details page

Example of the extensibility inventory overview screen:

When clicking the custom business object “bonusrelevance for” you can see the following example of a drill down to a specific object:

This custom business object is used by two tiles (apps).  And furthermore, you see that a custom field uses this custom business object as well. This is a new feature shipped with SAP S/4HANA Cloud 1708.

Since SAP S/4HANA Cloud 1705 custom business objects can be used for associations:

  • Define your custom fields (define your own custom table)
  • Add logic in ABAP to determine “after modification” or to validate “before save”
  • Associate a custom business object to another custom business object

New with SAP S/4HANA Cloud 1708

  • create a custom field and associate it to a custom business object

In the following example, you use the “Custom Fields and Logic” app and create a new custom field for your product master

In this example, you can create your own custom field, use a custom table as value help and finally validate your selected field. You just need to define your custom field as “association”

Example: use association of custom field “relevance” in the product master


End to End extensions scenario for Side-by-Side extensibility

With the SAP Best Practices Explorer you receive an updated example of an end to end Side-by-Side extension scenario.

The scope item 1RW describes a step-by-step process to allow customers and partners to develop their own SAP Cloud Platform side-by-side applications with adjustment to their own business scenarios.You start with a ready to run example in five steps:

1 sign up for SAP Cloud Platform account (Trial available)

2 download the Set up instructions of Side-by-Side extensibility scope item 1RW

3. prepare your S/4HANA Cloud system according to the end to end instructions

4. Download the SAP Cloud Platform application from GitHub

5 deploy and run

As you can see,  it is an easy to use and well explained scenario.

For further details see related blog

Try it out and send us your feedback.

We are planning to extend the end to end scenario of 1RW step by step .


How to proceed?

Considering the roadmap of the following releases of S/4HANA Cloud we plan to extend the capabilities of custom business objects. If you need to extend the standard functionality and you only need S/4HANA Cloud data, you will have a powerful option with custom business objects.

When you want to extend the scope e.g. for big data or to extend the addressable user the SAP Cloud Platform is the right choice.

So the seamless integration of S/4HANA Cloud and SAP Cloud Platform is a main focus topic. This will be further improved with the next releases. Considering the Java development on SAP Cloud platform you should check the S/4HANA Cloud SDK: SAP S/4HANA Cloud SDK Overview

In case you see further requirements or you simply have questions about strategy or functionality just tell me.

Assigned Tags

      1 Comment
      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      Hi Martin and thank you for this detailed explanations!

      I am lost with the version "SAP S/4HANA Cloud, Private option": I can read on the market place that it "reach the full S/4HANA On premise solution/ scope" with the "Full extensibility Framework".

      What does it means? My understanding is that it is a pre-configured S/4H on premise version but following a Cloud subscription model with the possibility to adapt the customizing.

      Could you explain futher what "Full extensibility Framework" means in the context of this version?


      Thank you in advance