Can you integrate MySQL with SAP Business ByDesign?

Explore a MySQL and SAP Business ByDesign integration with a Stacksync engineer. Stacksync support for SAP Business ByDesign is not established by the connector documentation reviewed for this page. Start with one record and the update your business needs to identify an implementation path.

Can MySQL and SAP Business ByDesign sync in both directions?

Confirm two-way support with Stacksync for the records and fields you need in both systems. Access to a vendor API does not confirm that its Stacksync connector supports write-back.

What should be ready before the MySQL and SAP Business ByDesign initial load?

Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Use one auto-generated primary key per selected table and grant the connected user the required table permissions. Identify the SAP Business ByDesign account, edition, environment, and business objects the integration must access. Use the pair worksheet to record ownership and acceptance criteria.

How fast does the MySQL to SAP Business ByDesign sync run?

Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.

Will existing duplicates merge automatically?

No. Stacksync documents that pre-existing duplicates are not merged automatically when two-way sync begins. Review the initial dataset and matching plan before enabling it; an empty destination can simplify the first load.

How do I map MySQL fields to SAP Business ByDesign?

Start with one business entity and a stable record ID. Map a small set of editable fields with compatible types, test required values and relationships, then expand after the pilot passes.

What should I do if a record fails to sync?

Check the destination error, field constraints, permissions, and current source value. The Stacksync issues dashboard supports retry and revert; retry reads current source values, so verify the intended record state before acting.

What does a MySQL and SAP Business ByDesign integration cost?

Use the current Stacksync pricing page and confirm the supported implementation with the team. Scope the required objects, record volume, update frequency, initial load, and support needs when comparing a managed connector with native or custom development.

Which records should the MySQL and SAP Business ByDesign pilot start with?

Start by reviewing Proposed customer table in MySQL (choose its name) in MySQL and Business Partners (Accounts) in SAP Business ByDesign. Check how these records relate in your workflow, then confirm the actual fields and supported operations. Test record matching and one failed or repeated update before adding more records.

Database / ERP · Two-way sync platform

MySQL and SAP Business ByDesign integration

Plan how MySQL and SAP Business ByDesign should share data across your business. Work with Stacksync engineers on record mapping, system access, and the requirements for running the integration.

Scope your workflow with an integration engineer
Review the systems, records, and updates you need

Integration planning

stacksync.com

MySQL

SAP Business ByDesign

Review the integration scope

Built for teams where self-serve, reliability and scale matter

Case study

Migrated from MuleSoft

Case study

Migrated from Celigo

Migrated from Heroku Connect

Migrated from Matillion

Case study

Migrated from Fivetran

Case study

Migrated from Celigo

Proposed workflow

Customer reporting workflow

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting eventA change involving the proposed customer table in MySQL or SAP Business ByDesign Business Partners (Accounts) needs a defined result in the other system.

Start with the proposed customer table in MySQL and SAP Business ByDesign Business Partners (Accounts). Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve person or company type, legal entity, business role, and any billing account before transactions.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

What to verifyTest an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

Review records and field ownership

Proposed record relationships

Records to connect

Use these examples to define record matching and field ownership for your technical review.

Download the mapping worksheet

CSV · No email required

Example record relationships between MySQL and SAP Business ByDesign
MySQL record	SAP Business ByDesign record	Record matching	Field ownership
Proposed customer tableProposed table; choose its name and schema.Reporting dataset	Business Partners (Accounts)Proposed record; confirm Stacksync object support.	Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient.	Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company.
Proposed customer invoice tableProposed table; choose its name and schema.Reporting dataset	Customer InvoicesProposed record; confirm Stacksync object support.	Retain the invoice ID, issuer/legal entity, and original order reference; invoice numbers alone may overlap.	The financial system owns posting and accounting treatment. A posted invoice may need a credit or adjustment process instead of an overwrite.
Proposed sales order tableProposed table; choose its name and schema.Reporting dataset	Sales OrdersProposed record; confirm Stacksync object support.	Preserve both the order ID and stable line IDs. Allow one order to relate to several shipments or invoices.	Decide which system approves the order and which can cancel or amend it after fulfillment begins.

