Differences

This shows you the differences between two versions of the page.

adminhelp:crmintegrationsetup:sap_variant_configuration_integration:sap_vc_integration_overview [2018/11/20 17:11]
atadic
adminhelp:crmintegrationsetup:sap_variant_configuration_integration:sap_vc_integration_overview [2018/11/30 09:37] (current)
atadic
Line 13: Line 13:
  
 Products that are imported from ERP in this way become simple products in SAP CPQ and are placed in the preselected category. If there is a product hierarchy in ERP, the hierarchy will also be replicated in SAP CPQ as a category, which means that one product will belong to two categories -- the category it belongs to in ERP and the preselected category in SAP CPQ.  If categories that exist in ERP (also known as hierarchy) do not exist in SAP CPQ, they will be replicated in SAP CPQ. On the other hand, the [[adminhelp:crmintegrationsetup:sap_variant_configuration_integration:defining_preselected_category|preselected category]] needs to be manually created.\\ Products that are imported from ERP in this way become simple products in SAP CPQ and are placed in the preselected category. If there is a product hierarchy in ERP, the hierarchy will also be replicated in SAP CPQ as a category, which means that one product will belong to two categories -- the category it belongs to in ERP and the preselected category in SAP CPQ.  If categories that exist in ERP (also known as hierarchy) do not exist in SAP CPQ, they will be replicated in SAP CPQ. On the other hand, the [[adminhelp:crmintegrationsetup:sap_variant_configuration_integration:defining_preselected_category|preselected category]] needs to be manually created.\\
-If products imported from ERP have product versions, all these versions will be active. Product versions for ERP products are managed by SAP Product Configuration, and they cannot be added or deleted in SAP CPQ. Product versions differ in effective date.\\ 
  
 Moreover, it is also possible to quantify products by entering an ISO code containing up to three characters in the **Unit of Measure** field in **Products** > a particular product > **Definition** (for example, EA, PCE or PK).\\ Moreover, it is also possible to quantify products by entering an ISO code containing up to three characters in the **Unit of Measure** field in **Products** > a particular product > **Definition** (for example, EA, PCE or PK).\\
  
-Simple products previously imported from ERP get their attributes and new product display type via knowledgebase synchronization. During the first synchronization, just like in knowledgebase, attributes are assigned to a specific characteristic group, which is a product tab in SAP CPQ.  With every new synchronizationnew attributes will be added, but they will not be assigned to any product tab in SAP CPQ. This means that administrators will have to reorder attributes and assign them to appropriate product tabs by using the drag-and-drop functionality of the configuration layout in SAP CPQ.\\  +Simple products previously imported from ERP get their attributes and new product display type via knowledgebase synchronization. During the first knowledgebase synchronization, attributes are assigned to a specific characteristic group, which is a product tab in SAP CPQ.\\  
 +**Note**: SAP CPQ product [[adminhelp:generalsettings:tabs|tabs]] are globally definedwhich means that any change to tab name in SAP CPQ will affect all products the tab is included in.\\
  
-Additionally, prices for simple products are sent from ERP to SCPI over IDocs. SCPI then calls SAP CPQ SOAP API for pricing and loads prices into SAP CPQ pricebooks, which is why pricebooks need to be manually created in SAP CPQ. Moreover, updated prices in ERP will be synchronized with pricebooks in SAP CPQ.\\+----
  
-Furthermore, as illustrated in the image above, knowledgebase synchronization is initiated from SAP CPQ. Knowledgebase synchronization converts simple products to configurable products by calling SAP Product Configuration to get attribute namedescription and valueAs previously explained on the [[adminhelp:crmintegrationsetup:sap_variant_configuration_integration:connecting_sap_cpq_to_sap_product_configuration|SAP Product Configuration integration]] pageknowledgebase synchronization is run on a daily basisIn case the synchronization fails, the administrator is notified via emailand the job will be rescheduled for execution during the next synchronizationThe job will get information about products that were created or updated in the last 24 hours +**Example**: In SAP CPQ, there is a **Hardware** tabThe said tab is added to the following products: //Monitor////Keyboard// and //Mouse//After some timeyou decide to change the name of the **Hardware** tab to **Gaming**Once the tab is renamed, the changes are visible in the aforementioned products, that is, the **Gaming** tab is now a part of //Monitor//, //Keyboard// and //Mouse//.\\ 
-Moreover, product rules are executed only in SAP Product Configuration.\\ + 
 +---- 
 + 
 +With every new synchronization, new attributes will be added, but they will not be assigned to any product tab in SAP CPQThis means that administrators will have to reorder attributes and assign them to appropriate product tabs by using the drag-and-drop functionality of the configuration layout in SAP CPQ.\\   
 + 
 +Additionally, prices for simple products are sent from ERP to SCPI over IDocs. SCPI then calls SAP CPQ SOAP API for pricing and loads prices into SAP CPQ pricebooks, which is why pricebooks need to be manually created in SAP CPQ. Moreover, updated prices in ERP will be synchronized with pricebooks in SAP CPQ.\\
  
 +Furthermore, as illustrated in the image above, knowledgebase synchronization is initiated from SAP CPQ. Depending on the knowledgebase structure, the synchronization converts simple products to either configurable products or parent-child products by calling SAP Product Configuration to get attribute name, description and value. As previously explained on the [[adminhelp:crmintegrationsetup:sap_variant_configuration_integration:connecting_sap_cpq_to_sap_product_configuration|SAP Product Configuration integration]] page, knowledgebase synchronization is run on a daily basis. In case the synchronization fails, the administrator is notified via email, and the job will be rescheduled for execution during the next synchronization. The job will get information about products that were created or updated in the last 24 hours. Additionally, every change made to SAP ERP will result in a new knowledgebase version, which in turn will lead to a new product version in SAP CPQ. Product versions cannot be added or deleted in SAP CPQ. Additionally, product versions differ in effective date.\\
 +Moreover, product rules are executed only in SAP Product Configuration.\\
 +\\ 
 Prices for configurable products are synchronized in real time from SAP Product Configuration, and are displayed in the responder. Prices on attribute values in the configurator are not supported. Prices for configurable products are synchronized in real time from SAP Product Configuration, and are displayed in the responder. Prices on attribute values in the configurator are not supported.
  
You are here: SAP CPQ Online HelpAdmin Page HelpCRM Integration SetupSAP Variant Configuration IntegrationSAP VC Integration Overview