cancel
Showing results for 
Search instead for 
Did you mean: 

Inactive MultiProvider

Former Member
0 Kudos

Hello,

During transport of out BPC-solution we get the following warnings and errors:

InfoObject /CPMB/G8DJBGV__/CPMB/G8P6O8J does not exist in InfoProvider /CPMB/G8IGBLG; Assignment was deleted

Assignments for InfoObject /CPMB/G8DJBGV__/CPMB/G8P6O8J have not yet been maintained -> Long text

InfoObject /CPMB/G8DJBGV__/CPMB/G8P9T79 does not exist in InfoProvider /CPMB/G8IGBLG; Assignment was deleted

Assignments for InfoObject /CPMB/G8DJBGV__/CPMB/G8P9T79 have not yet been maintained -> Long text

InfoObject /CPMB/G8DJBGV__/CPMB/G8PBR8Z does not exist in InfoProvider /CPMB/G8IGBLG; Assignment was deleted

Assignments for InfoObject /CPMB/G8DJBGV__/CPMB/G8PBR8Z have not yet been maintained -> Long text

InfoObject /CPMB/G8DJBGV__/CPMB/G8PC29V does not exist in InfoProvider /CPMB/G8IGBLG; Assignment was deleted

Assignments for InfoObject /CPMB/G8DJBGV__/CPMB/G8PC29V have not yet been maintained -> Long text

InfoObject /CPMB/G8DJBGV__/CPMB/G8PCUWX does not exist in InfoProvider /CPMB/G8IGBLG; Assignment was deleted

Assignments for InfoObject /CPMB/G8DJBGV__/CPMB/G8PCUWX have not yet been maintained -> Long text

InfoObject /CPMB/G8DJBGV__/CPMB/G8PM9Z4 does not exist in InfoProvider /CPMB/G8IGBLG; Assignment was deleted

Assignments for InfoObject /CPMB/G8DJBGV__/CPMB/G8PM9Z4 have not yet been maintained -> Long text

InfoObject /CPMB/G8DJBGV__/CPMB/G8PS386 does not exist in InfoProvider /CPMB/G8IGBLG; Assignment was deleted

Assignments for InfoObject /CPMB/G8DJBGV__/CPMB/G8PS386 have not yet been maintained -> Long text

Inconsistencies were found when checking MultiProvider /CPMB/G8MGBLG

Error activating MultiProvider /CPMB/G8MGBLG

Failed to create dimension attribute

As a consequence of this the MultiProvider in the test system is sometimes (but not always) inactive after transporting.

The reason for the messages is that several attributes are marked as navigational in the MultiProvider but not in the cube. But this is all controlled by BPC so it seems to be a bug. I don't know why BPC defines some attributes as navigational. I don't see why "navigational attributes" would have a meaning for BPC at all.

Has anyone else experienced this problem? Have you found a workaround?

Best regards,

Christoffer Owe

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

I met the same problem today and found this thread. Our situation is opposite to yours: We check the navigation attribute in base cube but multiprovider. Here is the solution and wish it helpful if others have the same problem:

Click on "Identify Characteristics" (pushbutton), find your infoobject, then check. After that, you can active your multiprovider.

Tim

Answers (2)

Answers (2)

0 Kudos

Hello,

One very important information regarding the table RSDCHABAS:

if there is no entry to iobj 0REQUID in version 'A' in this table, you MUST NOT change the table RSDCHABAS directly.

Instead, please reactivate the InfoObject 0REQUID to recover the record as follows:

- run transaction RSD5,

- enter 0REQUID in the InfoObject field,

- click on the 'Activate' button.

Regards,

Olivier Vidal

pravin_datar
Employee
Employee
0 Kudos

Did you try to transport /CPMB objects through BW transport manually? BPC related BW objects should not be transported with BW transports. UJS_ACTIVATE_CONTENT may be useful in resolving some of these errors.

Regards

Pravin

Former Member
0 Kudos

Hello,

We have always tried to avoid that. We transported the cube once though. That was after building some transformations which were not included in the BPC-transport. I created a transport using Transport Connection and added the transformation to this transport. The cube was included as a mandatory object. I considered editing the transport to remove the cube, but regarded this as a risk as well. To elimitate the problem you describe, we imported a BPC-transport afterwards.

I still think it is unlikely that this have caused inconsistensies between the InfoCube and the MultiProvider in the development system. And it's this inconsistency (which strangely enough has never caused an inactive MP in development) that causes the problems after import in the test system.

Best regards,

Christoffer Owe

Former Member
0 Kudos

Hi,

we faced the same problem. We solved it in a customer message. Here is SAP OSS answer.

BW team has updated the message, as they mentioned, the active version of 0REQUID in table RSDCHABAS is missing, they advise you to add the entry in table or re-install this content.

Regards

Jan