How To Fix SCPR_ATC019 - View/table contains tables with different cascading attributes

SCPR_ATC019 - Overview

• Message type: E = Error

• Message class: SCPR_ATC - Message class for ATC checks on BC sets

• Message number: 019

• Message text: View/table contains tables with different cascading attributes

What causes this issue?

The cascade property of a view/table consists not only of the delivery
class of the view or the primary table of the table, but also the
properties of all tables involved. That is, one of the following groups
of delivery classes must include all tables of the view/table:
o No client cascade: Delivery class 'C' and 'A'
o With client cascade: Delivery class 'S', 'E', 'G', and 'W'.
Probably table property was changed post creation of BC-Set.

System Response

The complete view/table cannot be added in the concrete BC set.
Activation of such BC-Set might lead to data inconsistencies.

How to fix this error?

Following options can be considered:
- Adjust the delivery classes of all tables/views under customizing
object to the same group of delivery classes.
- Split the tables/views into different BC-Sets which would be under
same group of cascading properties.

Procedure for System Administrators

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message SCPR_ATC019 - View/table contains tables with different cascading attributes ?

  The SAP error message SCPR_ATC019 indicates that there is an issue with a view or table in the ABAP Dictionary where the cascading attributes of the underlying tables do not match. This typically occurs when you are trying to create or modify a view that includes multiple tables, and those tables have different settings for cascading updates or deletes.
  
  Cause:
  The error arises when:
  
  You have a database view that includes multiple tables.
  The tables involved have different settings for cascading updates or deletes (e.g., one table may have cascading deletes enabled while another does not).
  This inconsistency prevents the system from determining how to handle cascading operations across the different tables.
  
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check the Tables: Identify the tables involved in the view that is causing the error. You can do this by examining the definition of the view in the ABAP Dictionary (transaction SE11).
  
  
  Review Cascading Attributes: For