These relationships do not establish connector availability. Review the required connection and record operations with Stacksync.

Record coverage to review

Use documented coverage where available. Catalog record types are starting points for review and do not confirm Stacksync support.

MySQL

Read and write support varies by record

Record types covered in the setup guide

Record types	Coverage and requirements
Tables	See connector requirements. Confirm field permissions and sync direction.

Read the MySQL connector guide

SAP Business ByDesign

Connection and object support require review

Record types to review with Stacksync

Record types	Coverage and requirements
Business Partners (Accounts) Contacts Sales Orders Customer Invoices Materials / Products Purchase Orders	Confirm support for this record type and the direction you need.

Discuss SAP Business ByDesign requirements

Connection essentials

Confirm Stacksync support and account requirements for undocumented connections. Interface information alone does not establish connector availability.

View setup requirements and limits

Connection requirement	MySQL	SAP Business ByDesign
Integration interface	SQL wire protocol (MySQL client/server protocol)	SOAP web services plus OData services for analytical and custom data access
Authentication	Database credentials entered as a connection string or parameters, with optional SSL root certificate upload and optional SSH tunnel	Confirm the credentials, API plan, and permissions required for SAP Business ByDesign.
Change detection	Stacksync creates database triggers for change logging.	Confirm how Stacksync detects changes for this connector and the objects you need.
Read access	Available for supported records	Confirm with Stacksync
Write access	Available for supported records	Confirm with Stacksync

Enterprise controls

Security and control for your integrations

Explore security controls

Compliance and data transfers

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

Record-level recovery

Inspect sync errors and use retry and revert controls to resolve failed updates.

Read the recovery guide

Implementation

Technical reference

Review setup, record relationships, testing, and recovery for your implementation.

Authentication, permissions and API limits

Connection requirements and limits

MySQL

Integration interface: SQL wire protocol (MySQL client/server protocol)
Authentication: Database credentials entered as a connection string or parameters, with optional SSL root certificate upload and optional SSH tunnel (SSH user + SSH host)
Change detection: Stacksync creates database triggers for change logging. Trigger permissions and binary-log settings must allow their creation.
Read access: Available for supported records
Write access: Available for supported records

Setup requirements

Use one auto-generated primary key per selected table and grant the connected user the required table permissions.
Verify that Stacksync can create triggers. When binary logging is enabled, an administrator may need to enable log_bin_trust_function_creators.

Limitations to check

Composite keys are unsupported and schema/table/column renames require a sync configuration update.

Technical documentation

Documentation reviewed 2026-09-15. Check the linked guides for current account and record requirements.

MySQL setup guide

SAP Business ByDesign

Integration interface: SOAP web services plus OData services for analytical and custom data access
Authentication: Confirm the credentials, API plan, and permissions required for SAP Business ByDesign.
Change detection: Confirm how Stacksync detects changes for this connector and the objects you need.
Read access: Confirm with Stacksync
Write access: Confirm with Stacksync

Setup requirements

Identify the SAP Business ByDesign account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for SAP Business ByDesign, including read/write support, authentication, and initial-load limits.

Limitations to check

Confirm Stacksync support for SAP Business ByDesign and the record types your workflow needs.
Review write-back, deletion handling, update timing, and account limits with the integration team.

Prepare MySQL and SAP Business ByDesign access

Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.

MySQL setup checklist

Use one auto-generated primary key per selected table and grant the connected user the required table permissions.
Verify that Stacksync can create triggers. When binary logging is enabled, an administrator may need to enable log_bin_trust_function_creators.

Setup guides: Authorize MySQL

SAP Business ByDesign setup checklist

Identify the SAP Business ByDesign account, edition, environment, and business objects the integration must access.
Confirm a Stacksync connector or implementation path for SAP Business ByDesign, including read/write support, authentication, and initial-load limits.

