How To Fix SCPR592 - Data record with key '&1' of tab. &2 not put in BC Set

SAP Error Message - Details

• Message type: E = Error

• Message class: SCPR - BC Sets

• Message number: 592

• Message text: Data record with key '&1' of tab. &2 not put in BC Set

What causes this issue?

The data record with the key '&V1&' for table &V2& is not put in the BC
Set.
This is, for example, the case if the data record contains a language
which is not to be put in the BC Set.

System Response

The system ignores the data record at this point in the BC Set
processing.

How to fix this error?

Determine the point in the BC Set processing at which the error
occurred:
If the BC Set is based on a transport request and has not yet been
saved, you can ignore this message. In this case, only records in the
logon language are extracted from the transport request. When the BC Set
is saved in the database, all languages are read, according to the user
settings.
If the error occurs when you save the BC Set, the data record is not put
in 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 SCPR592 - Data record with key '&1' of tab. &2 not put in BC Set ?

  The SAP error message SCPR592 indicates that a data record with a specific key (represented by &1) in a particular table (represented by &2) was not included in a Business Configuration Set (BC Set). This error typically arises during the process of creating or modifying BC Sets, which are used to transport configuration data between different SAP systems.
  Cause:
  The error can occur due to several reasons, including:
  
  Missing Data: The data record with the specified key may not exist in the source table, or it may have been deleted or not yet created.
  Inconsistent Data: The data record may not meet the criteria for inclusion in the BC Set due to inconsistencies or validation errors.
  Authorization Issues: The user may not have the necessary authorizations to access or modify the data in the specified table.
  Configuration Settings: There may be specific settings or filters applied to the BC Set that exclude certain records based on predefined criteria.
  
  Solution:
  To resolve the SCPR592 error, you can take the following steps:
  
  
  Check Data Existence: Verify that the data record with the specified key exists in the table. You can do this by querying the table directly in the SAP system.
  
  
  Review Data Integrity: Ensure that the data record is complete and meets all necessary criteria for inclusion in the BC Set. Check for any missing mandatory fields or invalid values.
  
  
  Authorization Check: Ensure that the user creating or modifying the BC Set has the appropriate authorizations to access the data in the specified table.
  
  
  Review BC Set Configuration: Check the configuration settings of the BC Set to ensure that there are no filters or conditions that would exclude the data record in question.
  
  
  Debugging: If the issue persists, consider using transaction codes like SE80 or SE37 to debug the function module or program that is responsible for processing the BC Set. This may provide more insight into why the record is being excluded.
  
  
  Consult Documentation: Review SAP documentation or notes related to BC Sets and the specific tables involved to see if there are any known issues or additional requirements.
  
  
  Related Information:
  
  BC Sets: Business Configuration Sets are used in SAP to transport configuration settings and data between different environments (e.g., development, testing, production).
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SCPR20 (for managing BC Sets) and SE11 (for data dictionary) to help troubleshoot the issue.
  SAP Notes: Check the SAP Support Portal for any notes related to SCPR592 or the specific tables involved, as there may be patches or updates that address known issues.
  
  If the problem continues after following these steps, consider reaching out to SAP support for further assistance.