Written by Zhang — Paddy & Water Inc. / Data & Analytics

Designing and Implementing Business Transformation with a Generative AI Copilot

June 2026

Introduction: The Era When AI Assistants Become “Business Infrastructure”

Generative AI has rapidly permeated the business world since the emergence of ChatGPT in late 2022. However, there is a fundamental difference between “general-purpose AI chat tools” and “AI assistants integrated into business systems.” General-purpose AI can answer a wide range of questions, but it cannot access company-specific data (sales performance, inventory status, HR information) and cannot directly operate business systems.

SAP Joule is the “SAP-native generative AI copilot” that bridges this gap. Its name is derived from the joule, the physical unit of energy, embodying the concept of “accomplishing more work with less energy (fewer operations).” Joule is not merely a chatbot; it is an AI agent that connects directly with real business systems such as SAP S/4HANA, SAP SuccessFactors, SAP Ariba, and SAP Analytics Cloud, executing transaction processing, information retrieval, data analysis, and content generation through natural language instructions.

This article serves as a practical reference for those considering or promoting the adoption of Joule, covering its functional overview, architecture, usage scenarios across SAP products, technical implementation settings, and case studies from other companies.

1. What Is SAP Joule: Four Copilot Capabilities

The Definition of Joule and Its Position in the SAP AI Portfolio

Joule (SAP Joule) is a copilot function embedded across the entire SAP product suite, built on a generative AI service that runs on the SAP Business Technology Platform (BTP). SAP announced it in September 2023 and has continuously expanded the supported products and features since then. As of 2025, Joule is available in major SAP products including SAP S/4HANA Cloud, SAP SuccessFactors, SAP Ariba, SAP Analytics Cloud, and SAP Build Work Zone.

The AI assistance that Joule provides is broadly classified into four categories.

• Transactional: Instructing Joule in natural language to execute ERP transactions. Example: “Approve purchase requisition PUR-2025-0451” or “Check Ichiro Suzuki’s overtime hours for this month.” Joule performs the system operation on the user’s behalf.

• Navigational: Guiding users through complex ERP screens when they “don’t know where to go.” For example, Joule navigates directly in response to requests such as “Open the production order confirmation screen” or “Where is the inventory valuation report?”

• Informational: Answering questions about data, documents, and settings within the system. For example: “What is the current stock of material MM-001?” or “What does this error code mean?”

• Analytical: Instant analysis of business data through integration with SAP Analytics Cloud. For example: “How are sales by region this month?” or “Which product group has the lowest inventory turnover?” Charts and metrics are returned immediately in response to natural language queries.

The Meaning of “Copilot”: Decision-Making Remains with Humans

Joule is, first and foremost, a “copilot,” not an AI that completes business tasks autonomously. Joule offers proposals, provides information, generates drafts, and assists with procedures, but the final execution of transactions and decision-making are confirmed and approved by the user. The design philosophy at the core of SAP’s AI strategy is not “delegating work to AI” but “working together with AI.”

2. Joule’s Architecture: A Generative AI Service on BTP

Technical Foundation: SAP AI Core and LLMs

Joule uses large language models (LLMs) that run on SAP AI Core, an AI infrastructure service on SAP BTP. In addition to its partnership with OpenAI (GPT-4-series models), SAP has partnered with multiple LLM providers such as Anthropic (Claude) and Google (Gemini), and the optimal model is selected depending on the use case. SAP has adopted a multi-LLM strategy to avoid dependence on any single general-purpose LLM.

The reason Joule can deliver business-specific value is that general-purpose LLMs are combined with SAP business context information, the user’s role information, and real-time data from connected systems. This combination is called “SAP Business Context,” and it is precisely what makes Joule’s responses fundamentally different from those of general-purpose AI.

Data Privacy and Security: The AI “Fence”

Data privacy is the aspect enterprises value most when using Joule. SAP has clearly stated the following data protection principles for Joule.

• Customer data is not used for AI training: Data entered by users into Joule and business data referenced by Joule are not used for LLM model training. This is one of the most significant points of differentiation from general-purpose AI services such as OpenAI’s.

• Data remains within the enterprise tenant: When Joule references SAP S/4HANA data, that data is processed within SAP’s tenant boundary. There is no risk of customer data leaking out as training data for another company’s LLM.

