How To Fix SCPR356 - Customizing data not recorded in BC Set (see long text)

SCPR356 - Overview

• Message type: E = Error

• Message class: SCPR - BC Sets

• Message number: 356

• Message text: Customizing data not recorded in BC Set (see long text)

<ZK>&CAUSE&</>
You have activated automatic customizing recording in BC Sets, but you
want to cancel save without BC Set recording.

System Response

If you continue, the customizing data will be saved without BC Set
recording. If you no longer need this function, you can deactivate it
as described below. Otherwise you can go back to the BC Set name entry
window.

How to fix this error?

<ZK>Automatic customizing recording in BC Sets:</>
You can activate and deactivate automatic customizing recording in BC
Sets, in the user settings in the BC Set maintenance transaction SCPR3
and the BC Set activation transaction SCPR20, and in the user data
personalization settings (transaction SU01 -> enter user name ->
"Personalization" -> "BC Set Transaction Personalization").
The user setting "Activate Automatic Customizing Recording " under
"General Settings" determines whether the transport contents are
searched for data which is to be recorded in BC Sets, when customizing
data is changed (i.e. after getting the transport request).

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 SCPR356 - Customizing data not recorded in BC Set (see long text) ?

  The SAP error message SCPR356 indicates that there is an issue with the Customizing data not being recorded in a Business Configuration Set (BC Set). This error typically arises when you are trying to create or modify a BC Set, and the system cannot find the necessary Customizing data that should be included.
  
  Cause:
  
  Missing Customizing Data: The most common cause is that the Customizing data you are trying to include in the BC Set has not been properly defined or is missing in the system.
  Incorrect Configuration: There may be an issue with the configuration settings or the way the BC Set is being created.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to access or modify the Customizing data.
  Technical Issues: There could be underlying technical issues, such as database inconsistencies or problems with the transport layer.
  
  
  Solution:
  
  Check Customizing Data: Verify that the Customizing data you want to include in the