How To Fix SCPR365 - Table/view &1 cannot be put in a BC Set

SAP Error Message - Details

• Message type: E = Error

• Message class: SCPR - BC Sets

• Message number: 365

• Message text: Table/view &1 cannot be put in a BC Set

What causes this issue?

Table/view &V1& cannot be put in a BC Set.
This could be because:
The table does not exist (any longer) in the system
It is a master or transaction data table: Only customizing tables can
be put in BC Sets.
It is a system table (e.g. TADIR)
It is a table/view with forbidden key fields:
The table has an address field in the key (key fields with domains of
type 'ADRNR', 'CADRNR' and 'AD_ADDRNUM' are not allowed)
The table/view has a field of type GUID/UUID (global/universal unique
identifier). These fields are not allowed in views and tables with
generated maintenance dialogs. In database tables without generated
maintenance dialogs, they can be put in the BC Set.
The table/view has a field of type 'STRING' or 'RAWSTRING' in the key
The table/view has a field in the key which is more than 255 characters
wide
The table/view is explicitly excluded. This is the case for some SAP
tables which are not allowed in BC Sets for reasons which the person
responsible for the table can explain.

System Response

The table/view &V1& is not put in the BC Set, i.e. no entries from this
table are copied.
If the BC Set already contains data records from this table/view (e.g.
if the table/view used to exist, but has been deleted), they are
automatically deleted when you save the BC Set.

How to fix this error?

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

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message SCPR365 - Table/view &1 cannot be put in a BC Set ?

  The SAP error message SCPR365, which states "Table/view &1 cannot be put in a BC Set," typically occurs when you attempt to include a table or view in a Business Configuration Set (BC Set) that is not allowed. BC Sets are used in SAP to transport configuration settings between systems, and not all tables or views are eligible for inclusion in BC Sets.
  Cause:
  
  Ineligible Objects: The object you are trying to include in the BC Set is not designed to be part of a BC Set. This can include certain system tables, temporary tables, or tables that are not meant for configuration purposes.
  Technical Restrictions: Some tables may have technical restrictions that prevent them from being included in BC Sets due to their nature or the way they are used in the system.
  Custom Development: If the table or view is a custom development, it may not have been properly defined to be included in BC Sets.
  
  Solution:
  
  Check Object Eligibility: Verify if the table or view you are trying to include is eligible for BC Sets. You can refer to SAP documentation or consult with your SAP Basis or ABAP team to confirm this.
  Use Alternative Methods: If the object cannot be included in a BC Set, consider using other methods for transporting configuration, such as:
  
  Transport Requests: Use standard transport requests to move configuration settings.
  Manual Configuration: Manually replicate the configuration in the target system if feasible.
  
  
  Review Custom Development: If the object is custom, ensure that it is designed correctly. You may need to adjust the development to allow it to be included in BC Sets.
  Consult SAP Notes: Check for any relevant SAP Notes that might address this issue or provide additional guidance.
  
  Related Information:
  
  BC Sets: Business Configuration Sets are a way to bundle configuration settings for easy transport and management.
  SAP Documentation: Refer to the official SAP Help Portal for detailed information on BC Sets and their limitations.
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  If the problem persists after trying the above solutions, consider reaching out to SAP support for further assistance.