cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Commerce onprem to Marketing Cloud integration: which option?

vervinckt_joyca
Active Contributor
0 Likes
662

Hi all,

We are planning to integrate an onprem SAP Commerce system (1811 version) with Marketing Cloud.

So we found a package on the API hub, read the documentation pages linked to from that package on API hub, everything looked good, we had our estimates and planning ready.

Then suddenly I bumped into this blog.

Which states in the introduction "You must be on SAP Commerce core version 1905 or higher.".

I doublechecked. On the API hub package and the sap help pages, this version prerequisite is nowhere mentioned.

So yeah, quite a headache 😞

Is that little phrase from the blog still valid? Or can the integration package over CPI be somehow activated on lower Commerce versions anyway?

This other blog mentions alternative options with Datahub and Expressway. But for datahub it mentions API's are used that are now deprecated in Marketing Cloud, and Expressway is not supported...

So I'm really doubting about the best way forward on this :s Can someone advise please?

Thanks

Joyca

Accepted Solutions (0)

Answers (3)

Answers (3)

tylermac
Product and Topic Expert
Product and Topic Expert

vervinckt.joyca,

To be able to use the BTP Integration Suite (formerly SCPI) iFlows to connect SAP Commerce Cloud and SAP Marketing Cloud you need to be on SAP Commerce core version 1905 or higher. The article you linked to is correct. The Integration APIs features in SAP Commerce core required for the marketing iFlow did not get released until SAP Commerce core 1905. The Help Documentation you linked to is pointing at the 2102 Integration Extension Pack, which requires SAP Commerce 2011. The integration extension packs were released alongside SAP Commerce core 2005 to decouple integration work from the core commerce features. If you're trying to use the iFlows with SAP Commerce 1905 you will need to look at the documentation at https://help.sap.com/viewer/bad9b0b66bac476f8a4a5c4a08e4ab6b/v1905/en-US/4eafdd5dbd3c49d5b4a6430ab53...

Please also note that as of Aug 30, 2021 only versions of SAP Commerce core 1905 and newer will still be in mainstream maintenance (

https://help.sap.com/viewer/dc198ac31ba24dce96149c8480be955f/latest/en-US/1c6c687ad0ed4964bb43d40981.... If you are on 1811 you will no longer receive any of the monthly patches, which include bug/security/performance fixes.

SCHNEIDERT
Active Contributor

Hi Joyca,

we have been in the same situation. In our case the customer then decided to upgrade commerce to 2005 first and I think this was the right decision which I would also recommend instead of building your own integration.

Kind Regards

Tobias

deanmg1
Participant

Hi vervinckt.joyca ,

We had similar challenges before our recent Commerce upgrade

The call we made previously was to use Expressway. Basically direct API calls from an SMC perspective... we did not hit many bottlenecks but we did implement queueing later on. The queuing mechanism was managed in Commerce and what this did was to enable or disable batching of Contact and Interaction data. When we expected high volume we enabled the queues (batching) which impacted a bit of customer experience features but ensure that the SMC import queue would not be backed up with hundreds of thousands of single payloads

Cheers,

Dean

vervinckt_joyca
Active Contributor

Thank you very much for your comment Dean.

I also read meanwhile that "Expressway leverages the same SAP Commerce Cloud extensions that are being deprecated (in accordance with the CUAN_IMPORT deprecation)". In the download center for ExpressWay I do see there are a couple of enhancements made in 1708 like "ymktCustomer1708CronJob to send Customers using the new Marketing OData API (API_MKT_CONTACT_SRV)". But checking further I found that is actually /sap/opu/odata/sap/API_MKT_CONTACT_SRV;v=0002/ while Version 4 is the newest one. And unfortunately Version 4 is also the only one that we can use, as we activated contact-to-account relations in marketing cloud...

I fear I'll need to scrap the datahub and expressway options then... leaving only 2 options: upgrade commerce, or custom build. Sigh 😞