Enterprise Architecture Blog Posts
Need a little more room to share your thoughts with the community? Post a blog in the SAP Enterprise Architecture group to explain the more complex topics.
cancel
Showing results for 
Search instead for 
Did you mean: 
former_member12038
Product and Topic Expert
Product and Topic Expert

Disclaimer:

  • Information provided in this blog serves only as a general overview and does not replace any legal agreements between SAP and its contractual parties. As this blog may not be updated regularly, please refer to your assigned SAP Account or Partner Manager for up-to-date information, especially regarding roadmaps, licensing, and pricing models.
  • The SAP Reference Solution Architecture (at solution value flow level) provides a first orientation and high-level implementation guidance while covering a broad business and solution scope. Based on the breadth of the scope covered as well as the high-level nature (e.g. the guidance assumes a complete adoption of the SAP portfolio which is rarely the case in a real customer situation), SAP recommends assessing the architecture guidance in the context of a specific customer scenario. Additional integration development and enhancements might be required to achieve the desired outcome.

The blog SAP Reference Architecture Content: An Overview [1] explained how the standardized SAP Reference Architecture Content follows the SAP Enterprise Architecture Methodology, which aims to align Business Architecture Domain with IT Solution Architecture Domain.

MariaGoltz_0-1673530195213.png

 Figure 1 - SAP Enterprise Architecture Methodology – Linking Business and IT

Based on the SAP Enterprise Architecture Methodology, the standardized SAP Reference Architecture content provides a harmonized Business and Solution Architecture reference content which supports the Business and IT alignment by mapping business capabilities and processes with IT solutions. As such, it is composed of 2 parts:

  • SAP Reference Business Architecture (RBA) describes the scope and undertaking of any enterprise, in a business-centric and product-agnostic way.
  • SAP Reference Solution Architecture (RSA) explores how SAP addresses a customer’s business challenge with its unique product portfolio.

In this blog, we will take a closer look at the SAP Reference Solution Architecture Content (RSA) – what it is, how it is structured, and how it complements the SAP Reference Business Architecture (RBA).

A closer look at the SAP Reference Solution Architecture (RSA)

The SAP Reference Solution Architecture (RSA) shows how certain SAP products interact to realize a business process. It presents an implementable solution architecture, which is composed of different elements and has been created based on guidance from the SAP Product Engineering unit.

Capability Perspective – Bridging business and IT at the strategic-level

In the SAP Reference Business Architecture (RBA), the Business Capability describes the “what”, specifically the ability an enterprise needs to deliver value to its customers.

Equivalent to the Business Capability, the SAP Reference Solution Architecture (RSA) introduces the concept of the Solution Capability. 

The Solution Capability describes the “how”, particularly how a Business Capability can be concretely implemented by one or more Solution Components. Multiple Solution Capabilities can exist for a Business Capability when there are different ways to implement the Business Capability. The SAP Reference Solution Architecture provides a high-level recommendation on the most suitable Solution Capability for a specific business context.

Below is a simplified illustration of the relationship between Business Capability, Solution Capability and Solution Component. 

MariaGoltz_1-1673530607346.png

Figure 2 – Example of Solution Capability

The Solution Capability associates the Solution Component needed to realize a Business Capability. A Solution Component represents a single or a group of software products. There can be one or multiple mandatory Solution Components that are needed to realize the minimum viable scope of the Business Capability. In addition, there can be optional Solution Components that provide enhanced features, for example with respect to automation or optimization. If there are multiple Solution Components involved, they are typically technically integrated.

Process Perspective – Bridging business and IT at the operational-level

In the SAP Reference Business Architecture (RBA), an enterprise is described using 8 end-to-end Business Process patterns. An end-to-end Business Process contains Business Activities, which describe how value is generated by using certain Business Capabilities.

Corresponding to the Business Process, the SAP Reference Solution Architecture (RSA) has the concept of the Solution Process, Solution Value Flow, and Solution Process Flow.

The Solution Process is an implementation of a Business Process, using a defined set of Solution Components. A Solution Component represents a single or a group of software products.

In the SAP Reference Solution Architecture, there are various architectural artefacts that represent the Solution Process. One such architectural artefact is the Solution Value Flow, which displays the activities supported by the set of Solution Components. 

Below is a simplified illustration of a Solution Value Flow, which shows only a partial content for the Process Module “Deliver Service to Fulfill”. 

MariaGoltz_2-1673530963918.png

Figure 3 – Example of Solution Value Flow

On the other hand, the Solution Process Flows are more detailed diagrams, which depict the control flow and the specific sequence of steps in the process flow. The Solution Process Flow uses the Business Process Model Notation (BPMN).

Below is a simplified illustration of a Solution Process Flow, which shows only a partial content for the Service Order process flow.

MariaGoltz_3-1673531080490.png

Figure 4 – Example of Solution Process Flow

 

In Summary

