How SAP S/4HANA customer master, materials, prices, sales orders and billing documents can reach HubSpot, and how won HubSpot deals can become S/4HANA sales orders, using the OData and SOAP APIs SAP publishes for S/4HANA.
S/4HANA runs order-to-cash for the business. HubSpot runs the customer relationship and the sales pipeline. The integration lets each system do its job and gives sales the ERP facts it needs.
Public documentation. The client's own admin issues credentials, with no vendor approval needed.
Open API. Services are catalogued publicly on the SAP Business Accelerator Hub. The client's SAP team sets up communication arrangements or activates the OData services.
Based on the vendor's public documentation. Access terms are confirmed with the vendor and the client in discovery.
S/4HANA publishes the APIs this integration needs, so HubSpot can see every account, order and invoice while SAP stays the system of record for finance.
Campaign Creators assessment
SAP catalogs released OData (v2 and v4) and SOAP APIs for S/4HANA on the SAP Business Accelerator Hub, including Business Partner, Sales Order, Sales Quotation, Billing Document and Product master. HubSpot does not publish its own SAP app, so this is a custom build on those APIs. Two things set the pace: how the client runs S/4HANA (Cloud Public Edition exposes APIs through communication arrangements; Private Edition and on-premise systems need the OData services activated and a secure network path), and the SAP sales structures (sales areas, partner functions and pricing procedures) that every customer and order carries.
Ratings are CC judgments from SAP's public documentation. The client's deployment, released services, custom fields and limits are confirmed during discovery.
Business partners, sales orders, billing documents and products each have a released API with a published data model. Sales orders carry a LastChangeDateTime, so changes can be read in small batches.
A customer in S/4HANA is set up per sales area (sales organization, distribution channel, division) with partner functions such as sold-to, ship-to, bill-to and payer. HubSpot needs clear rules for which of these become companies, and how orders find the right ones.
Cloud Public Edition needs a communication user and arrangements. On-premise and Private Edition need the services activated and a network path agreed with IT and Basis. Both come before any build.
Seven S/4HANA surfaces matter to HubSpot. Four carry the integration, two enrich it, and one is a scope decision the client makes early.
The customer master. One business partner holds the organization, its addresses, contact persons and the customer role with company code and sales area data.
to_Customer → to_CustomerSalesArea for sales org, channel, divisionto_BusinessPartnerAddress; partner functions in A_CustSalesPartnerFuncCreate and read sales orders with items, partners and pricing elements. The main path for won HubSpot deals.
SoldToParty, SalesOrganization, TotalNetAmountto_Item, to_Partner, to_PricingElementInvoices, credit memos and debit memos issued from S/4HANA, with partners (including payer) and items.
Materials with descriptions, units and sales data per sales organization and distribution channel.
Sales price conditions by condition type. Used to show list prices in HubSpot, not to recalculate SAP pricing.
SAP quotations for businesses whose official quote is issued from S/4HANA rather than from HubSpot.
When a HubSpot deal closes for a new company, someone must create the SAP customer. The client chooses whether the integration creates it through the API or sends a request to the master data team.
HubSpot never calls S/4HANA directly. A CC-built integration layer reads changes from S/4HANA, matches them to HubSpot records, writes in batches, and sends won deals back as sales orders after validation.
HubSpot owns prospects, contacts, deals and pre-sale quotes. S/4HANA owns the customer master once created, materials, prices, orders, billing and credit.
HubSpot line item prices are a guide. S/4HANA prices the order with its own pricing procedure, and the integration writes the SAP total back to the deal.
Each HubSpot deal creates at most one SAP order. The SAP order number is stored on the deal, and any failure goes to a queue a person can replay.
Each phase ends on a gate the client signs off before the next begins. Master data goes live first, then orders, then billing.
Confirm the deployment (Cloud Public, Private or on-premise), the sales areas in scope, and which system owns each record type. Decide how new SAP customers are created.
Set up the communication user and arrangements in Cloud Public Edition, or activate the OData services and agree the network path with IT and Basis for other deployments.
Agree how SAP business partners match HubSpot companies, how partner functions map, and which custom fields come across. Read the client's $metadata to confirm field names.
Create the properties, product library settings, order and invoice pipelines, association labels and property groups in a HubSpot sandbox.
Build master data sync, then order write-back with validation, then billing reads. Test against the SAP quality system, never production.
Load customers, products and an agreed history of orders and invoices, then compute rollups once.
Run order write-back alongside the current process for two weeks, then switch on.
Field names come from SAP's published API data models. Custom fields (extension fields) and the exact services in the client's system are confirmed from its $metadata during discovery.
| S/4HANA field | HubSpot property | Object | Direction | Notes |
|---|---|---|---|---|
| Business partner · customer master | ||||
| BusinessPartner | s4_bp_number | Company | S/4 → HS | Primary match key. Unique. |
| OrganizationBPName1 | name | Company | ↔ Both | SAP name wins once the customer exists in SAP. |
| Address (StreetName, CityName, PostalCode, Country) | address, city, zip, country | Company | S/4 → HS | Default address from to_BusinessPartnerAddress. |
| EmailAddress (contact person) | Contact | ↔ Both | Contact persons match on email. HubSpot keeps new contacts it creates. | |
| SalesOrganization, DistributionChannel, Division | s4_sales_area | Company | S/4 → HS | From to_CustomerSalesArea. Multi-select if one customer has several. |
| Currency (sales area) | s4_currency | Company | S/4 → HS | Customer's order currency. |
| Customer payment terms | s4_payment_terms | Company | S/4 → HS | From sales area data. Confirm field in discovery. |
| Ship-to / bill-to / payer partners | Child companies + association labels | Company | S/4 → HS | Partner functions become labeled associations to the sold-to company. |
| Products & prices | ||||
| Product | hs_sku | Product | S/4 → HS | SAP material number as SKU. Unique. |
| ProductDescription | name | Product | S/4 → HS | Description in the client's sales language. |
| BaseUnit | s4_base_unit | Product | S/4 → HS | Unit of measure for line items. |
| ProductGroup | s4_product_group | Product | S/4 → HS | For reporting and segments. |
| ConditionRateValue (list price) | price | Product | S/4 → HS | From pricing condition records. Confirm condition type in discovery. |
| Deals → sales orders | ||||
| SoldToParty | s4_bp_number (company) | Deal | HS → S/4 | Taken from the associated company. |
| SalesOrderType, SalesOrganization, DistributionChannel, OrganizationDivision | s4_order_type, s4_sales_area | Deal | HS → S/4 | Defaults per pipeline, overridable by the rep. |
| PurchaseOrderByCustomer | s4_customer_po | Deal | HS → S/4 | Customer PO number captured in HubSpot. |
| to_Item: Material, RequestedQuantity | hs_sku, quantity | Line item | HS → S/4 | One SAP item per HubSpot line item. |
| to_Partner: PartnerFunction ship-to | Ship-to association label | Deal | HS → S/4 | Ship-to selected on the deal; defaults from SAP if blank. |
| SalesOrder | s4_sales_order | Deal | S/4 → HS | Written back after SAP accepts the order. |
| TotalNetAmount, TransactionCurrency | amount, deal_currency_code | Deal | S/4 → HS | SAP-priced total replaces the estimate. |
| Orders & billing | ||||
| A_SalesOrder (header) | Order record | Order | S/4 → HS | All SAP orders for synced customers, including those entered in SAP. |
| OverallDeliveryStatus, OverallOrdReltdBillgStatus | s4_delivery_status, s4_billing_status | Order | S/4 → HS | Drives service and follow-up workflows. |
| TotalCreditCheckStatus | s4_credit_status | Order | S/4 → HS | Credit blocks alert the account owner. |
| BillingDocument, BillingDocumentDate | Invoice record | Invoice | S/4 → HS | Read-only copy of SAP billing documents. |
| TotalNetAmount (billing) | s4_billed_ytd | Company | S/4 → HS | Rolled up in the integration layer. |
| Open receivables | s4_open_ar | Company | S/4 → HS | From finance data. Confirm the source API in discovery. |
Values SAP does not publish are marked for confirmation. The client's deployment decides the connection method.
| Topic | S/4HANA | HubSpot |
|---|---|---|
| Access model | Cloud Public Edition: a communication system, communication user and one communication arrangement per scenario (Business Partner uses SAP_COM_0008). Private Edition and on-premise: OData services activated on the SAP Gateway. | Self-serve in the client portal. Custom objects need an Enterprise hub; orders and invoices are standard objects. |
| Interfaces | OData v2 and v4 REST services and SOAP services, catalogued on the SAP Business Accelerator Hub. Each system's $metadata lists its exact fields. | REST APIs: CRM objects, associations, products, line items, orders, invoices, webhooks. |
| Authentication | Communication user with user and password or X.509 client certificate. OAuth 2.0 where the scenario supports it. Confirm in discovery. | Private app access token or OAuth 2.0 public app, scoped per object. |
| Network | Cloud Public Edition is reachable over HTTPS. Private Edition and on-premise need a secure path agreed with IT (allowlisted connection or VPN). | Public HTTPS endpoints. |
| Change detection | Delta reads by last-change timestamp (sales orders carry LastChangeDateTime). S/4HANA business events where the client's landscape publishes them. | Webhooks on deal stage change trigger order write-back. |
| Rate limits | Not published. Confirm with SAP and the client's Basis team. | Per-10-second burst and daily limits by subscription tier. |
| Environments | Write-back is built and tested against the SAP quality system first. | HubSpot sandbox for build and test. |
Severity reflects impact on the SOW, not technical difficulty alone.
Cloud Public Edition, Private Edition and on-premise each connect differently. Make access a client-owned dependency in the SOW, with IT and Basis named.
One SAP customer can sell through several sales areas and ship to many locations. Agree which sales areas are in scope and how ship-to, bill-to and payer appear in HubSpot before mapping starts.
An order cannot be created for a customer SAP does not know. The client decides whether the integration creates business partners or routes a request to the master data team.
Condition-based pricing cannot be repeated in HubSpot. HubSpot shows list prices, and the SAP-priced total is written back to the deal after the order is created.
Client-specific fields must be added to the API as extension fields, and Cloud Public Edition exposes only released APIs. Budget a short discovery spike to read $metadata.
Order and billing history can be large. HubSpot receives an agreed history window and rollups, not every line from every year.
Reps stop re-keying orders. The deal carries the SAP order number and the SAP-priced total, and errors land in a queue someone owns.
Orders, billed revenue and open receivables sit on the company record, so sales and service see the whole relationship in one place.
Customers who stop ordering, or order less than usual, enter HubSpot lists and tasks for the account owner.
Credit blocks and delivery status reach the account owner as tasks, so the customer hears from sales first.
HubSpot products match SAP materials, so quotes and line items use the same codes the ERP does.
Pipeline and billed revenue meet in HubSpot dashboards, split the same way finance splits them.
HubSpot runs the pipeline up to the signed deal. S/4HANA runs fulfillment and finance from the sales order on. The integration hands over at close and reports back at every step after.
All custom properties use the s4_ prefix in an SAP S/4HANA property group. Rollups are calculated in the integration layer so every report agrees.
| Internal name | Label | Object | Type | Source / logic |
|---|---|---|---|---|
| s4_bp_number | SAP Business Partner | Company | Single-line text | BusinessPartner; unique |
| s4_sales_area | SAP Sales Area | Company | Multiple checkboxes | Sales org / channel / division combinations |
| s4_currency | SAP Order Currency | Company | Single-line text | Sales area currency |
| s4_payment_terms | SAP Payment Terms | Company | Dropdown | Sales area payment terms |
| s4_billed_ytd | Billed YTD | Company | Number (currency) | Sum of billing document net amounts |
| s4_open_ar | Open Receivables | Company | Number (currency) | Open items from finance; source confirmed in discovery |
| s4_base_unit | SAP Base Unit | Product | Single-line text | BaseUnit |
| s4_order_type | SAP Order Type | Deal | Dropdown | SalesOrderType default per pipeline |
| s4_customer_po | Customer PO | Deal | Single-line text | PurchaseOrderByCustomer |
| s4_sales_order | SAP Sales Order | Deal | Single-line text | SalesOrder returned on create |
| s4_delivery_status | SAP Delivery Status | Order | Dropdown | OverallDeliveryStatus |
| s4_credit_status | SAP Credit Status | Order | Dropdown | TotalCreditCheckStatus |
Choose the modules and fields for this engagement and the direction each one syncs. Required fields are the keys the integration cannot run without. Copy the summary into the SOW or a reply to the client.
Based on public documentation. Each item marked for confirmation is verified against the client's SAP system and with SAP during discovery.
Yes, through a custom integration. HubSpot does not publish its own SAP app, so Campaign Creators builds on the released OData and SOAP APIs that SAP catalogs for S/4HANA on the SAP Business Accelerator Hub, including Business Partner, Sales Order, Billing Document and Product master.
S/4HANA business partners sync to HubSpot companies and contacts, and products with list prices sync to HubSpot products. Won HubSpot deals create S/4HANA sales orders. Order status, billing documents, billed revenue and open receivables are written back to HubSpot.
Yes, but access is set up differently. Cloud Public Edition exposes released APIs through a communication user and communication arrangements. Private Edition and on-premise systems need the OData services activated and a secure network path agreed with the client's IT and Basis teams.
Seven phases, each closed by a client sign-off: landscape and ownership, API access, matching and mapping rules, the HubSpot data model, build and test against the SAP quality system, backfill, and a two-week parallel run before order write-back is switched on.
Timeline and cost depend on the S/4HANA deployment, the sales areas and partner functions in scope, custom fields and the history to load. Campaign Creators confirms these in discovery and provides a fixed scope before the build starts.