Do you have any question about this error?
Message type: E = Error
Message class: FARR_CONTRACT_MAIN - Revenue Accounting: Contract Management
Message number: 752
Message text: No new main cond type when deleting old main cond type &1 on POB &2.
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_MAIN752
- No new main cond type when deleting old main cond type &1 on POB &2. ?The SAP error message FARR_CONTRACT_MAIN752 typically occurs in the context of contract management within the SAP system, particularly when dealing with condition types in a contract. This error indicates that there is an attempt to delete an old main condition type, but there is no new main condition type defined for the contract.
Cause:
The error arises due to the following reasons:
- Missing Main Condition Type: When you try to delete an existing main condition type, the system expects that a new main condition type is defined. If there is no new main condition type specified, the system cannot proceed with the deletion.
- Contract Configuration Issues: There may be issues with the configuration of the contract or the condition types associated with it.
- Data Inconsistencies: There might be inconsistencies in the data related to the contract or the condition types.
Solution:
To resolve this error, you can take the following steps:
Define a New Main Condition Type:
- Before deleting the old main condition type, ensure that a new main condition type is defined for the contract. You can do this by navigating to the relevant transaction in SAP and specifying the new main condition type.
Check Contract Configuration:
- Review the configuration settings for the contract to ensure that all necessary condition types are correctly set up. This may involve checking the condition type settings in the customizing settings of SAP.
Review Condition Records:
- Check the condition records associated with the contract to ensure that they are correctly maintained. You may need to adjust or create new condition records as necessary.
Consult Documentation:
- Refer to SAP documentation or help resources for specific guidance on managing condition types in contracts. This can provide insights into best practices and troubleshooting steps.
Contact SAP Support:
- If the issue persists after trying the above steps, consider reaching out to SAP support for further assistance. They can provide more detailed insights based on your specific system configuration and data.
Related Information:
ME33K
(Display Contract) or ME31K
(Create Contract) to manage contracts and condition types.By following these steps, you should be able to resolve the error and manage your contract condition types effectively.
Get instant SAP help. Start your 7-day free trial now.
FARR_CONTRACT_MAIN751
Currency key of contract &1 is different from what is configured in IMG.
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_MAIN750
The amount of POB &1 (condition &4) in local currency &2 &3 cannot be 0.
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_MAIN753
Invoice quantity is zero in invoice item &1 for quantity based POB &2
What causes this issue? For a delivery related invoice, its quantity cannot be zero while its invoice amount is not zero.System Response Invoice pro...
FARR_CONTRACT_MAIN754
POB &1 has SSP &2. This value must not 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.