How To Fix RMOR035 - No security price could be determined

SAP Error Message - Details

• Message type: E = Error

• Message class: RMOR - OR: Open Reporting

• Message number: 035

• Message text: No security price could be determined

Self-Explanatory Message

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.

What else can you do?

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message RMOR035 - No security price could be determined ?

  The SAP error message RMOR035, which states "No security price could be determined," typically occurs in the context of financial transactions or reporting involving securities. This error indicates that the system was unable to find a valid price for a security that is required for processing a transaction or generating a report.
  Causes:
  
  
  Missing Price Data: The most common cause is that the security does not have a price recorded in the system for the relevant date. This can happen if the price data has not been updated or if the security is new and has not yet been priced.
  
  
  Incorrect Valuation Date: The valuation date used in the transaction may not correspond to a date for which a price is available. If the date is in the future or if there is no price for that specific date, the error will occur.
  
  
  Data Source Issues: If the system relies on external data sources (like market data feeds) for pricing, any issues with those feeds (e.g., connectivity problems, data feed not being updated) can lead to this error.
  
  
  Configuration Issues: There may be configuration issues in the SAP system related to how security prices are maintained or retrieved.
  
  
  Security Not Active: The security might not be active or might have been deactivated in the system, leading to the inability to retrieve its price.
  
  
  Solutions:
  
  
  Check Price Data: Verify that the security has a price recorded in the system for the relevant date. You can do this by checking the price history or market data for the security.
  
  
  Update Prices: If the price is missing, update the security price in the system. This can often be done through transaction codes like MR1M (for market price) or through the relevant pricing maintenance transactions.
  
  
  Review Valuation Date: Ensure that the valuation date used in the transaction is correct and corresponds to a date for which a price is available.
  
  
  Check Data Sources: If the system relies on external data sources, check the connectivity and ensure that the data feeds are functioning correctly. You may need to contact your data provider if there are issues.
  
  
  Configuration Review: Review the configuration settings related to security pricing in the SAP system. Ensure that all necessary settings are correctly configured.
  
  
  Activate Security: If the security is inactive, you may need to reactivate it in the system.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE38 (for executing reports), MR1M, or OMN1 (for managing securities).
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP Notes can provide additional context or solutions.
  Documentation: Review SAP documentation related to financial transactions and securities management for best practices and troubleshooting steps.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP support team or a technical consultant who specializes in SAP financial modules.