How To Fix RSO_SEGR036 - Sem. Group '&1': DB-partitioning could not be adapted for member '&2'

SAP Error Message - Details

• Message type: E = Error

• Message class: RSO_SEGR - Messages for TLOGO = SEGR (Semantic Group of ADSOs)

• Message number: 036

• Message text: Sem. Group '&1': DB-partitioning could not be adapted for member '&2'

What causes this issue?

It is not possible to derive a database-partitioning schema for member '
<(>&<)>1' from the database-partitioning schema of the reference
advanced DataStore object.
The system therefore tried to create the member without any
database-partitioning schema.
This might result in errors during activation, for example if a
temperature-schema is used, which explicitly needs a
database-partitioning schema.
The following two methods are used to derive a partitioning schema from
the reference:

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

first scenario:
The interval, which is defined by the smallest and the largest value in
the db-partitioning of the reference, includes the
semantic-group-criteria of the current member.
For each member, the system now computes the 'intersection' between the
db-partitioning schema and the semantic-group-criteria, as used as
db-partitioning-schema of the member. (Because of the
half-open-intervals, which are used to specify the db-partitioning
schema, the intersection might not be correct, with the upper bound
larger than needed.)
If the derived db-partitioning is empty, the member is created without
any db-partitioning.
Example:
reference-ADSO:
db-partitioning: [2000], [2001], [2002], [2003-2006[, [2006]
members:
semantic-group-criteria:
MEMBER1: 2000, 2003-2004
MEMBER2: 2001-2002
MEMBER3: 2005
MEMBER4: 2006
MEMBER5: 2007
derived db-partitioning:
MEMBER1: [2000],[2001],[2002],[2003-2006[ <<< 2. and 3. interval
are added as they lie in the range
< 4.interval is not shrunk
MEMBER2: [2001],[2002]
MEMBER3: [2005-2006[
MEMBER4: [2006]
MEMBER5: <<<
empty intersection, no partitioning
second scenario:
This method to derive the db-partitioning schema is only used for
time-characteristics.
Here it is tried to replicate and adapt the existing db-partitioning
schema of the reference adso to the members.
(The algorithm computes the difference between the min value of the
db-partition and the semantic-group-criteria and then move all intervals
of the db-partitioning by this difference.)
If different time-characteristics are used in the db-partitioning of the
reference and the semantic-group-criteria, the system tries to convert
the times.
This is not always possible however, for example because of different
numbers of periods per year for '0CALWEEK' and '0FISCPER' (for certain
fiscal-variants).
Example:
reference-ADSO:
db-partitioning: [01.2000],[02.2000-04.2000[,[04.2000]...[12.2000]
members:
semantic-group-criteria:
MEMBER1: 2000 = [01.2000-12.2000]
MEMBER2: 2001 = [01.2001-12.2001]
MEMBER3: 2002 = [01.2002-12.2002]
derived db-partitioning
MEMBER1: [01.2000],[02.2000-04.2000[,...[12.2000] <<< this is
handled via scenario 1
MEMBER2: [01.2001],[02.2001-04.2001[,...[12.2001]
MEMBER3: [01.2002],[02.2002-04.2002[,...[12.2002]

System Response

How to fix this error?

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 RSO_SEGR036 - Sem. Group '&1': DB-partitioning could not be adapted for member '&2' ?

  The SAP error message RSO_SEGR036 indicates an issue with the database partitioning for a specific semantic group in the context of SAP BW (Business Warehouse) or SAP BW/4HANA. This error typically arises when there is a problem with the data model or the configuration of the semantic group.
  Cause:
  
  Inconsistent Data Model: The semantic group may have inconsistencies in its data model, such as missing or incorrectly configured InfoObjects or InfoProviders.
  Database Partitioning Issues: The database partitioning settings for the semantic group may not be correctly set up or may have become corrupted.
  Transport Issues: If the semantic group was transported from one system to another, there may be issues with the transport that affect the database partitioning.
  Missing Authorizations: The user executing the operation may not have the necessary authorizations to modify the database partitioning settings.
  
  Solution:
  
  Check Data Model: Review the data model associated with the semantic group. Ensure that all InfoObjects and InfoProviders are correctly defined and activated.
  Reconfigure Database Partitioning: Go to the semantic group settings and check the database partitioning configuration. You may need to reconfigure or reset the partitioning settings.
  Transport Validation: If the issue arose after a transport, validate the transport request to ensure that all necessary objects were included and correctly transported.
  Authorization Check: Ensure that the user has the necessary authorizations to perform operations on the semantic group and its database partitioning.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error. There may be patches or updates that resolve known issues related to this error message.
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like RSA1 (Data Warehousing Workbench) to access the semantic group and its settings.
  SAP BW Documentation: Refer to the official SAP BW documentation for detailed information on semantic groups and database partitioning.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  
  If the problem persists after trying the above solutions, consider reaching out to SAP support for further assistance.