What's 'Process dimension member' and 'Refresh dimension member'

We're using BPC 7.5 NW SP8 patch 001.
I often have confusion about these two buttions of dimension library on BPC admin console.
When clicking 'Process dimension member' and 'Refresh demension member', clearly we see BPC is performing some activities.
If I switch tracing in ST05, some tables, such as UJD_DIMENSION, UJD_DOC and temperory tables. were accessed and updated.
For my understanding, table UJD_DOC is using to find sheet template in UJFS and table UJD_DIMENSION is using to control versions between file service and BW infoobject tables.
But I cannot understand what's necessarity for 'Refresh dimension member'.
Does this activity will fetch data from BW infoobject tables and refresh files in UJFS ? But I cannot see 'Update' action in ST05 tracing file.
The other one - 'Process dimension member': does that mean syncroniization between files in UJFS and BW infoobject tables ?
If so, why temperory table /1CPMB/B_* is storing some records?
Could BPC expert guide me the way to understand? Appreciated.

Hi Brad,
Refresh Dimension members is to update client infomration.
When you log on to an application set whose structure has changed (there are changes to dimensions and templates stored on the server), the system automatically updates your client information. You can also initiate this procedure manually, which you should do only when instructed by your administrator. Hope this helps.
Regards,
Sanjeev

Similar Messages

What is processing album art and determining gapless playback?

Whenever I add music to my itouch, it takes forever because it determines gapless playback and processing album art.
What exactly happens if I hit the X when processing art?

and is this in relation to my library on the pc or my ipod?

Selection objects and Time Dimension

I have instantiated QueryClient object using the query manager. I have 5 dimension in my MOLAP cube where one of the dimension is TIME dimension. I create a selection object for each dimension and apply the selection array to the queryClient object. I create selection objects by using its constructor which takes dimension unique id as argument. I get OLAP Source not found error when I take this approach. When I do create a selection object by queryClient.createQueryAccess.getSelection("DimUniqID") for time dimension only, everything works fine and I see results. What is special about selections and time dimension ? Can anybody throw some light on this or there is some flaw in my understanding ?
Thanks
Swapan.

Did you review the topic "Defining a Query Programmatically" that is part of the BI Beans Help documentation. This has some good examples.
Hope this helps
Business Intelligence Beans Product Management Team
Oracle Corporation.

New calculated member based on existing measure and a dimension value

Hi
I’m trying to create a new calculated member in my cube based on an existing measure and a dimension value.
I can do it easily in DSW but I want to do it as a Calculated Member in Calculations tab from my cube.
I have a dimension called Product in which one attribute is UOM (unit of measure) and a measure called Quantity. The relationship with the fact table is “Regular”.
For each product we have a unit of measure and an associated quantity measure:
Product Name
UOM     Quantity
Product 1
          Km
         50
Product 2
          Kg
         60
Product 3
          Kw
          25
Product 4              L
15
Product 5              T
         1.5
Total                                     151.5
The calculated member I want to create is “Kw” and has to contain the value from Quantity measure when Product.UOM is “kW” and should look like this:
Product Name
UOM     Quantity
Kw
Product 1
          Km
         50
Product 2
          Kg
         60
Product 3
          Kw
          25
25
Product 4              L
             15
Product 5              T
         1.5
Total                                     151.5
25
So far I tried using the MDX with “IIF” or “Case” but with no results.
What statement I should use in this case?
Thank you.

Hi Cees,
Thank you for your answer.
I never used yet the “Scope” statement and yet it’s an elegant solution.
I use it as in your example:
CREATE
MEMBER CURRENTCUBE.[Measures].[Kw]
AS NULL,
FORMAT_STRING =
VISIBLE = 1 ,
ASSOCIATED_MEASURE_GROUP =
'TR Other';
Scope [Measures].[Kw];
Scope [Product].[UOM].[kW];
This = [Measures].[Quantity];
End
Scope;
End
Scope;
…and the calculations are solid…with one exception: when I took out UOM from the query there are no more any resuts:
Product Name    Quantity    Kw
Total
It’s only working
if using UOM in the query.
I also thought that a
tulpe might be another solution as:
([Measures].[Quantity],[Product].[UOM].&[kW])
On this last one I’ve got the expected results with one exception: when I use UOM in the query all the other UOM values are listed each one of them
having the [Kw] measure calculation value.
Product Name    UOM     Quantity    Kw
Product 1              Km
         50
Product 2              Kg
         60
Product 3              Km
          25            25
