How To Fix FARR_CONTR_LIFECYCLE061 - Cannot change POB &1 end date to be earlier than the last change date.

SAP Error Message - Details

• Message type: E = Error

• Message class: FARR_CONTR_LIFECYCLE - Message from Contract Lifecyle (RAR 2.0 Object Model)

• Message number: 061

• Message text: Cannot change POB &1 end date to be earlier than the last change date.

What causes this issue?

If there is the possibility of a prospective change, the end date of
performance obligation can't be modified. Since the contract has been
already changed and there is the effective date from this change. So the
end date is earlier than the existing effective date of the last change.

System Response

The change process of this contract is terminated.

How to fix this error?

1) Change the change type determination BADI and set this performance
obligation as retrospective change. Or
2) Adjust the end date of this performance obligation

Procedure for System Administrators

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message FARR_CONTR_LIFECYCLE061 - Cannot change POB &1 end date to be earlier than the last change date. ?

  The SAP error message FARR_CONTR_LIFECYCLE061 indicates that there is an attempt to change the end date of a Purchase Order (POB) to a date that is earlier than the last change date of that POB. This is a validation error that prevents the system from allowing such a change, as it would create inconsistencies in the data.
  Cause:
  
  Date Validation: The system has a built-in validation rule that prevents the end date from being set earlier than the last change date. This is to ensure data integrity and to avoid scenarios where historical data would be invalidated.
  Incorrect Date Entry: The user may have mistakenly entered an incorrect end date that is earlier than the last change date.
  System Configuration: There may be specific configurations or customizations in the SAP system that enforce this rule.
  
  Solution:
  
  Check Last Change Date: Review the last change date of the POB. You can do this by navigating to the relevant transaction in SAP (e.g., ME23N for display of Purchase Orders) and checking the change log.
  Adjust End Date: Change the end date to a date that is equal to or later than the last change date. This will comply with the validation rule and allow the change to be saved.
  Review Change History: If necessary, review the change history of the POB to understand why the last change date is set as it is and ensure that any changes made are valid.
  Consult Documentation: If you are unsure about the correct dates or the implications of changing them, consult your organization's documentation or reach out to a colleague or SAP consultant for guidance.
  System Configuration Review: If this error occurs frequently and seems to be an issue with the system configuration, consider discussing it with your SAP Basis or configuration team to see if adjustments can be made.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ME23N (Display Purchase Order), ME22N (Change Purchase Order), and ME21N (Create Purchase Order) to navigate and check the details of the POB.
  SAP Notes: Check SAP Notes for any known issues or updates related to this error message. SAP Notes can provide additional context or solutions for specific scenarios.
  User Authorization: Ensure that you have the necessary authorizations to make changes to the POB, as lack of proper authorization can also lead to errors.
  
  By following these steps, you should be able to resolve the error and successfully change the end date of the Purchase Order.