Our 53 SAP Integration Points
“Direct integration” means there are only two software systems involved—SAP, and your Corevist solution. There is no middleware passing data between these systems.
Your Corevist solution acts as a window into your SAP system, reflecting and enforcing the relevant SAP business rules in real time. This ensures that SAP remains the “one true truth” for your business data.
You’ll never have conflicting data between SAP and Corevist Commerce, and you’ll never have to update your business rules in more than one system. Whatever changes you make in SAP take effect immediately in Corevist, and customer actions performed in Corevist are posted to SAP immediately.
We have fewer integration points than you’ll find with a catch-all integration or middleware platform—but more eCommerce integration points than competing SAP-integrated eCommerce solutions.
We strike a balance between performance and comprehensiveness for eCommerce purposes. Our application is more performant than a catch-all integration platform, but also more thorough than competing SAP-integrated eCommerce solutions.
ABAP is the programming language used to modify and maintain an SAP ERP instance. Corevist’s 426 ABAP objects were built by dedicated SAP experts to provide a powerful, prebuilt SAP integration. They’re the foundation of our integration, which is SAP-certified for both NetWeaver and S/4HANA.
At a high level, Corevist offers 3 ways to integrate securely with your SAP environment:
- SAP Router
- Secure site-to-site VPN
- SAP Router behind a secure site-to-site VPN
All of these options provide the means to restrict and control access, specifying both the source and destination IP addresses (or subnets) and the specific TCP ports available for access. In all 3 cases, only the minimum access required is allowed.
Please contact us to learn more about our extensive security documentation (and options for connecting to your SAP system).
We caution manufacturers from embarking on that journey. If you’re building the integration yourself, that means you’re working with a standalone, conventional eCommerce platform. Though these eCommerce platforms include basic B2B functionality, they require significant customization to map to the complexity of manufacturers’ transactions. With that in-house customization (and homegrown integration) comes ongoing troubleshooting when the integration breaks down.
We’ve spoken to many manufacturers who’ve gone down this road and found it to be unworkable. The integration continues to break—or, worst case, it never even gets off the ground after years of effort and millions of dollars invested.
That’s why we architected Corevist on top of a prebuilt, configurable SAP integration. Our solutions remove the uncertainty in SAP integration so IT can focus on bigger problems.
Middleware makes sense in a B2C eCommerce scenario. Complex B2B business rules—like contract pricing, personalized inventory/ATP, quantity/bundling rules, and more—simply aren’t in effect. Syncing eCommerce and SAP via batch updates rarely affects B2C customer experience, and this kind of architecture allows greater decoupling of the front-end experience from the ERP, which is a plus in consumer markets.
However, in a B2B scenario, transactions must conform to complex business rules. If they don’t, Customer Service will have to follow up to fix errors before processing eCommerce orders by hand. At scale, this friction-heavy process costs manufacturers millions every year. It also undermines the viability of eCommerce, which is supposed to offer 100% self-service to customers. Hence the need for an integration that enforces all relevant SAP business rules in the eCommerce store—including account-level personalization like contract/scaled pricing, personalized inventory/ATP, mapping of multiple ship-to/sold-to, and more.
A middleware solution will require building all this complexity from scratch. This is expensive and wasteful, since the business logic already exists in SAP. If that business logic is essential to creating well-formed orders, and if the logic is working in SAP, it stands to reason that you should integrate with SAP directly, rather than rebuilding your business rules. That way, you maintain business logic in one place only, SAP, rather than having to maintain it separately in 3 places—SAP, middleware, and eCommerce.