ERP LN Upgrades

We are interested in connecting with other companies that have implemented an ERP Upgrade Strategy or Process. We highly customized our Baan IV environment which makes it impossible for us to take upgrades or monthly solution packs. With our implementation of ERP LN we would like to create an environment that makes it possible to keep the software more current and take advantage of new functionality enhancements. This is a big paradigm shift for us. If anyone would be able to share their strategy and experiences around decision making, business involvement, process, roles, testing, etc., please let me know. Thanks.

Find more posts tagged with

Baan / LN - General Discussions

Comments

unknown

We are also heavily customized. However we were able to upgrade from Baan IVc3 to BaaN IVc4. We used Qkey which enables some customization but does not modify source code.

I've also heard that you should have 2 servers. One to test an upgrade prior to installing in production system.

bonnie-dziadkowiec

Hello Laura--We have several customer profiles featuring Baan to LN upgrades on our website that you can review. Go to: www.infor.com/solutions/erp/ and select the individual links to each customer profile. And if you want to speak to a customer about their experience, please let your sales rep know and he'll connect you with a customer. Hope this helps!

unknown

What I am always recommending are the following key points:
* Have source code available, even if you do not modify it (for debugging, programming customizations against standard libraries, etc.)
* Make maximum use of the "User Exit" functionality
* All addon logic goes into DLLs. One or more DLLs per required functionality, but not more then one functional requirement in one DLL (seperation of concerns)
* If you require a new field in a session, modify the standard table. DON'T create a "rucksack" table. Table modifications are cheap in terms of maintainability. Rucksack tables need a lot of glue code in the scripts, so they are not.
* Customizing Reports is the most expensive thing you can do in terms of maintainability. In contrary to common believe, modifying standard scripts is cheaper(!), when done properly. So don't allow for five different purchase order reports and five different sales order acknowlegemnet reports. Stick to a single report, using different layouts to serve multiple requirements.
* COMMENT PROPERLY when modifying standard scripts, using the bla.o, bla.n, bla.sn etc. tags that have been introduced by Baan developers long ago.
* Keep the changes in a standard script to a minimum: As already said: The logic goes into a DLL, the script only calls the DLL (whereever possible, of course).

best regards
Uli

--
Dipl. Ing. Ulrich Fuchs
www.ulrich-fuchs.de

Copyright © 2025 Infor. All rights reserved.