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: 034
Message text: Performance obligation &1 must have exatly one main cost cond. type.
A performance obligation must always have exactly one main cost
condition type except if no cost conditions exist at all. This error
occurs, if the system detects, that at least one main cost condition
type is added to a performance obligation although another main cost
condition type already exists. Or if a main cost condition type is
deleted from a performance obligation but other non-main cost condition
types exist.
The system has stopped processing of the affected contract.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
FARR_CONTR_LIFECYCLE034
- Performance obligation &1 must have exatly one main cost cond. type. ?The SAP error message FARR_CONTR_LIFECYCLE034 indicates that there is an issue with the configuration of a performance obligation in the context of contract accounting or revenue recognition. Specifically, the error states that a performance obligation must have exactly one main cost condition type associated with it.
Cause:
This error typically arises due to one of the following reasons:
Incorrect Configuration: The performance obligation may not be configured correctly in the system. It should have exactly one main cost condition type defined, but it may have none or more than one.
Data Entry Issues: During the creation or modification of a performance obligation, the user may have inadvertently entered multiple cost condition types or left the main cost condition type blank.
Master Data Issues: The master data related to the performance obligation may not be set up correctly, leading to inconsistencies in the expected configuration.
Solution:
To resolve this error, you can follow these steps:
Check Performance Obligation Configuration:
- Navigate to the configuration settings for performance obligations in your SAP system.
- Ensure that each performance obligation has exactly one main cost condition type assigned.
Review the Cost Condition Types:
- Go to the relevant transaction (e.g., using transaction codes like
FARR
orFSP0
) to review the cost condition types associated with the performance obligation.- If there are multiple main cost condition types, determine which one should be the main type and remove the others.
Correct Data Entry:
- If the error occurred during data entry, go back to the transaction where the performance obligation was created or modified and ensure that only one main cost condition type is selected.
Consult Documentation:
- Review SAP documentation or help resources related to performance obligations and cost condition types to ensure compliance with the required setup.
Testing:
- After making the necessary changes, test the performance obligation to ensure that the error no longer occurs.
Related Information:
FARR
(Contract Accounting) and FSP0
(Manage Performance Obligations).If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a consultant who specializes in SAP contract accounting for further assistance.
Get instant SAP help. Start your 7-day free trial now.
FARR_CONTR_LIFECYCLE033
Cannot delete main price cond. type from performance obligation &1.
What causes this issue? A Performance Obligation must always have exactly one main price condition type. This error occurs if the system detects, tha...
FARR_CONTR_LIFECYCLE032
Linked performance obligation &1 cannot have a main price cond. type.
What causes this issue? A linked performance obligation (also called additional performance obligation; POB_ROLE = 'A') must never have a m...
FARR_CONTR_LIFECYCLE035
Derecognition cannot exceed recognized revenue from perf. oblig. &1.
What causes this issue? A contract change or fulfillment resulted in the derecognition of revenue (e.g. goods return). The quantity to be derecognize...
FARR_CONTR_LIFECYCLE036
Transaction price of perf. oblig. &1 cannot change from pos. to neg.
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.