# @mlatha_naidu on Instagram

- **Type:** Video
- **Original URL:** https://www.instagram.com/p/DdZeyZ2zfLf
- **Gondola URL:** https://gondola.cc/posts/70661556-mlatha-naidu-instagram
- **Thumbnail:** https://img.gondola.cc/tr:w-,h-,fo-auto/postThumbnails/bcb573de76.jpg
- **Posted:** 2026-09-17T18:15:30.000+00:00
- **Account Owner:** Madhulatha Pelluri (@mlatha_naidu) — https://gondola.cc/mlatha_naidu

## Caption

Story Book 1073:  Day 57 -🚀 SAP BTP Learning Journey — The Cockpit may change, but the architecture fundamentals remain
Today I explored the refreshed SAP BTP Cockpit as part of my hands-on SAP Business AI architecture learning journey.
The updated experience surfaced several areas that are worth understanding beyond simply knowing where to click:
🔹 Account Explorer — understanding Global Accounts, directories and subaccounts
🔹 Entitlements — understanding what services a subaccount is allowed to consume
🔹 Boosters — guided setup for supported BTP scenarios
🔹 System Landscape — connecting the wider SAP landscape with BTP
🔹 Security & Usage — identity, authorization, governance and consumption visibility
🔹 Resource Providers — integrating supported external cloud resources
One item particularly caught my attention: “Set Up MCP Server.”
MCP (Model Context Protocol) introduces an important architecture concept for the agentic AI world: enabling AI clients and agents to interact with tools, APIs and enterprise capabilities through a standardized protocol.
Conceptually:
AI Agent → MCP → Enterprise Tool/API → Business System
In an SAP architecture, this opens interesting future patterns around CAP services, SAP Integration Suite, enterprise APIs, HANA Cloud and AI agents.
But I’m deliberately not jumping into MCP yet.
My hands-on roadmap is:
SAP CAP → HANA Cloud → APIs & Integration → Generative AI → RAG / Vector Search → Security → MCP → Joule / Agents → Governance
The current POC is intentionally simple: a CAP Learning Tracker built in SAP Business Application Studio using Node.js, CDS, OData V4 and SQLite.
The goal is to understand every layer before adding the next one—and eventually evolve the same application into an enterprise AI/agent architecture.
Next checkpoint: get the CAP service running in BAS and understand the complete flow:
CDS → CAP Service → OData V4 → Event Handler → Persistence
#SAP #SAPBTP #SAPBusinessAI #CAP #SAPCAP BusinessApplicationStudio MCP GenerativeAI Joule EnterpriseAI CloudArchitecture LearningJourney OperationSelfLearnings

## Stats

- **Views:** 293
- **Likes:** 2
- **Shares:** 0
- **Comments:** 0

## Tags

sapbtp, cap, sap, sapbusinessai, sapcap

---
Copyright (c) Gondola