BPC Transport Too many characteristics (024) are assigned to dimension

[abraham_mendez]

Hi Gurus,

We are implementing BPC Consolidation for NetWeaver 7.5, and we're facing the following situation:

Too many characteristics (024) are assigned to dimension /CPMB/Q6IW0EVD

Diagnosis

Too many characteristics are assigned to the given dimension.

For a "normal" InfoCube, the database table to be created for a dimension may contain a maximum of 249 fields. This means that no more than 248 characteristics may be assigned.

However, if the property "DIMIDs One-to-One" is set, a unique index on the characteristics of the dimension is created. In this case each dimension may not contain more than 16 characteristics.

Any suggestions?

Thanks in advance

Best Regards

Abraham Méndez

[abraham_mendez]

Full optimization seems not working correctly.

[Former Member]

Hi Abraham,

Did you find any solution to this issue? i am having the same issue when doing a transport.

Any help would be really appreciated.

Thanks,

Carlos

[abraham_mendez]

Hi Sheldon,

Thanks for answering my question.

I already ran that full optimization you talked about but i dont see some changes in BW, what i can see is the shadow cube that the full optimization creates but i cant see how the full optimization solves that bunching of too many BPC dimensions on one BW cube dimension afterwards.

The fact is that when the transport order generated by BPC transaction UJBPCTR is imported into the Productive environment the error still raising, with the same description:

u201CToo many characteristics (024) are assigned to dimensionu201D

Could you help me by telling me how full optimization solves that dimension bunching? Another question is Why does the error appear until the transport order is imported and not when you are working in development?

Thanks in advance.

Regards.

Abraham Mendez.

Edited by: Abraham Mendez on Apr 29, 2011 5:13 PM

[SEdelstein]

Hello Abraham -

I am assuming that the error message you are posting is referring to too many BPC dimensions being assigned to one BW cube dimension.

If you run a full optimization process on the targeted application the system will reorganize the BW cube dimensions for optimum performance. The bunching of too many BPC dimensions on one BW cube dimension should also be resolved after optimization.

Regards,

Sheldon

[abraham_mendez]

Hi Sheldon,

Thanks for answering my question.

I already ran that full optimization you talked about but i dont see some changes in BW, what i can see is the shadow cube that the full optimization creates but i cant see how the full optimization solves that bunching of too many BPC dimensions on one BW cube dimension afterwards.

Could you help me by telling me how full optimization solves that dimension bunching?

Thanks in advanced.

Regards.

Abraham Mendez.