Intro: Integrating Magento and SAP Business One

First published on: 08/10/2023/6:54 pm

The Basics

Vision33’s The Saltbox Platform is a cloud-native, low-code integration platform as a service (iPaaS) solution that empowers small and midsized companies to integrate disconnected systems like ERP, CRM, and eCommerce. 

Technology modules called connectors work with The Saltbox Platform to facilitate the integration.

This connector enables users to:

1. Integrate Magento and SAP Business One
2. Automate common transactions between applications (using starter workflows)

These starter workflows accelerate integration projects by getting data flowing between systems quickly. Workflows can then be customized to address business-specific processes and requirements. 

Magento-SAP Business One ExpressConnect Workflows 

Don't see what you're looking for?

These workflows can be customized, or new workflows can be created from scratch to address your unique requirements.

Contact us to start the discussion.

How Long Does It Take To Build an Integration? 

It takes approximately 16 weeks from project kickoff to completion to build a standard integration (with limited customizations).

This timeline could be extended if:

• Requirements aren't well defined or change mid-project
• Client availability or subject matter knowledge is limited
• The project isn’t prioritized
• The applications being integrated aren't live
• Data quality is poor

If we avoid these pitfalls, the project could be completed early.

What Does a Typical Integration Project Look Like? 

A typical Saltbox integration project follows this process:

• Vision33 sets up (provisions) your instance of Saltbox, your account, and the workflow(s) you purchased.

• Vision33 leads a collaborative mapping session to review the purchased workflows and how the affected data will map between the integrated applications. A templated document, aka a blueprint, is updated to document the workflow settings and revised mappings.
  • Vision33’s implementation team uses this document to instruct the implementation.
• The blueprint is sent to you for signature.
• You assess and prepare third-party and/or SAP Business One data quality to ensure it’s ready for the integration.
• You perform user acceptance testing (UAT) with support from your Vision33 delivery team.
• Together, we do a final project review and user acceptance testing sign-off.
• Vision33 migrates the project to the production environment, and it goes live!
• The completed project enters Hypercare, a two-week monitoring period to catch issues.
• The Vision33 implementation team performs a soft transfer to the TOTAL Care customer support team, who will support you should issues arise.

The Integration Project Team 

Licensing and Technology Requirements

SAP Business One

SAP Business One integration projects require:

• An SAP Business One indirect user license
• Giving Vision33 access to the sandbox and production sites for SAP Business One
• Clients using SAP Business One on-premises or not hosted by Vision33 will require additional technical infrastructure:
  • For Microsoft SQL: Application server to host the B1WebAPI
  • For SAP HANA: Proxy Server to protect the database server from direct exposure to the internet

(Vision33 can support these requirements for an additional fee.)

Magento

The client must give Vision33 access to the following for both sandbox and production sites:

• Admin Site URL & credentials

• API URL

• API User Name

• API Password

• Authentication Type

  • Auth

  • No Auth – access token required

  • Auth with 2FA – secret key required

If Using Add-Ons With Magento

Any add-ons used with Magento must be identified early in the project. Failure to do so could cause project delays and affect workflow setup, project scope, cost, and timelines.

Version Support

Vision33’s standard workflows support Magento V2.0 or higher.

Vendor API Changes

This section outlines how we handle vendor API changes and customer responsibilities:

• Vision33 uses APIs to exchange data between third-party applications and The Saltbox Platform.
• Occasionally, third-party vendors release API changes with little to no warning, which can lead to failed integration(s).
  • Vision33 is not responsible for changes third-party vendors make to their software or APIs or the impact of those changes on your business. Should an unplanned change occur, we will do our best to minimize the effect on your business.
• We regularly monitor API release notes for planned changes and, when announced, assess and communicate their impact to all customers with active integrations. 
• If work must be completed to eliminate disruption to your integration(s), Vision33 will provide a scope of work, next steps, and cost estimate.
  • Work will not begin without your explicit consent, and timing will be coordinated in advance with you.
• Additional costs could apply to both planned and unplanned vendor API changes. 
• Any work and related costs must be approved in writing before work can begin.

Required Skill Set for Self-Implementation of Starter Workflows

Self-implementation requires a working knowledge of:

• XML
• The ERP system (queries, custom/user-defined fields, etc.)
• The third-party application
• Data types
• Data transformation