SAP S/4HANA
SAP S/4HANA is where a large organisation keeps the truth about its own operations — what was ordered, what was delivered, what was invoiced, what is still owed and what is sitting in a warehouse. Connecting an assistant to it means customers and staff stop asking people to look things up in it.
SAP S/4HANA is where a large organisation keeps the truth about its own operations — what was ordered, what was delivered, what was invoiced, what is still owed and what is sitting in a warehouse. Connecting an assistant to it means customers and staff stop asking people to look things up in it.
What SAP S/4HANA holds, and why that matters here
S/4HANA is the operational core of many large Saudi enterprises: manufacturing, distribution, utilities, large retail groups and much of the public sector supply chain. It is the record of what physically and financially happened, which makes it the single most valuable thing an assistant can be pointed at — and the one most carefully guarded.
The reason it generates so much contact is that the information inside it is exactly what people ask about, and almost nobody outside the business has direct access to it. Every "where is my order" and "has that invoice been paid" is a question whose answer already exists in S/4HANA and is currently being retrieved by a person on the asker's behalf.
- Sales and delivery — orders, line items, delivery notes, shipment status, backorders.
- Finance — invoices, payment status, credit position, open items, dunning state.
- Materials — stock on hand, stock by location, availability dates, reservations.
- Procurement — purchase requisitions and orders, goods receipts, supplier confirmations.
- Master data — customers, vendors, materials, pricing conditions and terms.
Questions Elbi can answer from SAP S/4HANA
Where is my order?
Order status, the delivery note it sits on, and the expected date — answered from the live record rather than an estimate, and phrased as a sentence rather than a status code.
Is this in stock?
Availability by item and by location, including whether the quantity asked for can actually be met and when the next inbound arrives if it cannot.
Has our invoice been paid?
Open items and payment state for a given account, so finance teams stop fielding the same call at month end.
What is our credit position?
Available credit and blocked-order state, which is the real reason many orders stall and the thing customers are rarely told without asking.
When will the purchase order arrive?
Goods receipt status and supplier confirmation dates for internal users chasing procurement.
What did we agree on price?
The pricing condition that applies to this customer for this material, rather than list price — the single most common cause of disputed invoices.
How Elbi reads SAP S/4HANA
- Released APIs, not screens or tablesS/4HANA exposes its business objects — sales orders, deliveries, billing documents, purchase orders, business partners — through OData APIs documented on the SAP Business Accelerator Hub. The assistant reads through the APIs your team releases to it, which keeps the connection on interfaces SAP maintains from one upgrade to the next.
- A technical user with a display-only roleOn premise or in a private cloud, your security team creates a technical user and a role for it in the usual way. In S/4HANA Cloud the same job is done with a communication arrangement and a communication user. Either way, the role is restricted to display and to the organisational levels in scope — a sales organisation, a company code, a set of plants.
- Through your middleware, if you have itMany S/4HANA landscapes route every integration through SAP Integration Suite or another middleware layer. Where yours does, that is usually the right path for the assistant's reads too, so your integration team monitors it alongside everything else.
- Each question maps to a document chain"Where is my order" becomes the sales order, its outbound delivery, goods issue and billing document. "Has our invoice been paid" becomes the open and cleared items on the customer's account. The asker is identified through your own sign-in and matched to a business partner number before anything is read.
- Credit blocks are explained, not exposedWhen an order is held by credit management, the customer is told that it is on hold and who can help — not the credit limit or the risk class behind it. The wording for that case is agreed with your credit team before launch.
- Posting stays with people unless you decide otherwiseReading is the default. If you want the assistant to create something — a customer enquiry, a service request — it is enabled per action through the relevant API and can be held for a person to confirm before it is saved.
Roles, organisational levels and what stays yours
| Direction of access | Display authorisations only, by default. Any create or change operation is a separate decision, taken per API and per action, and can wait for human confirmation. |
|---|---|
| Who can see what | The technical user's role is limited by organisational level, so an assistant scoped to one sales organisation cannot read another's orders. Customers and suppliers see only documents under their own business partner number; employees see what their own role would show them. |
| Credentials | The technical or communication user is created and held by your team. Locking it, or revoking its credentials, stops every read at once and needs nothing from us. |
| Where data goes | Order, invoice and credit details read from S/4HANA serve the one reply they were fetched for. Messages are destroyed within 24 hours, in most cases the moment the conversation closes, and no external AI service is involved at any point. |
| Audit | Every read can be logged with the question, the document returned, the agent and the conversation, which gives your SAP security team something concrete to review alongside their own logs. |
| If it is unavailable | During a maintenance window, or whenever the service cannot be reached, the assistant says it cannot get to SAP and offers a person, rather than repeating the last figure it saw. |
What this replaces in an S/4HANA organisation
The pattern in most organisations is the same. A customer asks a question. A call-centre agent cannot see S/4HANA, so they raise an internal request. Someone in customer service or finance who does have access looks it up, replies, and the agent relays the answer. The round trip is measured in hours or days, for a fact that was available in milliseconds.
Connecting the assistant collapses that. The lookup happens while the customer is still in the conversation. The internal request is never created. The person who would have done the lookup keeps their afternoon, and the customer stops phoning to chase the chase.
The second thing it removes is the screenshot habit. Where staff cannot get answers quickly, they build private workarounds — exported spreadsheets, screenshots in chat groups, personal notes of who to ask. Those copies are stale the moment they are made and are a genuine data protection problem. An assistant that answers reliably removes the reason they exist.
How S/4HANA organisations in different sectors use it
Manufacturing
Production order status, material availability, and delivery commitments — asked by sales staff who need an answer while the customer is on the line.
Distribution
Stock by location and lead times, which is the entire conversation in wholesale and the reason quotes go stale.
Public sector supply
Purchase order and goods receipt status for suppliers chasing payment, which is high-volume, low-value contact that nobody wants to staff.
Utilities
Connection and works order status, where the customer wants a date and the record has one.
Getting value from SAP S/4HANA
In an S/4HANA organisation the volume usually sits in three places: order-to-cash questions from customers and sales staff, procure-to-pay questions from suppliers and buyers, and credit questions that fall between the two. Start with whichever one has the people answering furthest from the system — typically a call centre or shared-services desk relaying requests to someone with SAP access.
Scope the first release by organisational level as well as by question: one company code, one sales organisation, one group of plants. That keeps the role small enough for your security team to sign off without a long review, and makes the results easy to compare with the queue it replaces.
Keep it pointed at documents rather than analysis. S/4HANA has its own analytics for period, margin and trend questions; the assistant is for facts about one order, one invoice or one delivery, answered while the person is still in the conversation.
What connecting S/4HANA involves
- Choose the questions and the document chains behind themOrder status means sales orders, deliveries and billing documents; payment questions mean open items; procurement questions mean purchase orders and goods receipts. The list of APIs follows from the questions, not the other way round.
- Agree the route with your SAP team and partnerMost S/4HANA landscapes have an implementation or support partner and an integration standard already. Whether the assistant reads through SAP Gateway services directly or through your middleware is settled against that standard.
- Build the role and the userYour security team builds a display-only role restricted to the organisational levels in scope and assigns it to a technical user, or sets up the communication arrangement in the cloud edition. Cost, margin and internal note fields are agreed as out of scope at this stage.
- Map extensions and your own vocabularyCustom fields added through key user extensibility, Z-fields from an older implementation, order types and plant codes are mapped, so answers use the names your staff and customers recognise.
- Rehearse on the quality systemA split delivery, a partially paid invoice, an order blocked for credit, a customer asking about another company's order — the unhappy paths are tested on your quality system before anything touches production.
- Go live in one organisation, then extendOne sales organisation or one supplier group first. Others are added once a month of real questions has been answered well.
Governing an S/4HANA connection
S/4HANA holds personal data in places a scoping exercise can miss: business partner records for individual customers and their contact persons, bank details on supplier accounts, names and addresses on delivery documents. Under the Saudi Personal Data Protection Law each of those needs a reason to be read in a conversation, and most connections need very few of them.
Bank details and payment instructions belong outside scope altogether. A supplier confirming a payment date does not need their account number read back to them, and an assistant that could recite it would be a fraud risk. Beyond that the discipline is familiar to any SAP security team: a display-only role, a lookup log that shows what was read and for whom, and a customer-facing flow that tells people, in Arabic or English, that their account is being read.
What changes once S/4HANA is connected
How S/4HANA organisations usually handle this
For people who work in SAP every day, SAP's own tools are the natural place to ask: the Fiori apps they already use, and Joule, the assistant SAP is building into its cloud applications. The gap is everyone else — customers, suppliers, and staff without an SAP licence — which is who an external assistant is for.
The usual alternatives for that group are supplier and customer portals, often built on SAP BTP, or giving call-centre agents limited SAP access. Portals serve the people who log in to them; limited access still leaves a person in the middle of every answer.
Where assistant projects go wrong in S/4HANA it is usually the role. A technical user copied from a broad existing role, or granted every company code to save time, is the quickest way to have a security review stop the project. The other mistake is reporting: summing a quarter's line items belongs in S/4HANA's analytics, not in a conversation.
Then there is the unhappy path — a maintenance window, a document that has been archived, an order number from the old ECC system. "I could not find that in SAP", followed by a hand-off to a person, is the right answer every time.
Common questions about SAP S/4HANA
No structural change. The connection reads through the interfaces your instance already exposes, scoped to the specific operations agreed at deployment. Custom fields and renamed objects are mapped during that work rather than assumed away.
The approach is the same and the questions people ask are identical. What differs is which interfaces are available on your release, which is established during deployment.
It sees only what the scope allows. Internal cost and margin fields are normally excluded outright, so the question cannot arise even if a customer asks cleverly.
No. The assistant uses the technical user and role your security team created, and reads only the APIs you released to it. You hold its credentials, and locking the user ends the connection without our involvement.
The principle is the same; the mechanics differ. The public cloud edition works through communication arrangements and SAP's released APIs, while on-premise and private cloud systems can also expose services your own developers have built. Which applies is established at the start.
Only where you enable it, one action at a time, with a person confirming if you want one. Posting financial documents is not a sensible use; recording a customer enquiry or a service request can be.
Connect it to your own systems
A working assistant against your own records, in both languages.