Salesforce to S/4HANA Cloud Accounts Migration
home
This template moves a large set of accounts from Salesforce to SAP S/4HANA Cloud ERP. Trigger the template via an HTTP call either manually or programmatically.
Accounts are upserted so that the migration can be executed multiple times without worrying concerns about duplicating information. This template uses MuleSoft's batching capabilities to move a large set of data easily and transparently from Salesforce into SAP S/4HANA Cloud.
Dependencies
- Anypoint platform Enterprise Edition subscription or a trial account.
- An entitlement to the Anypoint connector for SAP S/4HANA Cloud.
Use Case
This Anypoint template serves as a foundation for setting an online synchronization of accounts data from Salesforce into SAP S/4HANA Cloud. The template will obtain data for accounts from Salesforce based on the specified criteria, and populate SAP S/4HANA cloud by to creating or updating the business partner data.
As implemented, this template leverages the MuleSoft's batch module. The batch job is divided into _Process_ and _On Complete_ stages.
Overarching steps in this template:
- The integration is triggered by the HTTP endpoint to fetch all the Salesforce Accounts suitable for migration.
- The fetched accounts are passed to the batch module as an input.
- In the batch module, the
business partneris fetched from SAP S/4HANA by its name. If it exists, its business partner identifier is resolved against SAP S/4HANA. If it doesn't exist, then new business partner number is fetched from SAP S/4HANA. - Every subsequent account from Salesforce is sent to SAP S/4HANA where it is asynchronously updated or created.
- Finally, during the
_On Complete_stage the template logs output statistics data into the console and sends a notification e-mail with the results of the batch execution.
Considerations
To execute this template, there are certain preconditions that must be considered. All of them deal with the preparations in both systems (i.e. Salesforce and SAP S/4HANA Cloud), that are needed to smoothly execute the template.
Failing to do so could lead to unexpected behavior of the template.
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 as indicated below.
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
Before using this template, please familiarize yourself with the S/4HANA Cloud connector.
Executing this Template
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
Application Configuration
- http.port
9090 - page.size
1000
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
SMTP Services Configuration
- smtp.host
smtp.gmail.com - smtp.port
587 - smtp.user
email@example.com - smtp.password
password
Email Details
- mail.from
batch.migrateAccounts.migration@mulesoft.com - mail.to
your@email.com - mail.subject
Batch Job Finished Report
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 mainFlow 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 provides the inbound and outbound sides of your integration app.
This template has only an HTTP Inbound Endpoint as the way to trigger the use case.
HTTP Inbound Endpoint - Start Synchronization
${http.port}is set as a property to be defined either on a property file or in CloudHub environment variables.- The path configured by default is
migrateaccountsand you are free to change for the one you prefer. - The host name for all endpoints in your CloudHub configuration should be defined as
localhost. CloudHub will then route requests from your application domain URL to the endpoint. - The endpoint is configured as a request-response since as a result of calling it the response will be the total of Accounts migrated and filtered by the criteria specified.
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.
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.