A very different road
The door you haven't opened with the biggest difference in steps from this one.
9. Keep AI outside SAP for now
Open door 9
Door 3Draft
Build AI on SAP BTP next to ECC
What this road promises
“Generative AI Hub gives governed access to many AI models.”Source: SAP Help Portal
Ask yourself:
1Get a BTP account and AI entitlementsAsk yourself:Do we already have BTP credits hidden somewhere in our contract?
Set up BTP with AI Core access.
2Connect ECC through Cloud ConnectorAsk yourself:Security will want to review a tunnel into ECC.
Install Cloud Connector so BTP reaches ECC.
3Expose the data and functions the AI needsAsk yourself:Few ready APIs in our ECC. Each missing one is development.
Build the APIs the AI needs.
4Choose models in Generative AI HubAsk yourself:How do I estimate token costs before the first bill shows up?
Pick models. Usage is billed per token.
5Build the app or agentAsk yourself:Do I have anyone who actually knows BTP, or is this another SI project?
Develop the app on BTP.
6Set up authorizations and governanceAsk yourself:Does the AI see data with the user's permissions, or a technical user's?
Decide who signs in and sees what.
7Test, deploy, runAsk yourself:Who maintains this after the SI leaves?
Test with users, go live, watch costs.
8When we migrateAsk yourself:Which parts get rebuilt when ECC is replaced?
Rework connections when ECC is replaced.
Where this road lands
- AI you get
- Whatever you build, use case by use case.
- Time to production
- No public benchmark.
- Team load
- Medium to high. BTP developers or an SI.
- New systems
- BTP, AI Core, Cloud Connector.
- Survives migration
- Apps stay. ECC connections need rework.
- Security and licensing
- Cloud tunnel to review. API policy applies.
- Source: SAPinsider (Independent press and analysts)
- Adoption risk
- Depends on each app.
Add this road to my plan
Open another door
Another road you haven't opened
One of the doors you haven't opened, picked at random.
1. Get SAP's AI after moving to S/4HANA
Open door 1