How To Fix EQ362 - Actual move-out date for contract &2 comes before the move-in date &3

SAP Error Message - Details

• Message type: E = Error

• Message class: EQ - Cross-IS-U functions

• Message number: 362

• Message text: Actual move-out date for contract &2 comes before the move-in date &3

What causes this issue?

You have tried to enter a move-out using an actual move-out date that is
earlier than the move-in date of the contract.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Correct the actual move-out date by selecting a date later than the
move-in.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message EQ362 - Actual move-out date for contract &2 comes before the move-in date &3 ?

  The SAP error message EQ362 indicates that there is a conflict with the move-out and move-in dates for a contract in the system. Specifically, it means that the actual move-out date for a contract is set to a date that occurs before the move-in date. This situation is not logically valid, as a tenant cannot move out before they have moved in.
  Cause:
  
  Data Entry Error: The most common cause is a mistake during data entry where the move-out date was entered incorrectly.
  System Configuration: There may be issues with how the system is configured to handle contract dates.
  Contract Changes: If there were changes made to the contract dates after the initial entry, it could lead to inconsistencies.
  
  Solution:
  
  Check Dates: Review the move-in and move-out dates for the contract in question. Ensure that the move-out date is set to a date that is after the move-in date.
  Correct Data: If the move-out date is incorrect, update it to reflect the correct date that is after the move-in date.
  Review Contract Changes: If there have been recent changes to the contract, ensure that all related dates are consistent and correctly reflect the intended timeline.
  Consult Documentation: If you are unsure about the correct dates, consult any relevant documentation or stakeholders involved in the contract to confirm the correct dates.
  System Configuration: If the issue persists and seems to be a systemic problem, consult with your SAP administrator or technical team to review the configuration settings related to contract management.
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like IE02 (Change Equipment) or IE03 (Display Equipment) to view and edit the contract details.
  SAP Notes: Check SAP Notes for any known issues or patches related to contract management and date handling.
  User Roles: Ensure that you have the appropriate permissions to make changes to contract dates in the system.
  
  By following these steps, you should be able to resolve the EQ362 error and ensure that the contract dates are logically consistent.