Salesforce to S/4HANA Cloud Product Broadcast
home
Broadcasts changes to products in Salesforce to S/4Hana Cloud in real time. The detection criteria and fields to move are configurable. Additional systems can easily added to be notified of changes. Real time synchronization is achieved via outbound notifications or a configurable rapid polling of Salesforce.
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.
Use Case
This Anypoint template serves as a foundation for setting an online sync of products from Salesforce to SAP S/4HANA.
Everytime there is a new product or a change in already existing one in Salesforce instance, the template will fetch it and send it to SAP S/4HANA to update product there.
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 Mule batch module.
The batch job is divided in Process and On Complete stages.
The integration is triggered by poll to Salesforce Products. New or modified products are passed to the batch as input.
In the batch the product is fetched from SAP S/4HANA by its name.
Afterwards every product from Salesforce is updated or created in SAP S/4HANA.
Finally during the On Complete stage the template logs output statistics data into the console.
Considerations
To make this template run, there are certain preconditions that must be considered. All of them deal with the preparations in both systems, that must be made for the template to run smoothly.
Failing to do so could lead to unexpected behavior of the template.
Before using this template, you may want to check out this Documentation Page, that will teach you how to work
with SAP S/4HANA and Anypoint Studio.
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 Source
If the user who configured the template for the source system does not have at least read only permissions for the fields that are fetched, then an InvalidFieldFault API fault displays.
java.lang.RuntimeException: [InvalidFieldFault [ApiQueryFault
[ApiFault exceptionCode='INVALID_FIELD'
exceptionMessage='Account.Phone, Account.Rating, Account.RecordTypeId,
Account.ShippingCity
^
ERROR at Row:1:Column:486
No such column 'RecordTypeId' on entity 'Account'. If you are attempting to
use a custom field, be sure to append the '__c' after the custom field name.
Reference your WSDL or the describe call for the appropriate names.'
]
row='1'
column='486'
]
]SAP S/4HANA Considerations
Here's what you need to know to get this template to work with SAP S/4HANA.
As a Data Destination
There are no considerations with using SAP S/4HANA as a data destination.
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. - 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
100 - scheduler.frequency
10000 - scheduler.start.delay
5000
Watermarking default last query timestamp e.g. 2016-12-13T03:00:59Z
- watermark.default.expression
2014-06-26T12:30:00.000Z
SalesForce Connector Configuration
- sfdc.username
bob.dylan@sfdc - sfdc.password
DylanPassword123 - sfdc.securityToken
avsfwCUl7apQs56Xq2AKi3X
SAP S/4HANA Connector Configuration
- s4hana.baseUrl
your.s4hana.address.com - s4hana.username
your.s4hana.username - s4hana.password
your.s4hana.password - s4hana.productType
s4hana.productType - s4hana.baseUnit
s4hana.baseUnit - s4hana.productGroup
s4hana.productGroup
API Calls
There are no particular considerations for this template regarding API calls
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 one flow responsible of executing the logic.
For the purpose of this particular template the businessLogicFlow just executes the Batch Job which handles all the logic of it.
This flow has Error Handling that basically consists on invoking the On Error Propagate Component defined in errorHandling.xml file.
endpoints.xml
This file is conformed by two Flows.
The first one we'll call it schedulerFlow flow. This one contains the Scheduler endpoint that will periodically trigger queryFlow flow and then executing the batch job process.
The second one we'll call it queryFlow flow. This one contains watermarking logic that will be querying Salesforce for updated/created Products that meet the defined criteria in the query since the last polling. The last invocation timestamp is stored by using Objectstore Component and updated after each Salesforce query.