Message type: E = Error
Message class:  SZDM_CC_CHKS_TITLES - Title messages related to check classes 
Message number: 136
Message text: An XPRA report performed a non-declared write-access to a table
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 the ZDO declarations
of the XPRA.
The name of the XPRA, 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 XPRA 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:
Call transaction SLAPI
Search for an entry with name
SAP_XPRA_<name of the XPRA-report> or
<namespace>SAP_XPRA_<name of the XPRA-report>.
If there is no such entry, then create a new one with this name.
For this SLAPI-entry, select "Used database tables" in the navigation
area.
Enter the names of the accessed tables with an appropriate value for
"Access type" and "Lock mode".
If the RFC-module calls an APIs that is listed in transaction SLAPI,
then enter the name of this APIs in "Ref to other API".
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.
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_TITLES136 indicates that an XPRA (a type of report used in SAP to perform database changes during an upgrade or modification) has attempted to perform a write operation on a database table that it does not have permission to modify. This typically occurs when the XPRA is not properly defined or when it tries to access a table that is not included in its declaration.
Cause: Improper XPRA Configuration: The XPRA report may not have been correctly configured to include the necessary tables for write access. Authorization Issues: The user executing the XPRA may not have the required authorizations to perform write operations on the specified table. Database Locking: The table may be locked by another process, preventing the XPRA from writing to it. Upgrade Issues: This error can also occur during system upgrades if the XPRA is not compatible with the current database schema.
Solution: Check XPRA Configuration: Review the XPRA report
 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_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_TITLES132 A Configuration-Task performed a non-declared read-access to a table
What causes this issue?  A trace in one of the SAP internal test systems has found that your configuration-task read from a database table that is not...
SZDM_CC_CHKS_TITLES137 A Configuration-Task 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 configuration-task wrote to a database table that is not ...
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...
Click on this link to search all SAP messages.