Integration Cloud 6.6.0 | Recipes | SAP C4C to Marketo Appointment Activity Data Sync
 
SAP C4C to Marketo Appointment Activity Data Sync
This section describes the recipe for the data sync between SAP Cloud for Customer Apointment business object and Marketo custom object for Appointment records
SAP Cloud for Customer (C4C) is a cloud solution to manage customer sales, customer service, and marketing activities efficiently and is one of the key SAP solutions to manage customer relationships.
Marketo provides software platforms and technologies designed for marketing departments such as account-based marketing, which includes email, mobile, social, digital ads, web management, and analytics.
Business Use Case
The business purpose of this integration is to extract SAP Cloud for Customer Appointment records and upserts them into Marketo Custom object for Appointment records.
Custom Fields
When the Appointment record gets synced in Marketo, it needs to be created or updated with the below mentioned custom fields.
On Marketo
Comments
c4CAppointmentID
Custom field needs to be created in the Marketo custom object for Appointment record.
Product Compatibility
The recipe is tested for SAP Cloud for Customer product version 1908.04.0006. Hence the recipe is compatible to run for the tested and older versions of the product.
Data Sync Flow
This integration "SAPC4CToMarketoActvtyAppoinDataSync" is designed to run for initial as well as ongoing sync. As part of the initial sync, all the Customer Appointment records present in SAP C4C will be synced to Marketo. On the other hand, as part of the ongoing sync, the updated or newly created Customer Appointment records will be synced to Marketo for the provided date range.
Below flow diagram gives representation of creating or updating an appointment activity in Marketo from SAP C4C:
Input Parameters
Sl.No
Parameter
Description
1
isInitialSync
Set to true in case of initial sync and to false in case of ongoing sync(true/false).
2
syncInterval
The sync interval can be entered either in hours/minutes/seconds or all of them and corresponding pattern & timezone if required.
3
logRecordStatusFlag
The log status of each record processed. It can either be true or false.
Operations Used
This recipe has a sub flow to handle the obsolete contact record in SAP C4C, that is, updateDeletedSAPC4CContactsToMkto.
Sl.No
Operations Used
Application
Description
Query
1
queryAppointments
C4C
Query SAP C4C
Appointments.
LastChangeDateTime
ge datetimeoffset'%
fromDateString%'
2
upsertAppointme_
SAPC4CAct_to_MktoAct
Marketo
Upsert Appointments in
Marketo.
NA