How To Fix SZDM_CC_CHKS_DETAILS099 - R3TR OBJA &1: Table &2 accessed by an API cannot be set to read only.

SZDM_CC_CHKS_DETAILS099 - Overview

• Message type: E = Error

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

• Message number: 099

• Message text: R3TR OBJA &1: Table &2 accessed by an API cannot be set to read only.

What causes this issue?

INCLUDE SZDM_CC_LAT_DET_INTRO_PROC OBJECT DOKU ID TX
In this case the owner of the SLAPI implementation &v1& has specified
that the SLAPI implementation accesses table &v2& and that this table
shall be read-only for the productive application during the ZDO
upgrade. (See ABAP transaction SLAPI. Choose the "Position..." button to
find that SLAPI's metadata definition named &v1&. Select this entry and
choose "Used Database Tables".)
INCLUDE SZDM_CC_LAT_DET_RO_IMPOSSIBL OBJECT DOKU ID TX

How to fix this error?

As an alternative to setting the complete table to read-only the
application needs to make sure that only the key ranges accessed by the
SLAPI implementation has become read-only while all other table entries
are still writeable for the productive application.

Error message extract from SAP system. Copyright SAP SE.

SZDM_CC_CHKS_DETAILS099 - Details

• The SAP error message SZDM_CC_CHKS_DETAILS099 indicates that a specific table (denoted as &2) is being accessed by an API in a way that conflicts with its read-only status. This typically occurs when there is an attempt to modify or access data in a way that is not permitted for that table, which is set to read-only.
  
  Cause:
  
  Read-Only Table: The table in question is defined as read-only in the system, meaning that it should not be modified or updated through standard operations.
  API Access: The API being used is trying to perform an operation that requires write access to the table, which is not allowed.
  
  Configuration Issues: There may be a misconfiguration in the API or the way it interacts with the database, leading to this error.
  Data Model Changes: Changes in the data model or the way the application is designed to interact with the database can also lead to this error.
  
  
  Solution:
  
  Check Table Definition: