{"id":55657,"date":"2026-11-12T16:36:52","date_gmt":"2026-11-12T15:36:52","guid":{"rendered":"https:\/\/www.altares.be\/?p=55657"},"modified":"2026-11-12T16:41:42","modified_gmt":"2026-11-12T15:41:42","slug":"sap-integration-via-sap-btp-from-custom-development-project-to-subscription","status":"publish","type":"post","link":"https:\/\/www.altares.be\/en\/blog\/master-data-management\/sap-integratie-via-sap-btp-van-maatwerkproject-naar-abonnement\/","title":{"rendered":"SAP integration via SAP BTP: from custom development project to subscription"},"content":{"rendered":"

Creating a supplier in SAP starts with finding the right company information. For users, this is a routine part of their daily work. For IT, however, it often involved an entire project. The integration had to be built, configured and retested after every SAP upgrade. At Altares Dun & Bradstreet, we have supported customers and their SAP partners with this work for many years.<\/p>\n\n\n\n

Together with SAP partner Talan, we developed dataxess for SAP<\/a>.The integration runs on SAP Business Technology Platform (SAP BTP) and is available as a subscription. This also changes our role. As the provider, we manage the application ourselves. What does this mean for the integration, maintenance and access to your data?<\/p>\n\n\n\n

\"sap<\/figure>\n\n\n\n

What changes when an SAP integration is offered as SaaS?<\/h2>\n\n\n\n

With a custom-built SAP integration, you have an integration developed specifically for your own environment. After go-live, someone needs to maintain the code, manage the hosting and test whether the integration still works after an SAP upgrade.<\/p>\n\n\n\n

When you subscribe to an integration as Software as a Service (SaaS), the provider takes care of hosting, application management and updates. With dataxess for SAP, Altares takes on these responsibilities. Your IT team can focus on configuring and testing the connection to your own SAP environment.<\/p>\n\n\n\n

This division of responsibilities matters when working with a system that supports processes such as procurement, invoicing and logistics. A change in SAP can affect multiple teams. That is why you want to know in advance what is required to connect the integration and which processes need to be tested.<\/p>\n\n\n\n

Interesting to read:<\/strong> SAP deadline 2030: prepare your data for S\/4HANA<\/a><\/p>\n\n\n\n

How does SAP BTP support the Clean Core approach?<\/h2>\n\n\n\n

With SAP's Clean Core approach, you keep the core system as close to standard as possible. SAP BTP provides an environment where extensions can run outside that core. Dataxess for SAP exchanges data with your SAP system through interfaces. This means you do not need to install custom code in the SAP core for this integration.<\/p>\n\n\n\n

Altares manages the application from a central SAP BTP account. Within this account, your organisation gets its own subaccount and a dedicated URL to access the application.<\/p>\n\n\n\n

How do you connect dataxess for SAP?<\/h2>\n\n\n\n
    \n
  1. Altares sets up your subaccount<\/strong> and activates the subscription.<\/li>\n\n\n\n
  2. Your IT team provides a technical user account<\/strong> with the permissions required by the integration.<\/li>\n\n\n\n
  3. The connection is configured and tested.<\/strong> For example, you check whether supplier information is transferred to the correct fields in a Business Partner.<\/li>\n\n\n\n
  4. Users log in<\/strong> via your organisation's URL.<\/li>\n<\/ol>\n\n\n\n

    Interesting to read:<\/strong> SAP Clean Core: why innovation starts alongside the core<\/a><\/p>\n\n\n\n

    What are the benefits of multitenancy for your SAP integration?<\/h2>\n\n\n\n

    With dataxess for SAP, multiple customers use the same application. Each customer works in their own logically separated environment. This is known as multitenancy<\/em> and offers seven practical benefits<\/p>\n\n\n\n