Do you have any question about this error?
Message type: E = Error
Message class: FARR_CONTR_LIFECYCLE - Message from Contract Lifecyle (RAR 2.0 Object Model)
Message number: 085
Message text: Start date missing for time-based POB &1; cannot calc. scheduled revenue.
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_CONTR_LIFECYCLE085
- Start date missing for time-based POB &1; cannot calc. scheduled revenue. ?The SAP error message FARR_CONTR_LIFECYCLE085 indicates that there is a missing start date for a time-based Profitability Object (POB) in the context of revenue recognition. This error typically arises in the SAP Revenue Accounting and Reporting (RAR) module when the system attempts to calculate scheduled revenue but cannot do so due to the absence of a required start date.
Cause:
- Missing Start Date: The primary cause of this error is that the time-based POB does not have a defined start date. This is essential for calculating scheduled revenue over a specific period.
- Incorrect Configuration: There may be issues with the configuration of the POB or the related revenue recognition settings.
- Data Entry Errors: During the creation or modification of the POB, the start date may not have been entered or was inadvertently deleted.
Solution:
Check POB Configuration:
- Navigate to the relevant POB in the SAP system.
- Verify that the start date is correctly entered in the POB settings.
- If the start date is missing, enter the appropriate start date.
Review Related Documents:
- Check any related sales orders, contracts, or billing documents to ensure that they are correctly linked to the POB and that all necessary dates are populated.
Data Consistency Check:
- Run a consistency check for the POB to identify any other missing or incorrect data that may affect revenue calculation.
Consult Documentation:
- Refer to SAP documentation or help resources for guidance on setting up time-based POBs and ensuring all required fields are populated.
Testing:
- After making the necessary corrections, test the revenue calculation again to ensure that the error has been resolved.
Related Information:
If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a technical consultant who specializes in SAP RAR for further assistance.
Get instant SAP help. Start your 7-day free trial now.
FARR_CONTR_LIFECYCLE084
Quantity of performance obligation &1 turned positive.
What causes this issue? Performance obligation &v1& was created with a negative quantity. With the current contract change it would turn posi...
FARR_CONTR_LIFECYCLE083
Quantity of performance obligation &1 turned negative.
What causes this issue? Performance obligation &v1& was created with a positive quantity. With the current contract change it would turn nega...
FARR_CONTR_LIFECYCLE086
Manual POB &1 cannot have a main price condition type.
What causes this issue? A manual performance obligation cannot have a main price condition type. This error occurs if the system detects, that a main...
FARR_CONTR_LIFECYCLE087
POB &1: Delivered quantity cannot be negative.
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.