Ellipse Gradient for Header
SAP Business ByDesign logo

SAP Business ByDesign Integration Guide

Integrate SAP Business ByDesign with enterprise applications through OData APIs, SOAP business services, selected outbound messages, and scheduled workflows.

SAP Business ByDesign integration options at a glance

SAP Business ByDesign supports OData services for selected business objects and operations, including querying, creating, updating, pagination, metadata discovery, and supported batch requests. It also provides SOAP-based business object web services for structured and document-oriented transactions. Selected business processes can publish outbound messages through configured communication arrangements, although event coverage is not universal. Document and attachment services are available for selected objects, while larger loads may use service-specific bulk or asynchronous patterns. Martini can consume these APIs, receive supported outbound messages, schedule incremental polling, transform JSON or XML, and expose controlled APIs for downstream applications.

Integration pointSupported by SAP Business ByDesign?Common use casesHow Martini supports it
OData APIsYesQuery, create, update, and delete supported Business ByDesign resources such as Accounts, Products, Sales Orders, and Customer Invoices. Filtering, field selection, expansion, pagination, metadata discovery, and selected batch requests may be available by service.Martini can consume OData endpoints from workflows, manage request configuration, transform responses, and expose APIs that abstract Business ByDesign operations.
SOAP APIsYesUse business object web services for customer and supplier data, Sales Orders, invoices, products, accounting, service, and project transactions. SOAP is suitable for structured or document-oriented processes.Martini can consume SOAP services, use service-specific WSDL and XML mappings, orchestrate multi-step transactions, and handle transport and business faults.
Outbound messagesLimitedSelected business processes can send outbound messages through configured outbound services and communication arrangements. Coverage depends on the process and service and is not a universal event mechanism.Martini can receive supported outbound messages at an API endpoint or workflow trigger, validate the payload, and invoke downstream workflows.
Bulk, async, and batch APIsLimitedSelected OData services may support batch requests, while SOAP services may support document-oriented or bulk messages. Large loads can require service-specific migration or asynchronous capabilities.Martini can group requests where the service supports batching, orchestrate asynchronous status checks, and apply controlled throttling and retry policies.
File and attachment APIsLimitedDocument and attachment services are available for selected business objects. File size, media type, relationships, and supported operations vary by service.Martini can create or update a business document, upload an attachment through the relevant service, preserve returned identifiers, and recover from upload failures.
AuthenticationYesCommunication users, communication arrangements, role permissions, and service-specific configuration control access. Basic authentication, OAuth 2.0, and client certificates may depend on the service and tenant.Martini can use environment-managed credentials, certificates, and endpoint configuration in workflows without embedding secrets in mappings or source logic.
Database accessNoDirect database access to the Business ByDesign tenant is not a standard customer integration mechanism. Published APIs, business services, outbound messages, and supported exports should be used instead.Martini can persist integration checkpoints or canonical data in an approved external database, but it should not connect directly to the Business ByDesign tenant database.

How SAP Business ByDesign exposes data and business events

SAP Business ByDesign OData APIs

SAP Business ByDesign exposes OData services for selected business objects and processes. Supported services can provide filtering, field selection, expansion, pagination, metadata discovery, CRUD operations, and in some cases batch requests.

Martini implementation pattern

Martini implementation pattern: a workflow calls the configured OData service using environment-managed authentication, retrieves a page or filtered change set, transforms the response, applies business rules, and writes the result to the target system or returns it through a Martini API.

Implementation sequence

Configure the communication system and communication arrangement
Store the endpoint and credentials as environment-managed secrets
Retrieve a filtered OData page or changed-object set
Follow pagination or continuation information
Map the response into the target model
Apply validation and business rules before writing the result

SAP Business ByDesign SOAP APIs

SAP Business ByDesign provides SOAP-based business object web services for customer and supplier data, Sales Orders, invoices, products, accounting, service, and project processes. The WSDL and message structure depend on the selected communication scenario.

Martini implementation pattern

Martini implementation pattern: a workflow consumes the selected WSDL-defined service, builds the required XML business document, submits it through the configured arrangement, parses the response or SOAP fault, and coordinates any subsequent document or status operation.

Implementation sequence

Select the Business ByDesign SOAP service and communication scenario
Configure the WSDL-based endpoint and authentication
Build the namespace-qualified XML request
Submit the business document from a Martini workflow
Parse the response and capture document identifiers
Classify SOAP faults as retryable or non-retryable

SAP Business ByDesign outbound messages

Selected Business ByDesign processes can send outbound messages through configured outbound services and communication arrangements. These event-style notifications are generally SOAP-based and do not cover every object or event.