• Linked to role-based access control (RBAC): Joule recognizes the user’s system permissions and responds only within the scope of data the user can access and transactions the user can execute. There is no possibility of data the user lacks access rights to being exposed through Joule.

Joule Integration Flow via BTP

Joule is provided as a service on SAP BTP. Enterprises run the “Joule Booster” from the BTP Cockpit, which automates the configuration needed to integrate Joule into SAP products. An overview of the integration architecture is as follows.

• SAP Identity Authentication Service (IAS): Joule uses SAP IAS as its authentication foundation. Through IAS, the enterprise’s single sign-on (SSO) and MFA settings are also applied to Joule.

• Integration with SAP Build Work Zone: Joule is embedded in SAP Build Work Zone (formerly SAP Launchpad Service), allowing the Joule panel to be invoked from any SAP screen within the Fiori launchpad UI.

• Destination configuration: Through the Destination service of the BTP subaccount, Joule is connected to the APIs of each product, such as S/4HANA and SuccessFactors.

3. Using Joule in SAP S/4HANA: Putting ERP Work into Natural Language

Overview of S/4HANA and Joule Integration

In SAP S/4HANA Cloud (public cloud edition), Joule is integrated by default and can be invoked instantly from the Joule icon on the Fiori launchpad. Integration via BTP is also available for the S/4HANA private cloud edition and on-premise edition.

The following outlines Joule usage scenarios in S/4HANA by function.

Use in Finance (FI/CO)

By using Joule, finance staff can process complex inquiries and posting tasks in natural language.

• Accounts receivable inquiries: When asked, “Tell me customer XYZ Corp.’s accounts receivable balance and the date of the last payment,” Joule looks up FI-AR and immediately returns the balance, the last payment date, and the number of open line items.

• Cost center reports: In response to a query such as “What is the variance between actual and planned costs for Manufacturing Department 1 this month?”, Joule provides a summary of cost center actuals equivalent to KSB1.

• Guidance on payment execution: Instructions such as “List accounts payable due today” or “Approve the payment to this vendor” are supported through FI-AP inquiries and payment execution assistance.

Use in Procurement and Inventory (MM)

• Support for creating purchase requisitions: From a natural language input such as “Create a purchase requisition for 10 units of material PC-LAPTOP-001 to the Tokyo plant, with a delivery date of end of July 2026,” Joule automatically fills in the purchase requisition form. The user only needs to check, revise, and submit it.

• Inventory inquiries: Joule instantly answers questions such as “Show me the inventory of material SFG-100 across all plants” or “Which materials are below the safety stock level?”

• Vendor inquiries: A request such as “Show me the five most recent purchase orders from A Shoji Corporation” can be completed with text input alone.

Use in HR (SAP SuccessFactors)

In SAP SuccessFactors (HR and payroll management), Joule offers particularly advanced use cases.

• Recruiting support: With an instruction such as “Draft a job posting for a Marketing Manager. Key skill requirements are digital marketing, data analysis, and team management,” Joule generates a draft job posting. HR staff can edit and review the content and publish it immediately on SuccessFactors.

• Learning and development recommendations: When an employee enters “Recommend training courses that match my career goals,” Joule matches courses within SuccessFactors Learning against the employee’s competencies and career path and recommends them.

• Leave request support: An instruction such as “Apply for paid leave from next Monday to Wednesday” directly enters the request into SuccessFactors Time Off.

• Goal-setting support (Performance): An instruction such as “Create a draft of my goals for this fiscal year based on last year’s achievements” prompts Joule to generate a draft of the goals.

4. Using Joule in SAP Analytics Cloud (SAC): Democratizing Data

How Analytical Insights Works

The integration between SAC and Joule is offered as “Analytical Insights.” When a user types a business question into Joule’s chat window in natural language, Joule references SAC’s data model and generates a real-time answer in the form of charts, figures, and text.

The following are examples of questions that can be used.

• “Show me this month’s sales performance by region as a bar chart” → Regional sales data is instantly retrieved from the SAC data model and a bar chart is generated.

• “Which product group has improved sales the most compared to the same month last year?” → A comparative calculation is performed and the answer is returned in ranked form.

• “Identify product categories where inventory turnover is below the industry average” → Configured KPIs are matched against industry benchmarks and displayed as a list.

