Do you have any question about this error?
Message type: E = Error
Message class: RSCUR - Texts for Quantities and Currencies
Message number: 030
Message text: Parameter row &1; source key figure is not of type CURR
Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.
To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.
Unfortunately, there isn't any extra information in this error notice.
First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).
Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.
You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.
RSCUR030
- Parameter row &1; source key figure is not of type CURR ?The SAP error message RSCUR030 indicates that there is an issue with a parameter row in a query or report where the source key figure is expected to be of type "CURR" (currency), but it is not. This typically occurs in the context of SAP BW (Business Warehouse) or SAP BI (Business Intelligence) when working with queries that involve currency key figures.
Cause:
- Incorrect Data Type: The source key figure that you are trying to use in your query is not defined as a currency key figure in the InfoObject settings. It may be defined as a different type, such as a number or a text.
- Modeling Issues: There may be issues in the data model where the key figure is not properly set up to handle currency values.
- Query Design: The query might be incorrectly designed, where a non-currency key figure is being used in a context that requires a currency key figure.
Solution:
Check InfoObject Definition:
- Go to the InfoObject in the SAP BW modeling environment.
- Verify that the key figure is defined as a currency key figure. If it is not, you may need to create a new currency key figure or modify the existing one.
Modify Query:
- Open the query in the Query Designer.
- Check the key figures being used in the query. Ensure that the key figure causing the error is indeed a currency key figure.
- If necessary, replace the non-currency key figure with a valid currency key figure.
Data Source Validation:
- Ensure that the data source (e.g., InfoProvider) from which the key figure is being pulled is correctly set up to provide currency data.
- Check the transformation rules and ensure that the data is being loaded correctly.
Testing:
- After making the necessary changes, test the query again to see if the error persists.
Related Information:
If the issue persists after following these steps, it may be beneficial to consult with your SAP BW administrator or a technical consultant who can provide deeper insights into the specific configuration of your SAP environment.
Get instant SAP help. Start your 7-day free trial now.
RSCUR029
Parameter row &1; source key figure &2 is not contained in data object
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RSCUR028
Parameter row &1; currency translation type is initial
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RSCUR031
Parameter row &1; target key figure &2 not contained in data object
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
RSCUR032
Parameter row &1; target key figure is not of type CURR
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.