How To Fix UCT8035 - Mapping rule for &1, row &2: Use source field or constant, but not both

SAP Error Message - Details

• Message type: E = Error

• Message class: UCT8 - Message class for UCT8(mapping)

• Message number: 035

• Message text: Mapping rule for &1, row &2: Use source field or constant, but not both

What causes this issue?

The mapping rule for target field &V1& contains a move in row &V2&. In
the details of the move, a row has been defined that contains both a
constant and a source field. However, a row must contain only one of the
two.

System Response

The settings cannot be saved. The system issues this error message.

How to fix this error?

In the details of the move, find the row that contains both a constant
and a source field/attribute. Then delete one of the two. Alternatively,
cut and paste the constant or the source field/attribute to a different
row in order to concatenate the two.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message UCT8035 - Mapping rule for &1, row &2: Use source field or constant, but not both ?

  The SAP error message UCT8035 indicates that there is an issue with a mapping rule in a data transformation process, specifically in the context of SAP Data Services or similar ETL (Extract, Transform, Load) tools. The error message states: "Mapping rule for &1, row &2: Use source field or constant, but not both." This means that in the specified mapping rule, both a source field and a constant value have been used simultaneously, which is not allowed.
  
  Cause:
  The error occurs when:
  
  A mapping rule is defined in such a way that it attempts to use both a source field (a field from the input data) and a constant value (a fixed value) in the same mapping expression.
  This is typically a configuration or design error in the data transformation logic.
  
  
  Solution:
  To resolve this error, you need to modify the mapping rule to ensure that only one of the two options is used:
  
  Use Only a