Prepare to go live

Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.

Use the MySQL and SAP Business ByDesign planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.

Talk to an engineer · Review current pricing

Record identity and field ownership

Use these data-model references to describe the records your connection needs. They are planning examples; connector availability and supported operations must be established before implementation.

Download the mapping worksheet · CSV, no email required

Reporting dataset

Proposed customer table in MySQL (choose its name) / Business Partners (Accounts)

Plan a customer dataset while preserving its source meaning.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

MySQL: Your database schema
SAP Business ByDesign: Object support to establish
Record identity: Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient.
Field ownership: Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company.

Fields to include

Source customer ID
Person/company classification
Legal entity or business unit
Destination identity reference

Record dependencies: Resolve person or company type, legal entity, business role, and any billing account before transactions.
Validation: Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
Recovery: Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

Reporting dataset

Proposed customer invoice table in MySQL (choose its name) / Customer Invoices

Plan a customer invoice dataset while preserving its source meaning.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

MySQL: Your database schema
SAP Business ByDesign: Object support to establish
Record identity: Retain the invoice ID, issuer/legal entity, and original order reference; invoice numbers alone may overlap.
Field ownership: The financial system owns posting and accounting treatment. A posted invoice may need a credit or adjustment process instead of an overwrite.

Fields to include

Source invoice ID
Customer or supplier reference
Line totals
Currency
Posting/payment status

Record dependencies: Resolve the customer or supplier, account codes, tax, currency, and accounting period before posting.
Validation: Test a posted invoice, a partial payment, tax rounding, and a closed accounting period. Compare financial totals within the same entity and currency.
Recovery: Determine whether a transaction posted before retrying. Follow the approved adjustment process for posted records.

Reporting dataset

Proposed sales order table in MySQL (choose its name) / Sales Orders

Plan a sales order dataset while preserving its source meaning.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

MySQL: Your database schema
SAP Business ByDesign: Object support to establish
Record identity: Preserve both the order ID and stable line IDs. Allow one order to relate to several shipments or invoices.
Field ownership: Decide which system approves the order and which can cancel or amend it after fulfillment begins.

Fields to include

Source order ID
Customer reference
Line references and quantities
Order status
Currency

Record dependencies: Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
Validation: Test a multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.
Recovery: Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.

Reporting dataset

Proposed contact table in MySQL (choose its name) / Contacts

Plan a contact dataset while preserving its source meaning.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

MySQL: Your database schema
SAP Business ByDesign: Object support to establish
Record identity: Use a stable person/contact ID and an explicit cross-system lookup. Email can change and can be shared, so treat it as a matching clue rather than a universal key.
Field ownership: Keep consent and communication preferences under an agreed authority; a general contact update must not silently resubscribe someone.

Fields to include

Source person ID
Display name
Email address
Organization reference
Consent state

Record dependencies: Resolve the organization relationship and any owner or consent references required by the destination.
Validation: Test an email change, two records sharing an email, and a person associated with multiple organizations.
Recovery: Hold ambiguous matches for review and reconcile the person ID before retrying; preserve the consent decision already recorded by its owner.

Reporting dataset

Proposed product or catalog item table in MySQL (choose its name) / Materials / Products

Plan a product or catalog item dataset while preserving its source meaning.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

MySQL: Your database schema
SAP Business ByDesign: Object support to establish
Record identity: Distinguish the product ID, variant ID, SKU, and price-list entry; they are not interchangeable keys.
Field ownership: Assign ownership for catalog content, price, and stock separately.

Fields to include

Source product ID
SKU or variant reference
Description
Unit of measure
Price-list reference

Record dependencies: Resolve units, variants, categories, and applicable price lists before order lines.
Validation: Test two variants of one product, a changed SKU, and a price that applies to only one market or currency.
Recovery: Repair the variant or price-list reference before retrying affected order lines; preserve existing transaction prices.

Reporting dataset