The SAP Reference Architecture Content helps align Business and IT by mapping business challenges with IT solutions. It is composed of two parts:

  • SAP Reference Business Architecture (RBA) describes the scope and undertaking of any enterprise, in a business-centric and product-agnostic way.
  • SAP Reference Solution Architecture (RSA) explores how SAP addresses a customer’s business challenge with its unique product portfolio.

The long-term vision of the SAP Reference Architecture Content is to support customers in their business transformation, from discovering the recommended SAP solutions, understanding their business impact, and supporting their technical implementation along an integrated business process. Thus, the SAP Reference Solution Architecture contains different architectural artefacts. For strategic guidance, artefacts such as Solution Value Flows and Solution Capability Model cover a broad scope, focusing on the end-to-end Business Process. On the other hand, artefacts such as APIs, events, and data model provide technical implementation guidance, but only for a limited business and solution scope.

MariaGoltz_4-1673531239145.png

Figure 5 – SAP Reference Solution Architecture - From Strategy to Implementation

Do you want access to the SAP Reference Architecture Content? The SAP Reference Architecture Content is available as part of the One Process Acceleration Layer practice.  SAP Signavio Process Explorer [2], the gateway to access and explore content generated as part of the One Process Acceleration Layer practice, will be generally available in January 2023.

Reference

[1] SAP Reference Architecture Content: An Overview

https://groups.community.sap.com/t5/enterprise-architecture-blog/sap-reference-architecture-content-...

[2] SAP Signavio Process Explorer

https://www.signavio.com/products/process-explorer/

11 Comments

Great summary of RBA and RSA, thanks for this and your previous blog post, Maria! There is a lot of power in the connections between the two, e.g. between Business Capability and related Solution Capabilities, or between Business Processes and Solution Processes. These connections bridge the gap between purely business related, vendor independent modelling and the implementation of specific software that addresses business needs in real life.  It is the moment of truth and where the rubber hits the road, making the combination of RBA and RSA so powerful and unique.

juhik2003
Explorer

Very informative blog about SAP Reference Architecture. Capability and Process perspective connect the dots between end-user requirement and solution implementation level details. Mapping of various Business and IT components give a concrete starting point for any SAP Enterprise Architect. 

former_member12038
Product and Topic Expert
Product and Topic Expert

Additional Information: The SAP Reference Solution Architecture contains different architectural artefacts. Architectural Artefacts such as APIs, events, and data model provide technical implementation guidance, but only for a limited business and solution scope. To learn more, please check out SAP API Business Hub .

0 Kudos

Great content. Thank you!

I have one question: It is all about communication towards our peers and clients. Pictures and diagrams are a very helpul way to support this task. I wonder, if there is any resource available which could be used to show an overall solution architecture stack diagram of S/4HANA. Everybody is drawing it's own PPT / Visios and I would expect, that there might be also some SAP content available to be used?

Thanks in adance!

MartinMysyk
Product and Topic Expert
Product and Topic Expert
0 Kudos

Feel free to include artefacts that you use to communicate here on the site. You can add attachments to your posts or discussion entries. I know there are some good diagrams out there...

TimCa
Discoverer
0 Kudos

I think there is already considerable information available already from SAP which links business capabilities to solution components.  What is not clear is the consistency between these capability model views and this latest RBA / RSA ?  For example, SAP Transformation Navigator provides the ability to start with a pure capability view where it is possible to select all the relevant capabilities and see a clear mapping to solution components.   Are the capabilities in SAP TN the same as the capabilities in the RBA ?

Thanks

AVAShabAni
Explorer
0 Kudos

Hi Maria

 

I was wondering if the SAP Reference Solution Architecture content in Signavio, includes Solution Collaboration and Integration documents as well as Solution Data Model. Cause I am not able to find them.

 

cheers 

Birger
Explorer
0 Kudos

Please use the release SAP Signavio Process Explorer (SAP unified user id required)

https://www.signavio.com/products/process-explorer/

AVAShabAni
Explorer
0 Kudos

hi Birger, thanks for your response. I have been using teh process exlorer in Signavio. my question is the SAP Architecture Reference Content available in Signavio doesnt include Solution Collaboration and Integration documents as well as Solution Data Model. Have you been able to locate them?

Birger
Explorer
0 Kudos

integration content you can find in the Business Accelerator Hub

https://api.sap.com/allprocess

Data model besides the scope item regarding master data, I have not seen so far

 

add. Information:

I asked today in an EA partner session. answer was so called DFDs, Data flow documents in the api hub.

https://api.sap.com/search?searchterm=dfd&tab=All&refinedBy=true&top=12

e.g.

https://api.sap.com/dfd/SP1H1-DFDMasterDataFlows

 

 

 

 

AVAShabAni
Explorer
0 Kudos

thanks Birger, but that is not what I refering to. the SAP Architecture Refernce Content in SAP documentation is referring to multiple artifacts that dont exist in Signavio e.g. Solution Collaboration and Integration and Solution Data Model. I was wondering if I am missing something or when they are going to get published.