Perspectives from the field.

The content track follows where buyers actually need clarity, not where marketing keywords are densest. Recurring topics include SAP Sapphire 2026 takeaways (Joule Studio 2.0, the Autonomous Enterprise, A2A and MCP), AI agent architectures for SAP (the five-layer pattern, governance and auditing as architecture, the Company Intelligence Layer), S/4HANA migration patterns (ECC end-of-support, RISE vs GROW selection, brownfield/bluefield/greenfield trade-offs), BTP delivery (clean-core extensions, Integration Suite, PI/PO migration), master data and data quality, programme rescue patterns (the seven failure modes documented in the Rescue Playbook), and the partnership stack (SAP + Google Cloud, Anthropic Claude). Articles aim to be field-grade — practical guidance an SAP architect or programme leader can act on — not vendor positioning.

Engineers. Bylines belong to DEBCOR's senior architects and the firm's founder, Gareth de Bruyn — the same people who run client engagements. Gareth co-authored the first ABAP textbook ever published (Introduction to ABAP/4 Programming for SAP, Prima Publishing, 1996) and is the author or co-author of 13 SAP technical books in total. The Chief Architect holds every SAP architect-tier certification SAP currently offers (Enterprise Architect, Solution Architect BTP, Data Architect BDC, LeanIX) plus the SAP Generative AI Developer credential. The standard for an Insights article is that the writer has built whatever they are writing about — not described it second-hand from a vendor briefing.

Roughly weekly, with two patterns. First, ongoing analysis — Sapphire 2026 commentary, Joule Studio 2.0 deep dives, AI on SAP architecture posts, ECC end-of-support guidance — published as the underlying material warrants it (when SAP changes a product roadmap, when a new pattern lands in client engagements, when a buyer question recurs enough times to be worth answering once in writing). Second, the field-note posts — short, specific lessons from active engagements, posted as they surface. The pace is set by whether there is something worth saying, not by a content calendar.

The books are reference works — Introduction to ABAP/4 Programming for SAP (Prima, 1996, the first ABAP textbook ever published), Implementing SAP Solutions on Cloud, ABAP Performance Tuning, and ten others authored or co-authored by Gareth de Bruyn — written for engineers learning the discipline. Three more SAP books are forthcoming in 2026. The Insights articles are shorter, more current, and field-driven: a book chapter takes a year to update; an Insights post can address a roadmap change SAP announced last month. Together they cover the same intellectual territory but at different depths and cadences. The books page (debcor.com/about/published-works) lists the full catalogue with ISBNs and publishers.

Yes. The newsletter is the primary subscription channel — short, weekly, links to the most-substantive recent posts plus the occasional standalone piece written for subscribers. LinkedIn carries the article posts as they publish; the DEBCOR LinkedIn page is the right follow for direct distribution. For research-grade content (gated white papers and the Rescue Playbook), the Resources section on the homepage delivers PDFs in exchange for an email. The standard across all channels: no sales sequences disguised as newsletters — if a piece is sponsored or commercial, it says so on the page.

S/4HANA (Cloud Public Edition / GROW, Cloud Private Edition / RISE, and on-premise), ECC (with a documented end-of-support transition focus through 2027), SAP BTP (Cloud Foundry, Kyma, Integration Suite, Build Code, Build Apps, the Generative AI Hub, AI Core, Joule and Joule Studio 2.0), SAP Business Data Cloud, the SAP Knowledge Graph, SAP Datasphere, Ariba and SuccessFactors integration patterns, and the partner ecosystem (Anthropic Claude on SAP, Google Gemini on BTP via the partnership, OpenAI and other foundation model access). Older platform coverage (PI/PO, classic ECC custom code patterns) appears specifically in the context of migration content — what to do with it, not how to extend it.