SAP OMF (2) – Receipt of orders

Orders API is available on the SAP Business Accelerator Hub and offers a wide range of fields to work with. These fields can be generally categorized into fixed and variable values, which must be populated by the Order Capture System. For instance, a fixed value like the Market ID is crucial, as it plays a key role in managing SAP OMSA sourcing strategies, the sales area in S/4HANA, and orchestration rules (more on this in Part 3 of this series). It’s recommended to create at least one Market ID per Order Capture System and include it as a fixed element in the Order Payload.

While fixed values are important, variable values make up the majority of the data. The Order Capture System is responsible for providing customer data, product information, prices, discounts, and fees. SAP OMF offers the capability to include all necessary details for customer orders. For example, you can differentiate between “Sold-To”, “Ship-To”, and “Bill-To” customer types, apply discounts at either the header or line-item level, and specify the type of discount (e.g. coupon code). Gift vouchers can also be managed with ease.

However, it’s important that this information comes from the Order Capture System, as SAP OMF uses it to orchestrate and set up the order in the Fulfilment System.

If specific customer requirements can’t be met by the standard Orders API, custom fields can be used. These custom fields can be inserted into the Order Payload at the relevant points and sent without requiring additional changes. They will then appear in the OMF UI, where you can later decide whether to use these custom fields for certain orchestrations or forward them to the Fulfilment System. A typical example of this is an identifier for dropshipping products. Based on this identifier, a Fulfilment Request can be sent directly from SAP OMF to the dropshipper via SAP CI, allowing the corresponding item type for S/4HANA to be determined.