How To Fix 6D799 - &1 remains available although tenant RA has been shortened, as rented

6D799 - Overview

• Message type: E = Error

• Message class: 6D - Real Estate Messages

• Message number: 799

• Message text: &1 remains available although tenant RA has been shortened, as rented

What causes this issue?

You have shortened the assignment of object &V1& to a tenant rental
agreement, or removed it from the agreement altogether. Usually the
system sets the status of an object for the period in which it is no
longer tenant rented to "not available" (including the subobjects; this
generally makes the higher-level objects only partially available).
However, this was not possible since object &V2& is rented through
rental agreement &V3&. The rental period and the "not available" period
(&V4) would overlap.

System Response

The system sets the status of the object in the time gap to "available"
and thus allows the rental to continue.

How to fix this error?

Check whether object &V1& is really available; terminate the rental
agreement if necessary.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 6D799 - &1 remains available although tenant RA has been shortened, as rented ?

  The SAP error message "6D799 &1 remains available although tenant RA has been shortened, as rented" typically indicates an issue related to the management of resources in a multi-tenant environment, particularly in the context of resource allocation and availability.
  
  Cause:
  
  Resource Allocation Issues: The error suggests that a resource (denoted by &1) is still marked as available even though the tenant's resource allocation (RA) has been shortened. This could be due to a misconfiguration or a failure in the system to update the status of the resource correctly.
  Data Inconsistency: There may be inconsistencies in the database or application state that prevent the system from recognizing the change in the tenant's resource allocation.
  System Bugs: There could be bugs in the SAP system or the specific module you are using that lead to this error message being triggered.
  
  
  Solution:
  
  Check Configuration: Review the configuration settings for the tenant and the resource in question. Ensure that the