True B2B functionality requires SAP integration.

Learn how the 53 integration points included in all Corevist solutions
provide the B2B features you need. SAP certified, no middleware required.

Schedule intro call

 

Here’s our secret:

We deliver mission-critical B2B features
through 53 SAP integration points and
426 ABAP objects, all pre-built by SAP experts.

The Details:

Our prebuilt connector is fully configurable to your SAP instance.

It includes 53 integration points in 9 categories. (Click to jump)

 

 

Material master data integration points:

1. Returns list of materials based on search criteria (number, description) for all sales areas the user is assigned to/the sales area of an order.

2. Material availability check (SHOWN).

Corevist Commerce Catalog with SAP data

Customer master data integration points:

3. Customer master data maintenance

4. Maintain contact person

5. Retrieves the user’s assigned partner data (sold-tos, ship-tos and payers) for all sales areas the user is assigned to (SHOWN).

6. Deletes a credit card.

7. Saves customer credit cards, including the customer’s preferred credit card with a nickname.

 

8. Gets customer address.

9. Retrieves individual partner data (sold-to, ship-to or payer) for all sales areas the user is assigned to.

10. Returns a list of partners (sold-tos, ship-tos or payers) based on the search criteria (name, city, postal code, customer number) for all sales areas the user is assigned to.

11. Retrieves the requested partner functions of a specific customer.

Product availability integration:

12. Returns material availability and related data for a material/plant.

Order creation integration points:

13. Simulates cross-sold master data objects in the cart.

14. Simulates or creates an order (SHOWN).

15. Maintains sales docs in SAP SD.

Order change integration:

16. Simulates or creates an order change.


 
 
Corevist Commerce Cart with SAP data

Order tracking integration points:

17. Retrieves a sales document based on the entered number (incl. doc flow info). Ensures only users assigned to the sold-to/ship-to and/or sales area are getting to see it.

18. Returns a sales document list based on the entered search. (sold-to, ship-to, material, date range, delivery number, invoice number, ETA search). Ensures only results the user is allowed to see are returned (SHOWN).

19. Returns a combination of schedule lines and delivery lines for an order.

20. Returns summary information about the requested sales documents as well as optionally the open items.

21. Returns a list of deliveries.

22. Updates deliveries.

 
 

Accounts receivable integration points:

23. Returns invoice by invoice number (restriction by user authorization).

24. Returns invoice list by search criteria (payer, material, date range, delivery number, order number; restriction by user authorization).

25. Returns open items, with restriction by user authorization (SHOWN).

26. Returns payment history.

27. Pays open items, allowing customers to pay outstanding invoices via credit/debit cards and eChecks.

28. Clears invoices immediately in the A/R module of SAP.

29. Payment integration with Paymetric, Delego, Enterprise Payments, and many other providers.


Technical/foundational objects:

30. Downloads B2B code.

31. Program to find customers/materials/orders/invoices.

32. Generates mock data.

33. IMG for Corevist.

34. Magento material data extract.

35. Test execution of PDF generation for Adobe.

36. Export translations for units of measure.

Auxiliary integration points:

37. Sample BTE user exit for A/R statements.

38. Refresh dynamic product proposal data.

39. Generate PDF of document output type (SHOWN).

40. Return list of tax jurisdiction codes based on ZIP code.

41. Generate pricing details for carts, orders, and invoices.

42. Calculate additional header totals for carts, orders and invoices.

43. Read SAP short dumps.

44. Submit a report for return to Web.

45. Get alternate selling units.

46. Simple email using SAPOffice.

47. RFC Parsing utility.

48 Reads configuration

49. Gets attributes of a date

50. Transfers 1 or more files via SFTP

51. Adds an object attachment

52. Gets a document attachment

53. Lists document attachments

FAQs


 

“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:

  1. SAP Router
  2. Secure site-to-site VPN
  3. 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.

Ready to learn more?

Schedule an intro call, and let’s talk
about your needs in a B2B web channel.