How To Fix RY355 - Volatility type & not maintained

RY355 - Overview

• Message type: E = Error

• Message class: RY - Messages for RM Basis

• Message number: 355

• Message text: Volatility type & not maintained

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 RY355 - Volatility type & not maintained ?

  The SAP error message RY355, which states "Volatility type & not maintained," typically occurs in the context of SAP's Financial Supply Chain Management (FSCM) or when dealing with derivatives and financial instruments in the SAP system. This error indicates that a specific volatility type has not been defined or maintained in the system, which is necessary for certain calculations or processes related to financial instruments.
  
  Cause:
  
  Missing Configuration: The volatility type referenced in the error message has not been set up in the system. This could be due to a lack of configuration in the relevant customizing settings.
  Incorrect Data Entry: The volatility type may have been incorrectly entered in the transaction or master data, leading to the system not recognizing it.
  Transport Issues: If the configuration was recently transported from another system (e.g., from development to production), it may not have been properly transported or activated.
  
  
  Solution:
  
  
  Maintain Volatility Type:
  
  Go to the relevant customizing transaction