0% found this document useful (0 votes)
116 views2 pages

Pricefx Api Connect: Tax Engine

This document outlines an integration pattern for updating sales order status in S/4HANA from various business platforms like Salesforce, Dynamics 365, and Virto in an asynchronous way using microservices on SAP Business Technology Platform to process events from Solace and make API calls to S/4HANA. Errors during order creation would be captured and published back to Solace to allow for retries. The solution is meant to handle high volumes of sales order data in a scalable and fault-tolerant manner without impacting S/4HANA performance.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
116 views2 pages

Pricefx Api Connect: Tax Engine

This document outlines an integration pattern for updating sales order status in S/4HANA from various business platforms like Salesforce, Dynamics 365, and Virto in an asynchronous way using microservices on SAP Business Technology Platform to process events from Solace and make API calls to S/4HANA. Errors during order creation would be captured and published back to Solace to allow for retries. The solution is meant to handle high volumes of sales order data in a scalable and fault-tolerant manner without impacting S/4HANA performance.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 2

MTC Integration Pattern: Sales Order Create- Inbound to S4/HANA TAX

PriceFX
(Async) ENGINE

API Connect
UCE
A BTP S4/HANA
z
Dyn365 u microservices Sales
order
r Solace CC API
e Topic
F Creatio
Error &

u
n error
which
retry of
priceFx
HANA
UCE call
n want to
capture
c

Platform work Integration work Platform work

Business scenario Steps


1. 5/6 Million sales order/day
2. Every SO will be calling Price and Tax engine API before getting stored into 1.UCE will create an Order and Publish on Solace Through Event.
S4/HANA tables (VBAK, VBAP etc) 2.BTP will pick the event for further processing.
3. Every change in SO in S/4HANA also will make a call to Price and Tax engine 3.Once the request is Picked, call will happen to Price FX to get the price.
4.In the next step the request is made to CORE through API for creation of Sales Order.
Technical Solution needed 5.Once its successful, Event is Triggered to publish the Information back to Solace, In
1. High performance, High scalable (auto) platform with microservices which can handle turn UCE will Filter based on the requirement and pick the Information
such huge number of SO and can push to S/4HANA in a staggered way to avoid any
performance issue in S/4 6. If any error, as UCE needs error information during creation, that will be pushed to
2. Fault tolerance and graceful solution, which can handle any error in calling Price and Tax Solace via BTP
engine gracefully
3. To keep S/4 HANA clean and to avoid any introduction of staging table and lot of classic
ABAP code
MTC Integration Pattern: Sales Order Status update in business
platform- Outbound to S4/HANA (Async)

UCE
SalesForce
S4/HANA

Dyn365
Direct to
Solace or via
Boomi or via
Solace ASAPIO
Add-on
Azure func Topic
Virto

Platform work Integration work Platform work

Assumptions :

1. During the publish of Event, It is understood that each event will have a Tagging, whether it is a Create/Change/Status/Error Event.
2. Once the Event is published from CORE to Solace, there is no option to Retrigger/Reprocess again from CORE, it has to be handled from Solace.
3. Dashboard available at Solace level to check all the Events.
4. File Format is JSON
5. In Case of Events, EDM Attributes will be sent to Solace. Filter is done at Solace to pick the required Attributes.
6. Currently 3 Events Identified (Create, Change, Status Change). New Event :Error needs to be added
7. All the Field Mapping are in line to EDM Fields.

You might also like