AWM Calculated MESURE

Hi All,
I created a dimensions and a cube using AWM.
My dimension name dimens_x with levels level1_x_id and level2_x_id( which maps a table tab_x in my database column1_x and column2_x)
My cube name is cube1
I need to create a calculated mesure number_elements_diff_than_value
I created it using the wisard, but my problem is the correct syntax of the MDX query I need to have : My mesure needs to do something like this : select count() from My_FACT_TABLE where level1_x<> 'value'; *
The mesure must give, for each dimension, the number of rows in the fact table where the value of the column level1_x( dimension dimens_x )
I need the query to put in AWM wizard when creating the calculated mesure ...
Any clue ??
Thanks so much !!

If you are looking for a COUNT measure, then see the following old posts by David Greenfield:
Count of Weeks where a certain measure is > 0
A measure to calculate distinct count
Analytic workspace manager - simple count?
.

Similar Messages

AWM Calculated Measure for Percent of Total Across Multiple Dimensions?

I noticed that AWM has a Share function that gives me a percent total of a grain from a specific hierarchy's Top of Hierarchy, but is there any way to do that with multiple dimensions? For example, if I had a Share of Dimension X = 55% Where Time = 1/1/2013 and a Share of Dimension Y = 32% Where Time = 1/1/2013, then could I have a Share of both Dimension X and Dimension Y = 16% Where Time = 1/1/2013?

I had used an alternate solution which is a bit more cumbersome using native OLAP_DML formulae/expression.
The above expression using OLAP Expression Syntax is much better (if it works).
I was not aware of this OLAP expression syntax when i needed to create a kpi for similar requirement.
We had Qty measure and Share along dimension like "Qty - Share at Year level", "Qty - Share of Total Customer".
We needed to get "Qty - Share at Total Customer, Year".
Cube= SALESCUBE
Base Meas = QTY
Step 1) Create Measure which represents "Qty - Total Customer, Year" which will work in any reporting context ...
Note: For time=day1/2/3/ within same year and customer=cust1/2/3/... or Total Customer, the expression result will be constant (result fixed for any dimension members/status along the 2 dimensions - TIME and CUST). Denominator Value changes each year since we have constrainted time dimension to the ancestor of current cell at YR level. If we choose anscestor at TOP level TOTTIME say then the value is fixed for all time dimension members/values.
olap dml expression: QUAL(SALESCUBE_QTY, CUSTOMER limit(CUSTOMER to CUSTOMER_LEVELREL 'TCUST'), TIME limit(limit(TIME to ANCESTORS USING TIME_PARENTREL TIME(TIME TIME)) KEEP TIME_LEVELREL eq 'YR'))
in awxml - this becomes:
ETMeasureColumnName="QTY_TCUST_YR"
Name="QTY_TCUST_YR"
MeasureExpression="OLAP_DML_EXPRESSION('QUAL(SALESCUBE_QTY, CUSTOMER limit(CUSTOMER to CUSTOMER_LEVELREL ''TCUST''), TIME limit(limit(TIME to ANCESTORS USING TIME_PARENTREL TIME(TIME TIME)) KEEP TIME_LEVELREL eq ''YR''))', NUMBER)">
<Classification
Value="AwmDescriptionType=OLAP_DML_CALC"/>
<Description
Type="LongDescription"
Language="AMERICAN"
Value="Qty - Total Customer, Year">
Step 2) Define the share measure explicitly since we have already calculated the denominator needed for composite share.
Check for division by 0 error before performing the share calculation explicitly as Numerator= Qty (for current cell/reporting context) and Denominator = Qty - Total Customer, Year (from Step 1)
olap dml expression: if SALESCUBE_QTY_TCUST_YR ne 0 then SALESCUBE_QTY / SALESCUBE_QTY_TCUST_YR else na
in awxml - this becomes:
ETMeasureColumnName="QTY_SHARE_TCUST_YR"
Name="QTY_SHARE_TCUST_YR"
MeasureExpression="OLAP_DML_EXPRESSION('if SALESCUBE_QTY_TCUST_YR ne 0 then SALESCUBE_QTY / SALESCUBE_QTY_TCUST_YR else na', NUMBER)">
<Classification
Value="AwmDescriptionType=OLAP_DML_CALC"/>
<Description
Type="LongDescription"
Language="AMERICAN"
Value="Qty - Share of Total Customer, Year">
</Description>
Report needs to use measure QTY_SHARE_TCUST_YR (Qty - Share of Total Customer, Year) defined in Step 2. It may be useful to expose/display intermediate measure QTY_TCUST_YR also so as to make the basis of calculation very clear to the user.
Nick,
If you customize above soln. to use Total Time, Total Prod and Total Organization (along 3 dimensions)... I am sure the fact table has a time dimension which should also be factored in in your calc/defn.
If you have missed out the join to Time dimension from fact in your queries, in olap reporting terms, its similar to Time Dimension selection of Time level = TTIME Total Time (1 node at TOP).
You need:
Step 1) Qty - Total Time, Total Product and Total Org
Step 2) Qty - Share of Total Time, Total Product and Total Org
Then the example you gave should be covered via QTY and QTY_SHARE_TTIME_TPROD_TORG (Step 2)
SUM(quantity)
2875should be QTY, QTY_SHARE_TTIME_TPROD_TORG (=100%) at Time level = TTIME, Product level = TPROD, Org level = TORG
SUM(quantity)
345 [12% of all products sold]should be QTY, QTY_SHARE_TTIME_TPROD_TORG (=12% hopefully) at Time level = TTIME, Product level = PROD with report filter on product = 'CX-867054', Org level = TORG
SUM(quantity)
977 [34% of all products sold]should be QTY, QTY_SHARE_TTIME_TPROD_TORG (=34% hopefully) at Time level = TTIME, Product level = TPROD, Org level = STORE with report filter on store = 'NY_ALBA_013'
SUM(quantity)
88 [3.06% of all products sold]should be QTY, QTY_SHARE_TTIME_TPROD_TORG (=3.06% hopefully) at Time level = TTIME, Product level = PROD with report filter on product = 'CX-867054', Org level = STORE with report filter on store = 'NY_ALBA_013'
HTH
Shankar

