ABAP4C Cloud Deployment Pipeline — Architecture 2: Capella

Prototype evidence or graceful placeholder

If an approved prototype image is unavailable, the PAL placeholder is shown deliberately instead of a broken-image icon.

Who it serves and what it addresses

AI or Coding Agent → VS Code / Cline / Python → Capella Control Plane → Local Eclipse Bridge → ADT / RIS / DDIC execution → SAP ABAP Cloud → receipts, evidence and rollback controls.

Intended users

SAP architects, platform owners, governed-delivery teams and automation engineers needing evidence-first ABAP Cloud deployment controls

Data dependencies

Approved Eclipse workspace session, ADT repository discovery, RIS search, DDIC update evidence, stateful session evidence, receipts and rollback references.

Last reviewed

2026-07-27

Maturity

Independent engineering prototype with bounded live execution evidence

Verified architecture vocabulary

• AI coding agent
• Cline
• VS Code
• Python
• Capella orchestration
• policy and governance controls
• local Eclipse bridge
• authenticated Eclipse workspace
• ADT repository discovery
• RIS search
• DDIC update
• stateful session handling
• controlled retry
• evidence receipts
• rollback references
• SAP ABAP Cloud

How the capability connects

Agent Hub: Represents the governed-bridge route for ABAP Cloud deployment when policy, recovery and receipts matter.

Engineering Control Center: Capella-style execution is governed through explicit lifecycle, validation, approval, execution receipts and rollback references.

Architecture 2 of the ABAP4C Cloud Deployment Pipeline capability: a Capella governed bridge with orchestration, policy controls, local Eclipse bridge, authenticated workspace, ADT repository discovery, RIS search, DDIC update, session handling, controlled retry, receipts and rollback references.

Control and confidentiality boundaries

Live-verified and unverified object types are separated. Controlled retry and recovery are bounded by evidence receipts and human approval gates.

Public description excludes credentials, tenant details, local bridge secrets, private repository data and unrestricted SAP system evidence.

Publication boundary

Architecture-level description with bounded live-execution evidence language.

Source availability

Selected public architecture material may be released separately

Future direction

Improve target-system variation handling and recovery evidence without claiming universal superiority over Architecture 1.

Product ↔ Publication ↔ LinkedIn ↔ YouTube