MFG Orders Process API - Implementation Template
home
This asset is a component of MuleSoft Accelerator for Manufacturing, which accelerates the implementation of essential integration use cases.
The solution unlocks rich data between SAP, Salesforce Manufacturing Cloud, Salesforce Rebate Management, OSIsoft PI System, Amazon Redshift, Tableau, and Salesforce Service Cloud with pre-built APIs, templates, reference architecture, and additional technical assets for manufacturing companies. Our foundational assets are expertly designed to jumpstart your top integration and business initiatives so that IT teams can spend more time innovating and less time building from scratch.
Overview
This integration template implements the MFG Orders Process API specification. It can be used to retrieve of Orders details from SAPS/4 HANA to create Orders into MFG Salesforce Cloud.
The Cloud Information Model (CIM) is leveraged to interact with each of the System APIs that have been developed for Customer sync use cases.
This integration template can be easily configured to sync to any other systems easily with inclusion of appropriate properties in the config files and do not require any changes to code. The default systems and configurations applicable for each accelerators are provided with the template.
Getting started
The Getting Started with MuleSoft Accelerators guide provides general information on getting started with the accelerator components. This includes instructions on setting up your local workstation for configuring and deploying the applications. |
Once your workstation has been set up and the application template imported into Anypoint Studio, proceed with the Prerequisites section.
Prerequisites
This implementation template has the following dependencies:
- Anypoint MQ Destinations
- Accelerator Salesforce Orders System API
- Accelerator SAP HANA Orders System API
- Accelerator SAP HANA Products System API
- Accelerator Salesforce Products System API
- Accelerator Salesforce Customers System API
- Accelerator SAP HANA Customers System API
- Accelerator Salesforce MFG Cloud System API
Please review the use cases described on the MuleSoft Accelerator for Manufacturing solution pages for more information about dependencies on other APIs and services.
API dependencies
The following table lists endpoints that are enabled by default in this API.
API name | Endpoint | Action |
---|---|---|
Accelerator Salesforce Orders System API | post:/orders | Create Sales Orders |
Accelerator SAP HANA Orders System API | patch:/orders | Update Sales Orders |
Accelerator SAP HANA Products System API | get:/products | Get Products details |
Accelerator Salesforce Products System API | get:/products | Get Products details |
Accelerator Salesforce Customers System API | get:/customers | Get Customers details |
Accelerator SAP HANA Customers System API | get:/customers | Get Customers details |
Accelerator Salesforce MFG Cloud System API | get:/sales/agreement | Get Sales Agreement details |
Anypoint MQ destinations
In addition to the Anypoint MQ client application credentials, the following destinations must be created and made accessible to this API:
- mfg-slsorder-update-queue
- mfg-slsorder-update-dl-queue
The Accelerator Common Resources asset contains a Postman collection, which can be used to create the destinations and client application required for use by accelerator applications.
Deployment
Each Accelerator implementation template in Exchange includes Bash and Windows scripts for building and deploying the APIs to CloudHub. These scripts depend on repositories, global settings, deployment profiles, and associated properties configured in the Maven settings.xml
file. In particular, make sure the common properties for your environment have been provided in the CloudHub-MFG-DEV
profile (e.g., Anypoint Platform client ID and secret).
For additional details, please refer to the Application Deployment section of the Getting Started Guide.
Required property overrides
Many templates can also be run from Anypoint Studio without having to customize the Run/Debug profiles. However, some templates make use of hidden deployment properties to protect sensitive information (e.g., passwords and secret keys). These properties must be supplied to the runtime by updating the configuration profile and adding them as VM arguments. At a minimum, the following properties must be customized to reflect the target deployment environment.
Property Name | Description |
---|---|
api.autodiscoveryID | Required if using API Manager to secure this API |
anypoint-mq.client-id | Anypoint MQ client id |
anypoint-mq.client-secret | Anypoint MQ client secret |
orders-prc-api.http-client.client-id | Client Id provided for Orders Process API to interact with all System API's |
orders-prc-api.http-client.client-secret | Client Secret provided for Orders Process API to interact with all System API's |
Additional resources
- Data mappings tab to learn more about how the request and response data structures are mapped between the API interfaces.
- Refer to the Accelerators documentation home for more information about the MuleSoft Accelerators.