Moving from BAAN IV to LN

unknown

Hello Infor user community.

I have a couple of question around how BAAN 4 compares to Infor LN 10.7:

• From an ERP move standpoint: when evaluating to move from BAAN 4 to Infor LN 10.7, should we consider this as a technological upgrade or as a fresh conversion to a new ERP system. In other words, from an effort perspective, moving to LN is the same as moving to ERP XYZ or is it a simpler road.
• From an end user change management perspective: Beyond the graphical interface, are the main business processes and data flows in LN 10.7 comparable to the ones in BAAN 4?

Other questions that come to my mind.

 

• Data dictionary: is the database table/field structure a continuation of what was already in BAAN 4. Is table/fields naming convention the same?
• Programming language: Is the programming language behind BAAN 4 the same as LN?

Thanks!

Infor dEPM v12.0.10 RT Whats New.mp4

pbenvenuti

We are in the process of moving from MK to LN 10.7 - very similar to BAAN 4.

To the technical/support staff, the underlying structure is familiar - table/session names are similar, but there are just many more of them and therefore relationships are a bit more complex.

It is a significant upgrade that will require a review of your business processes. Some are similar but there is a lot of additional functionality/flexibility thereby increasing complexity.

10.7 introduces the concept of "sites." My opinion is that this was released prematurely as rather than make the effort to update certain sessions, they were simply expired. One specific example: Display Stock by Production BOM - a tool we used just prior to commencing complex assemblies to ensure we would be able to complete a fixed order quantity. Gone in 10.7. It also introduces significant complexity to the engineering process. So much so for our company that we decided on a work-around - which brings me to my next point...

Workarounds/customizations are easier as no modification to the forms/sessions/reports/etc takes place - customizations are handled through a separate "extensions" module.