Do you have any question about this error?
Message type: E = Error
Message class: FARR_CONTRACT_MAIN - Revenue Accounting: Contract Management
Message number: 761
Message text: Virtual compound POB of POB &1 cannot have CI event type.
The problem occurs when the following criteria are met:
The compound performance obligation is derived in BRFplus.
Noted that a virtual compound performance obligation is the compound
performance obligation derived in BRFplus instead passed from sender
components.
The compound performance obligation is handled with simplified invoice
process.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Change the event type of the virtual compound performance obligation
from CI to other event types.
Error message extract from SAP system. Copyright SAP SE.
FARR_CONTRACT_MAIN761
- Virtual compound POB of POB &1 cannot have CI event type. ?The SAP error message FARR_CONTRACT_MAIN761 typically occurs in the context of contract management within the SAP system, particularly when dealing with the management of virtual compounds or POBs (Project-Oriented Business). This error indicates that a virtual compound POB cannot have a CI (Contract Item) event type associated with it.
Cause:
The error is generally caused by one of the following reasons:
- Incorrect Configuration: The system is configured in such a way that it does not allow certain event types for virtual compounds.
- Data Entry Error: There may be an incorrect entry or selection made while trying to create or modify a contract item.
- Business Logic Restrictions: The business rules defined in the system may restrict the use of CI event types for virtual compounds.
Solution:
To resolve this error, you can take the following steps:
Check Configuration:
- Review the configuration settings for contract management in your SAP system. Ensure that the settings allow the use of CI event types for the specific POB you are working with.
- Consult with your SAP Basis or configuration team to verify if any changes are needed.
Review Data Entry:
- Double-check the entries made while creating or modifying the contract. Ensure that the correct event type is selected for the POB.
- If you are using a specific transaction code, ensure that you are following the correct process as per the business requirements.
Consult Documentation:
- Refer to the SAP documentation or help files related to contract management and POBs. This may provide insights into the allowed configurations and event types.
Contact SAP Support:
- If the issue persists after checking the configuration and data entries, consider reaching out to SAP support for further assistance. They may provide patches or updates if this is a known issue.
Testing:
- If changes are made to the configuration or data, conduct thorough testing to ensure that the error does not reoccur and that the system behaves as expected.
Related Information:
FARR
(for contract management) and others that may be involved in the process.By following these steps, you should be able to identify the cause of the error and implement a suitable solution.
Get instant SAP help. Start your 7-day free trial now.
FARR_CONTRACT_MAIN760
-------------End of Used for Transition----------------------
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_MAIN759
&1 rows have been deleted from change type table.
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_MAIN762
Contract &1 Pob &2 has inconsistent inv amt: &3 and inv_delta_amt: &4.
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_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 ...
Click on this link to search all SAP messages.