Brief situation sketch:

Baan 5b

We basically manufacture to order, but after a production order (project) is completed, items are some times stored in a warehouse.

To avoid having project-items stored, custom items are being copied back to standard items before going into the warehouse.

A time consuming and ugly sollution.

Now I was thinking......

Using the item code segmentation in Baan V, would it be possible to lose the project segment in the warehouse module (only)?

If so, this sounds too perfect to be true.
But then...how do I go about in removing the project segment from the item code. The sessions that deal with this do not allow me to make any modifications the decent way.

What do you guys think?

Hi Francesco,


Now I was thinking......

Using the item code segmentation in Baan V, would it be possible to lose the project segment in the warehouse module (only)?

If so, this sounds too perfect to be true.


Indeed it sounds too perfect to be true. For that reason it is not true. Item segmentation is defined in a tools table (ttgfd422) and can only be viewed in session Item Segmentation (tcibd0500m000 -> tcibd0100s000).
When a baan environment is setup the segmentation parameters will be filled in the mentioned tools table. This segmentation definition is valid for all the companies in that baan environment. It is not even possible to change the segmentation parameters for another company within the same baan environment.
Reasons for this are table sharing in a multi-company setup.

I guess by now you understand that it is not possible to lose the project segment in one specific module only.

Thanks for your reply Frans, but I have a few buts up my sleeve..

The Baan help files tell me, under the heading 'Item Definition and Segmentation' that

The sement definition cannot be changed easily afterwards. So be carefule when you specify the segments!


Now not easily is not the same as not period, right?

First of all, I only have a single company...and even if I had more than one, I would want it to be across all companies.

By the way, when I said warehouse module, I (of course) meant warehouse _package_.

At this point I really don't care if I have to rebuild the entire program from scratch to make this happen. That's how big of an issue this is for me.

But if so, my question remains, can I have a separate segmentation for the wh package, just like I currently have a separate segmentation for the tc and the cp package?

The ‘Item Definition and Segmentation’ quote is valid… Not easily means that you have to clean your system (i.e. remove all items; not to say all data) before you can change the segmentation parameters. It’s a bit of an understatement, I guess.

Yep, I understood you meant the ‘wh’ package.

Suppose you define a new domain. Call it whitem. For this new domain you specify in the segmentation definition that only the Item Base is valid. This was easy, but next…

Next you’ll have to replace all the tcitem domain in the ‘wh’ package with the new whitem domain. This implies program scripts, dlls, dals, reports, forms etc. Everything.

Besides that you’ll need to rewrite all the integration functions in the integration dlls. All item related input and/or output arguments need to be transformed from the tcitem domain to whitem and vice versa. Something similar happens in ‘cp’ package with a function copying items from tcitem to cpitem and vice versa.

After this enormous effort there is still the risk of malfunctioning. There might be things I overlooked now. In my opinion the effort and risk are too high to take it.
Please try an alternative solution!!!

I didn't realize that the segmentation was bound to a domain.

Off course now that you mention it, it makes perfect sense. Duh!:rolleyes:

Thanks for setting me straight.