How To Fix RMSL_WUI390 - Calculation run returned with redundant entries

SAP Error Message - Details

• Message type: E = Error

• Message class: RMSL_WUI - Labeling Web UI: RMSL Class Messages Converted for Web UI

• Message number: 390

• Message text: Calculation run returned with redundant entries

What causes this issue?

The calculation data is inconsistent or the calculation has returned
with duplicate entries.

System Response

The system may delete the redundant results and retain one.

How to fix this error?

Check that you have not defined overlapping calculations. Maintain your
calculations and their settings in the dialog structure.
To do this, check your entries in the following Customizing activities:
<LS>Define Recipe Calculations </>under <LS>Logistics - General ->
Product Lifecycle Management (PLM) -> PLM Web User Interface -> Recipe
Development -> Recipe -> Calculations</>
<LS>Set Up Connection to Recipe Development (PLM-WUI-RCP) </>under
<LS>Logistics - General -> Product Lifecycle Management (PLM) -> PLM Web
User Interface -> Recipe Development -> Labeling</>

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

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 RMSL_WUI390 - Calculation run returned with redundant entries ?

  The SAP error message RMSL_WUI390, which states "Calculation run returned with redundant entries," typically occurs in the context of the SAP Retail Management System (RMS) or similar modules where calculations are performed on data sets, such as pricing, inventory, or sales data.
  Cause:
  The error indicates that the calculation run has produced duplicate or redundant entries in the results. This can happen due to several reasons, including:
  
  Data Duplication: The input data may contain duplicate records, leading to redundant results during the calculation.
  Configuration Issues: Incorrect configuration settings in the calculation run or the underlying data model may lead to unexpected results.
  Logic Errors: There may be issues in the logic of the calculation itself, such as incorrect formulas or conditions that do not filter out duplicates.
  Data Integrity Issues: Problems with data integrity, such as missing keys or incorrect relationships between data entities, can also lead to redundancy.
  
  Solution:
  To resolve the RMSL_WUI390 error, you can take the following steps:
  
  
  Check Input Data: Review the input data for duplicates. Ensure that the data being processed does not contain redundant entries. You can use SQL queries or data analysis tools to identify duplicates.
  
  
  Review Calculation Logic: Examine the logic used in the calculation run. Ensure that the formulas and conditions are correctly defined to avoid generating redundant results.
  
  
  Adjust Configuration Settings: Check the configuration settings related to the calculation run. Ensure that they are set up correctly to handle the data appropriately.
  
  
  Data Cleansing: If duplicates are found in the input data, consider implementing data cleansing processes to remove or consolidate duplicate records before running the calculation.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to the specific calculation run you are using. There may be known issues or additional configuration steps required.
  
  
  Testing: After making changes, run the calculation again in a test environment to ensure that the issue is resolved before applying changes to the production environment.
  
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or patches related to the RMS module or the specific calculation run you are using.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  Transaction Codes: Familiarize yourself with relevant transaction codes (e.g., SE80 for development, SE11 for data dictionary) that may help you analyze the data and configuration.
  
  If the issue persists after following these steps, consider reaching out to SAP support for further assistance.