How To Fix SZDM_CC_CHKS_DETAILS070 - R3TR XPRA &1: Table &2 cannot be copied.

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 070

• Message text: R3TR XPRA &1: Table &2 cannot be copied.

INCLUDE SZDM_CC_GENERAL_CLONING_HEAD OBJECT DOKU ID TX
XPRA reports are executed as a part of the upgrade. Therefore, the
author of an XPRA report has to specify all tables that the XPRA report
will write to. Subsequently, the ZDO procedure creates a copy of these
tables. These specified tables are visible in transaction SLAPI. (Call
transaction SLAPI, select the entry SAP_XPRA_&V1& and select "Used
Database Tables" in the navigation area. In column "Access", it is
specified whether the XPRA reads from or writes to the table.)
In this case, table &V2& is statically classified as "SHARED" or, too
large or too frequently updated for being copied.

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

&PROCEDURE&
Do not deliver XPRA &V1& with a Support Package or an enhancement
package. Or, modify the XPRA report in a way that it does no longer
write to table &V2&.
In case table &V2& is statically classified as SHARED and the change
cannot be withdrawn, get in contact with BC-UPG-DTM-TLA

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_DETAILS070 - R3TR XPRA &1: Table &2 cannot be copied. ?

  The SAP error message SZDM_CC_CHKS_DETAILS070 R3TR XPRA &1: Table &2 cannot be copied typically occurs during the execution of an XPRA (a type of transport request in SAP) when the system encounters an issue with copying a database table. This can happen for various reasons, and understanding the cause is essential for finding a solution.
  Possible Causes:
  
  Table Locking: The table you are trying to copy may be locked by another process or user.
  Table Structure Changes: There may be inconsistencies in the table structure, such as missing fields or incompatible data types.
  Authorization Issues: The user executing the XPRA may not have the necessary authorizations to access or modify the table.
  Database Constraints: There may be constraints (like foreign key constraints) that prevent the table from being copied.
  Transport Issues: The transport request may be incomplete or corrupted.
  
  Solutions:
  
  
  Check Table Locking:
  
  Use transaction SM12 to check for any locks on the table. If there are locks, you may need to wait for them to be released or contact the user holding the lock.
  
  
  
  Review Table Structure:
  
  Use transaction SE11 to check the structure of the table. Ensure that it matches the expected structure and that there are no missing fields or incompatible data types.
  
  
  
  Verify Authorizations:
  
  Ensure that the user executing the XPRA has the necessary authorizations. You can check this using transaction SU53 after the error occurs.
  
  
  
  Check Database Constraints:
  
  Review any constraints on the table that might prevent copying. You can do this in transaction SE11 under the "Technical Settings" of the table.
  
  
  
  Transport Request Integrity:
  
  Check the transport request for completeness. You can do this using transaction SE01 or SE09. If the transport is corrupted, you may need to recreate it.
  
  
  
  Run the XPRA in a Different Environment:
  
  If possible, try running the XPRA in a development or test environment to see if the issue persists. This can help isolate the problem.
  
  
  
  Consult SAP Notes:
  
  Search for relevant SAP Notes in the SAP Support Portal that may address this specific error message or provide additional troubleshooting steps.
  
  
  
  Contact SAP Support:
  
  If the issue persists after trying the above solutions, consider reaching out to SAP Support for further assistance.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SE11: Data Dictionary (to check table structure)
  SM12: Display and Delete Locks
  SU53: Authorization Check
  SE01 / SE09: Transport Organizer
  
  
  
  SAP Notes: Always check for any relevant SAP Notes that might provide specific fixes or workarounds for this error.
  
  
  By following these steps, you should be able to identify the cause of the error and implement a solution.