To use Analytical Insights, Joule integration must be enabled for the SAC data model. Administrators enable Analytical Insights from the “System → Administration → Joule” settings screen in SAC and configure the scope of SAC data models Joule can access (ACL control).

5. Joule for Consultants: Specialized Functionality for Consultants

What Is Joule for Consultants?

SAP Joule for Consultants is a set of functions that use AI support to help SAP implementation consultants and key users streamline technical SAP configuration, customization, and development work. Unlike Joule for general users (business support), it targets implementation work such as SAP customizing, BTP development, and ABAP extensions.

Key Functions for Consultants

• ABAP development support: In response to an instruction such as “Generate implementation code for a validation BAdI triggered on material change,” Joule generates a draft ABAP OO implementation. It is provided as SAP CLM (Joule in ABAP Development Tools for Eclipse) and is integrated into the ABAP editor.

• Configuration navigation: In response to a question such as “Where is the customizing setting for the price tolerance range for purchase orders?”, Joule guides the user to the relevant SPRO path. This significantly reduces the time needed to locate the exact configuration point within the vast SPRO tree.

• Documentation generation: Joule automatically generates drafts of design documents and test specifications for implemented customizations, reducing the effort required to produce project documentation.

• Error diagnosis: When SAP S/4HANA error messages or short dump (DUMP) information are pasted into Joule, it analyzes the cause and proposes remedies.

6. Joule Integration with Microsoft 365 Copilot

The Convergence of Two Copilots

Based on its strategic partnership with Microsoft, SAP has realized integration between “Joule (SAP’s AI copilot)” and “Microsoft 365 Copilot (Microsoft’s AI copilot).” This makes it possible to invoke Joule’s SAP business functions from Microsoft Teams and Outlook.

Here are some concrete scenarios.

• Creating a purchase requisition from a Teams chat: When a team member sends a message on Teams saying “We need 100 units of item XYZ,” entering “Create a purchase requisition for 100 units of item XYZ-001” into Joule (the Teams add-in) on the spot creates the purchase requisition directly in SAP S/4HANA.

• Handling suppliers from Outlook: While reading an email from a supplier, entering “Check the latest outstanding orders and expected delivery dates for this supplier” into Joule immediately returns the relevant SAP Ariba data.

The Technical Background of the Integration

The Joule–Microsoft 365 integration is achieved through SSO configuration between SAP BTP and Microsoft Azure Active Directory (Entra ID), together with the installation of the Joule plugin as a Microsoft Teams app. Joule’s API is registered as a Microsoft Copilot Plugin, and M365 Copilot automatically invokes the Joule plugin according to the user’s intent.

7. Setting Up Joule: BTP Booster and Onboarding

Prerequisites for Implementation

The following prerequisites are required to integrate Joule into an SAP environment.

• SAP BTP global account and subaccount: Because Joule is provided as a BTP service, the enterprise must have a BTP account.

• SAP Identity Authentication Service (IAS) tenant: Authentication for Joule is managed through IAS. The SAP products in use (S/4HANA Cloud, SuccessFactors, etc.) must be integrated with IAS.

• Unified Global User ID (GUID): It is assumed that the user’s GUID (globally unique ID) is unified across products such as S/4HANA and SuccessFactors. If the user ID differs between products, mapping must be configured in IAS.

• Entitlements for Joule-enabled products: A license agreement is required for the target products (such as S/4HANA Cloud Premium and SuccessFactors Joule integration).

An Example Workflow: Running the Joule Booster

• Log in to the BTP Cockpit (cockpit.btp.cloud.sap) and select the target subaccount.

• Search for and select “Set up SAP Joule” from the “Boosters” menu. The Booster proceeds in a wizard format and automatically provisions the required BTP services (Joule service, SAP Build Work Zone, Destination, etc.).

• After the Booster completes, manually perform the “Post Booster Configurations,” including “configuring the navigation service Destination,” “configuring the CDM content provider,” and “configuring the IAS trust domain.”

• After configuration is complete, confirm that the Joule icon (a lightning-bolt mark) appears in the Fiori launchpad of SAP Build Work Zone. Clicking the icon expands the Joule chat panel.

8. Multilingual Support and Japanese Language Support