Product 3              Kg
           25            25
Product 3              Kw
          25            25
Product 3              L
25            25
Product 3              T
25
  25
Product 4              L
            15
Product 5              T
         1.5
Total                                     151.5
25
…and without UOM in the query I have what I’m expected:
Product Name    Quantity
Kw
Product 1              50
Product 2              60
Product 3               25
25
Product 4
15
Product 5
1.5
Total                       151.5
25
Maybe we can work together to find a solution.
Thank you,
Oks

How to read all outline member and dimension names and display in excel

Hi All,
I am developing a custom excel application (VBA) and i need to display member names of a one essbase database of one application and display those members in excel sheet.
Is there any specific API which does that thing.
Thanks

Combo boxes -- if those are truly your controls of choice, you are going to (I am guessing at least) only going to be looking at small and simple dimensions -- otherwise it isn't going to be very good at navigating a large dimension.
You actually have a pretty fun process ahead of you -- writing code to get levels, relationships, etc.
Just a note of caution -- if you have really big dimensions and are trying to get this into a treeview, you might have to come up with some sort of paging approach as you'll overwhelm Excel VBA.
You may also want to go pure API for a lot of the dimension stuff.
Have you checked out AppliedOLAP's Dodeca? It can read Excel worksheets, has dimension handling built in, and oh, about 1,000 other cool things including scripting, easy access to the API, etc., etc., etc. No, I don't work for them, nor do I get a commission, but it is an awesome tool in every respect. I have used AppliedOLAP's products in the past and they (the products and the company) are awesome (used twice in a paragraph, but it is that cool).
Regards,
Cameron Lackpour

Dimension default member has a strange impact both in dimension browser and excel filters

Hello All,
I have a scenario where I need to set a default member in a dimension attribute.
The problem is that when I am browsing the dimension attribute (that is a parent-child) in Visual Studio I cannot see all the values only the ones that are filtered by the default member. In addition the same happens when I create
a pivot table in excel with filter values, even if I change the attribute that has a default value.
My goal is to list (by default) all the distinct values in excel filter selectors.
Is this a limitation? Is there any way to overcome this? Is this a problem related with parent-child attributes?
Best Regards,
André Cunha

Hello All, <o:p></o:p>
Update on the situation.<o:p></o:p>
We normalized the dimension and we achieved a
satisfactory solution maintaining the default values and aggregation
settings in the new dimensions and the parent-child attribute now shows
all possible values.<o:p></o:p>
I believe this is a by design that excel does not
reflect the applied filters in the pivot tables depending of the attribute
filters selected.<o:p></o:p>
Any thoughts, <o:p></o:p>
Regards, <o:p></o:p>
André<o:p></o:p>

MDX: Selecting specific dimension member and its descendants from parent child dimension where dimension member names can be same in dimension hierarchy

I'm creating a SSRS report using SSAS cube as a source.
When creating a dataset for the report, I'm having trouble with MDX to select a specific dimension member and its descendants from parent child dimension where dimension member names can be same in dimension hierarchy.
Lets say for example that I have an account dimension where,
In level 02 I have company ID:s 101, 102, 103 and so on...
In level 03 I have Balance sheet
In level 04 I have some account groups, Assets, Liabilities and so on... and In level 05 I have individual accounts
How can I select for example company 102:s Assets from level 04 and its descendants?
Normally in adventure works I would do this if I've wanted Current Assets and its descendants:
SELECT NON EMPTY { [Measures].[Amount] } ON COLUMNS, NON EMPTY
{ (DESCENDANTS([Account].[Accounts].[Account Level 03].[Current Assets]) ) } ON ROWS
FROM [Adventure Works]
But in my Account dimension at level 04 I have Assets member as many times as I have companies in level 02.
Tuomo

Hi Tuomo Helminen,
To this requirement of yours, I would recommend you use Cascading Parameters in Reporting services, you can refer to this FAQ How do I create cascading parameters when using cube database in Reporting Services at this link
http://blogs.msdn.com/b/sqlforum/archive/2011/04/11/forum-faq-how-do-i-create-cascading-parameters-when-using-cube-database-in-reporting-services.aspx
Thanks,
Challen Fu
TechNet
Subscriber Supportinforum
If you have any feedback on our support, please [email protected]
Please remember to mark the replies as answers if they help and unmark them if they provide no help.

How to populate member values to Year and Period Dimensions

