Abstract
"Delivering SAP with IBM Bob" is a practical guide for IBM consultants, SAP practitioners, and enterprise architects on using IBM Bob — IBM's AI-native engineering assistant — to accelerate and govern SAP development across S/4HANA, SAP BTP, SAP Integration Suite, and ECC landscapes.
The document covers the full delivery lifecycle: the case for AI-assisted SAP development and a comparison with SAP Joule; connectivity approaches for ABAP, BTP UI5/CAP, and CPI via MCP servers and IDE extensions; the operational governance model (Modes, Rules, Skills, and Clean Core enforcement); hands-on code generation across ABAP, UI5, CAP, and Groovy; enterprise integrations with ServiceNow, GitHub/CI-CD, Tricentis Tosca, Signavio, and LeanIX; environment setup with a Crawl–Walk–Run adoption roadmap; and a governance and scaling framework with a 30–60–90 day action plan for moving from individual productivity to enterprise-scale, auditable AI-assisted delivery.
Authors
Dharma Atluri, Tuhin Bhaduri, Shubhangi Joshi, Phillip Gerrard, Meher Charan Vangipurapu and Mohammad Zubair
- Introduction
- Using IBM Bob for SAP
- Connecting IBM Bob to SAP
- Working with IBM Bob
- Development with IBM Bob
- Integrations and Operation
- Hands-on environment setup for governed SAP development with IBM Bob
- Governance and scale
- Abbreviations
- Additional Resources
- Appendix: Program example zdownload_abap_object.abap
- Notices
- Trademarks
- Notice on content examples
- AI Attribution
- Version History
Notices
This information was developed for products and services offered in the US. This material might be available from IBM® in other languages. However, you may be required to own a copy of the product or product version in that language in order to access it.
IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing IBM Corporation North Castle Drive, MD-NC119 Armonk, NY 10504-1785 United States of America
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.
Any references in this information to non-IBM websites are provided for convenience only and do not in any manner serve as an endorsement of those websites. The materials at those websites are not part of the materials for this IBM product and use of those websites is at your own risk.
IBM may use or distribute any of the information you provide in any way it believes appropriate without incurring any obligation to you.
Trademarks
The following terms are trademarks of the International Business Machines Corp.
-
IBM, the IBM logo, and IBM Bob are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both.
-
SAP, SAP S/4HANA, SAP ECC, SAP BTP, ABAP, SAP NetWeaver, and other SAP products and services mentioned herein are trademarks or registered trademarks of SAP SE in Germany and other countries.
-
Other company, product, or service names may be trademarks or service marks of their respective owners. Mention of third-party products, community extensions, or open-source utilities (such as abapGit) is for reference and informational purposes only and does not imply direct endorsement or ongoing vendor warranty.
Notice on content examples
Purpose of Examples and Illustrative Content
All examples, walkthroughs, demonstration scenarios, code snippets (including ABAP, JSON, XML, shell scripts, and configuration files), architectural diagrams, and integration patterns presented in this book are provided solely for demonstration and educational purposes.
-
Not Released or Production-Grade Product Code: The code samples and scripts contained herein do not constitute officially released, commercially warranted, or production-ready software deliverables from IBM, SAP SE, or any other technology vendor.
-
User Responsibility and Due Diligence: Any adoption, reproduction, adaptation, or execution of the code snippets, configuration scripts, or integration logic provided in this document is done entirely at your own discretion and risk. Organizations and individual practitioners must thoroughly evaluate, test, adapt, and validate all logic in accordance with their enterprise standards, security policies, transport procedures, and governance frameworks before deploying to non-production or production environments.
Anonymized Systems, Hostnames, and Identifiers
All system identifiers, application IDs, server hostnames, IP addresses, endpoint URLs, user accounts, organization names, and transport numbers referenced throughout this book are entirely fictional and illustrative.
-
Any resemblance to actual live systems, internal enterprise networks, or active environments is purely coincidental.
-
This publication does not provide or grant credentials, licenses, or access rights to any IBM, SAP, GitHub, or third-party infrastructure.
-
To establish connections or acquire access to specific enterprise environments, repositories, or API endpoints, users and project teams must follow their organization's standard procurement, security, and administrative access-request procedures through the appropriate authorized owners.
Custom MCP Servers and Architectural Patterns
The custom Model Context Protocol (MCP) servers, connector wrappers, and middleware patterns demonstrated across the publication serve as conceptual communication blueprints designed to illustrate how AI assistants interact with enterprise backends.
-
They are intended to build technical understanding and demonstrate possibility.
-
When designing and implementing actual enterprise-grade integrations, architects and developers should apply the architectural concepts and principles discussed here while engineering solutions that adhere to their enterprise security baselines, network isolation boundaries, encryption standards, and maintenance requirements.
Point-in-Time Technical Validity and Software Evolution
The technical guidance, configuration parameters, API references, code syntax, and IBM Bob capabilities documented in this book reflect the software state, feature sets, and best practices available at the time of writing.
-
Version Context: The demonstrations and walkthroughs in this publication were developed, tested, and validated using IBM Bob Version 2.0.5.
-
Evolving Tooling: Software features, user interfaces, CLI commands, extensions, API endpoints, and platform capabilities evolve continuously across release cycles for IBM Bob, SAP S/4HANA, SAP BTP, Visual Studio Code, Git platforms, and open-source utilities like abapGit.
-
Readers and implementation teams are strongly advised to consult the latest official product documentation, release notes, and vendor support channels to confirm current syntax, supported release levels, and compatibility requirements during real-world implementations.
AI Attribution
This IBM Redbooks publication was produced with the selective assistance of three AI tools: Claude Code, IBM Bob, and ICA Edge (IBM Consulting Advantage Edge). These tools were engaged for specific, bounded tasks — not for the creation of original ideas or technical content. Claude Code was used to reconcile chapter text across multiple draft sources and to apply IBM Redbook formatting conventions including headings, callout boxes, and layout structure. IBM Bob assisted with reviewing SAP-specific and industry terminology and formatting code blocks for consistency. ICA Edge was used to create and format architectural diagrams and workflow visuals used in the book. All AI-generated or AI-assisted output was reviewed, approved, and verified by the co-authors before inclusion. The ideas, architecture patterns, demonstration code, and technical conclusions expressed in this book are entirely the author's own, drawn from real-world IBM consulting and implementation experience (with few client feedback inclusion). There are certain limits in terms of connectivity along with domain experience, for which premium package work is in progress. AI tools served as a formatting and production layer only — not as a source of substance, analysis, or judgment.
The content, demo code, and concepts in this Redbook are written solely by the author. AI tools were used only for reconciliation, formatting, and diagram creation tasks. AI was used to make stylistic edits, such as changes to structure, wording, and clarity. AI was used to make content edits, such as changes to scope, information, and ideas. AI was prompted for its contributions, or AI assistance was enabled. AI-generated content was reviewed and approved.
The use of AI tools in producing this Redbook is intentional and transparent. The book is written on "Delivering SAP with IBM Bob" which is itself subject of this book — using it as part of the authoring process reflects the author's confidence in their production readiness for senior IBM practitioners.