How To Fix SZDM_CC_CHKS_TITLES136 - An XPRA report performed a non-declared write-access to a table

SAP Error Message - Details

• 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

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 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.

System Response

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.

How to fix this error?

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 ...</>

Procedure for System Administrators

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_TITLES136 - An XPRA report performed a non-declared write-access to a table ?

  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 to ensure that it is correctly configured to include the necessary tables for write access. This may involve checking the code or configuration settings.
  User Authorizations: Ensure that the user executing the XPRA has the necessary authorizations to perform write operations on the affected table. This may involve adjusting roles or permissions in the SAP system.
  Database Locks: Check for any locks on the database table that may be preventing the XPRA from executing. You can use transaction codes like SM12 to view and manage locks.
  Review Upgrade Documentation: If this error occurs during an upgrade, consult the upgrade documentation for any specific instructions or prerequisites related to the XPRA.
  Contact SAP Support: If the issue persists, consider reaching out to SAP support for assistance. They may provide patches or additional guidance based on the specific version and configuration of your SAP system.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with transaction codes such as SE38 (to run reports), SE80 (Object Navigator), and SM37 (to monitor background jobs) for troubleshooting.
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address this specific error or provide additional context.
  System Logs: Check system logs (transaction SLG1) for more detailed error messages that may provide further insight into the issue.
  
  By following these steps, you should be able to diagnose and resolve the error related to the XPRA report and its write access to the database table.