Hi,
I have set up the following members in account dimension:
Lease From (Date Type)
Lease To (Date Type)
Lease Amount (Currency Type)
If I input Jan-2012 in Lease From, Nov-2013 in Lease To and 1,000 in Lease Amount, all in BegBalance->Fy12, how can I populate the 1,000 to the correponding Period and Year dimensions using business rule. I need 1,000 in Lease Amount->Fy12->Jan all way through to Lease Amount->Fy13->Nov. I do not want to create a input form with all the years and periods for monthly input as I may have over 100 lease information with different from and to dates.
Or is there any alternate method I can get the expected results.
Thanks.

Hi
This is a really complex problem! It may help you to look at the documentation around the CapEx planning module as this is Oracle's take on calculating asset depreciation etc on a similar basis (create asset in BegBalance -> NoYear and calculate which periods to poulate depreciation data in using dates, variables and rules). The business rules are presented in full in the doc below but I warn you the code is complex and not easy to understand, although you may get the principles
http://docs.oracle.com/cd/E17236_01/epm.1112/cpx_admin_11122.pdf
You ought to be able to do something using dates and period / year indicies (remember dates are stored in Essbase in something like the format YYYYMMDD, e.g. 20121107 so should be easy to compare whether the date for the period is within range of the dates entered).
I have also tried to do something similar using smartlists in a prototype before but this proved a bit more complicated and not necessarily any more reliable than using dates
Hope this helps
Stuart

Does anyone know what the entity property of the currency dimension does?

Hi,
I'm trying to figure out what the Entity property of the Currency dimension does. All the online documentation I can find has the definition below which is not all that useful. Has anyone uses this before and know how it can be used?
Thanks,
Morgan
Online definition
A 32-character field that can either be left blank or contain a valid
member name of the entity dimension associated to the current model. The ENTITY property is
validated against the entity dimension, and blank fields are allowed.

Sounds like it provides one (extra) internet phone number that goes to their servers first. Then it could work like this:
1) If you have the app running on your phone (oops, no background processing... perhaps this will be one of the first tests of background notifications), it uses the GPS to tell the server if you're near a landline that you've previously registered with it. If so, their server redirects the call to the landline phone.
2) While you're on a call, you can start a conference call that includes the alternative phone (landline or iPhone) and then hang up on the old one. That would give a "seamless" switchover.

How can I modify Time dimension to create a Top member above year members ?

Hi experts,
I would like to modify Time dimension to add a Top member above year members.
I already did a test:
I added a member in Time dimension which is the parent of all year members. I granted it these property values:
- ID = TOTAL
- EVDESCRIPTION = Total
- LEVEL = TOTAL
- HLEVEL = 1 (and I added 1 to all the other members)
- TIMEID = 10000001
All other properties were left blank for this member.
I processed the dimension. It went well. But when I tried an evdre in BPC excel it failed.
Any idea of something missing ?
I am working on SAP BPC MS 7 SP4
Thanks for your help
Ludovic

Hi Petar,
Thanks for your answer. No doubt that we could solve the issue using on of the way you suggested.
However, even though I had the evdre issue right after applying time dimension modifications, it occurs that the evdre issue was not due to time dimension modifications. I tested it better and I can tell that using "total" as a level works.
Best regards,
Ludovic

Consolidate YTD Member in Scenario Dimension

Hi All my Peers,
What Exactly the Purpose of " Consolidate YTD Member in Scenario Dimension. my Analysis is as bellow, please Guide me if my Thinking is Wrong and also is this Member Focus and Refer or Check or Cross Check with any other Member to Start its Execution?
Is Consolidated Member we can say and Understand easily. How to Understand Specifically Mentioned Member Consolidate YTD.?
By default we are using HFM For Consolidation as per our Customization.
Where exactly this Member Importance Comes in to Picture
Knowing to my Knowledge, Periodical data we will get every Month end from our ERP Systems
and one more concept Periodic automatically gets YTD,and YTD Automatically gets Periodic i am not able to understand how HFM Understand and do this. But i know Rollup,Aggregation,Immediate Parent,Ultimate Parent
I hope any of your answers will make me Clear on this attribute.