Proposed deal or opportunity table in MySQL (choose its name) / Opportunities

Plan a deal or opportunity dataset while preserving its source meaning.

Planning example. Stacksync support for the required connection and record operations needs a technical review.

MySQL: Your database schema
SAP Business ByDesign: Object support to establish
Record identity: Keep the opportunity/deal ID separate from any later order or invoice ID.
Field ownership: The sales process owns qualification and stage changes; downstream financial records have their own state and approval rules.

Fields to include

Source deal ID
Stage
Amount and currency
Expected close date
Company reference

Record dependencies: Map the customer and sales pipeline before the opportunity; map stage values deliberately.
Validation: Test a reopened won deal, a stage with no destination equivalent, and an amount using a different currency.
Recovery: Suspend downstream creation for a rejected deal and review whether an order already exists before retrying.

Compare integration approaches

Choose a method around one example record and the update your business needs. Use Proposed customer table in MySQL (choose its name) / Business Partners (Accounts) to review record matching and confirm Stacksync support for the required operations. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.

Stacksync managed sync

Best fit: Review compatibility with a Stacksync engineer using an example of the records and updates you need.
Operating responsibility: Fits ongoing record synchronization when the required operations are supported. Add workflow steps for approvals or business actions that go beyond copying fields.
Before you choose: Check record matching: Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient. Verify field coverage, deletion handling, and how changes are detected.

Native vendor integration

Best fit: A vendor-built integration may fit if it supports your MySQL and SAP Business ByDesign record types.
Operating responsibility: Can reduce setup for a supported workflow. You may need another method for records or business steps it does not cover.
Before you choose: First check whether either vendor offers this integration. If available, verify Proposed customer table in MySQL (choose its name) / Business Partners (Accounts), update direction, account tier, and related-record handling.

Custom API or workflow

Best fit: Consider when MySQL and SAP Business ByDesign need a transformation, approval, or action outside a direct record sync.
Operating responsibility: Provides control over business steps; the team owns credentials, version changes, error queues, and reconciliation.
Before you choose: Verify endpoint permissions, pagination, quotas, duplicate detection, and failure recovery. Separate reading history from actions that send messages, grant access, or post transactions.

File or scheduled snapshot

Best fit: Consider for a one-time MySQL / SAP Business ByDesign migration or a reporting need with an explicit freshness window.
Operating responsibility: Can simplify a bounded transfer; later changes and deletion history require another extraction or a separately designed incremental process.
Before you choose: Record the extraction cutoff, source IDs, encoding, date/number formats, and reconciliation totals.

Workflow scenarios and expected results

Customer reporting workflow

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting event: A change to the selected Proposed customer table in MySQL (choose its name) or Business Partners (Accounts) record needs a defined result in the other system.

Start with MySQL Proposed customer table in MySQL (choose its name) and SAP Business ByDesign Business Partners (Accounts). Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve person or company type, legal entity, business role, and any billing account before transactions.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

If it fails: Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

Customer invoice reporting workflow

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting event: A change to the selected Proposed customer invoice table in MySQL (choose its name) or Customer Invoices record needs a defined result in the other system.

Start with MySQL Proposed customer invoice table in MySQL (choose its name) and SAP Business ByDesign Customer Invoices. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve the customer or supplier, account codes, tax, currency, and accounting period before posting.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test a posted invoice, a partial payment, tax rounding, and a closed accounting period. Compare financial totals within the same entity and currency.

If it fails: Determine whether a transaction posted before retrying. Follow the approved adjustment process for posted records.

Sales order reporting workflow

Planning example. Stacksync support for the required connection and record operations needs a technical review.

Starting event: A change to the selected Proposed sales order table in MySQL (choose its name) or Sales Orders record needs a defined result in the other system.

Start with MySQL Proposed sales order table in MySQL (choose its name) and SAP Business ByDesign Sales Orders. Use the record-matching and field-ownership rules from your mapping worksheet.
Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.

