Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
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
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.
Due to the threat of data inconsistency, the planning scenario cannot
be activated.
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.
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.
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:
Check the key figure definition:
Correct the data type if necessary:
Check the query or report:
Transport and activation:
Key figure data types in BW:
Why type P is required:
SAP Notes and documentation:
If you need help identifying the key figure or changing its type, you can use transaction codes like RSA1 (BW Modeling) or RSRT (Query Monitor) to analyze the objects involved.
Get instant SAP help. Sign up for our Free Essentials Plan.
WXP569
Planning step &1 cannot be used for SAP BW
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
WXP568
Create RFC destination &1
What causes this issue? You want to use the SAP Business Warehouse to prepare actual data. A connection (RFC destination) to the BW system must exist...
WXP571
Aggregation behavior for key figure &1 is not "Total"
What causes this issue? You have not chosen the non-time-based aggregation behavior "Total" for key figure &V1& in planning step &a...
WXP600
*** Messages for interface usage in manual planning
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.