How To Fix SZDM_CC_CHKS_DETAILS084 - Table &1 in metadata of SL API &2 does not exist

SZDM_CC_CHKS_DETAILS084 - Overview

• Message type: E = Error

• Message class: SZDM_CC_CHKS_DETAILS - Detailed messages related to check classes

• Message number: 084

• Message text: Table &1 in metadata of SL API &2 does not exist

What causes this issue?

The properties of an API called by an after-import method (AIM) are not
correctly maintained.
In transaction SLAPI, you have declared table &V1& as a table which is
accessed by API &V2&. This table does not exist in this system. A GTADIR
query shows, that it doesn't exists in other development/maintenance
systems either. Therefore this is probably an erroneous declartion.
For more information about this check, see
<DS:TX.SZDM_CC_GENERAL_ZDO>here.</>
The metadata object of the API &V2& has been created. Table &V1& is
declared as accessed table, however this table does not exist.
You can maintain the required properties in a
<DS:TX.SCTS_SLAPI_REPOSITORY>Repository for Meta Data of an API called
by an After-Import Method</>.

How to fix this error?

Check and make sure that the correct tables are specified which are
accessed by the API.
To check and maintain the tables for the API &V2& to be called by
after-import methods, perform the following steps:
Call transaction SLAPI.
Select the line containing &V2&.
Choose "Used Database Tables".
Check table &V1& and adapt or remove it.
Check completeness of the tables and whether the attributes
<DS:DE.OB_LOCK_MODE>"Lock mode"</> and <DS:DE.OB_ACCESS_TYPE>"Access"</>
are correctly maintained.

Error message extract from SAP system. Copyright SAP SE.

SZDM_CC_CHKS_DETAILS084 - Details

• The SAP error message "SZDM_CC_CHKS_DETAILS084 Table &1 in metadata of SL API &2 does not exist" typically indicates that there is a problem with the metadata configuration for a specific Service Layer (SL) API in SAP Business One or SAP HANA. This error suggests that the system is trying to access a table that is not defined or does not exist in the metadata for the specified API.
  Causes:
  
  Missing Table Definition: The table referenced by &1 is not defined in the metadata for the Service Layer API &2.
  Incorrect API Version: The API version being used may not support the table or may have been deprecated.
  Database Issues: There may be issues with the database itself, such as corruption or missing objects.
  Configuration Errors: There could be misconfigurations in the Service Layer setup or in the application that is trying to access the API.
  Updates or Patches: Recent updates or patches may have altered the