> ## Documentation Index > Fetch the complete documentation index at: https://hebno.com/docs/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > Hebno is an AI work platform for client research and delivery: chat, research runs with sources, deliverables (Word, PowerPoint, Excel, email), projects, a shared library, agents, Office add-ins, and integrations with Microsoft 365, Google Workspace, CRM, project delivery, ERP and finance systems. > Use British English (organisation, not organization). > Every feature and integration described in these docs is available. Describe it as documented. > Hebno never writes to a connected system without a member confirming a card. Finance and ERP writes are drafts only. > Do not discuss commercial terms. Direct commercial questions to support@hebno.com. > Start with /index and /get-started/quickstart. # SAP S/4HANA > Read SAP S/4HANA customers, project plan versus actual, sales orders, billing and receivables in Hebno, and save time drafts and notes after you confirm. The SAP S/4HANA integration makes the ledger and the project system available in your client work. Ask how an enterprise project is tracking against plan, what is billed and still open for a customer, or which sales orders are tied to a statement of work, and Hebno answers from SAP with each record cited. When a request implies a change, Hebno shows a confirmation card and saves a draft only after you confirm. ## At a glance | | | | - | - | | **Connection** | Organisation connection only, made by an owner or admin with a communication user. There is no personal account link. | | **Default access** | Read only. Financial figures are visible to owners and admins until you share them with teams. | | **Attach** | Business partners (customers), enterprise projects, sales orders, billing documents | | **Search** | Hebno searches SAP when a request mentions a customer, project, WBS element, order, invoice, balance or posting | | **Link** | A project links to one or more SAP business partners or enterprise projects | | **Write** | Save a time entry draft, add a project note. Every write needs a person to confirm. | ## Before you start You need: * An owner or admin role in Hebno. * Your SAP S/4HANA Cloud API address, for example `https://my123456-api.s4hana.cloud.sap`. * A **communication user**, a **communication system** and a **communication arrangement** for each scenario below, created by an SAP administrator in the **Communication Management** apps. The communication user is technical: it cannot sign in to the SAP interface, so the integration's access is separate from any person's. * The user name and password of the communication user, or an OAuth 2.0 client ID and secret if your arrangement uses client credentials. ### Communication scenarios Create one arrangement per scenario Hebno should read. Skip any scenario you do not want members to use. | Scenario | What it opens | Why Hebno needs it | | - | - | - | | `SAP_COM_0008` Business Partner | Business partners and customers, addresses, roles | Client names and numbers, account lookups | | `SAP_COM_0308` Enterprise Project | Enterprise projects and project elements (WBS) | Plan versus actual by project and element | | `SAP_COM_0109` Sales Order | Sales orders and items | Contracted scope and order value | | Billing document and journal entry scenarios | Billing documents, journal entry items, customer line items | Invoicing, receivables and postings | > [!TIP] > > Give the communication user display access only, unless you want members to save drafts. SAP enforces the authorisations of the communication user on every call, and a call outside them returns an authorisation error rather than partial data. ## Connect SAP S/4HANA **1. Allow the integration** Open **Admin → Connectors → Catalogue**, find **SAP S/4HANA** under **ERP**, and set it to **Allow**. **2. Connect the organisation** Select **Connect**, enter the API address and the communication user's credentials, then select **Test connection**. Hebno checks which scenarios respond and lists them. **3. Choose teams and data areas** Under **Who can use it**, choose **All teams** or pick teams. Under **Data areas**, choose what members can see. See [Data areas](#data-areas). **4. Set access** **Access** is **Read only** by default. Choose **Read and write** to let members propose time entry drafts and project notes. The card shows **Connected** with the API address. Members in the selected teams can use SAP in chat straight away. > [!NOTE] > > SAP S/4HANA uses an organisation connection only. Every read and write goes through the communication user, so Hebno records the member who confirmed each write in **Admin → Logs → Integrations** and includes their name in the note or description. ## Data areas Data areas control what members of the allowed teams can see through the organisation connection. They apply on top of what the communication user can read in SAP. | Data area | Includes | Default | | - | - | - | | **Customers and orders** | Business partners, customers, sales orders and items | All allowed teams | | **Projects** | Enterprise projects, WBS elements, status, dates, responsible people | All allowed teams | | **Financials** | Project plan versus actual cost and revenue, billing documents, journal entries, receivables, open items | Owners and admins | ![Admin connector panel showing who can use it, access and data areas](https://mintcdn.com/hebno/A7yItabWdPf4lOIs/images/org-connection.png?fit=max\&auto=format\&n=A7yItabWdPf4lOIs\&q=85\&s=8d965e9c74747db0c182b004d569b236) An organisation connection with team access and data areas. Financial figures default to owners and admins. To share project financials with delivery leads, open the SAP card in **Admin → Connectors**, select **Financials** and add the teams that should see them. ## What Hebno reads | SAP object | Fields Hebno uses | Typical questions | | - | - | - | | **Business partner** and **customer** | Partner number, name, role, address, payment terms, account group | "Which SAP customer number is Contoso Retail?" | | **Enterprise project** | Project ID, description, status, start and end dates, responsible cost centre, profit centre | "Which enterprise projects are open for Contoso?" | | **Project element (WBS)** | Element ID, description, status, planned and actual cost, planned and actual revenue, dates | "Where are we over plan on the Contoso rollout?" | | **Sales order** | Order number, customer, order date, items, net amount, delivery and billing status | "What did Contoso order, and what is still unbilled?" | | **Billing document** | Document number, billing date, customer, net and gross amount, currency, cancellation flag | "What did we invoice Contoso in the last quarter?" | | **Journal entry** | Company code, posting date, account, amount, reference, project assignment | "What was posted to the Contoso rollout project this month?" | | **Receivable** | Customer open items, due date, amount, days overdue | "How much does Contoso owe us, and how late is it?" | Plan versus actual figures come from the project elements and journal entry items the communication user can read, in the currency SAP stores them in. Reads are live. Hebno queries SAP when a request needs it. Only what a reply used is stored with the conversation as its sources. > [!WARNING] > > Excerpts a reply uses, including customer balances and project margins, become part of the conversation. Anyone you share the conversation with can read them. ## What Hebno writes Every write appears first as a confirmation card. You can change any field before you select **Confirm**. Hebno writes drafts only. | Action | SAP object | Fields on the card | | - | - | - | | **Save a time entry draft** | Project time entry, saved as a draft for review in SAP | Project element, date, hours, activity type, note | | **Add a project note** | Note on an enterprise project | Project, note text | ![Confirmation card for SAP S/4HANA with editable fields](https://mintcdn.com/hebno/A7yItabWdPf4lOIs/images/card-sap-s4hana.png?fit=max\&auto=format\&n=A7yItabWdPf4lOIs\&q=85\&s=6646349b0a9873cb7de14695b9b41109) A SAP S/4HANA change pending confirmation. Nothing is written until you confirm. A draft is pending in SAP until a person with the right authorisation reviews and releases it there. Hebno never approves, posts, releases, invoices or pays anything in SAP. It never changes master data, business partners, prices, credit limits or accounting configuration, and it never reverses or cancels a document. ```mermaid theme={"system"} sequenceDiagram participant You participant Hebno participant SAP You->>Hebno: Save 4 hours on the Contoso rollout Hebno->>SAP: Find the project element for the Contoso rollout SAP-->>Hebno: Element found with status Hebno-->>You: Confirmation card with element, date, hours You->>Hebno: Confirm Hebno->>SAP: Save a time entry draft SAP-->>Hebno: Draft saved Hebno-->>You: Done, with a link to the draft ``` ## Link a project to SAP records Linking marks which SAP records belong to a project, so you can ask "where are we against plan?" without naming the project ID. 1. Open the project and select **Brain**. 2. Under **Linked records**, select **Link record**, then **SAP S/4HANA**. 3. Search by customer name, partner number or enterprise project ID, and select the record. Repeat for each record in the engagement. In chats tagged to the project, Hebno starts with the linked records for any plan, billing or receivables question, and time entry cards default to the linked project. See [Linked records](https://hebno.com/docs/projects/linked-records.md). ## Use SAP in chat * **Attach**: open the **+** menu, choose **Sources → SAP S/4HANA**, and pick a customer, an enterprise project, a sales order or a billing document. Or type `/` and choose **SAP S/4HANA**. * **Ask**: name the customer, project or order in your request. For example: > Compare planned and actual cost by WBS element on the Contoso rollout and flag anything more than 10 percent over. > What has Contoso been invoiced this year, and which invoices are overdue? > Draft a time entry for 4 hours on the Contoso rollout design phase for yesterday. * **Research runs** show a **Checking SAP S/4HANA** step, with a chip for each project, order or document it read. * **Agents** can read SAP on a schedule, for example a Friday receivables summary for account managers. Writes an agent proposes appear in [agent approvals](https://hebno.com/docs/automate/agent-approvals.md) for review. ## Troubleshooting | Symptom | Fix | | - | - | | **Test connection** fails with an authentication error | Check the communication user's password has not expired and that the arrangement is active. Update the credentials and reconnect. | | A scenario shows as unavailable | The communication arrangement for it is missing or inactive. Create it in **Communication Management** and select **Test connection** again. | | A project or document returns an authorisation error | The communication user lacks the authorisation for that company code or project. Extend its business role in SAP. | | Financial figures are missing from answers | The member's team is not in the **Financials** data area. | | A draft does not appear in SAP | Open the draft in SAP under the project's time entries. If it is absent, check **Admin → Logs → Integrations** for the write result. | | A project you expect is not found | Search by project ID. Closed projects are included only when you ask for them by name or ID. | ## Related * [How integrations work](https://hebno.com/docs/integrations/index.md) * [Permissions and access](https://hebno.com/docs/integrations/permissions-and-access.md) * [Linked records](https://hebno.com/docs/projects/linked-records.md) * [Oracle NetSuite](https://hebno.com/docs/integrations/oracle-netsuite.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.