Kontakt

Ansicht
Dokumentation

SIMG_T160M_GA_S4 - Deactivate Compatibility Check for Configuration Classes

SIMG_T160M_GA_S4 - Deactivate Compatibility Check for Configuration Classes

BAL Application Log Documentation   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.
SAP E-Book

In this Customizing activity, you can change the message category of message MH334 (Combination of config. class and charact. prof./merch. cat. not allowed) from Error Message (E) to No Message () and vice versa.

In the SAP S/4HANA system, the Error Message message category activates a compatibility check of classification and configuration data. The check is executed during the creation or reclassification of generic articles. You can prevent the execution of the compatibility check by changing the message category to No Message.

If the compatibility check is activated, message MH334 is issued when the configuration class used and the merchandise category or characteristics profile used are not compatible with regard to the assigned variant-creating characteristics. In this case, the creation or reclassification of the relevant generic article is not possible.

This check ensures compatibility when working with generic articles, which are handled differently in SAP S/4HANA compared to SAP ERP and in a scenario where it is planned to distribute generic articles between SAP S/4HANA and SAP ERP using Application Link Enabling (ALE) technology.

Functional Background:

To create a generic article in SAP ERP, you usually assign variant-creating characteristics to either a merchandise category or a characteristics profile. In SAP S/4HANA, the characteristics assigned to a configuration class are used to create generic articles.

If an SAP S/4HANA system distributes generic articles to a SAP ERP system by means of the ARTMAS IDoc, the receiving SAP ERP system cannot process the generic articles if the variant-creating characteristics are not assigned to a merchandise category or a characteristics profile. To prevent this ARTMAS inbound error situation, when a generic article is created, a compatibility check of the classification and configuration master data is performed in the sending SAP S/4HANA system. This ensures that the classification and configuration master data used in the sending system is maintained in such a way that it can be seamlessly distributed to an SAP ERP system or a compatible legacy system by using Application Link Enabling (ALE) technology. The same check is performed during reclassification when a generic article is moved to another merchandise category or a characteristics profile.

This function is required in SAP S/4HANA when generic articles are used and the generic articles, the merchandise categories, and the characteristics profiles are distributed from an SAP S/4HANA system to an SAP ERP system or a legacy system compatible to SAP ERP by using ALE.

Based on the assumption that conversion has taken place from an SAP ERP system to an SAP S/4HANA system, the old assignments of variant-creating characteristics to merchandise categories or characteristics profiles still exist and can be used for the compatibility check of generic articles as follows:

  • If characteristics profiles are not used, the variant-creating characteristics assigned to the merchandise category used must be among the variant-creating characteristics assigned to the configuration class.
  • If there is an exact match for the variant-creating characteristics, the generic article can be assigned to the merchandise category and the configuration class without any conflicts.

  • If a merchandise category provides no variant-creating characteristics or only a subset of the required variant-creating characteristics, the system creates a corresponding characteristics profile linked to the merchandise category in the background with the same name as the configuration class and with the same variant-creating characteristics assigned to it. The system also assigns the generic article to the new characteristics profile in the background.

  • If a merchandise category provides more variant-creating characteristics than the configuration class, the system cannot resolve this incompatibility automatically; another combination of merchandise category and configuration class must be chosen manually.

  • In the worst case, a new configuration class must be created that matches the lower number of variant-creating characteristics given by the merchandise category.

  • If characteristics profiles are used, the variant-creating characteristics used in the characteristics profile must be identical to the characteristics in the configuration class. The name of the characteristics profile must be the same as the name of the configuration class. If this is not the case, the system identifies an incompatibility that cannot be resolved automatically. Another combination of merchandise category, characteristics profile, and configuration class must be chosen manually.
In the worst case, a new configuration class must be created that matches the name and the number of variant-creating characteristics of the characteristics profile.

If the SAP S/4HANA system has been set up from scratch or if new merchandise categories and characteristics profiles have been created manually after conversion to SAP S/4HANA, it is no longer possible to assign variant-creating characteristics to merchandise categories or characteristics profiles. In this case, the compatibility check for generic articles works as follows:

  • If characteristics profiles are not used, the merchandise category cannot provide any variant-creating characteristics; therefore, the system creates a corresponding characteristics profile linked to the merchandise category in the background with the same name as the configuration class and with the same variant-creating characteristics assigned to it. The system also assigns the generic article to the new characteristics profile in the background.
  • By default, characteristics profiles cannot provide any variant-creating characteristics; therefore, it is not possible to use characteristics profiles even if they are intended for use as informative characteristics only.

By default, the message category is set to Error Message to ensure compatible master data management when data is transferred to an SAP ERP system or a compatible legacy system.

You can deactivate the compatibility check by setting the message category to No Message for the following reasons:

  • If you are not planning to supply an SAP ERP or a compatible legacy system with classification and generic article master data from an SAP S/4HANA system, you can configure the system in such a way that incompatible assignments of configuration classes together with merchandise categories and characteristics profiles are allowed.
  • In an ALE distribution scenario with two SAP S/4HANA systems, we recommend that you switch off the compatibility check in the sending system.
If the compatibility check is switched on, the system creates unnecessary characteristics profiles and also links the generic articles to these characteristics profile without any necessity. These unnecessary characteristics profiles cannot be removed because they are then used by the generic articles.
  • If the compatibility check is switched on by mistake and generic articles have already been created and automatically assigned to a characteristics profile and if the generic article master data will never be distributed to an SAP ERP or compatible legacy system, it is possible to reassign the generic articles to the corresponding merchandise category using the reclassification functionality (transaction WRCR). To do this, first switch off the compatibility check. After reclassification, you can the delete the unnecessary characteristics profiles by using transaction CLWH

By default, this function is enabled to support the automatic creation of configuration classes and to meet compatibility requirements. If you initially switch off this function, but need to enable it later, then compatibility can only be ensured for newly created generic articles. The old generic articles will cause issues when you try to distribute them from an SAP S/4HANA system to an SAP ERP system.






BAL_S_LOG - Application Log: Log header data   CL_GUI_FRONTEND_SERVICES - Frontend Services  
This documentation is copyright by SAP AG.

Length: 9020 Date: 20240523 Time: 161708     sap01-206 ( 247 ms )