Do you have any question about this error?
Message type: E = Error
Message class: RY - Messages for RM Basis
Message number: 086
Message text: Start dates of the terms of the elementary trans. are not ascending (&1)
The start of the term of elementary transaction number &V1& is earlier
than the start of the term of the previous elementary transaction.
However, the start of the term of this elementary transaction must be
after that of the previous elementary transaction.
<ZH>Note:</> The system determines the number of the elementary
transaction for a generic transaction (transaction RCA00) by assigning
numbers, starting with 1, on each level of the hierarchy tree, starting
from the top and working downwards. In the external data transfer, this
number matches the NGIDNR, the sequential number for a GID in the FGET.
Example
Number,, Tree
1,,,, Elementary transaction (top level)
2,, ,, |_ Elementary transaction (second level)
4,,,, |_Elementary transaction (third level)
5,,,, |_Elementary transaction (third level)
7,,,, |_Elementary transaction (fourth level)
3,,,, |_ Elementary transaction (second level)
6,,,, |_Elementary transaction (third level)
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Correct your entry.
Error message extract from SAP system. Copyright SAP SE.
RY086
- Start dates of the terms of the elementary trans. are not ascending (&1) ?The SAP error message RY086 indicates that there is an issue with the start dates of the terms of the elementary transaction not being in ascending order. This typically occurs in the context of financial transactions, such as when dealing with payment terms, installment plans, or similar configurations in SAP.
Cause:
The error arises when the system detects that the start dates of the terms are not arranged in a sequential order. For example, if you have multiple terms with start dates, they should be organized from the earliest date to the latest date. If any term has a start date that precedes a term that is supposed to come after it, the system will throw this error.
Solution:
To resolve this error, you should:
Review the Terms: Check the terms associated with the elementary transaction. Look for the start dates of each term.
Correct the Order: Ensure that the start dates are in ascending order. If you find any terms that are out of order, adjust their start dates accordingly.
Re-enter Data: If necessary, you may need to delete and re-enter the terms to ensure they are correctly ordered.
Validation: After making the changes, validate the transaction again to ensure that the error has been resolved.
Related Information:
F-28
, F-32
, or others related to financial transactions.If the issue persists after following these steps, consider reaching out to your SAP support team or consulting with an SAP expert for further assistance.
Get instant SAP help. Start your 7-day free trial now.
RY085
Start of term &1 is before "Notification By" date of previous transaction
What causes this issue? The start of the term of elementary transaction number &V1& is earlier than the "Notification By" date of t...
RY084
Notification By fld of elem. trans. does not have ascending values (&1)
What causes this issue? The 'Notification By' date of elementary transaction &V1& is before the 'Notification By' date of...
RY087
Enter start of term for American-style exercising of option (&1)
What causes this issue? For options with American exercise category, the start of the term is the same as the notification period. The start of the n...
RY089
The underlying of a Bermuda option cannot have an underlying itself
What causes this issue? The hierarchy for a Bermuda option is restrictive. In a Bermuda option hierarchy, under each Bermuda option there can be only...
Click on this link to search all SAP messages.