My company desires to change the length of two fields in tiitm001.
tiitm001.item (domain tcitem), tiitm001.dsca (tcdsca) in our production PVRC (though obviously it would be done in development first). I need to know the best procedure to accomplish this as well as any ramifications/issues and other information you might feel pertinent. Any help or advice would be greatly appreciated.

Ev

I assume better switch to iBaan ERP 5.x ...

Hi there,

afaik there was a documentation about changing the domains for cuno and item, as there have been lots of customers that wished this (at least here in germany). Someone here should have this doc, unfortunately I havn't got it.

I remember having changed cuno accordingly and there where no problems.

Go through your DD and look for "item", to see whether there are tables that use an item-field with a different domain. (Especially if you have customized tables/sessions).
If you find such domains, change them too.
Then the reconfigure should work and change all tables concerned.
Probably you will find forms and reports that have to be changed/recompiled as their fields don't match the data's new length.

But as you have a development system, the whole thing doesn't sound dangerous. It might only turn out to be a some work.

Good luck and please give us a note whether there where flues.

regards

Norbert

norwim :Go through your DD and look for "item", ... and sitm, mitm and all other possible and impossible codes that are more or less related to the item field...

We changed our cuno and suno domain lengths to 7 (from std 6) and had LOTS of trouble at first. A number of Baan sessions had the field length hard-coded in the script rather than referencing our domain definition. It took quite a while to get BGS to provide appropriate patches. Now all is fine with the Baan program, but we still do run into problems when adding 3rd party apps to Baan (which also may presume std domain lengths). Knowing what I know now, I would have never changed the domain lengths.

...one more thing to mention as well.
Because we increased the field lengths, we had to modify MANY reports and forms that included those fields in order for the info not to be truncated when printed/displayed.
...lots of work and maintanence!