In previous blog post we gave you some insights and basic understanding of SAP One Domain Model and technical concept behind it. To summarize it again: as you already know, the Intelligent Enterprise Suite at SAP provides next generation customer experience by delivering E2E integrated, intelligent solution for each line of business across different business solutions and applications. To ensure a smooth communication between different applications along the processes, SAP uses the SAP One Domain Model (ODM). This is a coherent data model with common semantics used to exchange data between applications of the Intelligent Enterprise Suite and its ecosystem.
ODM is released via API Business Hub which provides a visual presentation of the ODM between business objects each other and their types. The ODM is structured by domains. Each domain captures the essence of a certain area of business and contains different types like aspects, codes, entities and enums. Each domain can also have subdomains.
The following picture shows the graphical view of the ODM. This graphical view provides an overview of connected business objects and shows how they are connected each other. With release v2.1, SAP customers can use the integrated filtering function for domains and their types. The following picture shows the root entity BusinessPartner which has been released with version 2.1.
In this graphical view it is possible to see all relations between BusinessPartner to other entities and other domain types like aspect, codes etc. This release of ODM provides an integrated filtering function for each domain type. It is possible to filter by the following types: Entities, Aspects, Codes, Types and Enums.
As mentioned above SAP One Domain Model supports now the object BusinessPartner in the Lead to Cash and Source to Pay process via MDI.
With the release 2.1. we enabled ODM BusinessPartner which describes an organization or person in which companies have a business interest. BusinessPartner is defined as ODM object and can be transmitted from/to MDI. Via MDI it can be shared and synchronized in the integrated Intelligent Suite and will be used as Customer within the Lead to Cash and Supplier in the Source to Pay processes.
You can get a more detailed look into these processes on the API Business Hub page for SAP’s reference business processes.
Below you can see the SAP One Domain Model for BusinessPartner released on the SAP API Business Hub (click on “Explorers”, “SAP One Domain Model”), which provides a visual documentation of all business entities and their relationships to each other.
WHAT COMES NEXT?
You can also find an official documentation where you can get more insights into SAP One Domain Model. Have fun in checking out the business objects of the SAP One Domain Model on the SAP API Business Hub.