MuleSoft Accelerator for Salesforce OMS

Automate omnichannel order lifecycle with Salesforce OMS and ERP Integration

Overview
- Description
- Glossary
- Solution overview
- Assumptions and constraints
- High-level architecture
- Systems involved
See also
- Downloadable assets

By integrating OMS with ERP, companies gain end-to-end visibility into their business processes, enabling better decision-making and improved customer service through timely updates on order status and delivery. By making operations smoother, this integration automates tasks, cuts down on manual work, and makes things run more efficiently. This leads to happier customers and increased satisfaction overall. Moreover, the scalability and adaptability provided by OMS to ERP integration empower companies to manage growth, expand into new markets, and respond to evolving business needs.

This use case provides templates to manage orders received via omnichannel channels sources, within Salesforce Order Management System (OMS). The solution is packaged with all the configurations, components and APIs required to manage the end-to-end orders across the fulfillment lifecycle.

Real Time Integration & End-to-end visibility

What’s included?

The solution comes bundled with the following artifacts, enabling organizations to rapidly deploy and start processing orders.

• Process & system API templates orchestrating end to end order lifecycle management with Salesforce OMS for ingesting orders and invoices and processing transaction lifecycle management as orders go through the fulfillment process in ERP.
• End-to-end sequence diagrams

Description

Glossary

Solution overview

This solution enables organizations to facilitate the completion of the order management process within ERP, catering to orders originating from both business-to-business (B2B) and business-to-consumer (B2C) channels. For instance, B2B channels might include bulk orders from wholesalers or procurement platforms, while B2C channels could involve individual purchases made through e-commerce websites or retail stores.

Before you begin

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.

Goals

• Process incoming fulfillment orders from Salesforce OMS and generate corresponding sales orders in SAP S/4HANA.
• Update the fulfillment order in Salesforce OMS with SAP S/4HANA order Id.
• The Pick and Pack process will be executed within SAP S/4 HANA and will update the status in fulfillment order on Salesforce OMS.
• After the ship order process is completed in SAP S/4HANA, the status of the fulfillment order in Salesforce OMS will be updated along with the below details from SAP S/4HANA.
• Tracking number
• Carrier information: The name of the shipping company or carrier responsible for delivering the package.
  • Shipping status
  • Estimated delivery date
  • Shipping method: The chosen shipping service level, such as standard, expedited, or overnight.
  • Shipping address
  • Shipping cost
• Authorized payment is captured by a Payment Processing Service triggered via Salesforce OMS
• Sales order invoice is generated in SAP S/4HANA.
• Fulfillment order invoice is generated in Salesforce OMS
• Salesforce OMS sends the invoice along with payment details to SAP S/4HANA
• SAP S/4HANA receives the invoice for each sales order and completes the order fulfillment process.

Use case considerations

• An Order Summary in Salesforce OMS can contain many fulfillment orders.
• For every fulfillment order incoming from Salesforce OMS, a sales order is created in SAP S/4HANA.
• The status on the fulfillment order in Salesforce OMS will be updated depending on the phase/status of the sales order in SAP S/4HANA.
• The fulfillment order status in Salesforce OMS will be updated:
  • when the sales order is initially created in SAP S/4HANA, the fulfillment order in Salesforce OMS is updated with SAP S/4HANA's Order Id.
  • when the sales order is in picking phase in SAP S/4HANA, the fulfillment order in Salesforce OMS is updated with picking status.
  • when the sales order is in the shipping phase in SAP S/4HANA,the fulfillment order in Salesforce OMS is updated with shipping status.
  • when the order is shipped, tracking details of the given fulfillment order will be updated in Salesforce OMS along with the order status as fulfilled.
• Once the authorized payment is captured, Salesforce OMS will generate an invoice for the fulfillment order which will trigger the reconciliation process in SAP S/4 HANA

Technical considerations

• Use CIM as the canonical data model where applicable, such as for Orders.
• High Scale Order API is used for Order and Order Summary creation in Salesforce OMS
• A simulator API is used to simulate the backend ERP and partner endpoints.

Assumptions and constraints

1. Customer is synchronized between Salesforce OMS and SAP S/4HANA.
2. Product is synchronized between Salesforce OMS and SAP S/4HANA.

High-level architecture

The following diagram represents the portion of the overall solution that pertains to this use case:

Activity diagrams

The following diagrams illustrate the processing sequences for the integrations activities between Salesforce OMS and SAP S/4HANA

Systems involved

• Salesforce Order Management System
• SAP S/4HANA

back to top

Downloadable assets

OMS System APIs

• Accelerator Salesforce OMS System API | API Specification | Implementation Template

ERP Process APIs

• Accelerator ERP Orders Process API | API Specification | Implementation Template

OMS Event Listeners

• Accelerator Salesforce OMS Event Listener | Implementation Template

SAP System APIs

• Accelerator SAP S/4HANA Invoice System API | API Specification | Implementation Template
• RCG SAP S/4HANA Orders System API | API Specification | Implementation Template
• RCG SAP S/4HANA Customers System API | API Specification | Implementation Template
• RCG SAP S/4HANA Products System API | API Specification | Implementation Template

Custom components

• Cloud Information Model for MuleSoft Accelerators
• Accelerator Common Core | Source
• Accelerator POM Parent | Source
• Accelerator B2B Common Library | Source
• Accelerator B2B Common Resources | Source

Shared APIs (can be used across any use case)

• Accelerator Slack System API | API Specification | Implementation Template
• Accelerator B2B Storage System API | API Specification | Implementation Template

---

back to top