Expected result: Test a multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.

If it fails: Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.

Reconcile SAP Business ByDesign business records with MySQL

This is an evaluation scenario; connector and operation support require confirmation.

Starting event: A finance-owned record in SAP Business ByDesign needs operational visibility through a selected destination dataset.

Select Business Partners (Accounts) or Contacts with the correct legal entity, period, and currency.
Define a reporting relationship in MySQL; do not equate customer records, ledger accounts, and posted transactions.
Decide whether the process only reports a financial state or requests an approved accounting action, and maintain a separate transaction ID for each action.

Expected result: Totals reconcile within the same entity/currency/window; a repeated handoff creates no duplicate financial transaction.

If it fails: Verify posting and settlement state before retrying. Use the approved adjustment path for already-posted transactions.

Initial load and acceptance testing

Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.

Proposed customer table in MySQL (choose its name) / Business Partners (Accounts)

Test case

Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.

Expected result

The expected customer relationship is preserved with no duplicate action or unintended write.

Proposed customer invoice table in MySQL (choose its name) / Customer Invoices

Test case

Test a posted invoice, a partial payment, tax rounding, and a closed accounting period. Compare financial totals within the same entity and currency.

Expected result

The expected customer invoice relationship is preserved with no duplicate action or unintended write.

Proposed sales order table in MySQL (choose its name) / Sales Orders

Test case

Test a multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.

Expected result

The expected sales order relationship is preserved with no duplicate action or unintended write.

Proposed contact table in MySQL (choose its name) / Contacts

Test case

Test an email change, two records sharing an email, and a person associated with multiple organizations.

Expected result

The expected contact relationship is preserved with no duplicate action or unintended write.

Direction and permissions

Test case

Bring an example source record and the intended destination operation to the compatibility review. Confirm the supported route before granting write access.

Expected result

Only an approved, supported direction and permitted fields are written.

Freshness and reconciliation

Test case

Measure source and destination times for the selected records under normal load and a burst. Reconcile IDs and values using the same filters and cutoff.

Expected result

The process meets its agreed freshness target and reconciliation has no unexplained differences.

Failed updates, retries and recovery

Start with the failed record and the destination error, then inspect the source value, field requirements, and access.

Rejected or repeated customer change

Investigate

Inspect MySQL Proposed customer table in MySQL (choose its name) and SAP Business ByDesign Business Partners (Accounts), their IDs, and the destination error.

Next action

Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.

Rejected or repeated customer invoice change

Investigate

Inspect MySQL Proposed customer invoice table in MySQL (choose its name) and SAP Business ByDesign Customer Invoices, their IDs, and the destination error.

Next action

Determine whether a transaction posted before retrying. Follow the approved adjustment process for posted records.

Rejected or repeated sales order change

Investigate

Inspect MySQL Proposed sales order table in MySQL (choose its name) and SAP Business ByDesign Sales Orders, their IDs, and the destination error.

Next action

Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.

A record type or update is unavailable

Investigate

Check the MySQL and SAP Business ByDesign connector guides, account permissions, and any operations marked On Request.

Next action

Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.

Source and destination disagree after a retry

Investigate

Compare current source values, destination validation, identity mappings, and any side effects already completed.

Next action

Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.

Read the Stacksync issues dashboard guide for retry and revert behavior.

Change detection and update delivery

How updates move between MySQL and SAP Business ByDesign

See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.

MySQL SAP Business ByDesign Direction requires confirmation

Detect changesStacksync creates database triggers for change logging. Trigger permissions and binary-log settings must allow their creation.

Apply updatesConfirm that Stacksync can create or update the records you need in SAP Business ByDesign.

SAP Business ByDesign MySQL Direction requires confirmation

Detect changesConfirm how Stacksync detects changes for this connector and the objects you need.

Apply updatesConfirm that Stacksync can create or update the records you need in MySQL.

Update timing and record limits

Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
Review write-back, deletion handling, update timing, and account limits with the integration team.

FAQ