Martini implementation pattern

Martini implementation pattern: expose a controlled Martini API or workflow trigger for the supported outbound message, authenticate and validate the request, retrieve additional Business ByDesign data when the message is only a notification, and dispatch the normalized event to downstream systems.

Implementation sequence

Enable the required outbound service and communication arrangement
Receive the outbound message at a Martini API endpoint
Authenticate and validate the inbound XML payload
Extract the business object and correlation identifiers
Retrieve complete data when the notification is insufficient
Map and route the event to downstream workflows

Scheduled SAP Business ByDesign synchronization

Where an outbound message is unavailable or incomplete, Business ByDesign data can be synchronized through scheduled OData or SOAP polling using a modification timestamp, status, or document identifier where supported by the service.

Martini implementation pattern

Martini implementation pattern: a scheduled workflow reads the persisted high-water mark, requests a bounded change set, processes pages or documents, writes successful results, and advances the checkpoint only after downstream processing completes.

Implementation sequence

Start the workflow on a defined schedule
Read the last successful timestamp or source identifier
Retrieve a bounded and filtered change set
Process pages and transform each object
Write successful results and record correlation identifiers
Advance the checkpoint after confirmed completion

SAP Business ByDesign attachments

Business ByDesign provides document and attachment-related services for selected business objects. Capabilities such as file size, MIME type, relationship, and supported operations vary by service.

Martini implementation pattern

Martini implementation pattern: create or update the primary business document, call the relevant attachment service, associate the returned attachment identifier, and retain enough correlation data to recover from an upload or downstream synchronization failure.

Implementation sequence

Create or identify the primary Business ByDesign document
Validate file size and media type against the selected service
Upload the attachment through the document service
Associate the attachment with the business object
Store the returned attachment identifier
Retry or quarantine failed uploads without duplicating the document

Common SAP Business ByDesign integration patterns

Pattern 1: Synchronize accounts and contacts with Salesforce

When to use this pattern

Use this pattern when Business ByDesign is the ERP system of record for customer or financial context while Salesforce manages sales activity. Synchronization can be bidirectional for master data, with Business ByDesign remaining authoritative for order or financial status.

Integration direction
SAP Business ByDesign
Martini
Salesforce
Example Mapping
SAP Business ByDesign FieldCanonical FieldTarget Field
Account.IDcustomer.externalIdSalesforce Account.External_Id__c
Account.Namecustomer.nameSalesforce Account.Name
Contact.Emailcontact.emailSalesforce Contact.Email
Account.Statuscustomer.statusSalesforce Account.Status__c
Martini implementation pattern

Martini receives a supported outbound message or runs an incremental OData poll, resolves Account and Contact relationships, normalizes ownership and status values, and invokes Salesforce APIs. Lookup-before-create logic and external identifiers prevent duplicates; validation failures are quarantined while transient API failures are retried.

Martini capabilities used
  • workflows
  • API consumption
  • data mapping
  • business rules
  • error handling

Pattern 2: Create sales orders from commerce or CRM applications

When to use this pattern

Use this pattern when Shopify, Salesforce, or another application captures the customer order and SAP Business ByDesign must validate references and create the operational Sales Order. The workflow should return the Business ByDesign document identifier and processing status.

Integration direction
Shopify
Martini
SAP Business ByDesign
Example Mapping
SAP Business ByDesign FieldCanonical FieldTarget Field
order.idsalesOrder.externalReferenceSales Order.External Reference
customer.idcustomer.externalIdSales Order.Account
line_items[].skulines[].productCodeSales Order.Item.Product
line_items[].quantitylines[].quantitySales Order.Item.Quantity
Martini implementation pattern

A Martini API or workflow trigger accepts the source order, validates the Account and Product references, applies currency and quantity rules, and calls the selected OData or SOAP operation. The result is correlated with the source order; ambiguous timeouts are checked before retrying to avoid duplicate Sales Orders.

Martini capabilities used
  • APIs
  • workflows
  • data mapping
  • business rules
  • retry handling

Pattern 3: Distribute customer invoices and payment status

When to use this pattern

Use this pattern when downstream finance, payment, warehouse, or customer-facing applications require Customer Invoices and payment status from Business ByDesign. Scheduled incremental retrieval is appropriate where outbound coverage is unavailable.

