In this lesson, we will dive into the prerequisites and setup for using SAP Order Management foundation. We will be covering aspects such as the types of master data used by SAP Order Management foundation, various integration options for this data, other setup prerequisites, and how to initiate the business configuration.

One fundamental point to understand is the critical role master data plays within SAP Order Management foundation. This type of data is primarily used for mapping purposes. For instance, when deciding on which systems to route specific requests to, certain information about those systems may be required.
There are two key reasons master data exists within SAP Order Management foundation: order validation and support for multiple backends. The process of order validation considers if an order can be processed or if more information is needed. For example, an order may need to be put on hold if a product isn't valid for its intended route or if customer information is missing. This validation goes beyond just technical validation, such as checking if the API call was correctly formed. In the case of supporting multiple backends, the data may be represented differently in various systems. For example, the SKU on your website may be represented differently in your warehouse management system versus a third-party dropshipper. To address this, we use key mappings to look up the correct information to use in the right context.
The two main types of master data used in SAP Order Management foundation are product data and customer data, which is referred to as 'business partner' from a SAP S/4HANA point of view.
In the next chapter, we will see how you can integrate this master data, explore the other prerequisites for setting up SAP Order Management foundation, and start the business configuration.