How To Fix EMV173 - A vacant status period is not intended during a contract change

SAP Error Message - Details

• Message type: E = Error

• Message class: EMV - Reserved for IS-U: move-in/out

• Message number: 173

• Message text: A vacant status period is not intended during a contract change

What causes this issue?

Move-in date &V1& does not immediately follow on after move-out date
&V2& for contract change &V3& (installation &V4&).

System Response

The move-in cannot be processed for the contract change.

How to fix this error?

Check the move-in date. .
If the vacant status period is correct, create a move-in and a move-out
as normal.
This means that you must first cancel the move-in section of the
contract change and re-create it.
You can then create the move-in.

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 EMV173 - A vacant status period is not intended during a contract change ?

  The SAP error message EMV173, which states "A vacant status period is not intended during a contract change," typically occurs in the context of contract management within SAP, particularly when dealing with contract changes or modifications. This error indicates that the system has detected an attempt to create a period in a contract that is marked as vacant or inactive, which is not allowed.
  Cause:
  
  Contract Status: The contract may have a status that does not allow for changes during certain periods. For example, if a contract is in a "vacant" status, it means that it is not currently active or valid for changes.
  Date Overlap: The change being made may overlap with a period that is already marked as vacant or inactive.
  Configuration Issues: There may be configuration settings in the contract management module that restrict changes during certain periods.
  
  Solution:
  
  Check Contract Status: Review the status of the contract you are trying to change. Ensure that it is active and not in a vacant or inactive state.
  Review Change Dates: Ensure that the dates you are trying to change do not overlap with any periods that are marked as vacant. Adjust the dates accordingly.
  Modify Contract Periods: If necessary, modify the contract periods to ensure that there are no vacant periods during the change.
  Consult Configuration: If the issue persists, consult with your SAP configuration team to review the settings related to contract management and ensure that they align with your business processes.
  Documentation: Refer to SAP documentation or help resources for specific guidelines on handling contract changes and the implications of contract statuses.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ME31K (Create Contract), ME32K (Change Contract), and ME33K (Display Contract) to navigate contract management effectively.
  SAP Notes: Check for any SAP Notes related to EMV173 for additional insights or patches that may address this issue.
  User Roles: Ensure that the user attempting to make the changes has the appropriate permissions to modify contracts.
  
  If the problem continues after following these steps, it may be beneficial to engage with SAP support or your internal SAP team for further assistance.