I am attaching an extract of ther post
The periodic or YTD consolidation of values is a matter of sequence. Note that the following discussion applies to Flow accounts (Income, Expense and Flow types).
When ConsolidateYTD flag of the scenario dimension is checked, HFM first consolidates the YTD values of accounts and then calculates the periodic values at the consolidated (group) level.
Conversely, when ConsolidateYTD flat is un-checked, HFM first consolidates periodic values of accounts and then at consolidated (group) level it forms the YTD amounts.
In both cases, whether you have loaded periodic or YTD values is irrelevant. The consolidation happens with the sequence described in each case above.
So, you think "what's the difference?". In fact there is no difference until you introduce a new subsidiary in the middle of the year. In this case you need to consolidate only the periodic values of accounts, starting on the month that the subsidiary was introduced to the group structure. If you don't the accumulated amounts from previous periods (YTD values) will consolidate, which you don't want.
For example: you introduce a new subsidiary during March. Until March the YTD value of sales was 100. During March the periodic value is 50, therefore the YTD sales for March is 150. You don't want to consolidate 150 since you did not own the company during the previous months. You need to consolidate only 50. In order to do this you have to populate the flow accounts for at least Feb so that HFM will calculate the periodic value for March correctly. In this case the contribution of the new subsidiary to the consolidated sales account for March is 50.

Problem with add new Member in Account Dimension

Hi Expert
I want to add new member in account dimension but occured some Error about a member count of a circular reference. Please help me for solve this error. Thank you so much
Best regards,
Bank

Hi,
This kind of error indicates faulty dimension formulas. There must be at least 2 formulas referencing each other. For example:
1. A=B+C
2. C=A*D
The above 2 formulas are dependent on each other. On one hand, you need C to calculate A. On the other hand, you need A to calculate C. So, causing a cross reference. Try to remove all the dimension formulas in your account dimension and process it. See, if its successful or not. If yes, then the formula was the definite reason. Now, try to add the formula one by one, till you get the error.
Hope this helps.

Group dimension separation. Group and currency dimension

Hi experts!
As I am concerned, a new functionality of SAP BPC NW 7.5. is to separate group dimension on two: group and currency.
Could any explain me how it affects to consolidation system process and how could I set up?
Thank you
GG
Edited by: algarciagomez on Jul 26, 2010 12:07 PM

Hi experts,
Finallly we find a solution attending to our experience. You must defione both dimension RPTCURRENCY only for currencies and LC, and GROUP only for scope groups and NON_GROUP value.
Data must be introdue in NON_GROUP member and LC, then in conversion program, system save data in NON_GROUP and group currency (for example EUR), and finally in consolidation program, system save data in G_01 (group scope) and EUR.
I hope this could help you.
Regards,
Gabriel Garcí

Degenerate and Junk dimensions

I am new to SSAS. I want to understand degenerate and junk dimensions in detail. It would be good if you provide with practical examples please.
Regards,
Ramu
Ramu Gade

Junk Dimensions
There are certain scenarios where you will find that the source for a fact table contains a bunch of low-cardinality attributes that don’t really relate to any of the other attributes describing these facts. Some of the more common examples are bit/character
based “flags” or “codes” which are useful to the end users for filtering and aggregating the facts. For example, imagine a user who wants to analyze orders from the order fact table that are flagged as “reprocessed”…they can either filter for facts with
the reprocessed flag if they are only interested in that subset…or they can group by the “reprocessed” flag calculate things like the percent of orders that are “reprocessed”…
Instead of building a separate dimension for each of these individual attributes, another option is to combine them and build what’s known as a Junk Dimension based on the Cartesian product of each of these attributes and they’re corresponding range of values.
This technique does 2 important things:
Saves Disk Space
consider a single 4byte integer key linking to the junk dimension vs. a handful of 4byte integer keys each linking to a separate dimension. Might not sound like a lot on a per-record basis, but once you extrapolate out over a 100mm record fact table the
savings really adds up.
Improves End-User Experience
By keeping the total number of dimensions down to a manageable size it will be easier for your end-users to find the attributes they’re looking for during ad-hoc analysis. Kimball recommends <= 26 dimensions per fact table – of course there are always a
few edge-case exceptions.
Degenerate Dimensions
The Degenerate Dimension is another modeling technique for attributes found in the source transaction table. The main differences between these attributes and the ones that would fall into our Junk Dimension are as follows:
Cardinality
these are typically high-cardinality attributes – in some cases having a 1 to 1 relationship with the fact. These are likely to be the business keys of the fact table such as Purchase Order Number, Work Order Number, etc. Another potential candidate
for the degenerate dimension is free-form comment fields.
Use Case for End-Users
these attributes are not going to be used for filtering/aggregating facts. Instead, these are the types of attributes that are typically going to be used in drilldown or data mining scenarios (ex. Market Basket Analysis). For example, imagine a user who is
analyzing purchase orders in the “delayed” status. After drilling down on the delayed POs for a certain supplier in a certain time period…the next step might be to pick up the Purchase Order Number which would allow this user to trace this small subset of
PO’s back to the source system to find out why they are “delayed”.
Storage
Despite the name, these attributes typically remain in the fact table. There really isn’t much point in moving them out to an actual dimension – because of the high-cardinality there’s likely to be zero space savings…in fact it would probably cost you space
due to the additional surrogate-keys. You’ll also likely be paying a heavy price on the join at query time.
Analysis Services Implementation
For Junk Dimensions, you will create a new dimension at the project-level pointing it to the table (or view) in the data warehouse that materializes the distinct combinations of values for the various junk-attributes. After configuring the dimension at
the SSAS project-level, it can be added to the cube(s) and linked up to the measure group(s) via regular relationships (where appropriate).
For Degenerate Dimensions, the process is the same except you base the project-level dimension off of the fact table (or view). Once the project-level dimension is configured, it can be added to the cube(s) and linked up to the measure group(s) using “fact”-relationships
(where appropriate).
Please mark as Answer if this helps!
Rajasekhar.

