Identifying Key Features and Capabilities of Extending SAP Sales Cloud and SAP Service Cloud Version 2 using Side-by-Side Extensibility

Objective

After completing this lesson, you will be able to explain the key features and capabilities of side-by-side extensibility for enhancing SAP Sales Cloud and SAP Service Cloud Version 2 while maintaining a clean core.

Extensibility Options for SAP Sales Cloud and SAP Service Cloud Version 2

SAP Sales Cloud Version 2 and SAP Service Cloud Version 2, hereinafter commonly referred to as SAP Sales Cloud and SAP Service Cloud Version 2, offer many settings to tailor the solution to the customer’s business processes and meet their business needs to a certain extent. If this is not sufficient, SAP Sales Cloud and SAP Service Cloud Version 2 can also be extended to enhance its features and functionality.

Extensibility options are often divided into two categories depending on where they are implemented:

  • In-App Extensibility allows minor enhancements with tools built into the cloud solution, such as adding new fields, validating user input, or adjusting the user interface.
  • Side-by-Side Extensibility allows greater flexibility and more complex enhancements but requires a separate hosting environment, such as SAP Business Technology Platform (BTP). Typical use cases are: Implementing complex logic or embedding a BTP-hosted web app into the cloud solution's user interface.

The following illustration provides an overview of the different extensibility options and typical use cases:

Figure illustrates typical use cases for In-App Extension and Side By Side Extensions. In App Extension typical use cases are - Dynamic Page Layout, Language Adaptation, Add Database Fields, Create Custom Buttons and Actions, Add Custom Logic, and Embed External UIs. Side By Side Extensions typical use cases are, Custom Applications, External Functions and Services, External Entities and Analytics, Data Science and Intelligence, and IoT & Big Data. Similar features are a secured connectivity in the UI, Rules and Workflow, APIs and Events and Meta Data.

Side-By-Side Extensibility and Tools

Side-by-side extensibility offers more customization possibilities than in-app extensibility. It also places higher demands on the initial setup and operation due to the nature of the external environment. This includes managing connectivity and security aspects, as well as the development process itself, which also requires a higher skill set for developing web apps.

With the following products and services, SAP offers a variety of tools to assist you with side-by-side extending your solutions:

  • SAP Build Apps is a low-code/no-code development platform to create apps for native mobile use and the web.
  • SAP Build Code is a pro-code development platform that leverages ready-to-use SAP services and SAP's generative AI copilot Joule to simplify the development of SAPUI5, SAP Fiori, mobile, and CAP applications running on SAP BTP using the Cloud Foundry runtime. It is the successor of SAP Web IDE and SAP Business Application Studio.
  • SAP Build Process Automation combines capabilities from SAP Workflow Management and SAP Intelligent RPA with a powerful, yet intuitive no-code development experience.
  • SAP BTP, Kyma runtime is a fully managed Kubernetes runtime based on the open-source project "Kyma" that allows developers to extend SAP solutions with serverless Functions and combine them with containerized microservices.

The following section compares Low-Code/No-Code and Pro-Code approach.

Comparison of Low-Code/No-Code and Pro-Code Extensibility

Just like the contrast between in-app and side-by-side extensibility, the low-code/no-code method has its advantages, disadvantages, and limitations, where the pro-code approach becomes relevant.

Low-Code/No-Code Approach

Advantages:
  • Less technical expertise required. These platforms enable non-technical users to create of modify applications with ease.
  • Faster development cycle. Low-code and no-code platforms dramatically shorten the time needed to develop and launch applications.
Limitations:
  • Limited customization. These solutions may not offer the degree of customization or complexity that certain specific applications require.
  • Vendor dependence. Available features rely on the given framework, which can lead to constraints even for non-complex projects.

Pro-Code Approach

Advantages:
  • Greater flexibility. More technical freedom over the application design and behavior.
  • Complete customization. Tailored to meet specific requirements.
Limitations:
  • Requires technical expertise. It requires a substantial level of coding experience and knowledge.
  • Time-consuming. Writing code to extend an application can be a time-consuming task.

In essence, the choice between low-code/no-code side-by-side extensibility and pro-code side-by-side extensibility is determined by the specific needs of the project, the complexity of the task, and the available resources.

Introduction to Clean Core

Clean core is a governance-first approach that treats SAP applications as the stable, upgradeable foundation while enabling business differentiation through well-governed, decoupled extensions. In a side-by-side context, this means implementing UIs, services, and integrations on an external platform (for example: SAP Business Technology Platform or BTP ) that interact with the core only through released APIs and business events.

Note

These released APIs are under a "stability contract" (not a legal contract, but a technical contract) that ensures the API remains stable in the future. With this, your extensions will remain stable—even over upgrades—leading to less effort in upgrades (less testing, fewer adoption issues due to higher confidence in stability).

The Five Guiding Principles of Clean Core

Visual listing guiding principles for clean core: Business processes, Extensibility, Data, Integration, Operations.

SAP has established five fundamental clean core principles that serve as the strategic foundation for maintaining business-critical systems. These five guiding principles ensure that organizations can keep their systems agile, cost-efficient, and ready to adopt innovations that drive growth.

