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

SCPR592 - Overview

• 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