SAP Commerce Cloud Integration

This article explains how to connect and use the SAP Commerce Cloud integration with your Bynder DAM.

Summary

The Bynder SAP Commerce Cloud integration automates asset management by connecting your Bynder DAM with SAP Commerce Cloud. This integration ensures real-time, bi-directional media and metadata synchronization across both platforms. When you update assets in Bynder, the changes reflect in SAP Commerce Cloud. Similarly, product metadata updates in SAP reflect back into Bynder metaproperties.

Who?

  • Bynder Administrators: Required to grant consent for metaproperty creation and manage asset tagging.

  • SAP Commerce Cloud Technical Administrators: Required to provide OData integration object details, catalog configurations, and authentication credentials.

  • Content Managers & E-commerce Editors: Users responsible for tagging assets with product SKUs and managing storefront media.

How?

Prerequisites

Before running the configuration wizard, ensure you have the following information ready:

  • Your SAP OData integration object names for inbound products, inbound media, and outbound products.

  • Your fallback SAP Product Catalog ID and Catalog Version.

  • The ISO language code for your localized text.

  • SAP Installation Package: The components that must be installed on SAP Commerce Cloud are provided in a separate package upon purchase of the integration. Ensure these components are fully installed in your SAP Commerce Cloud environment before beginning the configuration wizard.

Configuring the Integration

  1. Navigate to your integration management dashboard or i-Hub portal.

  2. Select Add Integration and choose SAP Commerce Cloud.

  3. Read the introduction screen and click Next to proceed to Authentication.

    introsap.png

  4. Enter your Bynder and SAP Commerce Cloud credentials to authorize the connection. 

    SAP1.png

  5. In SAP Setup Configuration Part 1, enter the Inbound Product Integration Object, Inbound Media Integration Object, and your fallback Default Catalog ID and Default Catalog Version.

    SAPpart1.png

  6. In SAP Setup Configuration Part 2, enter the Outbound Product Integration Object and your Localization Language code (for example, "en" or "de"). 

    SAPpart2.png

  7. In the Metaproperty Mapping screen, map your standard or custom SAP Product attributes to your corresponding Bynder metaproperties. 

    metap.png

  8. If needed, add custom values for specific metaproperty mappings in the custom values fields.

  9. On the Consent on Creating Metaproperties screen, review the required properties. If you grant consent, the system automatically creates the following fields in your Bynder portal if they do not already exist:

    • SAP Product ID (Text): Stores the unique technical SKU or product code.

    • SAP Image Type (Multi-Select): Contains the storefront target options (galleryImages, normal, others, picture, thumbnail, thumbnails, and video). 

      Consent.png

  10. Click complete to finish the wizard. The system will automatically register the webhooks and initialize the schema. 

    Configcomplete.png

Using the Integration

Once configured, the synchronization workflow operates automatically based on user actions:

  • Syncing Media from Bynder to SAP: Tag a Bynder asset with an SAP Product ID and an SAP Image Type. Bynder fires a webhook, and the integration automatically cleans special characters from the filename, appends the correct extension, and routes the asset to the correct SAP media slot or data sheet.

  • Syncing Metadata from SAP to Bynder: When product information changes in SAP, an event triggers the integration to pull the expanded product data. The Diff Engine evaluates the changes against your current Bynder metadata and updates only the modified metaproperties.

 

Updated