Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now

Close

How To Fix SCPR368 - BC Set contains data records for tables which are no longer allowed


SAP Error Message - Details

  • Message type: E = Error

  • Message class: SCPR - BC Sets

  • Message number: 368

  • Message text: BC Set contains data records for tables which are no longer allowed

  • Show details Hide details
  • What causes this issue?

    The BC Set contains data records from forbidden tables. This can happen
    for example if a table is no longer in the system, or copying data
    records from a table is prevented by an entry in a special "exclusion
    table". The tables concerned are flagged in the table list ("Tables and
    views for selected IMG activity") ("red dot" - see legend)

    System Response

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

    How to fix this error?

    Go to change mode. The inconsistent data records are deleted from the
    BC Set. Save the BC Set to record the changes.

    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 SCPR368 - BC Set contains data records for tables which are no longer allowed ?

    The SAP error message SCPR368 indicates that a Business Configuration Set (BC Set) contains data records for tables that are no longer allowed or supported in the current version of the SAP system. This typically occurs when a BC Set is being activated or transported, and it references tables or fields that have been deprecated or removed in the current release.

    Cause:

    1. Deprecated Tables/Fields: The BC Set may reference tables or fields that have been removed or are no longer supported in the current version of SAP.
    2. Version Mismatch: The BC Set may have been created in an older version of SAP and is not compatible with the current version.
    3. Custom Development: If there are custom developments or modifications that reference these tables, they may also lead to this error.

    Solution:

    1. Review the BC Set: Check the contents of the BC Set to identify which tables or fields are causing the issue. You can do this using transaction code SCPR20 (BC Set Management).
    2. Update the BC Set: If the BC Set is outdated, you may need to update it to remove references to the deprecated tables or fields. This may involve:
      • Removing the data records that reference the deprecated tables.
      • Modifying the BC Set to align with the current data model.
    3. Consult Documentation: Review the release notes or documentation for the current version of SAP to understand which tables or fields have been deprecated.
    4. Contact SAP Support: If you are unable to resolve the issue, consider reaching out to SAP Support for assistance. They may provide guidance on how to handle the deprecated elements in your BC Set.
    5. Testing: After making changes, ensure to test the BC Set in a development or quality assurance environment before transporting it to production.

    Related Information:

    • Transaction Codes:
      • SCPR20: Business Configuration Set Management
      • SCPR10: BC Set Activation
    • SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide guidance on handling BC Sets in your version.
    • Documentation: Review the SAP Help Portal for information on BC Sets and their management.

    By following these steps, you should be able to identify the cause of the SCPR368 error and implement a solution to resolve it.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Sign up for our Free Essentials Plan.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant