How To Fix SZDM_CC_CHKS_DETAILS087 - R3TR OBJA &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: 087

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

INCLUDE SZDM_CC_GENERAL_CLONING_HEAD OBJECT DOKU ID TX
If the application development creates a procedure (f.e. After-Import
Method, XPRA-report, Switch-BADI implementation) which has to be
executed as part of an upgrade, the author of the procedure has to
specify all tables accessed by this procedure. Some of these procedures
called APIs which the author of the procedure is not responsible for.
Therefore, the owner of such an API has to specify separately which
tables are accessed by his or her API. These specifications can be made
in the ABAP transaction SLAPI and are transported and delivered as the
transport object R3TR OBJA.
In this case, the specification delivered as R3TR OBJA &V1& says that
the API &V1& writes to table &V2&.
INCLUDE SZDM_CC_GENERAL_CLONETMP_CPY OBJECT DOKU ID TX
&PROCEDURE&
To solve this issue, choose one of the following options:
Make sure that no AIM, XPRA-report, or Switch-BADI implementation uses
this API.
Make sure that the API &V1& does not write to table <(>&<)>2 when called
during an upgrade with Zero Downtime Option.

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

  The SAP error message SZDM_CC_CHKS_DETAILS087 with the description R3TR OBJA &1: Table &2 cannot be copied typically occurs during a transport or when trying to copy an object in the SAP system. This error indicates that there is an issue with the specific table that is being referenced, which prevents it from being copied or transported.
  Causes:
  
  Table Locking: The table might be locked by another process or user, preventing it from being copied.
  Transport Directory Issues: There may be issues with the transport directory or the transport request itself.
  Missing Authorizations: The user attempting the operation may not have the necessary authorizations to copy the table.
  Inconsistent Data: The table may contain inconsistent data or structures that prevent it from being copied.
  Technical Settings: The technical settings of the table may not allow it to be copied (e.g., it might be a system table or a table with specific attributes).
  
  Solutions:
  
  Check Table Lock: Use transaction SM12 to check if the table is locked and by whom. If it is locked, you may need to wait for the lock to be released or contact the user who has locked it.
  Review Transport Request: Ensure that the transport request is correctly configured and that there are no issues with the transport directory. You can check the transport logs for any errors.
  Check Authorizations: Verify that the user has the necessary authorizations to perform the copy operation. You may need to consult with your SAP security team.
  Data Consistency Check: Perform a consistency check on the table to ensure that there are no issues with the data. You can use transaction SE11 to check the table structure and data.
  Technical Settings Review: Review the technical settings of the table in transaction SE11 to ensure that it is eligible for copying. If it is a system table or has specific attributes, it may not be allowed to be copied.
  Consult SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error message or provide additional guidance.
  
  Related Information:
  
  Transaction Codes: 
  
  SE11: Data Dictionary (to check table structure)
  SM12: Display and Delete Locks
  SE09/SE10: Transport Organizer (to manage transport requests)
  
  
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may provide additional context or solutions for this error.
  Documentation: Review SAP documentation related to transport management and data dictionary objects for further insights.
  
  If the issue persists after trying the above solutions, it may be beneficial to engage with SAP support for more in-depth troubleshooting.