sap-cap-capire

Run cds init with your project name, optionally adding features like sample, hana, or xsuaa. Then use cds watch to start a development server with live reload and cds add to enable additional capabilities later.

Define entities in db/schema.cds using built-in types like UUID, String, and Decimal, with managed associations letting CAP auto-generate foreign keys. Use aspects like cuid and managed from @sap/cds/common for standard key and audit fields.

Yes, CAP supports SQLite for local development, PostgreSQL, and H2 in addition to SAP HANA for production. Configure the database kind per profile in package.json and deploy schema with cds deploy --to hana.

Add deployment support with cds add hana,xsuaa,mta,approuter, then build the MTA archive with mbt build and deploy using cf deploy. The mta.yaml descriptor defines service modules, HDI containers, and XSUAA resources.

Authorization issues usually stem from incorrect @requires or @restrict annotations, missing XSUAA bindings, or unmapped role templates in xs-security.json. Verify scope names match and check user role collections in the BTP cockpit.

The @cap-js/mcp-server provides search_model for fuzzy searching compiled CSN entities and services, and search_docs for semantic CAP documentation queries. It runs locally without credentials and integrates with AI coding assistants.