S/4HANA Cloud to Salesforce Sales Order Broadcast
home
As a Salesforce administrator I want to synchronize sales orders between a SAP S/4HANA and a Salesforce organization.
This template is a foundation for the process of broadcasting sales orders from a SAP S/4HANA to a Salesfoce instance. Everytime there is new order or a change in an already existing one, the integration polls for changes in the SAP S/4HANA source instance and is responsible for upserting the order into Salesforce.
Requirements have been set not only to be used as examples, but also to establish a starting point to adapt your integration to your requirements.
As implemented, this template leverages the batch module. The batch job is divided into Process and On Complete stages.
The integration is triggered by a scheduler defined in the flow that triggers the application, queries the newest SAP S/4HANA updates or creations that match a filter criteria and executes the batch job. During the Process stage, each SAP S/4HANA order is be filtered depending on if it has an existing matching Order in Salesforce. The last step of the Process stage groups the sales orders and creates or updates them in Salesforce. Finally during the On Complete stage, the template logs output statistics data on the console.
License Agreement
This template is subject to the conditions of the MuleSoft License Agreement. Review the terms of the license before downloading and using this template. You can use this template for free with the Mule Enterprise Edition, CloudHub, or as a trial in Anypoint Studio.
Considerations
To make this template run, there are certain preconditions that must be considered. All of them deal with the preparations in both source (SAP S/4HANA) and destination (SFDC) systems, that must be made for the template to run smoothly. Failing to do so can lead to unexpected behavior of the template.
Before you continue with the use of this template, you may want to check out this Documentation Page, that teaches you how to work with SAP S/4HANA and Anypoint Studio.
SAP S/4HANA Considerations
Here's what you need to know to get this template to work with SAP S/4HANA.
As a Data Source
There are no considerations with using a SAP S/4HANA as a data origin.
Salesforce Considerations
Here's what you need to know about Salesforce to get this template to work:
- Where can I check that the field configuration for my Salesforce instance is the right one? See: Salesforce: Checking Field Accessibility for a Particular Field.
- Can I modify the Field Access Settings? How? See: Salesforce: Modifying Field Access Settings.
As a Data Destination
Here's what you need to know about Salesforce to get this template to work.
Run it!
Simple steps to get this template running.
Running On Premises
In this section we help you run this template on your computer.
Where to Download Anypoint Studio and the Mule Runtime
If you are new to Mule, download this software:
Note: Anypoint Studio requires JDK 8.
Importing a Template into Studio
In Studio, click the Exchange X icon in the upper left of the taskbar, log in with your Anypoint Platform credentials, search for the template, and click Open.
Running on Studio
After you import your template into Anypoint Studio, follow these steps to run it:
- Locate the properties file
mule.dev.properties, in src/main/resources. - Complete all the properties required as per the examples in the "Properties to Configure" section.
- Right click the template project folder.
- Hover your mouse over
Run as. - Click
Mule Application (configure). - Inside the dialog, select Environment and set the variable
mule.envto the valuedev. - Click
Run.After you import your template into Anypoint Studio, follow these steps to run it: - Locate the properties file
mule.dev.properties, in src/main/resources. - Complete all the properties required as per the examples in the "Properties to Configure" section.
- Right click the template project folder.
- Hover your mouse over
Run as. - Click
Mule Application (configure). - Inside the dialog, select Environment and set the variable
mule.envto the valuedev. - Click
Run.To make this template run on Studio there are a few extra steps that needs to be made.Check this Documentation Page: Enabling Your Studio Project for SAP S/4HANA.
Running on Mule Standalone
Update the properties in one of the property files, for example in mule.prod.properties, and run your app with a corresponding environment variable. In this example, use mule.env=prod.
Running on CloudHub
When creating your application in CloudHub, go to Runtime Manager > Manage Application > Properties to set the environment variables listed in "Properties to Configure" as well as the mule.env value.
Deploying a Template in CloudHub
In Studio, right click your project name in Package Explorer and select Anypoint Platform > Deploy on CloudHub.
Properties to Configure
To use this template, configure properties such as credentials, configurations, etc.) in the properties file or in CloudHub from Runtime Manager > Manage Application > Properties. The sections that follow list example values.
Application Configuration
Batch Aggregator Configuration
- page.size
200
Scheduler Configuration
- scheduler.frequency
10000 - scheduler.startDelay
100
Watermarking Default Last Query Timestamp
- watermark.default.expression
2019-08-01T00:00:00Z
SalesForce Connector Configuration
- sfdc.username
bob.dylan@sfdc - sfdc.password
DylanPassword123 - sfdc.securityToken
avsfwCUl7apQs56Xq2AKi3X - sfdc.pricebook.id
01s0J000002IZrUQAW - sfdc.pricebook.standard.id
01s20000001SwERAA0
SAP4HANA Connector Configuration
- s4hana.baseUrl
your.sap4hana.address.com - s4hana.username
your.sap4hana.username - s4hana.password
your.sap4hana.password
API Calls
SalesForce imposes limits on the number of API Calls that can be made.
Therefore calculating this amount may be an important factor to
consider. Order Broadcast Template calls to the API can be
calculated using the formula:
X / ${page.size}
Being X the number of Sales Orders to be synchronized on each run.
The division by ${page.size} is because, by default, Orders are gathered in groups
of ${page.size} for each Upsert API Call in the aggregation step. Also consider
that this calls are executed repeatedly every polling cycle.
For instance if 10 records are fetched from origin instance, then 1 api
calls to SFDC will be made (1).
Customize It!
This brief guide provides a high level understanding of how this template is built and how you can change it according to your needs. As Mule applications are based on XML files, this page describes the XML files used with this template. More files are available such as test classes and Mule application files, but to keep it simple, we focus on these XML files:
- config.xml
- businessLogic.xml
- endpoints.xml
- errorHandling.xml
config.xml
This file provides the configuration for connectors and configuration properties. Only change this file to make core changes to the connector processing logic. Otherwise, all parameters that can be modified should instead be in a properties file, which is the recommended place to make changes.
businessLogic.xml
Functional aspect of the template is implemented on this XML, directed by a batch job that's responsible for creations or updates. The several message processors constitute three high level actions that fully implement the logic of this template:
- Job execution is invoked from SchedulerFlow (endpoints.xml) every time there is a new query executed asking for created or updated orders.
- During the Process stage, each SAP S/4HANA order is filtered depending on if it has an existing matching order in Salesforce.
- The last step of the Process stage groups the orders and creates or updates them in Salesforce.
- Finally during the On Complete stage, the template logs the output statistics data on the console.
endpoints.xml
This file contains the endpoints for triggering the template and for retrieving the objects that meet the defined criteria in a query. You can execute a batch job process with the query results.
errorHandling.xml
This file handles how your integration reacts depending on the different exceptions. This file provides error handling that is referenced by the main flow in the business logic.