Custom fields in account management data model not syncing between C4C and S/4HANA

CRM SAP Customer Experience (SAP CX)
, , , , , , , ,
1

We recently extended the Account object in SAP C4C with custom fields (CustomerSegment, PreferredContactMethod, AccountTier) to capture additional business data. These fields are populated correctly in C4C and visible in the UI, but they’re not appearing in the replicated records in S/4HANA.

I’ve verified that custom field enablement for replication is set to ‘true’ in the extension fields configuration. When I check the OData metadata exposure through the service explorer, the custom fields appear in the AccountCollection entity, but the iFlow mapping in Cloud Integration doesn’t seem to be picking them up.

The standard account fields (name, address, industry) sync perfectly. Only our custom extensions fail silently - no error messages in the integration monitor, just incomplete master data on the S/4HANA side. Has anyone dealt with custom field replication issues between C4C and backend systems?

2

One more thing to check - make sure your custom fields are included in the delta token logic for change detection. If the iFlow uses delta queries, custom fields might not trigger replication events unless explicitly configured in the change tracking setup. Check the query filter parameters in your OData call.

3

I’ve seen this before. The OData service might expose the fields, but you need to explicitly add them to the communication arrangement payload mapping. Check your communication scenario configuration - custom fields don’t automatically inherit replication settings from standard fields.

4

Thanks for the pointer. I checked the communication arrangement and the payload mapping shows only standard fields. I tried adding the custom field technical names manually, but I’m getting a metadata validation error. Do I need to regenerate the service definition first?

5

Let me provide a complete solution addressing all three aspects of custom field replication:

1. Custom Field Enablement for Replication First, ensure your custom fields are properly configured for integration in C4C:

  • Navigate to Administrator > Business Configuration > Implementation Projects
  • Locate your Account extension project and open the custom fields section
  • Verify each field has these settings enabled:
    • ‘Enable for Web Services’ = checked
    • ‘Include in OData Service’ = checked
    • ‘Replication Enabled’ = checked (if available in your version)

2. OData Metadata Exposure Verification Confirm the fields are exposed in the service metadata:


GET /sap/c4c/odata/v1/c4codataapi/$metadata

Look for:
<Property Name="CustomerSegmentID" Type="Edm.String"/>
<Property Name="PreferredContactMethodCode" Type="Edm.String"/>
<Property Name="AccountTierID" Type="Edm.String"/>

If these don’t appear, you may need to refresh the service definition or regenerate the OData service cache.

3. iFlow Mapping Update This is typically where the issue occurs. In Cloud Integration:

  • Open your account replication iFlow
  • Locate the Message Mapping artifact (usually named AccountC4CToS4Mapping or similar)
  • Add explicit field mappings in the transformation:

Source: AccountCollection/CustomerSegmentID
Target: CustomerSegment

Source: AccountCollection/PreferredContactMethodCode
Target: ContactMethod

Source: AccountCollection/AccountTierID
Target: AccountClassification

Additional Configuration Steps:

  1. Update Delta Query Filter: If using delta synchronization, modify the OData query to include custom fields in the $select parameter:

$select=AccountID,Name,CustomerSegmentID,PreferredContactMethodCode,AccountTierID&$filter=ChangedOn gt datetime'[DELTA_TOKEN]'

  1. Target System Preparation: Ensure S/4HANA has corresponding extension fields or custom fields in the Business Partner master data to receive these values. The technical names must match your iFlow target mapping.

  2. Communication Arrangement: Update the communication arrangement in C4C to include the custom fields in the payload scope. This might require creating a new arrangement or modifying the existing one to include extended field sets.

  3. Testing: After making these changes:

  • Deploy the updated iFlow
  • Create or modify a test account in C4C with values in all custom fields
  • Monitor the integration flow execution in Cloud Integration
  • Verify the custom field values appear in S/4HANA Business Partner record

Common Gotcha: Custom field technical names in C4C often have suffixes like ‘_KUT’ or namespace prefixes. Make sure your iFlow mapping uses the exact technical names from the OData metadata, not the field labels from the UI.

If you still see silent failures after this, enable trace-level logging in your iFlow and check for field-level validation errors that might be getting swallowed by the error handling logic.