How To Fix SZDM_CC_CHKS_DETAILS101 - Table &1 in metadata of SL API &2 does not exist in this system.

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 101

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

What causes this issue?

The properties of an API called by an after-import method (AIM) might be
incorrectly 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, however, that it exists in other development/maintenance
systems.
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.

Smart SAP Assistant

• What is the cause and solution for SAP error message SZDM_CC_CHKS_DETAILS101 - Table &1 in metadata of SL API &2 does not exist in this system. ?

  The SAP error message "SZDM_CC_CHKS_DETAILS101 Table &1 in metadata of SL API &2 does not exist in this system" typically indicates that the system is trying to access a specific table that is expected to be part of the metadata for a Service Layer (SL) API, but it cannot find it in the current system. This can occur in various scenarios, such as during data integration, API calls, or when working with specific functionalities in SAP Business One or other SAP systems.
  Causes:
  
  Missing Table: The specified table (&1) does not exist in the database. This could be due to an incomplete installation, a missing component, or a misconfiguration.
  Incorrect API Version: The API version being used may not be compatible with the current system version, leading to discrepancies in expected metadata.
  Database Issues: There may be issues with the database itself, such as corruption or misconfiguration.
  Configuration Errors: The system may not be properly configured to recognize the table, possibly due to missing or incorrect settings in the Service Layer configuration.
  
  Solutions:
  
  Check Table Existence: Verify if the table specified in the error message actually exists in the database. You can do this by querying the database directly or using database management tools.
  Review API Documentation: Ensure that you are using the correct version of the API and that it is compatible with your current system version. Check the SAP documentation for any changes or updates related to the API.
  Reconfigure Service Layer: If the table is supposed to exist, check the configuration of the Service Layer. Ensure that all necessary components are installed and configured correctly.
  Database Repair: If you suspect database corruption, consider running database repair tools or restoring from a backup if necessary.
  Consult SAP Support: If the issue persists, it may be beneficial to reach out to SAP support for assistance. They can provide more specific guidance based on your system configuration and the error details.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues related to the error message. SAP frequently publishes notes that address specific problems and provide solutions or workarounds.
  System Logs: Review system logs for additional error messages or warnings that may provide more context about the issue.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed. Other users may have encountered the same problem and can offer insights or solutions.
  
  By following these steps, you should be able to diagnose and resolve the issue related to the error message you are encountering.