enosix can integrate SAP ECC and S/4HANA with Salesforce, as well as any other front-end system that can interface with a REST API (which is most of them).

Enosix has created a software technology that simplifies bringing real-time SAP data into modern front-end systems like Salesforce for viewing, creation, and updates.

Data integration can mean a lot of things to different organizations.  At one end of the spectrum would be approaches like manually importing/exporting spreadsheets to copy data between systems.  At the other would be systems that are tightly connected, for example via APIs, so that actions occurring in one system are almost instantly passed to the other system to handle whatever related tasks it needs to do.  This level of integration can make multiple systems effectively behave as if they were part of a single, overarching process for running the business.

Fundamentally, an eCommerce experience is about getting order information from the customer and passing it to the manufacturing, fulfillment, and finance functions.  Additionally, it’s often desired to bring information the other way (for example, to allow a customer to view and pay past invoices online).  In both cases, this typically requires an integration between the ecommerce platform (that the customer interacts with) and the ERP, which houses the data and serves the other, internal functions.  This integration can be as simple as exporting/importing spreadsheets by hand or as sophisticated as a real-time connection between the systems, providing instant access to live data.

In many companies, receiving a sales order is just the start of a broader set of activities, like manufacturing, shipping, invoice, and receivable management.  In enterprises, these are all typically managed by an ERP system, such as SAP.  So making sure sales orders are correctly created in the ERP (after being entered in a CRM, eCommerce site, etc.) is critical to ensure that customers receive their orders and the company collects payments in a timely fashion.

A CPQ (configure, price, quote) system helps to manage complex sales cycles including things like managing complex variations of products (configure), calculating prices (price), producing quote (quote).  These systems also typically support workflows and approval processes to ensure potential orders don’t get slowed down or lost along the way.  They are often part of or tightly integrated with a CRM tool (such as Salesforce).  For customers running SAP ERP systems, it is also necessary for the CPQ functionality to be tightly integrated to SAP to avoid having to duplicate configuration and pricing logic in two places.

A customer portal (or distributor portal, depending on the business model) is typically an internet site where a B2B company’s customers or distributors can login (they are usually closed to the public) and perform a variety of functions.  Depending on the sophistication of the system, this often includes viewing and paying invoices, looking up order status and delivery tracking information, viewing customer-specific product and pricing information, and even placing orders.

Salesforce relies on enosix to support the unique requirements of enterprise clients with SAP. We offer a set of pre-built integrations to bring SAP data and quote/order creation (including using SAP Variant Configuration) into virtually any Salesforce cloud – Sales, Service, CPQ, Experience (formerly Communities), and Commerce.  We also have an Apex SDK which allows you, your system integrator, or us to easily build custom solutions using our integration platform.

50 people might give 50 different answers, but to us customer engagement is the collection of interactions that an organization has with its customers.  That certainly includes sales experiences – whether in-person, remote, or through eCommerce.  But it also includes customer support and customer success teams, support forums, marketing efforts, invoicing and billing, and in some cases even just the act of a customer using the product.  For the pieces of this puzzle that involve customer’s accessing data about their account (whether self-service or through an employee of the serving organization), that data often must come from the ERP system and be delivered in an easier-to-use tool, such as a customer/distributor portal for self-service or a CRM for internal use.

Our framework wraps your already existing standard FM, table, and BAPI calls to initiate a specified SAP function. The enosix approach eliminates the need for you to code to SAP BAPIs from an external system, and calls get batched utilizing stateless sessions to ensure no long-running processes take up valuable resources.  This not only simplifies front-end development, but also improves scalability as less API calls are needed for each transaction and less data needs to move between systems.

No. Our proprietary Rapid Integration Objects (RIOs) allow for the consolidation of complex processes into familiar, customizable SAP ABAP objects. We minimize complexity on the Salesforce front-end by producing a native, readable object for a given SAP process. Similarly, our REST API wraps each process into an easy-to-use API call.

Instead of coding to hundreds of individual BAPIs and web services, front-end developers simply call on the enosix RIO to invoke the desired transaction. Whether that is viewing data or executing SAP transactions – such as pricing simulation, quote/order creation, variant configuration, and more – enosix simplifies this into one simple step. With enosix, your front-end developers don’t need to know SAP in order to effectively work with it. This approach speeds implementation times and drastically minimizes the effort to maintain and extend the solution.  And our pre-built Salesforce apps go even one step further, typically providing 80% of the needed functionality right out of the box.

All SAP data can be virtualized (i.e. queried when needed) or synced/replicated to the front-end as desired.  Typically sync are used for data that needs to reside in the front-end for performance or reporting purposes.

Enterprise companies that run SAP are constantly changing: adding products, changing sales areas, creating or eliminating payment terms, and more. Let’s take the example of a new shipping condition: with traditional integration, a new shipping conditions means writing new code to link that shipping condition to accounts, products and many other dependencies. It means a coordination of your Salesforce, middleware, and SAP resources to make sure the mapping is correct before the coding begins. Then, there’s testing. And project management. With enosix, that new shipping condition is available in the front-end immediately after it has been created. No coding. No testing. That’s the enosix advantage: unprecedented integration between SAP and front-ends like Salesforce with minimal effort.

