How To Fix WXP570 - Key figure &1 is not of type P -> BW read is not supported

WXP570 - Overview

• Message type: E = Error

• Message class: WXP - Retail Planning

• Message number: 570

• Message text: Key figure &1 is not of type P -> BW read is not supported

What causes this issue?

You have assigned key figure &V1& in the BW configuration to an
InfoObject. You have therefore indicated that you want to this key
figure to be filled when actual data is read from the connected BW
System. The key figure has the internal type '&V2&'. This type is,
however, not supported by the read interface. Reading actual data for
this key figure would result in the data not being saved completely in
the database.

System Response

Due to the threat of data inconsistency, the planning scenario cannot
be activated.

How to fix this error?

Delete the assignment of key figure &V1& to the BW InfoObject or select
the internal type 'P' for the InfoObject. Key figures of type DEC
(decimal numbers without unit), CURR (currency key figures) or QUAN
(quantity key figures), for example, have this type.

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 WXP570 - Key figure &1 is not of type P -> BW read is not supported ?

  The SAP error message:
  WXP570 Key figure &1 is not of type P -> BW read is not supported
  Explanation / 
  Cause:
  This error occurs in SAP BW (Business Warehouse) when a key figure used in a query or report is expected to be of type P (Packed Number), but the actual key figure is of a different data type. The BW system expects numeric key figures to be of type P (packed number) for certain operations, especially when reading or processing data. If the key figure is defined as a different type (e.g., integer, float, or character), the system cannot process it correctly, leading to this error.
  In other words, the key figure &1 (where &1 is replaced by the actual key figure technical name) is not defined as a packed number, which is mandatory for BW read operations.
  Common scenarios where this happens:
  
  When a key figure is created or modified with an incorrect