How to replace InfoObject with many attributes

[Former Member]

Hello,

our customer have in old system InfoObject with almost 150 attributes (the most of them are navigational) and then use this InfoObject as characteristic in InfoCube. We now think how can we replace this InfoObject in new system by another solution (providing the same/similar functionalities) because we are afraid of performance issues in the future (due to too many navigational attributes).

Do you have any recommendation/ideas?

Thank you in advance.

BR,

Jan Fic

[RamanKorrapati]

Hi Jan,

Accept with suman. No need to worry about number of attributes. just look at attributes how many are useful as your business needs. According them you set those settings at cube level or multi provider level.

When you want use the same functionalityies at new system, need to find all used nav attr and make them as enable at cube level. You can use query read modes and cache mode to improve the report performance.

Thanks

[Former Member]

Thank you Suman and Ramanjaneyulu for your replies.

Problem is that customer will probably need all 150 attributes from old system + some new ones. If you have almost 200 navigation attributes in 1 InfoObject with still growing amount of data (more than 1M records is now in old system) then can MasterData activation run very long time.

So we are not afraid only about the report performance, but we can have performance issues already by data load.

[MGrob]

Hi

Are they all needed as navigational attributes? If you would be able to derive them during the data load you can use them on transactional basis rather then nav attributes.

Are these attributes really all related to the same masterdata object? Maybe you can also group them in a more logical way.

hope that helps

Martin

[RamanKorrapati]

Hi,

if possible, is there any chance to add those info objects to info cube and fill thru routine or enhancing the data source. Check about those 200 attributes if possible load thru other master data/transaction objects. it will be good one if we reduce the navigation attr count from one info object.

Thanks

[former_member182470]

Hi Jan,

Nav Attrs are supplemental information of your main char. You can still have 200 Attrs(display and Nav) put together. If you so much concerned about the performance, then split your 200 Attrs in to another Char. I mean, you have to choose any other similar infoobject which can have similar Attrs and assign 100 Attrs to first char and assign 100 Attrs to second char.

Finally you can use these two main chars in your cube and switch on the required Nav Attr in the cube.

But my advice is, just live with 200 Attrs with the main Char. Infoobjects are meant to load huge amounts of data. You can fine tune Atr Change runs and Aggr Roll ups with other techniques.

Regards,

Suman

[former_member182470]

It all depends on the business requirement. If you do not want to use too many drill chars in your reports and if you don't want to use too many nav attrs in your query, then you can simply uncheck them in your cube-->Nav attr section.

Unless you use them , there is no harm to your cube or query. Your ACR will take some time and Aggr roll up may take some time, that's it..