Configuring SAP Sales Cloud and SAP Service Cloud Version 2 for Product Replication

In earlier units and lessons, several technical and functional settings have been discussed generally. This unit lists the specific settings and dependencies needed to replicate products from SAP S/4HANA to SAP Sales and Service Cloud Version 2 and explains a few selected ones in more detail.

• Communication Configuration:
  • Integrate Master Data with SAP S/4HANA
• Object References:
  • Sales Organizations
  • Product Groups
• Code Lists:
  • Distribution Channel
  • Division
  • Product Type
  • Unit of Measure

Please note that this list does not claim to be exhaustive, and additional dependencies may need to be maintained based on your environment‘s specific conditions and the ongoing development of the involved products (especially SAP Sales and Service Cloud Version 2).

The Communication Configuration Integrate Master Data with SAP S/4HANA was copied using the default settings as part of the overall technical preparation in a previous unit.

Remember: You can find the Communication Configuration through Settings→Integration→Communication Configuration. On the screen with all the Communication Configuration templates and the ones that are actually configured, it’s helpful to select your system from the Communication System filter to quickly hide all templates and only see the ones you’ve already configured.

For the product replication, we must ensure the following settings are made:

1. The relevant inbound service, Replicate Product from SAP S/4HANA, must be active, which means it must be listed under Inbound Configuration.
2. The Value Mapping Group must be assigned if you are using value mappings for product-related code lists. In the demo environment, S/4HANA is assigned.
3. The Communication Configuration itself must be set to active.

The following screenshot shows the communication configuration with the necessary settings applied.

With the Asynchronous Outbound ConfigurationConfirm Product Replication to SAP S/4HANA, the cloud CRM can send the assigned product ID to SAP S/4HANA, which may require additional steps in Cloud Integration and SAP S/4HANA. However, this is usually not necessary for uni-directional product replication, as long as your integration setup does not include a scenario where SAP S/4HANA needs to know the internal product IDs of SAP Sales and Service Cloud Version 2. In typical follow-up scenarios (such as sending sales quotes or orders to SAP S/4HANA), the cloud CRM sends the SAP S/4HANA product ID, which is sufficient.

Products are usually assigned to Sales Organizations and to Product Groups.

Since sales organizations are relevant for several business objects, they were discussed in a previous unit as an example of External ID Mappings. However, you must still take care of Product Groups. The following graphic illustrates the initial load sequence and object dependencies again.

You can either replicate Product Groups or manually maintain them, which also requires maintaining their External ID Mappings.

You can maintain them as follows:

• SAP Sales and Service Cloud Version 2:
  • Product Groups: Settings→Products→Product Groups
  • External ID Mappings: Settings→Integration→External ID Mapping with the Mapping Of: Product Group (Material Group ID)
• SAP S/4HANA:
  • Database Table: Transaction SE16N→T023
  • Customizing:
    • Transaction SPRO→Logistics→General→Material Master→Basic Settings→Material Types→Define Attributes of Material Types
    • Alternative Transaction: OMSF

In the demo environment, the Product Groups behave similarly to the Organizational Model. Only a small portion of the entries present in SAP S/4HANA is needed. Additionally, there are more options to divide the product hierarchy in the cloud CRM.

Therefore, the Product Groups should be manually maintained including their External ID Mappings:

1. On the Integration card, open External ID Mapping. In the drop-down for the Communication System, choose the one used for the integration with S/4HANA.
2. In the drop-down for Mapping Of, select Product Group and Material Group ID. For all material groups used during replication, enter the external value that can appear under productGroupDisplayId in the Product replication message. The product hierarchy in S4 is stored in the table T179 (transaction SE16)

The following screenshots show a comparison of the Product Groups of SAP S/4HANA on the right and SAP Sales and Service Cloud Version 2 on the left:

For a demonstration of the External ID Mapping maintenance, please refer to the lesson where functional settings were prepared.

Generally, it’s a good practice to review the system’s settings for a specific object to identify the most obvious code list dependencies.

Units of Measure – Piece and Each

The units of measure PCE (piece) and EA (each) essentially mean the same thing and can often be used interchangeably to refer to one individual unit or item.

• Piece (PCE) is recognized as a standard unit under ISO 80000-1, making it an official ISO code. This standardization helps facilitate international trade and ensures consistency across different regions and industries.
• Each (EA) is included in the UNECE (United Nations Economic Commission for Europe) code list, which provides standardized units for international trade. UNECE supports the facilitation of consistency in global business operations.

While you will typically find both codes in SAP S/4HANA, SAP Sales and Service Cloud Version 2 is initially shipped with EA only. This is a common pitfall that you may come across when replicating products for the first time and may cause a significant number of replicated products to fail due to the missing measure unit PCE.

This section is only relevant for you if the unit Piece (PCE) is used for products in your SAP S/4HANA system. You can verify this using transaction SE16 in the table MARA. Check whether there are products that use PCE in any of the unit fields, such as Base Unit (field name MEINS), Order Unit (field name BSTME), and others.

If you want to review the units of measurement definitions in your SAP S/4HANA system, use transaction CUNI and go to Units of Measure for AAAADL (no dimension) as shown in the following graphic.

To resolve the problem with the missing PCE in SAP Sales and Service Cloud Version 2, several solutions are possible:

1. Maintain Piece (PCE) in SAP Sales and Service Cloud Version 2.
2. Create a value mapping from PCE to EA.