Frequently Asked Questions
SAP Business Technology Platform: Frequently Asked Questions
Everything you need to know about SAP Business Technology Platform engagements with MYGO Consulting.
What is the difference between ABAP Cloud and side-by-side extensions?
ABAP Cloud runs inside the S/4HANA stack using the ABAP RESTful Application Programming model. It is ideal for extensions that need direct access to S/4HANA data and transactional logic. Side-by-side extensions run on BTP (Cloud Foundry or Kyma) as independent applications that communicate with S/4HANA through APIs and events. Side-by-side is better for extensions with their own data model, external integrations, or non-ABAP technology requirements.
How does SAP Integration Suite compare to middleware like MuleSoft or Boomi?
SAP Integration Suite offers native connectivity to SAP systems with pre-built adapters and content packages, reducing development effort for SAP-centric scenarios. It also includes API Management, Event Mesh, and Trading Partner Management in a unified platform. Third-party platforms may offer broader non-SAP connectivity or specific features, but add licensing cost and require SAP connector maintenance. We evaluate trade-offs for each client and often recommend a hybrid approach.
Can you migrate our existing PI/PO interfaces to Integration Suite?
Yes, we have a structured migration methodology for PI/PO to Cloud Integration. This includes automated interface assessment with SAP's Migration Assessment tool, semi-automated migration of ICOs to iFlows, and manual optimization. We prioritize interfaces by business criticality and run parallel operations during transition.
How do you handle authentication and SSO for BTP applications?
We configure SAP Identity Authentication Service (IAS) as the identity provider for BTP applications, with federation to your corporate IdP (Azure AD, Okta, etc.). This provides SSO across SAP and BTP applications with centralized user lifecycle management. For API consumers, we implement OAuth 2.0 client credentials or JWT bearer flows.
What governance model do you recommend for BTP?
We recommend a hub-and-spoke subaccount structure with a central governance subaccount for shared services and dedicated subaccounts per project or department. Entitlement distribution, naming conventions, and resource quotas are managed through a central platform team. New extension requests follow an intake process that evaluates business justification, architecture alignment, and cost impact.
How long does a typical BTP integration project take?
A focused integration project with 5-10 interfaces typically takes 8-12 weeks from architecture through production deployment. Complex programs involving custom app development, event-driven architectures, or large-scale PI/PO migrations may run 4-6 months. We deliver working integrations incrementally so the business sees value within the first few sprints.
Still Have Questions?
Talk to our SAP experts and get answers to your specific questions directly.