Do you have any question about this error?
Message type: E = Error
Message class: FARR_CONTRACT_MAIN - Revenue Accounting: Contract Management
Message number: 060
Message text: Time-based POB &1 cannot have linked POBs.
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_MAIN060
- Time-based POB &1 cannot have linked POBs. ?The SAP error message FARR_CONTRACT_MAIN060 indicates that there is an issue with a time-based Purchase Order (POB) that cannot have linked POBs. This typically occurs in the context of contract management or asset accounting within SAP, particularly when dealing with time-based contracts or agreements.
Cause:
The error arises when you attempt to link a time-based POB to another POB that is not compatible with the time-based nature of the original POB. This can happen due to several reasons:
- Incompatible POB Types: The POB you are trying to link may not be of the same type or may not support linking with time-based POBs.
- Contract Configuration: The configuration settings for the contract may not allow for linked POBs, especially if the main POB is defined as time-based.
- Data Integrity Issues: There may be inconsistencies or errors in the data that prevent the linking of POBs.
Solution:
To resolve this error, you can take the following steps:
Check POB Types: Ensure that the POB you are trying to link is compatible with the time-based POB. Review the definitions and types of both POBs.
Review Contract Settings: Go to the contract settings and verify if the configuration allows for linked POBs. You may need to adjust the settings or create a new POB that is compatible.
Data Validation: Check for any data integrity issues. Ensure that all required fields are filled out correctly and that there are no inconsistencies in the data.
Consult Documentation: Refer to SAP documentation or help resources for specific guidelines on handling time-based POBs and their linking rules.
SAP Notes and Support: If the issue persists, check for any relevant SAP Notes that may address this specific error. You can also reach out to SAP support for assistance.
Related Information:
FARR
for asset accounting and contract management.By following these steps, you should be able to identify the root cause of the error and implement a suitable solution.
Get instant SAP help. Start your 7-day free trial now.
FARR_CONTRACT_MAIN059
POB &1 is leading and also has a leading POB. This is not allowed.
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_MAIN058
Start date of time-based performance obligation &1 is empty
What causes this issue? Performance obligation &v1& has an event type that is time-based, but it does not have a start date.System Response ...
FARR_CONTRACT_MAIN061
Compound POB &1 has a compound/non-distinct POB as its higher-level POB
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_MAIN062
Distinct POB &1 has a compound/non-distinct POB as its higher-level POB
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.