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: 134
Message text: Revenue up to current period is not transferred for contract &3.
Revenue for contract &v3& has not been transferred up to (and including)
the period &v1& and fiscal year &v2& of the effective date of contract
combination.
Contract combination is not possible for contract &v3&.
Run program 'Transfer Revenue' for contract &v3& up to period &v1& where
revenue occurred.
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_LIFECYCLE134
- Revenue up to current period is not transferred for contract &3. ?The SAP error message FARR_CONTR_LIFECYCLE134 indicates that there is an issue with the revenue recognition process for a specific contract. The message states that the revenue up to the current period has not been transferred for the specified contract (denoted by &3).
Cause:
This error can occur due to several reasons, including:
- Incomplete Data: The contract may not have all the necessary data or configurations set up for revenue recognition.
- Posting Period Issues: The posting period may be closed, preventing any further postings related to revenue recognition.
- Contract Status: The contract might be in a status that does not allow for revenue recognition (e.g., it may be inactive or not fully approved).
- Configuration Issues: There may be issues with the configuration of the revenue recognition settings in the system.
- Missing Transfer: The revenue recognition process may not have been executed properly, leading to missing transfers of revenue data.
Solution:
To resolve this error, you can take the following steps:
- Check Contract Data: Verify that all necessary data for the contract is complete and correct. Ensure that the contract is active and approved for revenue recognition.
- Review Posting Periods: Check the posting periods in the system to ensure that the current period is open for postings. If it is closed, you may need to open it or post in a different period.
- Run Revenue Recognition: Execute the revenue recognition process again for the contract. This can typically be done through the transaction code related to revenue recognition (e.g., FARR).
- Check Configuration: Review the configuration settings for revenue recognition in the system. Ensure that all necessary settings are correctly configured.
- Consult Logs: Look at the application logs or error logs for more detailed information about why the revenue was not transferred. This can provide insights into specific issues that need to be addressed.
- Contact Support: If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting SAP documentation for further assistance.
Related Information:
By following these steps, you should be able to identify and resolve the issue causing the error message FARR_CONTR_LIFECYCLE134.
Get instant SAP help. Start your 7-day free trial now.
FARR_CONTR_LIFECYCLE133
An error occurred during inbound processing of &1.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FARR_CONTR_LIFECYCLE132
Error while processing costs for contract &1. No change type is expected.
What causes this issue? During the processing of a cost revenue accounting item (RAI)<(>,<)> the change type manager must not detect any ...
FARR_CONTR_LIFECYCLE135
An error occurred during inbound processing.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
FARR_CONTR_LIFECYCLE136
Mapping not found for source document &1 &2 &3 &4.
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.