SAP ABAP ADT development
Session
- Auth file:
.secrets/btp-abap.env(create withnpm run btp:auth; service key path is configured inpackage.json). - MCP server:
abap-adtin.cursor/mcp.jsonwith--exposition=readonly,high. - Reload Cursor after MCP or auth changes.
Where changes go
- Steampunk system: use
abap-adtMCP for ADT read, create, update, lock, unlock, validate, activate, and transport tools exposed by the server. - Workspace mirror:
btp-content/abap/<PACKAGE>/is a read-only snapshot until refreshed. - Git: tracks the mirror and tooling only. It is not the ABAP source of truth.
Develop and push workflow
- Confirm the target package and object (for example
ZZSD/ZCL_QAD_QUERYSHIPMENT_SVC). - Use MCP to read the live object before editing when the mirror may be stale.
- Lock, change, check, activate, and unlock through ADT MCP on the system.
- Refresh the mirror:
npm run btp:sync-package -- <PACKAGE>. - Commit mirror updates only when the user asks.
Safety
- Do not commit
.secrets/, service keys, or.envfiles with tokens. - Do not enable
lowexposition unless the user explicitly requests it. - Prefer small, reviewable ADT changes over bulk rewrites.