MultiCubes can be maintained using MultiProvider transaction from Rel 3.0

What causes this issue?

In Release BW 3.0A, the concept <ZH>MultiCubes has been extended to the
concept MultiProvider</>.
<ZH>MultiCubes </>exclusively contain InfoCubes whose data was grouped
together in the MultiObject by union operation. This concept has now
been extended so that additional BW objects such as DataStore objects
and InfoObjects can also enter the MultiObject (data merging through
union operation has remained the same). The name <ZH>MultiCube</> was no
longer suitable here and the more generalized term <ZH>MultiProvider is
now used</>. To classify the BW Objects, an individual BW TLOGO Object
<ZH>MultiProvider</> was created from a special InfoCube type (for
example, an InfoCube subset). This new BW LOGO object can be defined
using a newly created, separate maintenance transaction. This looks
exactly the same as the previous transaction from the user interface.

System Response

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

How to fix this error?

Maintain the previous MultiCube using the maintenance transaction for
MultiProvider. No particular conversions or other actions are required
to do this. The object will no longer appear as an InfoCube but as a
MultiProvider instead. In other words, another transaction is only
started after object maintenance is initialized.
MultiProviders (like MultiCubes previously) can also consist exclusively
of standard InfoCubes. All queries defined for MultiCubes are therefore
still valid.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.