10.2.0.1.0A AWM calculations not correct

I use 10.1.0.4 olap database, i have started using 10.2.0.1.0A AWM .
Dimensions are created as follows
1) create one level (this is from database table that contains 2 columns a)id b)id_desc )
2) create hierarchy -->level based and choose the above level
3) map dimension , i connect id of the dimension table to Member and id_desc to LONG_DESCRIPTION and SHORT_DESCRIPTION
Then I maintain the dimension and view the dimension, all the data is perfect.
Similarly my second dimension
I have created cube as follows.
1)create new cube, i do not choose "Use default aggregation plan for cube aggregation"
I choose the two dimensions i have created.
2)Under implementation details
a) sparse is checked.
b) Use Global Composites is checked
c) use compression is not checked
d) Partion cube is not checked
3) Under Rules operator is "SUM".
aggregation Hierarchies all the boxes are checked.
4) Under Summarise To
the two levels of two dimensions are checked.
5) Under Cache
Cache runtime aggregations using session cache is choosen
The above is applied
Next a measure is created
1)"Use aggregation specification from the cube" is choosen
2) Implementation details,rules,summarize to and cache are same as cube creation.
Mapping the cube:-
the 2 id's of fact table are connected to level discriptions under "Dimensions" and one measure of the fact table are
connected to "MEASURES"
Next Maintain cube "Aggregate the full cube" is choosen.
Then view the data. Then I i see the two dimension with measures."BUT THE MEASURE IS NOT THE SUM OF FACT VALUES(DATA)" .
MY FACT IS AS FOLLOW:-
ID1 ID2 MEASURE
1 1 10
2 1 10
3 16 25
4 1 10
3 1 20
MY DIM1 IS AS FOLLOWS:-
ID1 DESCRIPTION
1 DESC1
2 DESC2
3 DESC3
4 DESC4
MY DIM2 IS AS FLOOWS:-
ID2 DESCRIPTION
1 DISC_1
16 DISC_2
26 DISC_3
IN THE CUBE IT APPEARS AS FOLLOWS
NOTE: FOR MY MEASURE - RULE- OPERATOR IS "SUM"
MEASURE
(ID1) ----> DESC1 DESC2 DESC3 DESC4
(ID2)
|
DISC_1 1 1 2 1
DISC_2 # # 2 #
So the MEASURE is not getting aggregated according to the rule.
Kindly help!!
regards,
ROOPA

