Evaluating SAP Build

After completing this lesson, you will be able to:

After completing this lesson, you will be able to:

  • Compare citizen development versus traditional development
  • Differentiate between the different products in the SAP Build solution

The Emergence of the Builder

In the lesson Introducing SAP S/4HANA Cloud, we learned that one of the benefits of cloud computing is the rapid delivery of innovation in the form of frequent and regular software updates. Also, in the previous lesson, we discussed how a well designed and executed consumer-grade UX strategy leads to the successful adoption of software, and we saw how SAP Fiori apps provide a path for customers to ensure this adoption. There is another equally important and available path for customers to use for adoption, which we explore in this section.

The rapid innovations from cloud computing inevitably lead to rapid changes in business requirements. Business requirements that are changing rapidly mean software applications that need to be created and changed rapidly. While this is not necessarily a bad thing, a real resource constraint exists: IT capacity. While physical capacity, such as computing power, memory, and so on, can be scaled up to meet changing resource needs, people (specifically developers) do not scale quite so easily. This has led to a developer shortage in many, if not most, organizations' IT departments.

This tension between the need for both an increased number of apps to be developed along with the quick pace for their development has necessitated a change in thinking about who does development. Enter the Citizen Developer, which SAP refers to as a Builder. A builder is someone who builds apps (often for a specific LoB) using specialized tools preapproved by the IT department and released to be used for development. This gives businesses an additional option for application development beyond buying prepackaged apps or building apps from scratch (both of which require developers to be able to utilize).

Developers still require tools specialized for their purposes – tools based on a particular language and programming model, with integrated debuggers and advanced testing capabilities. Builders do not need the same type of tools. The tools preapproved by the IT department for builders to use are often referred to as low-code/no-code tools and they are often abbreviated as LCNC.

Low-code is a method of designing and developing applications using intuitive graphical tools and embedded functionalities that reduce traditional – or pro-code – writing requirements.

No-code is a method that benefits from a similar user experience as low-code, but goes the extra mile by allowing nontechnical business users to develop applications without having to write a single line of code.

SAP Build

SAP’s Low-Code/No-CodeToolset

While SAP Fiori is the UX framework in which the vast majority of SAP S/4HANA applications are developed in, LCNC is now a legitimate and viable strategy that customers can utilize. To help customers take advantage of citizen development, SAP has the SAP Build solution, which is precisely tailored to the needs of builders.

The SAP Build solution is composed of the following three different tools that work together:

  • SAP Build Apps
  • SAP Build Process Automation
  • SAP Build Work Zone

All three solutions are available as services through SAP Business Technology Platform (BTP) and thus are of part of SAP BTP’s unification of application development, data and analytics, integration, automation, and artificial intelligence capabilities under one roof.

SAP Build Apps

SAP Build Apps is a no-code solution to create applications. Builders can use SAP Build Apps to build user interfaces easily, using drag and drop techniques. The corresponding data models and business logic can be integrated seamlessly and without code. Applications can connect to SAP S/4HANA Cloud easily and securely by utilizing prebuilt connectors and standard released APIs. As a part of SAP BTP, SAP Build Apps integrates seamlessly with SAP BTP for authentication services when public standardized released SAP APIs are used for application development.

SAP Build Process Automation

Similar to SAP Build Apps, SAP Build Process Automation is also a no-code solution to create automated workflow processes. Builders can use SAP Build Process Automation to automate business processes and tasks without writing code. This is accomplished with drag and drop and also AI capabilities. In addition, as with SAP Build Apps, prebuilt connectors and public standardized released SAP APIs from SAP S/4HANA Cloud can be used.

SAP Build Work Zone

The final tool in SAP’s LCNC toolset is SAP Build Work Zone. Virtually all organizations offer one or more portals, which offer a standardized entry point to end users to execute all applications relevant to their role. For SAP Fiori, the primary portal product is the SAP Fiori launchpad. For SAP’s LCNC toolset, it is SAP Build Work Zone. Builders can use this tool to create dynamic and engaging role-based entry point sites accessible from any device quickly and easily.

Create a UX using SAP Build Apps

Log in to track your progress & complete quizzes