The SAP S/4HANA Element is the latest addition to our catalog, further enabling enterprise scale integration capabilities. As enterprise organizations continue to transition more services to become accessible from the cloud for their customers and employees, the rate of integrating, governing, and orchestrating data between ERP and non-ERP is exponentially rising. However, there are some interesting nuances to this Element compared to other Elements in our catalog that are worth calling out.
For a bit of background, SAP S/4HANA is the core ERP to many of the largest organizations in the world, automating and centralizing all aspects of their business. Because of this, the range of use cases and implementations of S/4HANA stretch across every vertical and type of business you can imagine, from sports cars to software to scented oils.
Given the extensive range and high level of customization with each implementation of S/4HANA, we had to create the ability for our customers to adopt this Element into potentially hundreds of different scenarios. To accomplish this, we created a general resource based on the BAPI (Business APIs) and ODATA framework of SAP that connects to the heart of the data flowing within an SAP S/4HANA Cloud environment. Our generalized resource can access the specific tables within S/4HANA. This approach gives the general access needed but allows for the complete customization to extend the Element into your (or your customer’s) tailored environment. Pretty neat.
Why is this important? This allows customers that are using a hybrid application environment (SAP and non-SAP) to access and govern the data they care about throughout their entire ecosystem. From the front line applications of CRM, Marketing Automation, and Human Capital Management all the way to their ERP of choice, in this case, SAP S/4HANA. This becomes tangible when orchestration different operation scenarios like: Hire to Retire, Quote to Cash, Lead to Loyalty and Bulk Migration.
Let's see this new Element in action by POSTing a new /Customer to S/4HANA. Wait a minute…where is the customer? One thing to note is SAP uses the concept of Business Partners instead of customers, as a partner could be a customer, supplier, partner or other 3rd parties. Here is a quick video showing business partners moving from S/4HANA to SalesForce, Microsoft Dynamics, and Sugar.
We’ve also included the ability to expand nested response values to get the full picture from each field as well as expand single objects, sub-objects, and multi-objects to find the exact information you need in S/4HANA.