How To Fix RMSL_WUI090 - Data origin &1 is invalid &2

RMSL_WUI090 - Overview

• Message type: E = Error

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

• Message number: 090

• Message text: Data origin &1 is invalid &2

What causes this issue?

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

The data origin you specified does not exist or is not valid on the key
date of the label.
A data origin in labeling can either be a recipe or a specification. You
can distinguish between the two according to the format of the message
displayed:
If the data origin is a recipe, the system indentifies it by its
Specification/Alternative/Version. (The data may be separated by other
than slashes if you have specified a different separator in the
Customizing under <ls>Recipe Development -> Recipe
-> General Settings</>.)
If the data origin is a specification, the system displays the
specification's name or identifier.

System Response

The system cannot perform the required process.

How to fix this error?

Specify a valid data origin.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

RMSL_WUI090 - Details

• The SAP error message RMSL_WUI090, which states "Data origin &1 is invalid &2," typically occurs in the context of SAP Retail or SAP S/4HANA when there is an issue with the data origin specified in a transaction or process. This error indicates that the system is unable to recognize or validate the data origin provided, which can lead to issues in data processing or reporting.
  Causes:
  
  Invalid Data Origin: The data origin specified in the transaction does not exist or is not recognized by the system.
  
  Configuration Issues: There may be configuration issues in the system related to the data origins defined in the relevant customizing settings.
  Data Integrity Issues: The data being processed may have integrity issues, such as missing or incorrect references to data origins.
  Version Mismatch: If there are different versions of data or configurations in use, it may lead to inconsistencies in data origins.
  
  Solutions:
  
  Check Data Origin: Verify the data origin specified