How To Fix SCPR369 - Inconsistent data records removed from the BC Set

SAP Error Message - Details

• Message type: E = Error

• Message class: SCPR - BC Sets

• Message number: 369

• Message text: Inconsistent data records removed from the BC Set

What causes this issue?

The BC Set contained data records for tables which are either:
no longer in the system,
flagged in an exclusion table, and not accepted in a BC Set.
redundant (duplicate) data records do not cause loss of information.

System Response

These data records have been deleted from the BC Set

How to fix this error?

Save the BC Set to record the changes.
You can see details of this message in the "BC Set Consistency check",
in display mode in the BC Set maintenance transaction. In change mode,
the data records are removed automatically. You can then no longer
dieplay detailed information.

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 SCPR369 - Inconsistent data records removed from the BC Set ?

  The SAP error message SCPR369 indicates that there are inconsistent data records in a Business Configuration (BC) Set, which have been removed during the activation or import process. This typically occurs when the data in the BC Set does not match the expected format or constraints defined in the system.
  Cause:
  
  
  Inconsistent Data: The data records in the BC Set may not conform to the required structure or rules. This can happen due to:
  
  Missing mandatory fields.
  Data type mismatches (e.g., numeric fields containing text).
  Referential integrity issues (e.g., foreign key constraints not being met).
  Changes in the underlying data model that affect the BC Set.
  
  
  
  Version Mismatch: The BC Set may have been created in a different version of the software or with different configuration settings that are no longer valid.
  
  
  Transport Issues: If the BC Set was transported from one system to another, there may have been issues during the transport process that led to data corruption or loss.
  
  
  Solution:
  
  
  Review the BC Set: Check the contents of the BC Set for any inconsistencies. You can do this by:
  
  Using transaction code SCPR20 to analyze the BC Set.
  Looking for any records that are highlighted as inconsistent.
  
  
  
  Correct Data Issues: If you identify specific records that are causing the issue, you may need to:
  
  Update or correct the data in the BC Set.
  Ensure that all mandatory fields are filled and that data types are correct.
  
  
  
  Recreate the BC Set: If the BC Set is significantly corrupted or outdated, consider recreating it from scratch, ensuring that all data adheres to the current system requirements.
  
  
  Check Dependencies: Ensure that any dependencies or related configuration settings are correctly set up in the system.
  
  
  Consult Documentation: Refer to SAP documentation or notes related to the specific BC Set you are working with for any known issues or additional guidance.
  
  
  SAP Support: If the issue persists and you cannot resolve it, consider reaching out to SAP Support for assistance. They may provide specific notes or patches that address the issue.
  
  
  Related Information:
  
  Transaction Codes: SCPR20 (to manage BC Sets), SCPR3 (to view BC Set logs).
  SAP Notes: Search for relevant SAP Notes in the SAP Support Portal that may address known issues with specific BC Sets or provide additional troubleshooting steps.
  System Logs: Check system logs for any additional error messages or warnings that may provide more context about the inconsistency.
  
  By following these steps, you should be able to identify and resolve the issues related to the SCPR369 error message.