You can integrate SAP Customer Order Sourcing with your ERP system to replicate ATP data. The replicated ATP data are used in SAP Customer Order Sourcing as availability raw data for further availability calculations in which also product reservations can be considered. There’s a number of steps you need to follow to make it work, and you have to do them in several systems – which also makes it a bit harder to find all the relevant information on what to do, and how. But don’t worry, we’re here to help you out! In this blog post, you will learn the necessary steps to make the integration happen!

How does it work?

This integration is available for SAP S/4HANA and SAP ECC 6.0 Ehp8 SP14 (and subsequent Service Packs). For this blog post, we’ll focus on what to do for the integration with SAP S/4HANA. Learn more about this and other integration scenarios in the official documentation.

Architectural Overview of the integration of S/4HANA and SAP Customer Order Sourcing

1. SAP S/4HANA 

   Availability data is generated in SAP S/4HANA using the parallelized ATP run functionality, which is part of omnichannel article availability and sourcing. The availability snapshot data are transferred via IDocs of the type W_OAA_ATP_RESULT. They are sent to SAP Cloud Platform Integration.

2. SAP Cloud Platform Integration 

   The integration package SAP Customer Order Sourcing Integration with SAP S/4HANA contains the template integration flow. It receives the data from the IDocs, maps the back-end properties to those in SAP Customer Order Sourcing, and sends the availability snapshot data to SAP Customer Order Sourcing.

3. SAP Customer Order Sourcing 

   SAP Customer Order Sourcing receives the data and stores it in the database as availability raw data.

And what needs to be done in order to make it work?

As stated before, there are several steps and different systems involved, so let’s get down to the nitty-gritty!

Set up SAP Customer Order Sourcing

First, you need to have a running instance of SAP Customer Order Sourcing. If you didn’t set it up yet, there are two options: You can use either the trial version or a productive system. For the setup of the productive system, follow the steps described here: Initial Setup.

If you want to try it out first, the trial’s just right for you. Learn how to set up a fully functional trial system of SAP Customer Order Sourcing here: Getting Started with SAP Customer Order Sourcing Trial.

Set up and configure SAP Cloud Platform Integration

Next, you need to set up and configure the integration flow in SAP Cloud Platform Integration. This is necessary because the ATP snapshot data is sent from SAP S/4HANA in the form of an IDoc, and it has to be mapped to the SAP Customer Order Sourcing endpoint data model for availability raw data.

But before you start with that, make sure you’ve gone through the onboarding process for SAP Cloud Platform Integration. If you’re not sure whether you’ve done that before, check out the documentation on Initial Setup of SAP Cloud Platform Integration in Cloud Foundry Environment for more information.

Now you can go to SAP Cloud Platform Integration and configure the integration flow as described here: Configuring the Integration Flow in SAP Cloud Platform Integration

Configure S/4HANA and ATP snapshot replication

Next, you need to configure your SAP S/4HANA system to replicate ATP snapshot data to SAP Customer Order Sourcing. The procedure has to be done for each client, so if your data is located on several clients, make sure to do this for each of them. You can find a step-by-step procedure here: Configuring IDoc Replication in SAP S/4HANA.

Now you’ll want to set up ATP parallelization in SAP S/4HANA Customizing, which improves the performance of the ATP runs considerably. You can find the location of the Customizing activities and a description of what you need to do here: Setting Up ATP Parallelization in SAP S/4HANA Customizing.

The replication mode must be ALE. You define the replication mode in the Customizing activity Sales and Distribution > Basic Functions > Availability Check and Transfer of Requirements > Availability Check > Availability Check with ATP Logic or Against Planning > Retail: Omnichannel Article Availability and Sourcing (OAA) > Define Replication Modes.

To freely define your set of product/DC combinations and include those in the ATP run, you can implement BAdI BADI_OAA_ATP_CTRL_SET_ARTICLE.

To start replicating the ATP snapshot data, you now have to schedule a job in the SAP S/4HANA system. We recommend to make this a periodic batch job, to keep the data in SAP Customer Order Sourcing in sync with the availability data in ERP.

The data exchange is done via IDocs of the type W_OAA_ATP_RESULT. The ABAP report OAA_GENERATE_ATP_SNAPSHOT should be used as basis for the batch job to trigger the generation and transfer of those IDocs. Here’s how to schedule the job in SAP S/4HANA, and which parameters you need to maintain for the ABAP report: Replicating Availability Information.

Monitoring – How does data get to SAP Customer Order Sourcing

Availability data sent through the iFlows can be monitored directly in CPI. To access monitoring, navigate to your SAP Cloud Platform Web UI.

Select the operations view and select the tile “All Integration Flows”.

You will see in the list which data flows have been processed in the past and whether they have been successful or not.

In case an integration flow fails, Cloud Platform Integration allows you to pin down the error through logs etc.

Example of a failed message flow:

Result

And that’s it! The ATP snapshot data is now being replicated to SAP Customer Order Sourcing on a regular basis, and can be used to calculate sourcing results that will make your customer promise more reliable.

Did you follow this tutorial? Please share your experiences in the comments section! We’re excited to hear what you think.

You want to learn more?

If you’re interested to find out more about SAP Customer Order Sourcing, please check out these great resources: