How To Fix EHPRC_CPM_EXPORT050 - Generation variant &1 uses normalization &2 with re rollup

EHPRC_CPM_EXPORT050 - Overview

• Message type: E = Error

• Message class: EHPRC_CPM_EXPORT - Export Messages

• Message number: 050

• Message text: Generation variant &1 uses normalization &2 with re rollup

What causes this issue?

The generation variant &V1& uses the normalization &V2& with rollup.
This means, the check is executed using the normalized data (without
saving the result) and the check results are passed upwards to the
highest product. However, this is only permitted when the export format
supports only one regulatory list.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Reset the rollup flag for normalization or choose another normalization
for the generation variant.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message EHPRC_CPM_EXPORT050 - Generation variant &1 uses normalization &2 with re rollup ?

  The SAP error message EHPRC_CPM_EXPORT050 typically relates to issues encountered during the generation of a variant in the context of the SAP EHPRC (Environment, Health, and Safety) module, particularly when dealing with normalization and rerollup processes.
  
  Cause:
  The error message indicates that the generation variant you are trying to use is configured to utilize a normalization process that is incompatible with the rerollup operation. This can happen due to several reasons:
  
  
  Configuration Issues: The variant may not be properly configured to handle the normalization and rerollup together.
  Data Inconsistencies: There may be inconsistencies in the data that prevent the normalization process from being executed correctly.
  Missing Parameters: Required parameters for normalization or rerollup may not be set or are incorrectly defined.
  
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Variant Configuration:
  
  Review the configuration of the generation variant (&1) to ensure that it is set up correctly for normalization (&2) and rerollup.
  Make sure that the