Officially Supported Languages

Joule officially supports the following 11 languages: English (US), German, French, Spanish, Portuguese (Brazil), Japanese, Korean, Chinese (Simplified), Vietnamese, Greek, and Polish. Japanese is included among the officially supported languages, so instructions and questions can be given to Joule in Japanese.

The language Joule uses automatically follows the system language setting of the SAP application (the Logon Language user parameter). Japanese-language users will receive responses from Joule in Japanese. In addition, some support is possible in languages outside the official list thanks to the capabilities of the LLM, but such use is not covered by quality assurance.

Implications for Japanese Companies

Being able to use an ERP copilot in Japanese carries important implications for the digitalization of Japanese companies. Overcoming the “English only” barrier of conventional AI tools, and making it possible to give natural business instructions in Japanese such as “Explain this month’s sales variance” or “Execute the payment to this supplier right now,” significantly lowers the difficulty of operating ERP systems and promotes ERP adoption among a broad range of business staff.

9. Case Studies from Other Companies

Case 1: Global Consumer Goods Manufacturer A — Transforming HR Productivity

Background and Challenges

Company A, a global consumer goods manufacturer with employees in 50 countries worldwide, found that its HR business partners (HRBPs) were spending so much time on routine tasks — employment verification, HR data inquiries, arranging training courses, and goal-setting support — that they could not focus on their core strategic work, such as organizational design, talent management, and leadership development.

SuccessFactors Joule Deployment and Results

Company A integrated Joule across all SAP SuccessFactors modules (Core HR, Performance, Learning, and Recruiting). HRBPs shifted to a model in which Joule automatically responds to most employee inquiries (such as “How much paid leave do I have left?” or “Can I use this training course?”). It is reported that the time HRBPs spend handling routine inquiries has been significantly reduced, freeing up time to be devoted to organizational development and career support for high-potential talent.

Case 2: Manufacturer B — Speeding Up Procurement

Background and Challenges

At mid-sized manufacturer B, procurement staff were fielding daily inquiries from department staff unfamiliar with operating SAP Ariba, such as “I don’t know how to create a purchase requisition” or “I want to check the approval status,” which took time away from the company’s core procurement strategy work.

Joule (Ariba Integration) Deployment and Results

Company B integrated Joule into the Ariba purchasing screen, introducing a mechanism that lets end users create purchase requisitions in natural language via Joule. From an input such as “Office supplies: five boxes of A4 paper, needed within one week,” Joule automatically performs item search, catalog selection, quantity entry, and organizational data entry, reducing the user’s task to simply reviewing and submitting. It is reported that inquiries to the procurement department have decreased significantly, creating an environment in which procurement staff can focus on strategic sourcing.

10. Joule’s Roadmap: Evolving Toward Agentic AI

AI Agents: The Shift to Autonomous Task Execution

Since 2024, SAP has clearly stated its direction of evolving Joule from a “copilot” into an “agent” (autonomous agent). Whereas a copilot responds sequentially to a user’s instructions, an AI agent, once given a “goal,” autonomously operates multiple systems and tools to complete the task.

The following next-generation agentic capabilities for SAP Joule have been announced and released.

• Multi-agent collaboration: Beyond Joule alone, specialized AI agents — such as a supply chain optimization agent, a financial error correction agent, and a recruiting candidate screening agent — work in parallel and in coordination to handle complex business tasks.

• Integration with SAP Build Process Automation: Joule invokes RPA and workflow automation (SAP Build Process Automation) to automatically execute multi-step processes that include manual work.

• Collaboration with external agents: Progress is being made toward “multi-vendor agent collaboration,” in which Joule works together via API with AI agents outside of SAP, such as Microsoft Copilot and Salesforce Agentforce.

The Strategic Significance of Adopting Joule

Joule is a means of realizing the democratization of ERP, enabling “anyone, from anywhere, to operate SAP systems in natural language.” This means that all employees can directly leverage the power of ERP regardless of their proficiency with system operations, closing the digital literacy gap. In addition, putting business processes into natural language also serves as the starting point for a data flywheel in which “AI learns from operational logs and continuously provides suggestions for process improvement.” Investment in SAP Joule is an important strategic choice not only for improving operational efficiency today, but also as a step toward the AI agent infrastructure of the future.

End