Message type: E = Error
Message class:  SZDM_CC_CHKS_TITLES - Title messages related to check classes 
Message number: 137
Message text: A Configuration-Task performed a non-declared write-access to a table
A trace in one of the SAP internal test systems has found that your
configuration-task wrote to a database table that is not declared in the
ZDO declarations of the configuration-task.
The name of the configuration-task, the name of the table and the name
of the system where the trace was executed and where you can find the
call stack leading to the non-declared write access can be found in the
detailed messages.
If the configuration-task runs as part of a zero-downtime-upgrade in a
customer system, then the upgrade procedure aborts with an error
message. Solving this kind of errors requires help from the SAP
development support.
If you have not yet declared the tables, then make the necessary
declarations in your development or maintenance system:
The class implementing your configuration task must implement interface
IF_TR_CTS_CFG_TASK.
In method GET_TASK_META_DATA, declare the tables the RFC-module accesses
by implementing a call of method IR_META_DATA->ADD_TABLE(...). For each
table, provide an appropriate value for ACCESS_TYPE and LOCK_MODE.
If the RFC module calls an API that is listed in transaction SLAPI, then
declare this API by implementing a call of IR_META_DATA->ADD_SLAPI(...).
If the RFC module calls an API that is not listed in transaction SLAPI,
then ask the owner of the API to create an SLAPI entry for this API and
declare all accessed tables there. Declare this new SLAPI entry in your
implementation of GET_TASK_META_DATA by implementing a call of
IR_META_DATA->ADD_SLAPI(...).
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
<DS:TX.SZDM_CC_GENERAL_ZDO>Further information ...</>Error message extract from SAP system. Copyright SAP SE.
The SAP error message SZDM_CC_CHKS_TITLES137 indicates that a configuration task has attempted to perform a write operation on a database table that it is not authorized to modify. This typically occurs in the context of SAP's configuration management, where certain tasks are expected to adhere to specific rules regarding data access.
Cause: Unauthorized Write Access: The configuration task is trying to write to a table that it has not been declared to modify. This can happen if the task is incorrectly configured or if there are missing authorizations. Incorrect Configuration: The configuration task may not be set up correctly, leading to attempts to access tables that are not part of its defined scope. Transport Issues: If the configuration was transported from another system, there may be discrepancies in the configuration that lead to unauthorized access attempts.
Solution: Review Configuration: Check the configuration task that is generating the error. Ensure that it is correctly set up and
 Get instant SAP help. Sign up for our Free Essentials Plan.
Get instant SAP help. Sign up for our Free Essentials Plan. 
SZDM_CC_CHKS_TITLES136 An XPRA report performed a non-declared write-access to a table
What causes this issue?  A trace in one of the SAP internal test systems has found that your XPRA wrote to a database table that is not declared in th...
SZDM_CC_CHKS_TITLES135 An After Import Method performed a non-declared write-access to a table
What causes this issue?  A trace in one of the SAP internal test systems has found that your after-import-method (AIM) wrote to a database table that ...
SZDM_CC_CHKS_TITLES404 RFC connection to GTADIR server is not possible
What causes this issue?  The ZDO ATC check requires a RFC connection to the GTADIR server. In the current system the connection is not possible or doe...
SZDM_CC_CHKS_TITLES898 Exception occurred (see details). If reoccur. create incid:BC-UPG-DTM-TLA
 INCLUDE SZDM_CC_GENERAL_INTRO_TITLE OBJECT DOKU ID TX In this case unexpected error occured while checking the object list. &PROCEDURE& If th...
Click on this link to search all SAP messages.