How To Fix UPB168 - No reference row is specified in row &1 of key figure scheme

SAP Error Message - Details

• Message type: E = Error

• Message class: UPB - BPS: Balance sheet planning messages

• Message number: 168

• Message text: No reference row is specified in row &1 of key figure scheme

What causes this issue?

In the key figure scheme, you have defined a step as relative or
calculating totals. However, you have not entered which other
calculation steps the current step refers to.

System Response

You can only continue processing when you have made the necessary
entries.

How to fix this error?

In the columns <ZH>From</> or <ZH>To</>, enter one or several of the
previous steps which should be included in the calculation of the
valuation element of the current step.

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 UPB168 - No reference row is specified in row &1 of key figure scheme ?

  The SAP error message UPB168, which states "No reference row is specified in row &1 of key figure scheme," typically occurs in the context of SAP Business Planning (BPC) or SAP Integrated Business Planning (IBP) when working with key figure schemes. This error indicates that a specific row in the key figure scheme is missing a reference row, which is necessary for the calculations or data processing to occur correctly.
  
  Cause:
  
  Missing Reference Row: The key figure scheme is designed to use reference rows for calculations or aggregations, and if a row is defined without a corresponding reference row, this error will be triggered.
  
  Configuration Issues: There may be a misconfiguration in the key figure scheme setup, where the relationships between rows are not properly defined.
  Data Integrity Issues: If the data model has been altered or if there are inconsistencies in the data, it may lead to this error.
  
  
  Solution:
  
  
  Check Key Figure Scheme Configuration:
  
  Go