# @mlatha_naidu on Instagram

- **Type:** Video
- **Original URL:** https://www.instagram.com/p/DYUnngTyUXd
- **Gondola URL:** https://gondola.cc/posts/65575392-mlatha-naidu-instagram
- **Thumbnail:** https://img.gondola.cc/tr:w-,h-,fo-auto/postThumbnails/f0adb0c39a.jpg
- **Posted:** 2026-05-14T14:19:25.000+00:00
- **Account Owner:** Madhulatha Pelluri (@mlatha_naidu) — https://gondola.cc/mlatha_naidu

## Caption

Story Book 534 🚀 | CAPM Day 25
Today I learned an important enterprise API design concept while working with SAP CAP and OData V4.
Initially, my PurchaseOrders entity stored simple text values like:
productName
supplierName
That approach works for small demos, but it is not how enterprise systems are usually designed.
So I redesigned the model using Associations.
Now:
PurchaseOrders
→ references Products
→ references Suppliers
instead of storing duplicate text values.
After that, I tested the OData $expand query:
/odata/v4/enterprise/PurchaseOrders?$expand=product,supplier
This allowed a single API call to return:
✔ Purchase Order data
✔ Related Product details
✔ Related Supplier details
in one response.
What I understood today:
Without $expand
→ APIs mostly return IDs/references
With $expand
→ APIs can return connected business context
This is important because real enterprise applications depend heavily on:
relationships between business objects
navigation across data models
reusable master data
connected transactional data
Today’s learning helped me understand how SAP CAP and OData support enterprise-style API modeling rather than only simple CRUD operations.
Learning continues:
SAP BTP | SAP CAP | OData V4 | Enterprise Architecture
#SAP #SAPBTP #CAP #OData #EnterpriseArchitecture SAPDeveloper LearningJourney OperationSelfLearnings

## Stats

- **Views:** 53
- **Likes:** 0
- **Shares:** 0
- **Comments:** 0

## Tags

odata, sapbtp, cap, sap, enterprisearchitecture

---
Copyright (c) Gondola