SAP One Domain Model – How SAP One Domain Model can help our customers?

[former_member728677]

In recent years, SAP has acquired several cloud solutions like Success Factors and Ariba to extend the solution portfolio. In contrast to past solutions, which were mainly based on a monolithic ERP (SAP ERP and S/4HANA) with tight local integration, the new ones must be explicitly integrated across different tenants to form consistent end-to-end scenarios and processes. The lack of out-of-the-box integration scenarios is still a major complaint for our customers, because integration built by the customers themselves can be expensive and not satisfactory. Our customers have a clear expectation of predefined integration scenarios among the different SAP solution offerings.

This requirement led to an SAP initiative to address this situation with Intelligent Enterprise scenarios. As we started to implement these scenarios, challenges emerged when it came to bringing applications together with a common understanding of semantics. On top of that, the micro-service approach for new cloud-native application development increased the urgency for semantic alignment, which is necessary for the delivery of end-to-end solutions by SAP. The more scenarios that are executed across different components, the more cross-system analytics are required to enable our customers with adequate reporting of end-to-end scenarios and processes. The SAP One Domain Model, as a taxonomy, is our answer to those challenges and use cases. We support our customers by delivering a harmonized domain model for business objects that are distributed to all the different solutions in the Intelligent Enterprise Suite. With a central integration point via SAP One Domain Model, we provide a solution to several challenges customers face in their day-to-day work, including:

• Eliminating the need for point-to-point integrations, by providing mapping capability to a central domain model for the master data.


• Allowing our customers to easily develop extensions that can be more stable in future backend updates and upgrades.


• Motivating to develop more and more applications and extensions based on a standard and stable data models to be leveraged in different line of businesses and Industries.


• Enabling the existence of consistent data models, so that the suite feels as one product.


• Providing the foundation for a logical data model that can be used for different uses cases, from simple analytics to more advanced analytics scenarios.

It also provides a basis for a consistent view of master data across the entire hybrid landscape by mapping objects to a central domain model. The integration of business processes always relies on compatible data models, and here is where SAP One Domain Model plays a big role.

When helping companies think about the best solutions to support their business and how their architectures will look in the future, is very important to both adapt the customer landscape to suit their business needs and to provide the best guidance. To address hybrid landscapes and hybrid clouds, the right integration strategy is the focus of more and more decoupled architectures.

Thanks for your reading. I would be more than happy to get your thoughts and feedback in the comment section of this blogpost.

Meltem Kahraman

Product Manager of SAP One Domain Model

WHAT COMES NEXT?

Have a look at our official documentation, where you can get more insight into SAP One Domain Model. Have fun checking out the business objects of the SAP One Domain Model on the SAP API Business Hub.

** Please be aware that this blog post is from 2021 and part of the content is already outdated, please refer to more updated ODM related blogs **