Skip to main content

SAP Integration Objects

1. Integration Overview

The integration consists of:

  • Reference data synchronisation (SAP → Hyperfox)
  • Transactional order submission (Hyperfox → SAP)

SAP remains the system of record. Unless otherwise agreed, synchronisation frequency is daily batch or event-driven.

2. Reference Data (SAP → Hyperfox)

Reference data enables customer recognition, product matching and validation.

2.1 Items (Materials)

FieldRequiredSource (SAP)Notes
Material Code (MATNR)YesMARAPrimary key
SKU (if separate)NoMARA / customOptional
EAN / GTINRecommendedMEANImproves AI matching
Name (Short Text)YesMAKT
Description (Long Text)NoMaterial textOptional
Base Unit of Measure (MEINS)YesMARASAP UoM code

Purpose: Material recognition and line-level matching.

2.2 Units of Measure

FieldRequiredSourceNotes
UoM CodeYesT006SAP standard code
DescriptionYesT006A

Purpose: Interpret ordered quantities correctly.

2.3 Item Units of Measure (Conversions)

FieldRequiredSourceNotes
Material CodeYesMARM
Alternative UoM CodeYesMARM
Conversion Factor to Base UoMYesMARMNumeric factor

:::important Alignment point Confirm whether Hyperfox sends:

  • Sales UoM and SAP performs conversion, or
  • Base UoM quantities.

This must be defined before go-live. :::

2.4 Billing Customer (Sold-to / Bill-to)

FieldRequiredSourceNotes
Customer Code (KUNNR)YesKNA1Primary key
NameYesKNA1
AddressYesADRC
Postal CodeYesADRC
CityYesADRC
CountryYesADRCISO code preferred
PhoneNoADR2
EmailRecommendedADR6Improves matching

2.5 Shipping Address (Ship-to)

FieldRequiredSourceNotes
Ship-to CodeYesKNVPPartner function WE
NameYesADRC
AddressYesADRC
Postal CodeYesADRC
CityYesADRC
CountryYesADRC
PhoneNoADR2
EmailNoADR6

Purpose: Correct delivery mapping in SAP.

2.6 Customer Items (Customer-Specific Product References)

FieldRequiredSourceNotes
Customer CodeYesSAP
Material CodeYesSAP
Customer ReferenceYesSAP customCustomer-specific article code

Purpose: Improves matching when customers use their own product codes.

FieldRequiredSourceNotes
Customer CodeYesSAP
Material CodeYesSAP
Order DateYesVBAK
QuantityYesVBAP
Unit of MeasureYesVBAP

Recommended: Last 12–24 months of historical order lines.

Purpose: Improves AI suggestions and anomaly detection.

3. Transactional Integration (Hyperfox → SAP)

3.1 Order Create Endpoint

The customer's SAP team will expose a secure endpoint allowing Hyperfox to submit validated orders.

3.2 Minimum Required Request Structure

FieldRequiredNotes
externalOrderReferenceYesCustomer PO number
orderDateYesISO format
soldToCustomerCodeYesSAP KUNNR
shipToCodeRecommendedIf applicable
requestedDeliveryDateOptional
freeTextNoteOptional

Lines

FieldRequiredNotes
lineNumberYes
materialCodeYesSAP MATNR
quantityYes
uomCodeYesSAP UoM code
customerItemReferenceOptional
lineTextOptional

3.3 Minimum Required Response Structure

FieldRequiredNotes
statusYesACCEPTED / REJECTED
sapOrderNumberIf acceptedSAP document number
errors[]If rejectedStructured error messages

Each error should contain:

  • errorCode
  • errorMessage
  • fieldReference (if applicable)

4. Synchronisation Principles

ObjectDirectionFrequencyOwner
ItemsSAP → HyperfoxDaily or event-basedSAP team
Units of MeasureSAP → HyperfoxDailySAP team
CustomersSAP → HyperfoxDailySAP team
Customer ItemsSAP → HyperfoxDailySAP team
Order HistorySAP → HyperfoxOne-time bulk + periodicSAP team
OrdersHyperfox → SAPReal-timeHyperfox → SAP team