{"ref":"content:patterns-for-using-llms-in-abap-development","page":"/content/patterns-for-using-llms-in-abap-development","json":"/content/patterns-for-using-llms-in-abap-development.json","generated":"2026-10-26","drafted_with_ai":true,"entity":{"id":"patterns-for-using-llms-in-abap-development","title":"Patterns for using LLMs in ABAP development","url":"https://docs.heliconialabs.com/patterns-for-using-llms-in-abap-development.pdf","content_type":"doc","published_on":"source:heliconia-labs","authors":["actor:larshp"],"drafted_with_ai":true,"offers":["concepts","reference"],"summary":"[Lars Hvam](actor:larshp) compares eight ABAP development setups: assistance in SE80 or Eclipse, virtual files and MCP over ADT, a centrally managed MCP service, sandboxes, local Git, Git with read-only system context, and temporary ABAP systems for development and CI. The overview describes where source changes, review and system access happen, including [abapGit](artifact:abapgit-abapgit) synchronization and [abaplint](artifact:abaplint-abaplint) checks. It is dated March 2026; its risk, cost and autonomy ratings are the writer’s assessments.","short":"Eight setups for using LLMs in ABAP development","explains":[{"ref":"capability:agent-code-access","what_it_covers":"Compares file-based and MCP access to ABAP source, distinguishing system writes from local editing and read-only context.","applies_to":{"ecosystems":["abap"]}},{"ref":"capability:abap-source-control","what_it_covers":"Describes ABAP source in Git repositories and abapGit synchronising changes into a central or temporary SAP system."},{"ref":"capability:abap-static-analysis","what_it_covers":"Places abaplint and CI checks in the local Git feedback loop before changes reach the central system."},{"ref":"capability:abap-code-review","what_it_covers":"Describes pull requests and human review as gates between local agent changes and the main ABAP system."},{"ref":"artifact:arc-mcp-arc-1","what_it_covers":"Places ARC-1 in two setups: a centrally hosted MCP service and read-only system context alongside local Git editing."},{"ref":"artifact:abapgit-abapgit","what_it_covers":"Uses abapGit for synchronising Git-held source into the SAP system in the off-stack patterns."},{"ref":"artifact:abaplint-abaplint","what_it_covers":"Names abaplint for static checks that feed results back to the coding agent."}],"sources":[{"url":"https://raw.githubusercontent.com/heliconialabs/patterns-for-using-llms-in-abap-development/main/src/index.adoc","title":"Heliconia Labs — document source","checked":"2026-10-15","quote":"Lars Hvam, Heliconia Labs, March 2026"},{"url":"https://docs.heliconialabs.com/patterns-for-using-llms-in-abap-development.pdf","title":"Patterns for using LLMs in ABAP development — PDF, March 2026","checked":"2026-10-15"},{"url":"https://github.com/heliconialabs/patterns-for-using-llms-in-abap-development","title":"Heliconia Labs — source repository and CC BY 4.0 licence","checked":"2026-10-15"}],"provenance":{"discovered_via":[{"source":"source:curator"}],"first_seen":"2026-10-15"},"history":[{"date":"2026-10-17","field":"explains","from":null,"to":"applies_to on capability:agent-code-access","reason":"Door scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md)."}]},"readings":{"liveness":[{"label":"Checked against the source","tier":"unknown","evidence":"nobody has checked it"},{"label":"Source reachable","tier":"unknown","evidence":"not crawled"},{"label":"Age","tier":"unknown","evidence":"no publication date"}],"compatibility":[{"label":"Version","tier":"unknown","evidence":"no version declared"},{"label":"Moved since?","tier":"unknown","evidence":"no publication date to compare"},{"label":"Findings","tier":"good","evidence":"none flagged"}],"reach":[{"value":null,"unit":"views"},{"value":null,"unit":"comments"},{"value":null,"unit":"likes"}]},"signals":null,"series":null,"edges":{"authors":[{"ref":"actor:larshp","name":"Lars Hvam","json":"/actors/larshp.json"}]}}