Error(1012016) Cannot calculate Dimension Member [CYG_BILAN] with restricted Member [CYG_BILAN].

Hello,Below is a validated script, with generate a run time error :Error(1012016) Cannot calculate Dimension Member [CYG_BILAN] with restricted Member [CYG_BILAN].See the script below (with the error message in comment).Why can't' I calculate a member which is fixed ? Where is it documented ? How should I modify this script to make it runable ? Thanks for help Philippe Cuisset SCRIPT======/* Basculement des comptes d'actif de solde négatif vers les comptes de dettes *//* Philippe Cuisset 31/05/03 */SET MSG INFO;FIX ( @DESCENDANTS(&organisation, 0), @LEVMBRS(dev,0), @DESCENDANTS(&annee, 0), ind_financier, @LEVMBRS(cra, 0), @LEVMBRS(geo, 0), @LEVMBRS(clifa, 0), @LEVMBRS(ana, 0), @LEVMBRS(nc, 0) ) /* Copie des données du cycle réel dans le cycle bilan */ FIX( flu_ouv, flu_mensu ) DATACOPY cyg_reel TO cyg_bilan; ENDFIX /* Pour le flux solde, et (chaque nature comptable (d'actif circulant) ayant un attribut bilan, ou chaque nature comptable de dettes financieres) */ FIX( cyg_bilan, flu_solde, @ATTRIBUTE( BILAN ), @DESCENDANTS( NC7_FINANCIERES, 0 ) ) /* Initialisation du solde mensuel du compte d'actif */ VAR var_solde_actif = 0; /* Initialisation du solde mensuel du compte de dettes */ VAR var_solde_dettes = 0;/***** ERROR ON FOLLOWING LINE *****//***** Local/buedmt2/buedmt2/Essadm/Error(1012016))Cannot calculate Dimension Member [CYG_BILAN] with restricted Member [CYG_BILAN] *****/ cyg_bilan ( /* Si nature comptable (d'actif) avec attribut bilan */ IF ( @ATTRIBUTESVAL( BILAN ) != "" ) /* Calcul du solde mensuel de la nature comptable d'actif */ var_solde_actif = flu_ouv + @ACCUM( flu_mensu ); /* Si le solde mensuel est < 0 */ IF ( var_solde_actif < 0 ) /* Raz du solde dans le compte d'actif */ cyg_bilan = 0; /* Ajouter la valeur du compte de bilan depuis l'actif vers les dettes */ var_solde_dettes = @MEMBER( @SUBSTRING( @ATTRIBUTESVAL( bilan ), 3) ) ; cyg_bilan = var_solde_dettes + var_solde_actif; ENDIF ENDIF ); ENDFIXENDFIX

Not sure where it is documented, but you can not calculate what you are fixing on. To me it seems a bit odd, but I believe the logic is, if it is sparese and you are fixing on it, how can you fix on what might not be there? If it is sparse, fix on all the other sparse dimensions thenFix (....) CYG_BILAN ( CYG_BILAN = ....; )EndFiX;Also, if it sparse, make sure the block exists (either datacopy data into it or set 'CREATE BLOCK ON EQUATION' on - I tend to copy data into it).If it is dense, you wouldn't want to fix on it anyway.Rich SullivanBeacon Analytics

What's 'Process dimension member' and 'Refresh dimension member'

Similar Messages

Maybe you are looking for