Demystifying One Domain Model w.r.t Master Data Objects
In the Cloud centric world of SAP, innovations are happening in lightning speed. Therefore it has become imperative to integrate core master data effectively among all these cloud systems. Never before there was more necessity to integrate core attributes of sap master data among the systems.
In this blog post, I will try to give a clear explanation about ODM by taking a simple master data object “Bank”.
SAP One Domain Model (ODM)
The SAP One Domain Model is a unified domain model for business objects distributed throughout different SAP applications, enabling those systems to speak the same language during data exchange.
Additionally, the SAP One Domain Model focuses on end-to-end Intelligent Enterprise Business processes and provides a visual representation of domains and models (example: Bank), creates a web of related domain classes, attributes, associations, and business rules that help in the integration of data from various SAP applications.
- Bank Master in SAP ERP:
Table name: BNKA
Bank Master (BNKA)
Tcode : SEGW – is used to create and model an OData service in gateway builder.
Tcode : /IWFND/MAINT_SERVICE – is used to register the OData service once created OData in SEGW.
2. Bank Master in SAP S/4HANA Cloud:
- TCode: LTMC (Legacy Transfer Migration Cockpit)
3. APIs for SAP BTP:
SAP Graph – ODATA V4 API
4. Consuming Bank API in SAP BTP
We have seen that the same data structure is maintained for the master data object – “Bank” in all the systems like SAP ERP, SAP S/4HANA, SAP BTP. The Domain Model i.e. the data elements of Bank are aligned between all 3 systems. This establishes the objective of One Domain Model (ODM) to have an Domain Model Alignment for the business objects distributed throughout different SAP applications, enabling those systems to speak the same language during data exchange.
Please read my other blog posts on SAP Master Data Governance on S/4HANA.