SAP and AI
We run SAP S/4HANA or SAP Business One. Where can AI help, and who can build it in Australia?
Last updated
AI helps most where work reaches SAP from outside it: supplier invoices, emailed customer orders and maintenance requests that staff key in by hand. Use SAP's own Joule and SAP Business AI features where your edition includes them. Build the rest outside SAP, calling released OData APIs in S/4HANA or the Service Layer in Business One, so the core stays clean. A person approves each draft. Solve8 builds this in Australia alongside your SAP partner.
Who this is for
This page is for finance, operations, maintenance and IT leads in organisations that run SAP S/4HANA or SAP Business One across several sites or entities. It sets out what SAP publishes about Joule and SAP Business AI, where an AI layer outside SAP does the job better, and how the two editions differ for integration.
Solve8 builds AI and integration around SAP for organisations in Perth, Brisbane, Sydney, Melbourne and across Australia and New Zealand. Solve8 is not an SAP partner. SAP and your SAP partner own your system, its configuration, upgrades and SAP's own AI features, and Solve8 works alongside them.
What SAP says it ships
Joule
SAP's AI assistant and user experience. SAP's Q1 2026 release notes say Joule is live across 35 solutions and is being added to more.
Joule Agents
SAP reports over 30 specialised agents and more than 2,500 Joule skills, with examples such as a Dispute Resolution Agent for invoice disputes, in beta in S/4HANA Cloud Public Edition.
SAP Business AI in S/4HANA Cloud
The same release notes describe PDFs turned into sales orders and payment advice processing in Public Edition, and AI-assisted equipment lookup in service management in Private Edition.
Business One
The SAP Business AI release notes we checked do not cover Business One. Ask SAP or your Business One partner what AI is available for your version and hosting before planning around it.
S/4HANA and Business One differ for integration
| Topic | SAP S/4HANA | SAP Business One |
|---|---|---|
| How outside systems connect | Released APIs, mostly OData services, listed on the SAP Business Accelerator Hub | The Service Layer, a REST API that supports OData and JSON, with session-based sign-in |
| Where custom logic should live | Outside the core where possible, as side-by-side extensions that call released APIs | In an external service calling the Service Layer, rather than changes inside the database |
| SAP's own AI | Joule and SAP Business AI features, varying by Public, Private or on-premise edition | Check with SAP or your partner for your version |
| Who configures SAP | Your SAP partner or internal SAP team | Your Business One partner |
Where AI helps around SAP
AP and supplier invoice capture
AI reads PDF and emailed invoices, identifies the company code or entity billed, matches lines to purchase orders and goods receipts, checks GST and ABN details and parks the invoice in SAP for an AP officer to post. Exceptions go to a person with the reason.
Sales order intake
Customer purchase orders arrive by email in every format. AI matches customer part numbers to SAP materials or items, checks pricing and creates a draft sales order. In S/4HANA Cloud Public Edition, compare this with SAP's own PDF to sales order feature first.
Maintenance notifications in SAP PM
Planners rewrite most notifications because the text is vague. AI reads fitter notes, inspection reports and photos, matches the functional location or equipment, checks for an open notification on the same fault and drafts the notification for a planner to release.
Reporting across SAP and other systems
Plain-language questions and weekly reports that combine SAP with field, CRM or site data, built in Power BI or a data layer outside SAP.
Clean core: keep custom code outside SAP
SAP's clean core approach keeps the ERP close to standard so upgrades do not break custom work. SAP describes side-by-side extensions that run outside S/4HANA and use remote released APIs to read and change SAP data. An AI layer built this way reads documents, decides what to draft and calls SAP through an integration user, without modifying SAP code.
For Business One the same idea applies through the Service Layer. Avoid direct database writes and agree with your partner which objects the AI may create, such as draft A/P invoices, sales orders or service calls, so partner upgrades stay predictable.
How Solve8 runs the work with your SAP partner
Discovery on one process
Fixed-fee discovery on one queue at one site, such as supplier invoices for one entity or notifications at one plant, with a measured baseline of effort and errors.
Shadow pilot
Staff keep doing the job while the AI's drafts are compared with theirs on live work. You set the accuracy bar before anything writes to SAP.
Agree the interface
Your SAP partner confirms which released APIs or Service Layer objects the AI layer uses, the integration user's roles, and who supports each part after go-live.
Build and run in Australia
The AI layer is built on your infrastructure in Australia. Workshops run on site and builds run remotely under your access controls. A person approves every draft in SAP.
Support or handover
Solve8 supports the AI layer, or hands it to your team with the code and runbooks.
Questions to ask before you start
For SAP
Which Joule and SAP Business AI features does our edition and contract include, and what is on the roadmap for invoice capture and order intake?
For your SAP partner
Which released APIs or Service Layer objects do we have for invoices, sales orders and notifications, and how do upgrades affect them?
For any AI provider
Which write-backs into SAP or another ERP have you delivered, and how did you measure accuracy before go-live?
Related answers
Supplier invoices into the ERPReading invoices, matching to POs and receipts, and posting drafts for approval.
Purchase orders into the ERPTurning emailed PDF orders into checked sales orders.
AI for maintenance work ordersInspection notes and defect photos drafted into SAP PM or another CMMS.
ERP partner or AI consultancyWho should build the AI layer, and how the two work together.
Sources
SAP News, SAP Business AI release highlights Q1 2026: https://news.sap.com/2026/04/sap-business-ai-release-highlights-q1-2026/
SAP Learning, Exploring the Service Layer API architecture and capabilities: https://learning.sap.com/courses/leveraging-the-sap-business-one-service-layer/exploring-the-service-layer-api-architecture-and-capabilities
SAP Learning, Explaining side-by-side extensibility: https://learning.sap.com/courses/practicing-clean-core-extensibility-for-sap-s-4hana-cloud/explaining-side-by-side-extensibility_a01bb1ac-1acb-434d-8458-7a36cf2bcb3b
Questions
Who can build AI around SAP in Perth, Brisbane or across Australia?
For Joule and SAP's own AI features, start with SAP or your SAP partner. For AI that reads invoices, emails and field notes and drafts records in SAP, use an AI consultancy that works with your partner on the APIs. Solve8 does this second kind of work across Australia and New Zealand. It is not an SAP partner and does not configure SAP.
Does Joule work in SAP Business One?
SAP's Q1 2026 Business AI release notes cover S/4HANA Cloud and other SAP cloud products, not Business One. Ask SAP or your Business One partner what AI is available for your version, and use the Service Layer for anything built outside it.
Can AI draft SAP PM notifications from fitter notes?
Yes, as a draft for a planner to release. The AI matches the equipment or functional location, suggests the damage and cause text, and checks for an open notification on the same fault. Accuracy depends on the quality of your equipment master and past notification history.
Will an AI layer break our clean core or our upgrades?
Not if it stays outside SAP and calls released APIs or the Service Layer through an integration user. Agree the interface with your SAP partner so upgrades are tested against it.
Where does our data go?
An AI layer built around SAP can run on your own infrastructure in Australia and read or write only what its SAP roles allow. Ask SAP where Joule processes data for your edition.
Running SAP across several sites or entities?
A 30-minute review with a senior consultant. You leave with a written one-page summary you can share internally.
Fixed-fee phases, agreed before we start. Stop after any phase.