Integration direction
SAP Business ByDesign
Martini
NetSuite
Example Mapping
SAP Business ByDesign FieldCanonical FieldTarget Field
CustomerInvoice.IDinvoice.externalIdNetSuite Invoice.ExternalId
CustomerInvoice.GrossAmountinvoice.totalAmountNetSuite Invoice.Total
CustomerInvoice.CurrencyCodeinvoice.currencyNetSuite Invoice.Currency
CustomerInvoice.PaymentStatusinvoice.paymentStatusNetSuite Invoice.Status
Martini implementation pattern

Martini retrieves changed invoices using supported timestamps or status filters, follows pagination, normalizes currency and date values, and writes the mapped invoice to the downstream application. A checkpoint advances only after confirmed success, while duplicate detection uses the Business ByDesign invoice identifier.

Martini capabilities used
  • scheduled workflows
  • API consumption
  • pagination handling
  • data transformation
  • checkpoint management

Pattern 4: Synchronize suppliers and purchase orders

When to use this pattern

Use this pattern when Business ByDesign manages purchasing while an external supplier or procurement application needs supplier master data and Purchase Order status. SOAP may be preferable when the purchasing process is exposed as a structured business document.

Integration direction
SAP Business ByDesign
Martini
Microsoft Dynamics 365
Example Mapping
SAP Business ByDesign FieldCanonical FieldTarget Field
Supplier.IDsupplier.externalIdDynamics 365 Vendor.AccountNumber
Product.ProductIDproduct.codeDynamics 365 Product.ProductNumber
PurchaseOrder.IDpurchaseOrder.externalIdDynamics 365 PurchaseOrder.ExternalReference
PurchaseOrder.StatuspurchaseOrder.statusDynamics 365 PurchaseOrder.Status
Martini implementation pattern

Martini consumes the relevant OData or SOAP service, maps supplier and Product identifiers, validates status transitions, and sends Purchase Order updates downstream. Business document faults are recorded for correction, while transport failures use bounded retries and correlation identifiers.

Martini capabilities used
  • SOAP and REST API consumption
  • workflows
  • mapping and transformation
  • business rules
  • error handling

Applications commonly integrated with SAP Business ByDesign

SAP Business ByDesign can be integrated with adjacent business applications when customer, product, order, invoice, supplier, service, or employee information must cross system boundaries. The exact scope depends on the Business ByDesign communication scenario, the selected service, and the APIs exposed by the other application.

Application Scenario Direction Martini Pattern
Salesforce Synchronize Accounts, Contacts, Leads, sales information, Sales Orders, and customer status between CRM and ERP processes. SAP Business ByDesign → Martini → Salesforce Martini can poll OData services or receive supported outbound messages, normalize Accounts and Contacts, apply ownership and duplicate rules, and invoke Salesforce APIs. Status and identifier mappings can be returned to Business ByDesign through a separate workflow.
Shopify Transfer customers and orders into Business ByDesign and return fulfillment or order status to the commerce platform. Shopify → Martini → SAP Business ByDesign A Martini workflow receives or retrieves Shopify orders, validates customer and Product references, creates a Sales Order through the appropriate OData or SOAP service, stores the Business ByDesign identifier, and publishes status updates back to Shopify.
NetSuite Exchange customers, products, invoices, and order information when both ERP platforms coexist during consolidation or system transition. SAP Business ByDesign → Martini → NetSuite Martini can orchestrate incremental extraction from Business ByDesign, map Customer Invoices and Sales Orders into NetSuite structures, reconcile identifiers, and route validation failures for review before retrying transport failures.
ServiceNow Synchronize customer, asset, service, or support-related information where ERP and service-management processes intersect. SAP Business ByDesign → Martini → ServiceNow Martini can consume Business ByDesign OData or SOAP data, apply object and status mappings, and invoke ServiceNow APIs. A reverse workflow can validate selected ServiceNow updates before writing supported Business ByDesign objects.
Workday Exchange employee, organizational, supplier, or financial reference data in environments using both Business ByDesign and Workday. Workday → Martini → SAP Business ByDesign Martini can schedule retrieval from Workday, transform organization and employee reference values, validate Business ByDesign permissions and code lists, and submit supported updates through the relevant communication arrangement.
Microsoft Dynamics 365 Synchronize customers, products, orders, invoices, or sales information across CRM, finance, and ERP applications. SAP Business ByDesign → Martini → Microsoft Dynamics 365 Martini can coordinate bidirectional API workflows, use stable external identifiers for reconciliation, transform Business ByDesign XML or JSON into Dynamics 365 payloads, and isolate business validation errors from retryable API failures.

How to build a SAP Business ByDesign integration in Martini

Objective

Establish the Business ByDesign communication system, communication arrangement, service endpoint, and permitted integration identity before building the workflow.

