on 2015 May 19 4:46 PM
Hi All,
I refresh the data in EPM as follow:
| Dimension 1 | Value |
|---|---|
| AAAAA | |
| BBBBB | |
| CCCCC | |
| DDDDD | |
| EEEEE | |
Then I change the master data for dimension 1. Instead of having 5 members, I have 3 members only (AAAA,BBBB,CCCC). Then I refresh the data in EPM again. The result is the same :
| Dimension 1 | Value |
|---|---|
| AAAAA | |
| BBBBB | |
| CCCCC | |
| DDDDD | |
| EEEEE | |
It will be only correct (showing only AAAA,BBBB,CCCC) if I delete all the rows and then refresh again. I notice this is because EPM doesn't clear / delete all the rows before refresh the data. So if the second refresh has less data, the reports will shows something like duplicate data because the rows which are not valid are still displayed.
Is there anything we can do to avoid this?
Thanks.
Request clarification before answering.
Hi,
which version of EPM add on are you using?
try clear metadata cache under more options and also run UJA_REFRESH_DIM_CACHE in SE38
Andy
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi U-One
whenever we connect to a model the structure of the model will be copied locally (i.e dimensions and its members) which will improve the performance.
when you try delete,add,update....dimension members either you have to logoff from the excel or clear the metadata cache to sync local copy with the structure of the model.
Please read the section 38.1 Metadata Cache in the below link
https://help.sap.com/businessobject/product_guides/boeo10/en/EPMofc_10_user_en.pdf
Thanks,
Dinesh.V
In general it's a very rare case when you have to delete master data...
Do you have a business case?
Vadim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It should be rare case to delete the master data. We are in the middle uploading the master data for the first time in production and after uploading we notice that we need to delete or change the master data.
After further testing and stimulation, I think the root issue is not the deletion of the master data. The error only applicable in following scenario (Please ignore the sample in the previous message) :
AAAA
BBBB
CCCC
AAAA
BBBB
CCCC
AAAA
BBBB
CCCC
And after that, no matter what context member we choose, the last 3 data (the bold one) always appear. It will only be ok if we delete the rows.
Looks like that the bold one is considered as outside the EPM range already. Any comment is appreciated to avoid this.
Thanks.
| User | Count |
|---|---|
| 10 | |
| 9 | |
| 6 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.