Change length of Info object

[Former Member]

Hello,

I have an infoobject with NUMC as data type and length 3. I need to change the length to 4 and keep the data type same. This infoobject is included in 6 or more ODS and cubes and is also a navigational attribute of another info object.

The infoobject already has MD loaded in it via a flat file. it can also be loaded directly through R/3, but the team has decided not to pursue that option.

My question is: Can I change the length to 4 without emptying the cubes and ODS? If so, how will it affect my MD? Is there any way to change the transactional data in the cube to 4 digits..by padding it with zero?

The only option that I see in front of me is to delete all the data in the infoobject. pad the data in the flat file so that it is 4 digits instead of 3 (I think I should be fine even if i don't do this). Delete all the ODS and cubes that contain this info object. Also delete all the data in the other info object that has this info object as a navigational attribute. Reload all the ODS and cubes and info object after the changes have been done.

Any other suggestions?

Thanks

Sam

[Former Member · Accepted solution]

Hi Sam,

usually is not a problem increasing, but decreasing !!!

Hope it helps!

Bye,

Roberto

[Former Member · Accepted solution]

Roberto,

I made those changes in Sandbox and after realigning the tables, it seems to be working. When I make these changes in DEV, would I need to collect the info cubes also?

1. Info object is in cube 1 - need to collect cube?

2. Info object is a navigational attribute of IO2 - i do need to collect IO2.

3. IO2 is in cube 2 - need to collect cube 2?

Thanks

Sam

[former_member184494 · Accepted solution]

Sam ,

we did something like this recently ...

things that you would have to do:

1. Increase the length and activate

2. Reactivate the ODS / Cube

3. Reactivate the Transfer rule / Comm Stru - make sure you see the length changing in the transfer structure detail view

4. Reactivate the Update rules

5. Also check if the data loads go through in DEV - if not try readjusting the tables using SE14

In our case we increased the length form 10 to 15 and had to go though a lot of changes and reactivation before it became allright..

Arun

[former_member184494 · Accepted solution]

Sam,

You do not need to do anything other than the transport --

However I notice that you have marked your post as answered by awarding points - but the post still shows as unanswered....

Arun

[Former Member · Accepted solution]

Thanks Arun,

I reopened the post because the Q about the transport was related to the same post. I did not want to have 2 threads open for the same thing.

It does seem that when I transported it to BWQ, the tranfer structure was activated, but the infoobject has not been activated and gives me an error. It states that the tables need to be converted. So i guess I have to make the changes manually in QA.

Thanks

Sam

[Former Member · Accepted solution]

I think you have to go with SE14 directly in your test system.

[Former Member]

I want to know if my CTS will get affected. I have a important piece that i have to transport and I'm adding this changed infoobject to the same transport. Will the IO be automatically activated in BWQ and BWP? Or would i need to manually again realign the tables and everything?

Thanks

Sam