Capabilities for SAP Joule, built for the people who will use them. Purchasers, accountants, planners and sales teams ask in plain language, and Joule answers from SAP’s own standard APIs, within each user’s SAP authorizations.
Capability map
Joule in the middle, the business areas around it and the personas in each area. Open an area to see the capabilities each of its personas gets in Joule.
2 personas · 5 capabilities
Purchaser
Procurement Manager
3 personas · 6 capabilities
Accounts Payable Accountant
Accounts Receivable Accountant
General Ledger Accountant
2 personas · 5 capabilities
Sales Representative
Billing Specialist
3 personas · 6 capabilities
Inventory Manager
Production Planner
Shipping Specialist
2 personas · 3 capabilities
Maintenance Planner
Maintenance Technician
Personas
Pick a business area to see its personas, what they ask Joule and the standard SAP APIs behind the answers. Every capability is built on released APIs from SAP Business Accelerator Hub.
Easy to deploy
You get every capability as source files in YAML format, ready to import into SAP Joule Studio (classic) or to deploy directly with the Joule Studio CLI. Create one SAP BTP destination to your SAP S/4HANA system, and your people can ask.
The complete capability as YAML: capability, scenarios, dialog functions, agent and texts. Yours to review, keep in Git and change.
It points Joule to your SAP S/4HANA system. Every capability calls SAP through it, so this is the only connection to set up.
Import into SAP Joule Studio (classic), or deploy directly with the Joule Studio CLI. Boidra Platform can run it with CI/CD.
The capability is there for every user whose SAP roles allow it. No change in SAP S/4HANA.
joule/
├── da.sapdas.yaml
└── capabilities/
└── operational_purchasing/
├── capability.sapdas.yaml
├── capability_context.yaml
├── scenarios/
│ ├── get_purchase_order.yaml
│ ├── get_purchase_order_items.yaml
│ └── search_purchase_orders.yaml
├── functions/
│ ├── get_purchase_order.yaml
│ ├── get_purchase_order_items.yaml
│ └── search_purchase_orders.yaml
├── agents/
│ └── PurchaserAgent.yaml
└── i18n/
└── messages.propertiesAn example: the URL is your system’s API host, and the name is the one the capability refers to.
Your SAP applications
Reports, SAP Fiori apps and your own SAPUI5 applications become reachable from Joule. People ask for what they need; Joule runs the report or opens the app in the right context.
“Run the open purchase orders report for plant 1010”
Joule runs the report and shows the result in the chat: no transaction, no selection screen.
“Open Manage Purchase Orders for supplier 100001”
Joule opens the right app on the right object, with the filters already set.
“Open our returns approval app for order 1234567”
Custom SAPUI5 applications become reachable from Joule, with their own context.
Custom capabilities
Not on this page? We build custom Joule capabilities for any business area and any persona: on standard APIs from SAP Business Accelerator Hub first, and on your own OData services or CDS views where your process needs them.
Custom Joule Agents and CapabilitiesAny persona
From a purchaser to a plant manager: the capability follows the job.
Standard first
Released SAP APIs wherever they exist; custom services only where needed.
Code-based Joule
Scenarios, dialog functions and agents in Git: reviewed, tested, repeatable.
Run with Boidra Platform
CI/CD, deployment to SAP BTP and Joule, traces and cost per request.
Joule capabilities pair with agents that do longer work, such as our SAP Operation Monitoring Assistant, and everything is run through Boidra Platform.
The capabilities shown here use the standard APIs of SAP S/4HANA Cloud Public Edition, as published on SAP Business Accelerator Hub. For SAP S/4HANA Cloud Private Edition or on-premise, we check which of the same APIs your release offers.
Yes. We build any custom Joule capability: for any business area and persona, on standard APIs first, and on your own OData services or CDS views where your process needs them.
Yes. We bring existing SAP applications into Joule: a user asks, and Joule runs the report and shows the result in the chat, or opens the right SAP Fiori or SAPUI5 app on the right object.
Yes. Every capability is ready to import into SAP Joule Studio (classic) or to deploy directly with the Joule Studio CLI, SAP’s pro-code tool to build, compile and deploy Joule capabilities. The capability, scenarios, dialog functions and, where a question needs several steps, an agent are kept as code in Git: reviewable, testable and repeatable across landscapes.
You receive the source files in YAML format and create one SAP BTP destination to your SAP S/4HANA system. Then you import the capability into SAP Joule Studio (classic) or deploy it directly with the Joule Studio CLI, or Boidra Platform deploys it. Nothing is installed in SAP S/4HANA.
Only where you want it to. Enquiry skills only read. Skills that create or change documents ask for confirmation, and approvals or postings are given only to the personas whose job includes them.
SAP decides. Joule reaches SAP through your SAP BTP destination; with principal propagation it calls the APIs as the user, so each person sees what their SAP roles allow. The personas describe the work; your roles stay as they are.
Tell us what you’re trying to automate in SAP. We’ll tell you - honestly - whether an agent is the right tool, and how we’d start.