How To Fix SCTS_HDI310 - Objects that only exist in HDI: &3

SCTS_HDI310 - Overview

• Message type: E = Error

• Message class: SCTS_HDI - Messages for CTS HDI API

• Message number: 310

• Message text: Objects that only exist in HDI: &3

What causes this issue?

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

System Response

The system detected that &V3& objects only exist in the HDI container
&V1& (the name of the physical container in the database is &V2&) and
not in the HTA Repository. The transport names (LIMU HOTO) of the
objects are listed in the following lines of the log.
There are several reasons why objects exist only in HDI:
In the development environment for HDI objects (SAP Web IDE for SAP
HANA), new HDI objects were created and deployed from here to the HDI
container but not checked in to the HTA Repository (for example using
HDI Namespace Editor in the ABAP Development Tools (ADT)).
The HDI objects were deployed to the HDI container using other tools and
not yet made known to the HTA Repository.

How to fix this error?

Check whether the objects in question were not checked in and check them
in if necessary. You can do this using HDI Namespace Editor.
If the objects were deployed to the HDI container using other tools,
make sure that these objects are also made known to HTA.

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 SCTS_HDI310 - Objects that only exist in HDI: &3 ?

  The SAP error message SCTS_HDI310 typically occurs in the context of SAP HANA Database and HDI (HANA Deployment Infrastructure) when there are issues related to database objects that exist only in the HDI container but are not recognized or cannot be accessed properly. This can happen during deployment or when trying to access certain database objects.
  
  Cause:
  The error message SCTS_HDI310 indicates that there are objects in the HDI container that are not properly synchronized or recognized by the system. This can happen due to several reasons, including:
  
  Deployment Issues: If there was an issue during the deployment of the HDI container, some objects may not have been created or updated correctly.
  Object Deletion: Objects that were expected to be present may have been deleted or are in a state that is not recognized by the current deployment.
  Version Mismatch: There may be a version mismatch between the HDI container and the application trying to