How To Fix NRSCNV320 - No IOBJ of type UNI selected/available. Key figure &1 cannot be added.

NRSCNV320 - Overview

• Message type: E = Error

• Message class: NRSCNV - Message class

• Message number: 320

• Message text: No IOBJ of type UNI selected/available. Key figure &1 cannot be added.

What causes this issue?

You tried to add a key figure of type AMO or QUA to the InfoCube. The
key figure comes with an InfoObject of type UNI which is not available
in either the InfoCube nor yet added by an operation.

System Response

The operation cannot be added to the remodeling rule.

How to fix this error?

Create a new operation in order to add the required InfoObject of type
UNI to the InfoCube before creating an operation to add the key figure.

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 NRSCNV320 - No IOBJ of type UNI selected/available. Key figure &1 cannot be added. ?

  The SAP error message NRSCNV320 indicates that there is an issue with the selection of InfoObjects (IOBJs) in a query or report, specifically that no InfoObject of type "UNI" (which typically refers to a characteristic or key figure) is available for the key figure specified in the error message. This can occur in various contexts, such as when working with SAP BW (Business Warehouse) or SAP HANA.
  
  Cause:
  
  Missing InfoObject: The key figure you are trying to use in your query or report is not associated with any available InfoObject of type UNI.
  Incorrect Query Design: The query may be incorrectly designed, leading to the selection of a key figure that does not have a corresponding InfoObject.
  Data Model Issues: There may be issues with the underlying data model, such as missing or inactive InfoObjects.
  Authorization Issues: The user may not have the necessary authorizations to access the InfoObject.
  
  
  Solution:
  
  Check InfoObjects: Verify that the InfoObject associated