SAP Business ByDesign integration services

Mostly two families. SOAP web services create business documents such as sales orders and price lists; SAP lists them on the SAP Business Accelerator Hub, and each tenant’s Service Explorer provides a WSDL with your extension fields. Custom OData services are simpler for reading materials, orders and deliveries, and analytics OData covers stock and reporting figures.

Usually not. Most integrations run outside the tenant and call web services and OData, which keeps upgrades simple. The Studio fits when logic must run inside ByDesign, such as a custom web service on a business object or a call to an external REST service. Studio solutions have their own build, test and deployment cycle, so we use them only when an external integration cannot do the job.

SAP’s standard ByDesign package includes one test tenant and one production tenant. We configure communication arrangements and run the acceptance tests in the test tenant, then repeat the configuration in production. SAP advises against applying Studio add-ons between the test and production upgrades, so releases are planned around your upgrade dates.

Yes, if you use the right service. SAP’s published ByDesign API samples create sales orders with external payment through the Manage Sales Orders web service, because that payment information cannot be created through OData. We follow the same pattern and keep the web order reference on the ByDesign documents so finance can match payments and refunds.

Yes. AIONDATA can build a custom MCP server that wraps selected ByDesign services, such as order status, stock overview and invoice lookups, as tools that run under a dedicated integration user. Read tools come first; any write action, such as creating a sales order, sits behind approval rules you define.