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

SZDM_CC_CHKS_DETAILS094 - Overview

• Message type: E = Error

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

• Message number: 094

• Message text: R3TR XPRA &1 : Table &2 read by XPRA &1 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?

Do not use the XPRA &V3&

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

  The SAP error message SZDM_CC_CHKS_DETAILS094 indicates that there is an issue with an XPRA (a type of program in SAP that is used for data migration or conversion during upgrades) trying to read a specific table. The error message states that the table cannot be set to read-only, which is necessary for the XPRA to perform its operations.
  
  Cause:
  
  Table Locking: The table in question may be locked by another process or transaction, preventing the XPRA from accessing it in a read-only mode.
  Database Constraints: There may be database constraints or settings that prevent the table from being accessed in a read-only manner.
  User Permissions: The user executing the XPRA may not have the necessary permissions to access the table in a read-only state.
  Inconsistent State: The table might be in an inconsistent state due to previous operations or transactions that were not completed successfully.
  
  
  Solution:
  
  Check Locks: Use transaction codes like SM12 to check for any