Instructions in Martini

  • Select the required OData or SOAP communication scenario
  • Configure the Business ByDesign communication system and arrangement
  • Create or identify the communication user or certificate
  • Confirm business roles, work centers, and service permissions
  • Store credentials, certificates, and endpoint settings as environment-managed secrets

Objective

Select an event-driven or scheduled initiation method based on the availability and coverage of the selected Business ByDesign service.

Instructions in Martini

  • Use a supported outbound message when the required business process provides one
  • Expose a Martini API or workflow trigger for inbound outbound messages
  • Use a scheduler for incremental OData or SOAP polling when notifications are unavailable
  • Define a timestamp, status, or identifier high-water mark where supported

Objective

Retrieve complete and bounded Business ByDesign data while respecting service-specific pagination, query, and payload constraints.

Instructions in Martini

  • Call the selected OData resource or SOAP business service
  • Apply filters and request only the fields required by the integration
  • Follow page or continuation information
  • Retrieve related objects or attachments through separate supported services when necessary
  • Capture source identifiers and correlation references

Objective

Build the Martini workflow that coordinates validation, enrichment, external calls, branching, and completion state across the integration.

Instructions in Martini

  • Sequence Business ByDesign calls and downstream API calls
  • Use conditional routing for create, update, and no-change outcomes
  • Separate transport failures from business validation failures
  • Persist checkpoints only after downstream processing succeeds
  • Use reusable services or workflow components for repeated logic

Objective

Transform Business ByDesign XML or JSON structures into a canonical model and the target application schema without losing identifiers or business context.

Instructions in Martini

  • Map Accounts, Contacts, Leads, Sales Orders, Products, and Customer Invoices explicitly
  • Preserve namespace-qualified SOAP fields and repeating line items
  • Normalize dates, time zones, currencies, decimals, and code values
  • Maintain source-to-target identifiers for reconciliation
  • Treat optional fields and localized values conservatively

Objective

Apply business rules that protect data quality and prevent duplicate or invalid transactions before writes occur.

Instructions in Martini

  • Validate required customer, Product, supplier, and document references
  • Use lookup-before-create or deterministic idempotency keys
  • Check status transitions and ownership mappings
  • Route invalid code-list values and missing permissions for review
  • Prevent retries from creating duplicate business documents

Common SAP Business ByDesign data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
AccountSynchronize customers, prospects, business partners, identifiers, and account status.Salesforce, Microsoft Dynamics 365, NetSuite, ServiceNowMartini retrieves or receives Account data, applies duplicate and ownership rules, maps identifiers and code values, and writes the target representation.
ContactExchange individuals associated with Accounts or other business relationships.Salesforce, Microsoft Dynamics 365, ServiceNowMartini resolves the parent Account, normalizes contact details, validates required fields, and uses stable source identifiers for updates.
LeadMove prospective sales information and qualification data between ERP and CRM processes.Salesforce, Microsoft Dynamics 365Martini maps qualification and ownership values, applies routing rules, and records source-to-target identifiers to prevent duplicate creation.
Sales OrderCreate and distribute customer orders, line items, quantities, pricing, fulfillment information, and processing status.Salesforce, Shopify, Microsoft Dynamics 365, NetSuiteMartini validates customer and Product references, calls the appropriate OData or SOAP operation, stores the Business ByDesign document identifier, and returns processing status.
ProductSynchronize materials, services, descriptions, pricing-related data, and purchasing references.Shopify, Salesforce, Microsoft Dynamics 365, NetSuiteMartini maps product codes, units, descriptions, and status values, while applying field-level validation and incremental synchronization criteria.
Customer InvoiceDistribute billing documents, amounts, tax information, payment status, and sales transaction references.NetSuite, data warehouses, payment applications, customer-facing applicationsMartini retrieves changed invoices, normalizes currencies and timestamps, maps payment status, and routes business validation failures separately from retryable transport errors.

Authentication and security considerations

Communication arrangements and identities

Business ByDesign integrations typically use a communication system, communication arrangement, communication user, and service-specific permissions. Business roles, work centers, and view assignments determine which objects and operations are available.

Authentication options

Basic authentication is common for configured SOAP and OData services. OAuth 2.0 and client certificates may be available for selected services and tenant configurations, so the required method should be confirmed for the chosen communication scenario.

Martini security

  • Store credentials, client secrets, certificates, and endpoints as environment-managed secrets.
  • Limit Business ByDesign permissions to the objects and operations required by the workflow.
  • Use controlled Martini APIs with authentication and authorization for downstream callers.
  • Do not place credentials or sensitive business data in mappings, logs, or error messages.

