Common unit to diaply at header level

[Former Member]

Hello All,

1.  Is it possible to have the common unit at header level in OLAP? we have this feature in BEX and analysis for excel.

2. Please correct if I am wrong in my below assumptions

a. The workspace autosave cannot be disabled, but the timeout to save can be extended by changing the .xml file (as in admin guide)

b. The column/row length cannot be set to autofit, should be done manually by dragging and adjusting the width as per cell.

c. For a small change like including a scaling factor in BW query will not be reflected in AOLAP?

Thanks.

Regards,

B

[I_MCA · Accepted solution]

Hello Balaji

To answer your questions:

1) Unfortunately Analysis OLAP always displays the units in the cells. This cannot be changed.

2a) The autosave can essentially be disabled by making the MDAS timeout at least double the BI Launchpad timeout. By default the tomcat timeout is 30 mins and the BI Launchpad timeout is 20 mins. This means BI will timeout before the web app server.... which is good. There is also an MDAS timeout (in mdas.properties) which is set to 30 mins. But AOLAP will autosave after 50% of that timeout has elapsed. In other words it will autosave after 15 mins. But this activity resets all the timeout counters. AOLAP will not autosave again if there continues to be no activity so the next time BI will timeout after 20 mins. In short, with autosave the real world timeout is 35 mins. If you set the MDAS timeout to be > 40 mins then BI will timeout before 50% of the MDAS timeout has elapsed... but the real world time will now be 20 mins.

2b) Not having autofit was a deliberate design decision. Because AOLAP pages in its data, at any given time it does not know the maximum width. It would be visually distracting if the widths kept resizing based on the current data, plus it would be a performance impact. Note that in the Properties task panel for the crosstab there is a setting that allows the widths of all columns to be changed at once. So you can quickly set a general width then manually changes those few columns widths as appropriate.

2c) AOLAP is an Analysis tool, not a reporting tool. It is designed to give analysts and business users the power to display their data as they want it, in an "easy to use" environment. Consequently it is able to manipulate the data in many of the same ways that the data can be manipulated in the query designer. Scaling factor is one such option. If the scaling factor is changed in the query, it is ignored by AOLAP because the scaling factor can also be changed in AOLAP. If AOLAP honoured the change in the query, then this would negatively impact the values displayed in all the existing AOLAP workspaces.

Hope the above helps to clarify.

Regards

[Former Member · Accepted solution]

Thanks Ian for your detailed reply. Will try out and let you know.

Regards,

B

[former_member621877]

Hello,

You can use Unit
conversions in the KF.

Once you maintain
unit conversion, the common unit will be displayed on the title of the column.

Steps are explained
in Below white paper:

Reporting
Data in Alternate Unit of Measure in BI 7.0 - SAP ...

It’s a 10 min job.

Thanks,

Jaydip Patel.

[Former Member]

Any reply on my question is appreciated.