on 10-23-2012 7:52 AM
Hi All,
I am in BPC 7.5 NW
I need to add a new dimension to an existing application with transaction data.
I have done it in the dev system and what I could see is for all the transaction records in the cube, the first member in the dimension member sheet got populated.
What I meant is, all the data records has the same dimension member. Is this the way it is supposed to work. If I need to populate data, how will I do it, Will I need to clear the data and reload again. How is it handled usually?
Also when there is a dimension property with more than 60 char length, how does the system handles it. I know that it will be extend the star schema again, but how does it work. Can I see the details of this? where can I get the table name if it is getting populated?
Regards,
Hi Arjun,
This is the typical behavior of the system.
You can export the existing data to flat file, make the changes and upload them once again.
Regarding your second query, these properties are maintained as navigational attributes in the BI system.
Hope this helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for the reply,
On the second query,
When a property with more than 60 char length it is saved a display attribute, anything less than 60 will be saved as nav attribute. now the issues where can I see the data, when I check the master data from RSA1, the property with more than 60 char length is not present there. I guess this is bcos BW has that limitation on the length of object.
When I call the property from EVDRE I am able to get the same. Was interested to see where it is saved in BW side.
Any thoughts?
After a lot of digging around, I've found BPC creates tables in the BW backend called /1CPMB/_xxxx or /1CPMB/B_xxxx, where xxxx is related to the technical name of the BW InfoObject of the BPC dimension.
So if the BPC dimension has BW InfoObject technical name /CPMB/PZDRRZD, then the name of this other BPC table will be /1CPMB/_PZDRRZD.
This /1CPMB/_xxxx table stores properties with length >60 chars, as type STRING. So you will be able to see the entire long text in this table.
This table must be where BPC reads it's properties when doing EVPRO and in ABAP world when calling lo_dim->read_mbr_data to retrieving dimension members.
The standard scenario to add new dimension to the existing application with data:
1. Create new dimension with one member (dummy or the most used).
2. Add dimension to the application - all existing values will be posted to this single member.
3. Add the required members to the new dimension.
4. Use scripts or standard DM packages to move data from single member to other members.
B.R. Vadim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
15 | |
3 | |
2 | |
1 | |
1 | |
1 | |
1 | |
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.