OData services
The standard path on S/4HANA. brisk4 consumes OData services published on the gateway, authenticated by OAuth or a technical user.
Integration · ERP
Official WhatsApp + SAP.
brisk4 connects omnichannel customer service to SAP, exposing to the end customer what today lives only inside the ERP. Integration uses OData services, BAPI calls or the integration layer already present in your landscape, depending on the installed version.
What syncs
SAP objects inside the conversation.
| SAP object | Direction | Trigger |
|---|---|---|
| Sales order (VBAK/VBAP) | SAP → brisk4 | A query by order number or customer code returns items, quantities and status. |
| Delivery and shipment | SAP → brisk4 | Creating the delivery fires a shipping notice with carrier and ETA. |
| Invoice and receivable | SAP → brisk4 | The customer requests the invoice in chat, or gets an automatic reminder as the due date approaches. |
| Business partner master | brisk4 ↔ SAP | Customer identified by business partner, with contact updates written back into SAP. |
| Service notification | brisk4 → SAP | A request logged in the conversation creates the service notification with the history attached. |
Ready-made flows
What goes live first.
- Sales order lookupThe customer provides the order number or is identified by business partner, and brisk4 returns items, quantities, status and the delivery document read from SAP.
- Automatic shipping noticeCreating the delivery in SAP fires the webhook: the customer receives carrier, ETA and tracking link on WhatsApp, with nobody typing anything.
- Invoice on demandA duplicate request in chat returns the billing document and the open amount, with identity validation before sending.
How we connect
Method and prerequisites.
BAPI and RFC
For ECC and cases where the object has no exposed OData service, through an integration layer or intermediate connector.
Business One Service Layer
On SAP Business One the integration uses the REST Service Layer, with session authentication and scope defined per company database.
- Covered products
- SAP S/4HANA, SAP Business One and SAP ECC
- Required access
- Technical user authorised on the queried objects
- Environment
- Gateway or Service Layer reachable from the integration network
- Authentication
- OAuth 2.0, technical user or session, depending on the product
- Write scope
- Approved by the Basis team and the process owner
- Staging
- SAP test client before production
Frequently asked questions
SAP and brisk4: questions.
Does brisk4 integrate with SAP S/4HANA?
Yes. On S/4HANA the integration runs through OData services published on the gateway, authenticated by OAuth 2.0 or a technical user. The most common objects are sales order, delivery, invoice, business partner and service notification.
What if the company still runs SAP ECC?
That works too. In ECC landscapes the integration uses BAPI and RFC through an integration layer or intermediate connector, defined with your Basis team during rollout.
Does the integration work with SAP Business One?
Yes. On Business One we use the REST Service Layer, with session authentication and scope per company database. Object mapping is done during the assessment.
Does brisk4 write data into SAP?
It can, but the scope is always agreed up front. Common cases are updating business partner contact details and creating service notifications. Every write is approved by the Basis team and the process owner.
See it running on your SAP.
In the free assessment a specialist maps your SAP version, the available services and the highest-impact flow.