Scott
I think what you said is absolutely true ,
As I drilled down the the Sales cube created using AWM 10.2.0.1.A and selected following memebers
1)time:---------Jan-04
2)channel:----Catalog
3)customer:--Computer Services Toronto
4)product:-----Mouse Pad
measures:Sales-------Units
results:-------40 ----------53
When I picked the records from fact table for the above criteria, surprise!!!!!!
1 select a.sales,a.units,a.month_id, b.item_dsc,c.ship_to_dsc,d.channel_dsc
2 from units_history_fact a,product_dim b,customer_dim c,channel_dim d
3 where a.item_id=b.item_id and a.ship_to_id=c.ship_to_id and a.channel_id=d.channel_id
4* and a.item_id=30 and a.month_id=103 and a.channel_id=3 and a.ship_to_id=56
SQL> /
---SALES---------UNITS----MONTH_ID---ITEM_DSC--------------SHIP_TO_DSC-----------------CHANNEL_DSC
40.2161062---------53-------103---Mouse Pad--------------Computer Services Toronto-----Catalog
40.2161062---------53-------103---Mouse Pad--------------Computer Services Toronto-----Catalog
40.2161062---------53-------103---Mouse Pad--------------Computer Services Toronto-----Catalog
40.2161062---------53-------103---Mouse Pad--------------Computer Services Toronto-----Catalog
I HAVE 4 records.
and my sum of all the above should have been as follows
1 select sum(a.sales),sum(a.units), a.month_id, b.item_dsc,c.ship_to_dsc,d.channel_dsc
2 from units_history_fact a,product_dim b,customer_dim c,channel_dim d
3 where a.item_id=b.item_id and a.ship_to_id=c.ship_to_id and a.channel_id=d.channel_id
4 and a.item_id=30 and a.month_id=103 and a.channel_id=3 and a.ship_to_id=56
5* group by a.month_id,b.item_dsc, c.ship_to_dsc, d.channel_dsc
SQL> /
SUM(A.SALES)--SUM(A.UNITS)--MONTH_ID---iTEM_DSC-----------------SHIP_TO_DSC------------------CHANNEL_DSC
160.864425-----212-------103------Mouse Pad-----------------Computer Services Toronto-----Catalog
As you said AWM is not aggregating but replacing it with similar record.
Materialized views means more storage and my fact has 40 million records and 9 dimensions.
Then what is the point to using oracle OLAP feature. I am working in cross platforms OLAP environments, it is not this complicated.(i mean MS olap).
Any other solutions please let me know.........
Thankyou,
Regards
Roopa

New object at universe designer

Hello Gurus,
1.Can we Create a new Object at Universe designer on top SAP BW.

Hi ,
Here is the MDX syntax for creating a calculated mesure object in the universe.
<EXPRESSION>@Select(Key Figures\Order Amount)*@Select(Key
Figures\Order Quantity)</EXPRESSION>
Go through the below link to know how to customize olap universe(from page#427)
http://help.sap.com/businessobject/product_guides/boexir31SP3/en/xi31_sp3_designer_en.pdf
Thanks,
Pramod

Change the Label of a measured calculation in AWM-Model view

Hello,
Is there a way to change the name of a Short or Long Label of a measured calculation in the AWM (Analytic Workspace Manager) without dropping & re-creating it?
In the Model view it does allow you to make the changes to the label in the text field, and it does prompt you to apply changes. I Selected OK. However when I exit out of the AWM & log back in... I saw the old name back in :). It was like the changes were not "committed".
Thanks!