By adopting standard processes while incorporating stable extensions and integrations for differentiating processes, these principles enable customers to flexibly adapt to changing business requirements. They also enable customers to seamlessly adopt new capabilities without compromising system integrity or upgrade stability.

These principles collectively foster a clean core system environment that promotes efficiency, flexibility, and strategic excellence.

  1. Business Processes: This principle highlights the importance of staying competitive while simplifying business processes. By streamlining and optimizing these processes, organizations can enhance their operational efficiency and responsiveness.
  2. Extensibility: By decoupling extensions from the standard core, organizations can implement needed customizations and enhancements without compromising the core’s stability or consistency, enabling greater flexibility and scalability.
  3. Data: Managing data according to the latest standards is crucial for ensuring accuracy, compliance, and security. This principle emphasizes the importance of handling data efficiently to support informed decision-making and maintain data integrity across the organization.
  4. Integration: This principle's core is ensuring the system landscape remains reliable and adaptable. Seamless integration of various systems and components is essential for efficient workflows and continuous information exchange. This supports overall system dependability and flexibility.
  5. Operations: The final principle emphasizes maintaining effective and efficient operations. By improving operational practices and removing redundancies, organizations can boost productivity and optimize resource use. This ultimately leads to greater operational success.

Understanding the Need for Clean Extension

Having established the five clean core principles as the strategic foundation for maintaining agile and cost-efficient business-critical systems, we now explore the second principle: Extensibility. This principle emphasizes the preservation of a reliable and adaptable system landscape while enabling competitive differentiation. Clean extensions are inherently decoupled from the core by using only released APIs, ensuring that custom functionality doesn’t threaten upgrade stability.

This strategic separation streamlines upgrades and minimizes technical debt. As a result, it speeds up the adoption of innovation and shortens the time to market, enabling businesses to respond quickly to market demands while maintaining their competitive edge.

Benefits of Clean Extensions

Visual listing benefits of clean extensions: Upgrade Stability, Simple Upgrade Process, Flexibility, Time-to-Market Acceleration, and Flexible SAP Extensibility Options.

Upgrade Stability: Clean extensions help you stand out from the competition while maintaining stability during upgrades. This is achieved by clearly separating core SAP functions from your custom extensions. Keeping the core clean and limiting changes to standard SAP code ensures your system stays compatible with future updates.

Simple Upgrade Process: Decoupling extensions simplifies your upgrade process, enabling you to adopt innovations faster.

Flexibility: Reducing technical debt and increasing transparency gives you greater flexibility.

Time-to-Market Acceleration: Technical separation shortens time-to-market from concept to deployment.

Flexible SAP Extensibility Options: Select from the full range of SAP extensibility options, either on-stack or side-by-side with SAP BTP, supporting both low-code and pro-code development needs.

How to Achieve Clean Extensions

Visual showing the stages of how to achieve clean extensions: Decoupled Extension Creation, Continuous Governance, and Technical Debt Management.
  1. Decoupled Extension Creation: To achieve clean extensions that ensure upgrade stability, organizations must focus on creating decoupled implementations through the strategic use of released APIs. By leveraging modern extensibility technologies with SAP Build, and applying an SAP BTP-first strategy, organizations can choose between on-stack and side-by-side approaches based on their specific use cases. At the same time, they maintain complete separation from the core system. This decoupling approach not only simplifies upgrade processes and reduces technical debt, but also accelerates innovation adoption and shortens time-to-market from concept to deployment.
  2. Continuous Governance: To support the technical foundation, organizations should implement continuous governance practices that span from initial requirements through design, implementation, and deployment.
    • Requirement: Only allow extensions that add clear business value and set you apart from the competition.
    • Design: Define guidelines to ensure the cleanest option is used.
    • Implementation: Encourage developers to follow the clean core approach and document technical debt transparently.
    • Deployment: Introduce mandatory code checks and a structured exemption process.

Now, let’s see how company ABC uses a clean core approach with SAP BTP to extend SAP Sales Cloud and SAP Service Cloud Version 2 and streamline sub-case handling—without touching the core.

Scenario: Company ABC operates in a highly competitive industry where efficient customer support is critical for maintaining customer satisfaction and loyalty. Their SAP Sales Cloud and SAP Service Cloud Version 2 setup successfully manages customer support cases but lacks the capability to automatically create sub-cases for internal handling processes. This functionality is pivotal for their operational efficiency and ensuring that all necessary steps in the support process are meticulously tracked.

Solution: To implement this requirement without compromising the integrity of the SAP Sales Cloud and SAP Service Cloud Version 2 core system, Company ABC adopts the clean core approach. They decide to build a side-by-side extension using SAP Business Technology Platform (BTP). This extension interacts with the core system through released APIs and business events, ensuring that its custom functionality does not interfere with the stability or upgradeability of the core system.

Summary

  • Side-by-side extensibility enhances SAP Sales Cloud and SAP Service Cloud Version 2 beyond standard configurations. It achieves this by utilizing a separate hosting environment, such as SAP BTP, and adhering to clean core principles.
  • The choice between low-code/no-code and pro-code extensibility depends on the project's complexity, required customization, and available technical skills.
  • Clean extensions leverage released APIs to ensure upgrade stability and minimize technical debt.
  • The five clean core principles provide a strategic foundation for maintaining agile and cost-efficient business systems.