Dimension property created with more than 60 chars, saving data incorrrectly in BW Infoobject

[former_member493004]

dear all,

we have a dimension XX having property YY with length 150.

while we were trying to read this property values from backend infoobject created, found that for this property, values are not getting correctly updated what we have maintained in BPC frontend.

This might be due to the length of info object is limited to 60 chars only in BW system.

in order to resolve this, we then read data for this property from other table for this dimension which is the data table for this which we found out from UJA_DIMENSION.

can anybody help me on this data table as i know abt info object being created when dimension is created.

also how are these two different.

Thanks,

Ambika

[former_member186338 · Accepted solution]

First - what for you need a property with 150 characters?

[former_member493004 · Accepted solution]

its just a future aspect that we kept the length as such.

but when property length is exceeded, then the data is not read correctly at all.

want to also understand if system can read 60 chars and could have saved the data but this did not happen.

[former_member186338 · Accepted solution]

"its just a future aspect that we kept the length as such" - in most cases I have seen in this forum the very long property is just a design error

"data is not read correctly at all" - what do you mean by not read?

It can be read in EPM report:

Report:

Vadim

[former_member493004 · Accepted solution]

Dear Vadim,

i meant data in the backend.

suppose i have dimension CAR with property COLOR with length 150

ID          COLOR

FIGO     sea grey

Maruti     metallic black

suppose i have above data saved in the frontend but when i see in the backend info object(master data table), the data is not correct, it is saved as below:

ID               COLOR

FIGO          FIGO    

MAruti     MAruti

Thanks,
Ambika

[former_member186338 · Accepted solution]

Sorry, but what do you want to achieve??? How do you want to present data?

[former_member493004 · Accepted solution]

i just want to read the property values based on the ids in my logic, i think that would be possible to read from info object but here as i mentioned earlier data is not stored correctly in the info object due to its length restricted to 60 chars.. so we used /1CPMB/ table to read the property values.

i just wanted to understand that why the properties did not get correctly stored.

thanks,

Ambika

[former_member200327 · Accepted solution]

Hi Ambika,

Property is correctly stored, BW (up to some version) has a restriction on length of an InfoObject. Since each Property is an InfoObject, that's why it's split in multiple InfoObjects when length is over 60 char.

I'd still recommend using /1CPMB/... table because there property is just a field and can be read easily.

Regards,

Gersh

[Former Member]

Hi Ambika,

What i remember is, the value of member property is not visible completely if you check from infoobject which means i think you are right. But some standart BPC methods can retrieve that informations for you if you are planning to use it in coding.

class:CL_UJAM_MEMBER

method: GET_MEMBERS_USING_QUERY

you can try this method

hope it ll help you.

good luck.

Yusuf

[former_member493004]

thank u for ur reply.

but i want to understand why 2 info objects, one with CPMB and other 1CPMB and whats the difference.

[former_member200327]

Hi Ambika,

You have only 1 InfoObject; there other is a table. When you display/edit data in Dimension screen it takes it and writes back to /1CPMB/... table. When you process the Dimension it updates it in /1CPMB/ table and writes back to /CPMB/ InfoObject.

Those 2 objects supposed to be in sync all the time except when you saved data, but haven't processed it. There is a FM ...REFRESH_DIM that brings data from /CPMB/ InfoObject to /1CPMB/ table.

If you want to know something more specific about those tables please provide such questions.

Regards,

Gersh

[former_member200327]

Hi Ambika,

When you are saying "the other table" are you talking about /1CPMB/... table?

Data is stored in both places. Just in the InfoObject it's split in multiple (3 in your case) attributes. So, the first one will have only first 60 characters of the property, second next 60 characters and so on.

Do you need more info on those 2 objects?

Regards,

Gersh

[former_member493004]

Hi Gersh,

Yes I am talking of /1CPMB/.. table.

if you can give more info on these objects, it will be a great help.

Thanks.

[former_member186338]

Can you explain the idea to use very long properties? What do you want to store?