Hi
Thanks for your help, actually that option works for the total displayed as the latest row, I mean the label for the total row. However, for the total column, the name stays as the same as the measure label.
Can you further help me on the issue?
Thanks

Problem with calculating measures in AWM

Hi,
We created dimensions and cubes in AWM (or in OWB) - without using materialized views. We we maintain cube using sum, min and max aggregation function eberythink is OK - we can see data in views, but when we maintain cube using other function e.g. average we see, that in view we have aggregated data using sum function, so:
sum makes sum
min makes min
max makes max
other functions makes sum
Oracle DB 11gR2 for win 64-bit
awm latest version 11.02 patchA
what to do? maybe we don't understand something?

One more time:
Hello,
I checked it. Unfortunately You're wrigth. I have simple CUBE AW_T5_V2 with three measures:
cena,
przebieg,
rok
and two simple dimensions:
aw_kolor with levels
KOLOR and
ODCIEN (ODCIEN_ID is foreign key)
aw_model with levels
MARKA
MODEL
SILNIK (SILNIK_ID is foreign key)
In point 1. and 2. everything is OK. (I mean in cube definition in dba_cubes:
SOLVE
AVG
ALLOW OVERFLOW
ALLOW DIVISION BY ZERO
IGNORE NULLS OVER CPOWBADMHD.AW_KOLOR,
AVG
ALLOW OVERFLOW
ALLOW DIVISION BY ZERO
IGNORE NULLS OVER CPOWBADMHD.AW_MODEL
and in AGG_MAP definition in OLAP Worksheet
DEFINE AW_T5_V2_SOLVE_AGGMAP AGGMAP LOCKDFN
AGGMAP
RELATION this_aw!AW_KOLOR_AGGRREL(this_aw!AW_T5_V2_SOLVE_AW_KOLOR_HVSET) PRECOMPUTE(NA) OPERATOR AVERAGE args DIVIDEBYZERO YES DECIMALOVERFLOW YES NASKIP YES COUNT YES
RELATION this_aw!AW_MODEL_AGGRREL(this_aw!AW_T5_V2_SOLVE_AW_MODEL_HVSET) PRECOMPUTE(NA) OPERATOR AVERAGE args DIVIDEBYZERO YES DECIMALOVERFLOW YES NASKIP YES COUNT YES
AGGINDEX NO
CACHE SESSION
END
But in cube_build_log I can see script in OUTPUT column:
<SQL>
<![CDATA[
SELECT /*+ bypass_recursive_check cursor_sharing_exact no_expand no_rewrite */
T14_ODCIEN_ID ALIAS_51,
T11_SILNIK_ID ALIAS_52,
SUM(T17_CENA) ALIAS_53,
SUM(T17_PRZEBIEG) ALIAS_54,
SUM(T17_ROKPROD) ALIAS_55
FROM
SELECT /*+ no_rewrite */
T1."PRZEBIEG" T17_PRZEBIEG,
T1."CENA" T17_CENA,
T1."ROKPROD" T17_ROKPROD,
T1."AW_KOLOR" T17_AW_KOLOR,
T1."AW_MODEL" T17_AW_MODEL
FROM
CPOWBADMHD."AW_T5_TAB" T1 )
T17,
SELECT /*+ no_rewrite */
T1."DIMENSION_KEY" T14_DIMENSION_KEY,
T1."ODCIEN_ID" T14_ODCIEN_ID
FROM
CPOWBADMHD."AW_KOLOR_TAB" T1 )
T14,
SELECT /*+ no_rewrite */
T1."DIMENSION_KEY" T11_DIMENSION_KEY,
T1."SILNIK_ID" T11_SILNIK_ID
FROM
CPOWBADMHD."AW_MODEL_TAB" T1 )
T11
WHERE
((T14_DIMENSION_KEY = T17_AW_KOLOR)
AND (T11_DIMENSION_KEY = T17_AW_MODEL) )
GROUP BY
(T11_SILNIK_ID, T14_ODCIEN_ID)
ORDER BY
T11_SILNIK_ID ASC NULLS LAST ,
T14_ODCIEN_ID ASC NULLS LAST ]]>/>
</SQL>
It should be AVG, where is SUM (I've checked that, when I update agg method to min or max function is changing from sum to mix or max). I suppose SQL should sum measures and devide by number of records.
OK, we know where is bug, what to do?

How to create an unsolved cube with awm???

hi all,
I readed the "Oracle Olap developer's guide to the Oalp api" and I found there's 2 type of Cube: Solved and Unsolved Cubes. And this document says: "... if all the data for a cube is specified by the DBA, then the cube is considered to be Solved. If some or all of the aggregate data must be calculated by Oracle OLap, then the cube is unsolved ..."
I tried with awm 10.2.0.3.0A to create an unsolvedCube but I can't. All cubes I created are solvedCube. To know if a cube is solved or unsolved, I wrotte an program in Java to read informations of package mtm.
Some one can tell me how to create an unsolved cube with AWM ou other soft please!

SH is not a relational OLAP data model which is quite different from the GLOBAL schema which is based on an Analytic Workspace.
If you change the aggregation method you will need to re-compute the whole cube which can be a very big job! You might be able to force the unsolved status be de-selecting all the levels on the Rules tab in AWM. However, I think by default analytic workspace OLAP models always provide a fully solved cube to the outside world. This is the nature of the multi-dimensional model.
Relationally, as keys are located in separate columns a cube can be unsolved in that the key column only contains values for a single level from the corresponding dimension tables. If more than keys for different levels within the same dimension appear within the fact key column then the cube is deemed as being solved.
Therefore, I am not sure you are going to get the information you require from the API. To changes the aggregation method you will have to switch off all pre-compute options and also disable the session cache to prevent previously calculated data being returned when you change the aggregation method.
Hope this helps
Keith Laker
Oracle EMEA Consulting
BI Blog: http://oraclebi.blogspot.com/
DM Blog: http://oracledmt.blogspot.com/
BI on Oracle: http://www.oracle.com/bi/
BI on OTN: http://www.oracle.com/technology/products/bi/
BI Samples: http://www.oracle.com/technology/products/bi/samples/

Nested Object Calculation using Adobe InDesign with JavaScriptExtended.

Hi
                      In my App.Document have different types of textframes and images with several parastyles. I want to make mesurement calculation (in mm)the between the particular parastyle data with image using Adobe JavaScriptExtended.
Ex:
<start:>
      <Obj:Image>abc.bmp
      <Para:Name>Sen
      <Para:Add>345, Annan Street
      <Para:City>KKT
<End:>
                     Like above, I have created data with different format, but I would like to calculate (between <start:> and <End:>)this particular type of data in my app.document.
Note:
        1. Parastyles are applied in Adobe Indesign
        2. Data from Tagged Text.
        3. Mesurement in .jsx [javascriptExtended].
                     I can mesure this issue, but the image indent was distrub to provide accurate mesurement. Please help me to solve this problems.
Thanks and Regards
Sen

I do know next to nothing about CEP5.
Just a question: Why do you try to escape "/" in the string "editor-vaCome\/ibraEEE" ?
At least this is my guess what you want to do here…
If you want to feed the argument string "editor-vaComet/ibraEEE" to peer.connect() you cannot "escape" that slash… At least not in terms of ExtendScript.
Uwe

Help me! AWM "maintain cube ... " performance: too slow with a small cube

Hi all,
I have 3 dimensions: TIMES, PRODUCTS, STORES
The hierarchy of TIMES, is in the order: year, quarter, month, week, day
The hierarchy of Products is in the order: sector, family, sub-family, product
The hierarchy of STORES is in the order: area, department, store
each hierarchy is mapped with a data set and the size is
730 lines (days) for the TIMES dimension
282 lines (products) for the PRODUCTS dimension
237 lines (stores) for the STORES dimension
With these dimensions, I create a cube and 2 measures: QUANTITY, BENEFIT
My measures used all 3 dimensions : TIMES, PRODUCTS, STORES.
I mapped in the end my cube with a dataset contains: store, day, product, quantity, benefit
This data set has 3921 lines.
I chosed the rule to aggregate all dimensions is SUM.
So when I do "maintain cube...", AWM takes much time to do it! (approximately 2h to maintain my cube)
Some one knows why it's long?
How can I do to accelerate it?
Due I modify the parameters in AWM or in my cube?
Thanks in advance!

thanks all for your reply!
I done maintain cube already in following your advice. I increased the rollback and tmp space and changed "NUMBER to DECIMAL" as type of data of cube.
But I have other question. I hope you can help me!
1. What's the effect of the option "Choose the regions of the cube to be presummarized and stored in the analytic workspace" in the table "Summarize To" when you create a cube? If I check this option for all hierarchy level, the next time, when I do the request,
the time of calcul will be optimize so fastest?
(I check this option in creating my cube but when I make a request for level of a particular hierarchy, it's so long to have the result. I use a software this can connect and do request from Oracle Olap DataBase.)
2. I done maintain cube last week. Today I created a new cube and added more data set. But I cant maintain cube again. This is the message error. Can you explain to me why?
( I increase already the rollback and tmp space. To know how and what I done, view this thread please!
Error when I do "Maintain Cubes ..." )
--------------------------------------java.sql.SQLException: ORA-00933: SQL command not properly ended
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:111)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:330)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:287)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:742)
at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:206)
at oracle.jdbc.driver.T4CStatement.executeForDescribe(T4CStatement.java:789)
at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1030)
at oracle.jdbc.driver.T4CStatement.executeMaybeDescribe(T4CStatement.java:829)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1123)
at oracle.jdbc.driver.OracleStatement.executeInternal(OracleStatement.java:1678)
at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:1644)
at oracle.olap.awm.dataobject.dialog.olapcatalog.TableDialog.populateTableDataModel(TableDialog.java:164)
at oracle.olap.awm.dataobject.dialog.olapcatalog.TableDialog.initialiseAndPopulate(TableDialog.java:68)
at oracle.olap.awm.dataobject.dialog.olapcatalog.TableDialog.<init>(TableDialog.java:57)
at oracle.olap.awm.wizard.awbuild.BuildWizardHelper.runBuild(BuildWizardHelper.java:252)
at oracle.olap.awm.navigator.node.modeler.cube.ModelerMeasureNode.actionPerformed(ModelerMeasureNode.java:226)
at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
at javax.swing.AbstractButton$ForwardActionEvents.actionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
at javax.swing.AbstractButton.doClick(Unknown Source)
at javax.swing.plaf.basic.BasicMenuItemUI.doClick(Unknown Source)
at javax.swing.plaf.basic.BasicMenuItemUI$MouseInputHandler.mouseReleased(Unknown Source)
at java.awt.Component.processMouseEvent(Unknown Source)
at java.awt.Component.processEvent(Unknown Source)
at java.awt.Container.processEvent(Unknown Source)
at java.awt.Component.dispatchEventImpl(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
at java.awt.Container.dispatchEventImpl(Unknown Source)
at java.awt.Window.dispatchEventImpl(Unknown Source)
at java.awt.Component.dispatchEvent(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
Thanks in advance!

Do awm 10.2.0.3.0A be the same awm 10.2.0.3.0 ???

hi all,
there is many post talk about awm 10.2.0.3.0 and its advances like: Sparcity Advisor ...
I use currently the awm 10.2.0.3.0A and in this version, there's not the function Sparcity Advisor. Can you explain me how to get the awm 10.2.0.3.0? What's differents between this 2 version (freeware, shareware)?
Thanks !

The sparsity advisor is displayed when you right mouse click on a cube. The readme file shows the following information:
http://www.oracle.com/technology/products/bi/olap/awm102030A_readme.html
Analytic Workspace Manager in Release 10.2.0.3.0 provides a Sparsity Advisor, which examines the source data and makes recommendations for defining OLAP cubes that will provide the best performance. The functionality of calculation plans has been enhanced to provide post-load forecasting, allocation, and aggregation. Analytic Workspace Manager also supports Java add-ins, so that any Java developer can extend and customize the tools in Analytic Workspace Manager. Please refer to the Oracle OLAP Application Developer's Guide 10.2.0.3 for further details.
Hope this helps
Keith Laker
Oracle EMEA Consulting
BI Blog: http://oraclebi.blogspot.com/
DM Blog: http://oracledmt.blogspot.com/
BI on Oracle: http://www.oracle.com/bi/
BI on OTN: http://www.oracle.com/technology/products/bi/
BI Samples: http://www.oracle.com/technology/products/bi/samples/

Creating a TEXT calculated measure

Is it possible to create a calculated measure of data type TEXT using AWM ?
I want to do the equivalent of defining an OLAP DML formula which returns a text value, but I want to be able to store the formula in the OLAP metadata.
I'm familiar with creating "dummy" calculated measures in AWM, saving to an XML template file, then editting the XML and reimporting, to define more complex calculated measures than the AWM wizard provides for, but I still haven't been able to successfully create a calculated measure which returns TEXT.
I've tried changing the XML from DataType="Decimal" to DataType="Text", but there are other sections in the XML such as:
CalcStep StepClass='oracle.dss.selection.calcStep.SimpleMathCalcStep
and:
CalcValue DataType='java.lang.Double'
which I think are also having an impact.
Any examples would be much appreciated.
Thanks,
Andy White

I have succesfully created text-valued measures with the AWM graphical interface. You need to make sure when you define the data cube that it does not have the "compressed" option checked, then you will get TEXT as one of the choices of data when you create a measure.

BPC75NW - Periodic Amount Not Calculating for records with blank YTD value

We are on BPC75NW SP6 and have a YTD consolidation application. Data is loaded on a monthly basis uising a process of importing data files from supplying systems and then loading them into BPC using the data manager append function with a transformation file. YTD amounts are as expected and 'most' periodic amounts are also calculated correctly via MDX mesures in reporting. However, in situations where we have a P&L YTD balance in one month (say January) and then in the next month (February) there is no longer a YTD balance in that P&L account, no record is loaded for February YTD and the system is not calculating any February periodic amount. Example:
January - Load $100 to a P&L Account which is the YTD amount
The January YTD amount = $100.
The January Periodic amount = $100.
February - Load no record to the same P&L account as above (as the YTD amount is now 0)
The February YTD amount in the system is blank
The February Periodic amount in the system is blank (This should be a NEGATIVE $100)
As a possible work around we have also tried to load a 0 to February. The data manager package shows the record as loaded successfully but since it is a 0 it really does not put it into the database.
Surely someone out there has already hit this situation and is willing to share the solution.
Thank you,
Vicki S.

This problem was resolved by installing SAP Note 1405993 - MDX: Error: Invalid MDX command with
CURRENTMEMBER. The current text on the note does not describe our error but SAP will not extend the text to cover this issue.
Prior to installing this note, the following other notes were also installed but they did not fix the periodic calculation issue. Under SAP's advisement we are going to leave them however as 'they should not have any side effects':
1529720 MDX: No data for calculated member and metadata reference
1590976 MDX: Incorrect data for IIF
1584196 MDX: Calculated members and different dimensions
1528374 MDX: System error GET_PRPTY_VALUE-02-
I will now close this message.
Vicki Shrontz

What happened to Allocation & Forecast in OLAP 11gR1 (AWM)?

Hello all,
Does anybody know what happened to allocation and forecast features in OLAP 11gR1 (AWM)?
These were available as step types in "Calculation Plans" in 10gR2. In 11gR1 "Cube Scripts" seems to be the descendant of "Calculation Plans"; but there are no allocation nor forecast steps types available in "Cube Scripts".
I suppose an OLAP DML script could be used for allocation/forecast but that doesn't seem to be a feaure for let's say a business analyst without programming knowledge (of OLAP DML).
Best regards,
Javor

You can create Allocation and Forecast in 10g style AWs only using AWM 11g
The newer 11g style AWs do not support Allocation and Forecast yet.

Bug LABVIEW 2014 - Calcul Quotient et Reste

Bonjour à tous,
Avez-vous remarqué ce bug dans labview 2014 sur la fonction quotient et reste?
J'ai lu sur le forum anglais que le bug a déjà été vu en 2009. Il est à nouveau présent!
C'est la seconde fois que je tombe dessus et qui m'oblige à utiliser un "patch maison", mais cette fois j'en informe la communauté:
Par exemple dans mon cas 8.6 / 0.1 = 85 et reste 0.1... (voir PJ).
Merci aux personnes concernées de prendre en compte ce bug dans vos prochaines mises à jour car c'est une fonction assez basique...
Bonne journée.
Julien P.
Certified LabVIEW Developer
Résolu !
Accéder à la solution.
Pièces jointes :
quotient.vi ‏7 KB

Bonjour à tous les deux,
En effet, comportement particulier mais qui n'est pas un bug.
Le "souci" vient des règles qui régissent la façon dont sont arrondis les nombres à virgule:
IEEE Rounding rules
C'est pour celà que dans l'aide détaillée de la fonction une remarque est présente (cf Quotient et reste (fonction)):
"Remarque Certains nombres réels ne peuvent pas être représentés par les nombres à virgule flottante de la norme ANSI/IEEE. Il est donc possible que des erreurs d'arrondi surviennent et que LabVIEW produise des résultats inattendus si vous utilisez les nombres à virgule flottante avec cette fonction. Pour obtenir des comparaisons et des calculs exacts, convertissez les nombres à virgule flottante en entiers."
Bonne journée,
Valentin
Certified TestStand Architect
Certified LabVIEW Developer
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
Travaux Pratiques d'initiation à LabVIEW et à la mesure
Du 2 au 23 octobre, partout en France

Build in OWB and make map in AWM?

Hi all,
Would it be possible to design and deploy the dimensional objects (dims/cubes) using OWB and make a mapping to populate them using AWM? These are all MOLAP objects. The advantage of designing in OWB is the editor and e.g. the ability to add calculated measures in cubes using the wizard.
Just did a quick test. When deploying a MOLAP dimension from OWB, in AWM it shows the map with several OWB-generated views to populate the object. I don't want to use those since I don't want to build a map in OWB. I have a simple 1-to-1 view to populate the object in AWM. However, when removing the OWB views from the map in AWM and replacing it by my view, when applying the changes it comes back with an error:
An error occurred creating DimensionMapGroup D_DIM_EMPLOYEE_M.TOTAL.MAPGROUP1.DIMENSIONMAPGROUP : ***Error Occured in DELETE_MAPPING_GROUP: You provided extra input starting at '$'.
The error detail window shows:
oracle.AWXML.AWException: An error occurred creating DimensionMapGroup D_DIM_EMPLOYEE_M.TOTAL.MAPGROUP1.DIMENSIONMAPGROUP : ***Error Occured in DELETE_MAPPING_GROUP: You provided extra input starting at '$'.
at oracle.AWXML.MappingGroup.Delete(MappingGroup.java:125)
at oracle.olap.awm.dataobject.modeler.ModelDO.deleteObjectInAW(ModelDO.java:533)
at oracle.olap.awm.dataobject.modeler.ModelDO.deleteAllMaps(ModelDO.java:1937)
at oracle.olap.awm.dataobject.modeler.DimensionDO.createMaps(DimensionDO.java:589)
at oracle.olap.awm.dataobject.modeler.DimensionDO.update(DimensionDO.java:746)
at oracle.olap.awm.dataobject.dialog.PropertyViewer.doApplyAction(PropertyViewer.java:770)
at oracle.olap.awm.dataobject.dialog.PropertyViewer.access$200(PropertyViewer.java:54)
at oracle.olap.awm.dataobject.dialog.PropertyViewer$1ApplyThread.run(PropertyViewer.java:550)
If this doesn't work it's just another blow to our olap-in-oracle implementation plan.
Does anybody have experience with this issue?
Thanks,
Ed

You'd better make the reservation of Genius Bar and show them about your problem.

AWM Calculated MESURE

Similar Messages

Maybe you are looking for