Operational considerations for SAP Business ByDesign integrations

Pagination and volume

Use filters, bounded page sizes, continuation information, and persisted high-water marks for OData synchronization. Avoid unfiltered large-dataset retrievals and confirm whether batch or bulk behavior is supported by the selected service.

Idempotency and retries

Maintain source-to-target identifiers and use lookup-before-create logic or deterministic idempotency keys. Retry transport failures with bounded backoff, but inspect ambiguous timeouts before resubmitting a document because the original request may have succeeded.

Schema and service variation

Business ByDesign coverage varies by service and release. Treat optional fields as optional, preserve SOAP namespaces and repeating structures, and test WSDL or metadata changes in a non-production tenant.

Errors and monitoring

Distinguish HTTP or SOAP transport faults, authorization failures, communication arrangement errors, validation failures, duplicate documents, and locking errors. Record correlation identifiers and response references while protecting credentials and sensitive business data.

Attachments and regional data

Attachment operations may require a separate service call. Validate file size and MIME type, retain document relationships, and normalize UTC timestamps, currencies, decimal precision, tax values, and localized code lists.

Why use Martini instead of scripts or point-to-point integrations?

Orchestrate complete business processes

Martini coordinates OData calls, SOAP documents, outbound messages, downstream APIs, validation, enrichment, and attachment operations in maintainable workflows rather than scattering logic across scripts.

Separate mappings from transport logic

Reusable mappings and transformation steps can translate Business ByDesign XML or JSON into canonical and target schemas while preserving identifiers, line items, currencies, and business context.

Make reliability explicit

Martini supports scheduled and event-driven workflows with checkpoints, conditional routing, error handling, and retry decisions. This helps distinguish retryable communication failures from non-retryable business validation errors.

Provide controlled integration APIs

Martini can expose APIs that shield downstream applications from Business ByDesign-specific service details, centralize authentication and business rules, and provide a stable contract as endpoint implementations evolve.

Frequently asked questions

How can SAP Business ByDesign be integrated with enterprise systems?

SAP Business ByDesign can integrate through OData services, SOAP-based business object web services, selected outbound messages, document and attachment services, and service-specific batch or asynchronous patterns. Communication systems, communication arrangements, permissions, and service-specific authentication control the available interface.

Can Martini integrate with SAP Business ByDesign?

Yes. Martini can consume SAP Business ByDesign OData APIs and SOAP web services, receive supported outbound messages, schedule incremental polling, transform XML or JSON, and expose APIs that abstract Business ByDesign operations. No native Martini connector is documented in the supplied materials.

Do I need a connector to integrate SAP Business ByDesign with Martini?

No. A dedicated SAP Business ByDesign connector is not required. Martini can use the product's supported OData APIs, SOAP services, outbound messages, attachment services, and configured authentication mechanisms through workflows and APIs.

Is there any extra Lonti cost to integrate SAP Business ByDesign with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate SAP Business ByDesign. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from SAP, cloud infrastructure, or other third-party systems depending on subscriptions, usage, and deployment model.

Should I use SAP Business ByDesign OData or SOAP APIs?

Use OData when the required object and operations are available through a resource-oriented service and the integration benefits from filtering, pagination, or standard CRUD behavior. Use SOAP when the process is exposed as a structured business object service, requires document-oriented processing, or depends on a service-specific transactional operation.

Can Martini receive SAP Business ByDesign events or webhooks?

Business ByDesign supports outbound messages for selected business processes through configured outbound services and communication arrangements, generally using SOAP-style messages. Coverage is service-specific rather than universal. Martini can receive supported messages at an API endpoint; scheduled polling can cover processes without suitable outbound notifications.

How does synchronization handle changed SAP Business ByDesign data?

A Martini workflow can use supported OData filters or service-specific criteria such as modification timestamps, statuses, or document identifiers. It can persist a high-water mark, process bounded pages, and advance the checkpoint only after downstream writes succeed. Stable source identifiers support reconciliation and duplicate prevention.

Can Martini expose an API façade for SAP Business ByDesign?

Yes. Martini can expose a controlled API that hides Business ByDesign-specific OData or SOAP details from downstream applications. The façade can authenticate callers, validate requests, apply business rules, orchestrate one or more Business ByDesign operations, and return a normalized response.

Related Martini documentation

SAP APIs

Triggers

Workflows

Security

Operations

Integrate SAP Business ByDesign with Martini

Connect SAP Business ByDesign to enterprise applications through governed APIs, workflows, mappings, and reliable synchronization patterns with Martini.

EXPLORE MARTINI
BOOK A DEMO