Message type: E = Error
Message class: SCPR - BC Sets
Message number: 365
Message text: Table/view &1 cannot be put in a BC Set
Table/view &V1& cannot be put in a BC Set.
This could be because:
The table does not exist (any longer) in the system
It is a master or transaction data table: Only customizing tables can
be put in BC Sets.
It is a system table (e.g. TADIR)
It is a table/view with forbidden key fields:
The table has an address field in the key (key fields with domains of
type 'ADRNR', 'CADRNR' and 'AD_ADDRNUM' are not allowed)
The table/view has a field of type GUID/UUID (global/universal unique
identifier). These fields are not allowed in views and tables with
generated maintenance dialogs. In database tables without generated
maintenance dialogs, they can be put in the BC Set.
The table/view has a field of type 'STRING' or 'RAWSTRING' in the key
The table/view has a field in the key which is more than 255 characters
wide
The table/view is explicitly excluded. This is the case for some SAP
tables which are not allowed in BC Sets for reasons which the person
responsible for the table can explain.
The table/view &V1& is not put in the BC Set, i.e. no entries from this
table are copied.
If the BC Set already contains data records from this table/view (e.g.
if the table/view used to exist, but has been deleted), they are
automatically deleted when you save the BC Set.
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.
SCPR365
- Table/view &1 cannot be put in a BC Set ?The SAP error message SCPR365, which states "Table/view &1 cannot be put in a BC Set," typically occurs when you attempt to include a table or view in a Business Configuration Set (BC Set) that is not allowed. BC Sets are used in SAP to transport configuration settings between systems, and not all tables or views are eligible for inclusion in BC Sets.
Cause: Ineligible Objects: The object you are trying to include in the BC Set is not designed to be part of a BC Set. This can include certain system tables, temporary tables, or tables that are not meant for configuration purposes. Technical Restrictions: Some tables may have technical restrictions that prevent them from being included in BC Sets due to their nature or the way they are used in the system. Custom Development: If the table or view is a custom development, it may not have been properly defined to be
Get instant SAP help. Sign up for our Free Essentials Plan.
SCPR364
System transport not filled
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SCPR363
Activatiin of table/view &1 in BC Set &2 is not supported
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SCPR366
BC Set &1 already exists
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SCPR367
BC Set &1 does not exist
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.