Do you have any question about this error?
Message type: E = Error
Message class: FARR_CONTRACT_MAIN - Revenue Accounting: Contract Management
Message number: 765
Message text: Non-distinct POB &1 cannot have event type CI and value relevant TRUE
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
The non-distinct performance obligation cannot be defined as:Error message extract from SAP system. Copyright SAP SE.
FARR_CONTRACT_MAIN765
- Non-distinct POB &1 cannot have event type CI and value relevant TRUE ?The SAP error message FARR_CONTRACT_MAIN765 indicates that there is an issue with a non-distinct Profitability Object (POB) in a contract that is trying to have an event type of "CI" (which typically stands for "Contract Item") while also being marked as "value relevant" (TRUE). This situation is not allowed in SAP's configuration for contract management.
Cause:
- Non-Distinct POB: The error arises because the Profitability Object (POB) is defined as non-distinct, meaning it does not have unique identifiers for different instances. In this case, the system cannot differentiate between multiple instances of the same POB.
- Event Type CI: The event type "CI" is used for contract items that are expected to have value-related postings. If the POB is non-distinct, it cannot have value-related postings, leading to this error.
- Configuration Issues: There may be a configuration issue in the contract settings or the way the POB is defined in the system.
Solution:
- Check POB Configuration: Review the configuration of the Profitability Object in the system. Ensure that it is set up correctly and that it is appropriate for the type of transactions you are processing.
- Change POB to Distinct: If possible, consider changing the POB from non-distinct to distinct. This will allow the system to handle multiple instances of the POB correctly and enable value-related postings.
- Review Event Type Settings: Ensure that the event type settings for the contract item are appropriate. If the POB is non-distinct, you may need to change the event type to one that is compatible with non-distinct POBs.
- Consult Documentation: Refer to SAP documentation or help resources for specific guidelines on configuring POBs and event types in your version of SAP.
- Contact SAP Support: If the issue persists after checking the configuration, consider reaching out to SAP support for further assistance.
Related Information:
By following these steps, you should be able to resolve the error and ensure that your contract management processes function correctly within SAP.
Get instant SAP help. Start your 7-day free trial now.
FARR_CONTRACT_MAIN764
Compound POB &1 cannot have event type CI and value relevant TRUE
Diagnosis The system issues an error message and will not allow you to continue with this transaction until the error is resolved. The compound perf...
FARR_CONTRACT_MAIN763
High/low level BOM POB &1 cannot have event type CI & value relevant TRUE
Diagnosis The system issues an error message and will not allow you to continue with this transaction until the error is resolved. The high and low ...
FARR_CONTRACT_MAIN766
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_MAIN767
Linked POB &1 has been soft-deleted. The leading POB was &2.
What causes this issue? Linked POBs are deleted, if the corresponding BRF+ settings in table DT_PROCESS_POB_ADD are removed.System Response The syst...
Click on this link to search all SAP messages.