cleanFiles/bookmap_SAP_Commerce_Cloud_Essentials_for_Develope_en-US_learning-sap-com_lsc-prod.zip (MMCP-DROPZONE) - 2024-11-21T07:42:21.000Z

Comparing Classification and Type Systems

<div id="content"><p tabindex="0">After learning about how the SAP Commerce Classification system works, it's also important for you to understand the essential difference between the classification system and the type system.</p><div class="kalturaVideoLessonWrapper"><div aria-label="This video evaluates classification system vs type system and gives each's pros and cons." class="kalturaVideoLessonContainer" data-testid="video" id="1_fz9dsus1"></div></div></div>

Classification System versus Type System

Exploring the Technical Essentials of SAP Commerce Cloud

Classification vs Type System

Now that you understand how the classification system works, you should also know the difference between the classification system and the Type System. We can use them to model similar situations, and yet, your choice will impact your project work significantly. First, product features, also known as class attributes in a classification system, are created from a classification system under classification categories. While product attributes in the Type System, are defined in the items.xml file, more specifically, product features are dynamically defined in Backoffice, and therefore no ant build or system update is involved, while any changes in the items.xml for the Type System require a rebuild, restart, and re-deployment, via system update. Product attributes are more efficient and simpler because of the direct mapping to the data model API and the corresponding database table. Product features, however, imply more cost in terms of performance, because the "classification system features" are implemented via a complex set of relations. Handling those relations consumes a lot of system resources. Furthermore, since product features are defined at run time, you can only access them by navigating the SAP Commerce API. Also, it's not easy to access product features via flexible search, because the dynamic definitions can't be known at build time. Product attributes, however, are statically defined in the Type System, meaning that they are known at build time already. In conclusion, product attributes should be used for attributes that most product items have in common, such as height or width of products, or for attributes that are Item references, for example a reference to a Media used to illustrate the product. Lastly, product features should be used for situations in which the available attributes change from time to time or for attributes that are shared by a small range of products.