on 01-09-2015 6:30 AM
Hi All,
Here is my report output in workbook
Purchase grp Country of Pur grp Region of pur grp Subregion of pur grp Key figure
10 fe t1 t11 100
10 fe # # 20
10 se d1 d11 500
10 se # # 60
I am unable to identify why this # is coming in my report.
Thanks,
Mayur
Hi,
This issue might be solved by constant selection.
For this, you have to create new selection, drag the key field and characteristics Region of pur grp, Subregion of pur grp. In the context menu of both characteristics choose "constant selection" option.
Thanks,
Swapna Jain
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Mayur,
This is a issue faced when you use Multiprovider and if the characterstics you select is not present in both the infoprovider's on which MP is built then '#' value appears.
Either make sure the charac selected in MP is present in all the infoproviders under MP, else use constant selection for the characterstic in query and filter with #.
There are number of SDN docs to explain step by step. Please check.
Regards,
Sankameshwar
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Mayur,
To what the experts above just described. I am trying to answer this problem on my understanding.
Multiprovider fetching the data from the cube right.
Cube getting data from different infoproviders right?
If this is true then this means the different flows that are coming into Cube
donot have all the characteristic
like 'Region of pur grp ' ' Subregion of pur grp ' along with other characteristics.
That is why Hash is appearing.
If you restrict hash values then the Key Figure will disappear in the report.
Please try to include those two characteristic at datasource level for all other flows that is
the datasources which are bringing data for all the DSOs and then include these two
infoobjects in those DSOs and change the transformation and map those two characteristics from all the DSOs
to the cube.
That can be another way for solving this problem.
Try this it will work.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Mayur,
Is this an infoset report , or is the data getting loaded from different source
Regards
Gajesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Mayur,
If the data is from MP, then there is a change that the data might be coming from multiple targets, and in one of them you have missing data for region and subregion.
What you can do is keep the infoprovider in the free character and move it to rows and check from which target this # is coming from.
Regards
Gajesh
Hi Mayur,
Perhaps you have two (2) or more providers in multiprovider..
For example, you have two (2) DSOs on your multiprovider, let's call them DSO1 and DSO2..
DSO1:
Purchase grp Country of Pur grp Region of pur grp Subregion of pur grp Key figure
10 fe t1 t11 100
10 se d1 d11 500
DSO2:
Purchase grp Country of Pur grp Key figure
10 fe 20
10 se 60
If this is your case, you will really have this result:
Purchase grp Country of Pur grp Region of pur grp Subregion of pur grp Key figure
10 fe t1 t11 100
10 fe # # 20
10 se d1 d11 500
10 se # # 60
To solve this, try using CONSTANT SELECTION in your keyfigure for the Region of pur grp and Subregion of pur grp..
Just post here if you don't know how to do this..
Regards,
Loed
Hi Dear,
The data in cube is perfect.Whereas what you are suggesting is to restrict the # exclusion in query it self .That means the data will show blank at that particular row.
My point is if the same data is showing for above row why isnt it showing for below row?
Best,
Mayur.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear Mayur,
There could be several reasons why # is reported.
1. Check you trasaction data within the cube there will be few records which has null values for these two fields
2. If they field are navigational attribute of master data than check the master data.
3. If the report is built on multiprovider that check if these two fields are enable from the correct cube for reporting.
4. Run RSRV to check the consistency of data on the cube.
Hope some of these scenario should help further.
Hi,
Check in your base cube or dso, how the data is showing.
If same in that, then delete the data and reload, still not resolved then restrict the # exclusion in query it self only. still need info let me know.
Thanks & Regards,
srinu.rapolu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
92 | |
11 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.