Do you have any question about this error?
Message type: E = Error
Message class: FARR_CONTRACT_MAIN - Revenue Accounting: Contract Management
Message number: 813
Message text: The RoR start date of perf. obl. &1 not updated; posting already occurred
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.
FARR_CONTRACT_MAIN813
- The RoR start date of perf. obl. &1 not updated; posting already occurred ?The SAP error message FARR_CONTRACT_MAIN813 indicates that there is an issue with the RoR (Revenue Recognition) start date of a performance obligation in a contract. Specifically, the error states that the RoR start date for the performance obligation has not been updated because a posting has already occurred. This typically happens in the context of revenue recognition processes in SAP, particularly when dealing with contracts and performance obligations.
Cause:
- Posting Already Occurred: The primary cause of this error is that a posting related to the performance obligation has already been made. This means that the system has already recognized revenue or made some financial entries that are tied to the performance obligation.
- Date Mismatch: The RoR start date may not align with the current state of the contract or the performance obligation, leading to inconsistencies.
- Configuration Issues: There may be configuration settings in the SAP system that are not aligned with the business processes or the specific contract terms.
Solution:
- Check Posting History: Review the posting history for the performance obligation to understand what has been posted and when. This will help determine if the RoR start date can be updated or if it needs to remain as is.
- Adjust RoR Start Date: If the RoR start date needs to be updated, you may need to reverse or adjust the previous postings related to that performance obligation. This can be complex and may require careful handling to ensure compliance with accounting standards.
- Consult with Finance Team: Work with your finance or accounting team to understand the implications of changing the RoR start date and to ensure that any changes made are in line with accounting policies.
- Review Configuration: Check the configuration settings in SAP related to revenue recognition and performance obligations. Ensure that they are set up correctly to avoid similar issues in the future.
- SAP Notes and Support: Look for any relevant SAP Notes that may address this specific error or provide guidance on handling it. If necessary, consider reaching out to SAP support for assistance.
Related Information:
By following these steps, you should be able to address the error and ensure that your revenue recognition processes are functioning correctly.
Get instant SAP help. Start your 7-day free trial now.
FARR_CONTRACT_MAIN812
Unit-distinct cannot be marked for for Perc-of-completion perf. oblig. &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FARR_CONTRACT_MAIN811
Unit-distinct cannot be marked for compound and non-distinct perf. ob. &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FARR_CONTRACT_MAIN814
Field unit-distinct should be Distinct or Non-distinct for perf. ob. &1
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FARR_CONTRACT_MAIN815
Compound perf. ob. &1 should be 'Not Unit Distinct'
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.