SAP Cloud for Customer

The interface labels this integration "C4C integration." The external system is SAP Cloud for Customer (SAP C4C) — the CRM module of the SAP Customer Experience suite.

This is a one-way, manually triggered import. Customer records flow from SAP into Deals.

This integration is tenant-specific. It may not appear in your interface if it is not enabled for your organization.

Prerequisites

Before the integration can be configured, the customer entity type must contain a custom field that SAP will use as the match key.

  1. Open the entity type administration area (Settings or Admin → Entity types → Customer).

  2. Add a new field of type String with the machine name accountId (case-sensitive, exact match).

  3. Save the entity type.

If this field is missing or has the wrong type, the sync will fail with a validation error when triggered. The error message names the missing field.

Configuration

  1. Open Settings → Sync → C4C integration.

  2. Enter the OData base URL for your SAP C4C tenant.

  3. Enter a username and password (the integration uses HTTP Basic authentication).

  4. Enable the integration and save.

An administrator with the Synchronization settings permission configures it.

Running the sync

Click Synchronize on the C4C integration section. The import runs each time someone clicks Synchronize.

When triggered, the sync:

  1. Reads the customers from SAP C4C page by page.

  2. Validates each incoming record.

  3. Matches each record against existing Deals customers by their accountId custom field value.

  4. For matches — overwrites the mapped custom fields with SAP values and updates the archive flag.

  5. For non-matches (customers that exist in SAP as active but have no Deals counterpart) — creates a new customer record.

Customers whose SAP lifecycle status is not "Active" are archived in Deals. Customers that are active in SAP are un-archived if they had previously been archived.

If another sync is already in progress for the same organization, it is canceled before the new one starts.

Field mapping

The sync writes SAP fields into custom fields on the Deals customer record. The fields below must exist on the customer entity type with the listed machine names for the mapping to populate them.

SAP field Deals custom field (machine name)

Account ID

accountId

Role

role

Industry

industry

Sub-industry

subIndustry

Address line 1

addressLine1

Address line 2

addressLine2

City

city

Postal code

postalCode

State code

stateCode

Phone

phone

Client code

clientCode

Client name

clientNameExtKut

Category

category

TIN (Tax Identification Number)

tin

BRN (Business Registration Number)

brn

New BRN

newBrn

GST-exempt flag

gstExempt

GST registration number

gstRegistrationNumber

SST-exempt flag

sstExempt

SST registration number

sstRegistrationNumber

E-invoice email

eInvoiceEmail

Agency commission flag

agencyCommission

Beware flag

beware

Blacklist flag

blacklist

The tax-related fields in this mapping — TIN, BRN, GST, SST — are shaped for one market. Organizations in other jurisdictions will not use all of them.

When a new customer is created from SAP data, the clientNameExtKut value is used as the customer name.

Sync log

After each run, the result is visible under Settings → Sync → Synchronization logs. The log shows the start and end time, whether the run succeeded or failed, the count of customers created and updated, and any error text.

Only the most recent run is retained.

Permissions

  • Configuring the C4C integration requires the Synchronization settings permission with update access.

See Roles & Permissions.