How To Fix SCPR_ATC021 - Field in BC Set is not in the table/view

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 021

• Message text: Field in BC Set is not in the table/view

What causes this issue?

A field of table/view as defined in BC Set is not present in DDIC
definition.
Corresponding field in the table / view has been changed in the DDIC
definition post creation of BC-Set ( e.g. in a system with a higher/more
recent release).

System Response

You cannot display or activate the contents of this field in this system
with any of BC Set transactions.

How to fix this error?

If you maintain the BC Set in this system in the maintenance transaction
SCPR3, this field is removed from the BC Set.

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_ATC021 - Field in BC Set is not in the table/view ?

  The SAP error message SCPR_ATC021, which states "Field in BC Set is not in the table/view," typically occurs when there is a mismatch between the fields defined in a Business Configuration Set (BC Set) and the actual fields present in the corresponding database table or view. This can happen during the activation or transport of BC Sets, especially if the underlying data model has changed or if the BC Set is referencing fields that no longer exist.
  Causes:
  
  Field Deletion or Renaming: The field that the BC Set is trying to reference has been deleted or renamed in the underlying table or view.
  Version Mismatch: The BC Set may have been created in a different version of the system where the field existed, but it has since been modified in the current version.
  Transport Issues: If the BC Set was transported from one system to another, there may be inconsistencies in the data model between the source and target systems.
  Custom Development: If there are custom fields or modifications in the database that are not reflected in the BC Set, this error can occur.
  
  Solutions:
  
  Check the BC Set Definition: Review the definition of the BC Set to identify which field is causing the issue. You can do this by navigating to the BC Set in the SAP system and checking its structure.
  Verify Table/View Structure: Check the structure of the table or view that the BC Set is referencing. You can do this using transaction codes like SE11 (Data Dictionary) to see if the field exists.
  Update the BC Set: If the field has been deleted or renamed, you may need to update the BC Set to reflect the current structure of the table or view. This may involve removing the obsolete field or adding a new field that corresponds to the current data model.
  Recreate the BC Set: If the BC Set is significantly outdated or corrupted, consider recreating it from scratch based on the current table/view structure.
  Consult Documentation: Review any relevant SAP notes or documentation that may provide guidance on changes to the data model or BC Set usage.
  Transport Consistency: If the issue arose after a transport, ensure that all related objects and dependencies were transported correctly and that the target system is in sync with the source system.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or fixes related to this error message. SAP frequently updates its knowledge base with solutions to common problems.
  Transaction Codes: Familiarize yourself with transaction codes like SE11 (Data Dictionary), SCPR20 (BC Set Management), and SE80 (Object Navigator) for managing and troubleshooting BC Sets.
  SAP Community: Engage with the SAP Community forums where other users may have encountered similar issues and can provide insights or solutions.
  
  By following these steps, you should be able to diagnose and resolve the SCPR_ATC021 error effectively.