André Dotzler
Henning Sanders
Introduction
In the fifth part of our article series, we explored how OMF and OMSA work together. Now, in the sixth and final part of this series, we’ll turn our attention to master data management. While these functions can be used within SAP OMF, they aren’t strictly necessary.
What master data is important for OMF?
There are two key types of master data for OMF:
- Business Partner Master Data
- Product Master Data
Both types of master data can be stored in SAP OMF and used later for validation and enrichment purposes. The data can be imported via SAP-provided APIs or, in the case of Business Partner Master Data, through the SAP Master Data Integration Service.
Business Partner Master Data
The main purpose of integrating customer master data into OMF is to enrich the customer order data. This enrichment ensures that not all customer details need to be transferred from the Order Capture System to OMF. For example, a simple Customer ID might suffice, which OMF can then enrich with the stored customer master data.
However, it’s not strictly necessary to supply the customer master data to OMF if the incoming order already includes all necessary information (e.g. required fields). Whether or not you use the information stored in OMF can be decided on a market-by-market basis.
Product Master Data
As with customer master data, importing product master data is aimed at validation and enrichment. For example, product master data include sales areas from S/4HANA, which are then reflected in the market settings. With this information, OMF can determine whether a product is eligible for sale in a particular sales area. Additionally, OMF can display and transfer further details, such as the Product Description, even if this type of data wasn’t provided by the Order Capture System. Again, whether or not you decide to use these features depends on each individual market.
Conclusion
By allowing for the import of customer and product master data, SAP offers the ability to perform validations and extract information and logic from the Order Capture System. However, feeding customer and product data into OMF isn’t a mandatory step, meaning it can be integrated as and when – i.e. according to the specific needs of each market.
Interested?
Interested in learning more about SAP OMF? Get in touch with us to find out more.
SAP OMF (1) – the central orchestration tool
The Order Management Foundation (OMF) is another key product in SAP’s Industry Cloud landscape, complementing SAP OMSA. But what exactly does OMF stand for, and what are the benefits of implementing this system?
SAP OMF (2) – Receipt of orders
In this article we’ll explore what information needs to be provided by the Order Capture System, such as a webshop, and discuss the additional capabilities SAP OMF offers for integrating and sharing custom data.
SAP OMF (3) – Orchestration within SAP OMF
Orchestration is one of the key features of SAP OMF, allowing fulfilment requests to be sent to fulfilment systems based on user-defined criteria.
SAP OMF (4) – Outgoing messages from SAP OMF
In the fourth part, we’ll focus on how orders exit OMF and are created in S/4HANA. Those are sent via SAP CI where the mapping will also take place.
SAP OMF (5) – Integration OMSA with OMF
In this article, we’ll take a closer look at the interaction between SAP OMF and SAP OMSA which enables an integrated sourcing of incoming orders.