Skip to Content
Technical Articles

ABAP in SAP Cloud Platform – Basic Fiori Application – Part 2

This is the second blog in the 2-part series on Basic Fiori Application development on SAP Cloud Platform, ABAP Environment. Here is the link to first blog:

Part 1

In this blog, we will cover the part of service generation based on the data model created in first blog.

Service Definition

Service definition is used to define which data is exposed as a business service. It is a consumer-specific but protocol-agnostic perspective on a data model.

One CDS view can be part of multiple service definitions, which are being used for applications created for different types of consumers.

I created service definition, where I exposed both CDS views:

Service Binding

Service binding is used to bind a service definition to a client-server communication protocol such as OData. It defines how a service is offered to a consumer, whether through a UI service or as a Web API.

I created service binding for the service definition defined in earlier section:

You can notice that Binding type is ‘ODATA V2’. So, service generated from here can be used as a UI service, for example, as a Fiori elements application. It can also be seen that CDS entities and their relationships are shown on the right side.

If you want to see the OData service generated from this development, click on ‘Service URL’ on the right-side of the screen.

Beauty of Steampunk is that you can see the ‘UI Preview’ of your application without going to the Web IDE. If you put cursor on ‘SalesOrderDetails’ and click ‘Preview’, It will open a new browser window, provide your credentials and you will see your generated Fiori screen.

When I press ‘UI Preview’ for my development, I see the Fiori elements generated application, where I can navigate and perform any actions as well. Here is the application for this development:

First Screen:

Press ‘Go’ and you see Sales Order Header Details:

Navigate to any line item details:

To conclude, I hope above development steps and explanations gave you fair idea about development in Steampunk system.

I strongly recommend you go through below links and understand Restful Application Programming model and create more such scenarios on Steampunk. Don’t forget to share your learnings!!

ABAP RESTful Programming Model

Development on SAP Cloud Platform ABAP Environment

4 Comments
You must be Logged on to comment or reply to a post.
  • Hi, thanks for that blog.

    If I understand this correctly, this Fiori app can only be accessed from developers using Eclipse.
    Is that correct? And what are the next steps in order to make the Fiori app accessible to end users?

    Cheers,
    Alej

    • Hi Alej,

      Next steps to make the Fiori app accessible to users would be to create a communication scenario for this service and then corresponding communication arrangement. OData service is then available over the internet and you can consume the same in any Web IDE to create Fiori application.

      I just checked that in trial version, provision to create communication arrangement is not enabled. Steampunk system’s dashboard Fiori launchpad doesn’t have communication related apps. So, I don’t think same can be developed in trial version.

      Regards

      GK

  • Thanks Gaurav,

    I will definitely give it a go when I get back from holidays

    But the scenario I usually think about for steampunk is to get data from rest sources. Sure, custom tables are a valid use case, but stoll looks like an odd example

    Marcello

    • Hi Marcello,

      Since creating a destination instance is not possible for trial steampunk instance, i wanted to keep the development to something people can try on trial instance.

      I agree that connecting other systems, mashing up the data from different systems is valid industry use case.

      Regards

      GK