A Note Up Front: SAP CAP Is a Preview Stack
SAP CAP (Cloud Application Programming Model) is a preview stack in Archiet. Generated CAP projects ship with a PREVIEW banner and are intended as a strong, reviewed scaffold for a SAP developer — not a zero-touch production deploy. SAP BTP environments vary enough that we will not claim a hands-off deploy we cannot guarantee. Use the output as a starting project, run it through cds watch, and adjust before deploying to BTP.
Here is what you get and how to run it.
What You Will Build
A SAP CAP project for a business process, generated from a paragraph:
- CDS (Core Data Services) entity definitions in the data model
- OData V4 services exposing those entities
- A project structure ready for
cds watch(local) andcds deploy(BTP) - Sample data for local development
Prerequisites
- An Archiet account (free at archiet.com/register)
- Node.js and the SAP CAP toolkit (
@sap/cds-dk) - 15 minutes
Step 1: Write a Minimal PRD
ServiceParts runs on SAP BTP for a manufacturer. Planners manage parts
(number, description, stock level) and orders (part, quantity, status). We
need an OData service for parts and orders so a Fiori frontend can consume
them.Archiet maps these to CDS entities (Parts, Orders) and an OData service definition.
Step 2: Open the Blueprint Wizard
Log in at archiet.com/login, click New Blueprint, paste the PRD, click Analyse, review the model.
Step 3: Choose SAP CAP
On the Generate screen, select SAP CAP (marked Preview) and click Generate.
Step 4: What You Get
service-parts/
├── db/
│ ├── schema.cds # CDS entity definitions
│ └── data/ # sample CSV data
├── srv/
│ └── service.cds # OData service definition
├── package.json
└── README.md (with the PREVIEW notice)The CDS data model and service are idiomatic CAP:
// db/schema.cds
namespace serviceparts;
entity Parts {
key ID : UUID;
number : String(40);
description : String(255);
stockLevel : Integer;
}
entity Orders {
key ID : UUID;
part : Association to Parts;
quantity : Integer;
status : String(20);
}// srv/service.cds
using serviceparts from '../db/schema';
service PartsService {
entity Parts as projection on serviceparts.Parts;
entity Orders as projection on serviceparts.Orders;
}CAP turns these definitions into a running OData V4 service with full CRUD — no controller code required.
Step 5: Run It Locally
cd service-parts
npm install
cds watchcds watch starts a local server with the OData service and an in-memory database seeded from the sample CSVs. Open the service URL it prints to browse the OData metadata document and query the entities.
When you are ready for BTP:
cds deployReview the project, confirm it matches your BTP environment's expectations, and adjust before deploying.
What to Do Next
Treat it as a reviewed scaffold: this is preview output. Confirm the CDS model and service projections match your data and authorisation needs before BTP deployment.
Add a Fiori frontend: the OData service is consumable by SAP Fiori elements or a custom UI5 app.
We will promote CAP from preview to stable once it clears the same deploy bar as the stable stacks. The PREVIEW banner is your signal to review before you ship.