How To Fix SZDM_CC_CHKS_DETAILS095 - R3TR OBJA &1: Table &2 read by XPRA &3 cannot be set to read only.

SZDM_CC_CHKS_DETAILS095 - Overview

• Message type: E = Error

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

• Message number: 095

• Message text: R3TR OBJA &1: Table &2 read by XPRA &3 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 XPRA report &v3& has specified that the
XPRA report 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 your XPRA
metadata definition &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 the read-only mode,
the application needs to make sure that only the key ranges accessed by
the XPRA report become read-only while all other table entries are still
writeable for the productive application.

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_DETAILS095 - R3TR OBJA &1: Table &2 read by XPRA &3 cannot be set to read only. ?

  The SAP error message SZDM_CC_CHKS_DETAILS095 indicates that there is an issue with a specific table being accessed by an XPRA (a type of program that performs database changes during an upgrade or support package installation). The error message states that the table cannot be set to read-only, which is typically required during certain operations to ensure data integrity.
  
  Cause:
  
  Table Locking: The table in question may be locked by another process or transaction, preventing it from being set to read-only.
  Database Constraints: There may be constraints or dependencies that prevent the table from being modified or set to read-only.
  Incorrect Configuration: The XPRA may be incorrectly configured or may not have the necessary permissions to modify the table.
  Data Consistency Issues: There may be data consistency issues that need to be resolved before the table can be set to read-only.
  
  
  Solution:
  
  Check for Locks: Use transaction codes like SM12 to check for any locks on the table.