The enosix framework and our Rapid Integration Objects (RIOs) provide an abstraction layer to the underlying tables, objects, and BAPIs. Because of this abstraction, the interaction from a front-end system like Salesforce is unchanged during a backend upgrade. Simply install an SAP certified add-on for your new system and configure—all without the need to re-write an integration on the front-end system or in some middleware appliance.

As many as you want!  We will provide a connection to dev, staging, and production environments, as well as different SAP instances serving different geographies, divisions, etc.

No. Your front-end developers do not need to understand SAP when leveraging the enosix framework, as we have “humanized” the traditional SAP nomenclature (German definitions) and eliminated the need for API users to understand BAPI calls, criteria for successful BAPI transactions, sequencing of calls, processes, table names and field names. So front-end  developers can rely less on their SAP counterparts, and more nimbly roll out new functionality at the request of the business.

Absolutely! enosix has an SDK that your team can be trained to utilize in order to make changes on your own. While we offer full support for our solution, including the use of our delivery resources for future development, it is completely optional to leverage the enosix team. Instead, we want to empower you to scale the solution autonomously as your business requirements dictate and we give you the tools to do so. This is meant to lower the total cost of ownership (TCO) to support a fully integrated solution over the long run.

Yes, unlike other vendors, we are both an SAP Silver Partner and a Salesforce Partner.  The enosix core framework is an SAP-certified add-on to SAP ECC and SAP S/4 HANA. Our Salesforce apps are listed on the Salesforce AppExchange and can be used across Salesforce Sales Cloud, Service Cloud, CPQ Cloud, Experience Cloud (formerly Communities), and Commerce Cloud.

The enosix approach focuses on virtualizing SAP data so that it can be viewed from the Salesforce application in real-time. We eliminate the need to batch, transform, and load data into Salesforce. There are many inherent pitfalls of the traditional ETL approach. By loading data, your users may not have the most up-to-date information, Salesforce will charge you additional data storage fees, and most importantly, you’re focusing on “data” orchestration—when you could be leveraging the power of “process” orchestration. The enosix framework is so much more than just access to SAP data—it is an engine that taps into all of the business logic your teams have painstakingly put into place on the SAP side, fully optimizing how SAP and Salesforce interact. With enosix, two really do become one.

No. It is not necessary to use Salesforce connect unless you would like to utilize our solution for Reporting Mash-ups. No other piece of our solution requires Salesforce Connect.

No.  The enosix platform includes a proprietary communication protocol that runs in the application layer in SAP and eliminates all the complexities and restrictions that come with these older SAP technologies. The Netweaver Gateway is highly version dependent, but enosix can run on virtually any version of ECC.  The JCo connector and IDOCs require significant configuration and complicated logic in the front-end to perform the needed tasks in SAP – we eliminate all of that.

The enosix framework works in real-time. No need to store data on a server somewhere in the cloud. Your data remains at its source and is displayed in real-time as your users need it. Even if you want to sync some of the data (such as for reporting purposes), the data moves from your SAP system to your front-end without ever going through an enosix server.

The enosix framework not only provides the ability to change data, but also keeps track of who made that change within the destination system. We do this by associating the SAP user to the external system user. Using this association, normal SAP permissions are enforced and the audit trail is maintained—even from external systems.

As many as you need to connect to!

Our Salesforce integrations can be delivered in 70-90% less time than competing technologies.  For read-only data, the entire process takes just a few hours of work.  And even for complex order creation and variant configuration scenarios, we can typically be ready for UAT in 6-8 weeks.

Our standard support offering gives you access to our support team via phone or our ticketing service.  We have an optional premium support offering that provides discounted, prepaid hours of professional services help each quarter for additional customization work, etc.

We finely tune our queries and objects based on the decades of experience we have with dozens of SAP customers. On top of this, consolidating calls, and wrapping them into lifecycle methods delivers a real-time, predictable result for each and every integration we provide. Sitting on the application layer within SAP allows for us to connect to the appropriate underlying resource and ensures the data is called in the same fashion each time.

Our framework allows for logging on both ends. Beyond this, our portal within SAP allows for testing of the exact procedures that are called remotely using our framework. Debugging is easily accomplished, as our framework utilizes native ABAP code (and Apex in Salesforce), with no proprietary language to learn.

Data security is handled by utilizing a mapping of front-end users to SAP users. Once the underlying users are mapped, the SAP authentication and authorization schemes are utilized.

The enosix framework is successfully being utilized by more than 100 enterprises in North America and Europe.

Whether you’re looking to learn more about our products and technology or you’re a current customer in need of support, we’re here to help you get the information you need — fast. Reach out to our team.