Presentation is loading. Please wait.

Presentation is loading. Please wait.

1 Walk-in slide. 2 Differences between MK and ERP LN Hands-on Demonstration David Cervelli Managing Consultant April 26, 2006.

Similar presentations


Presentation on theme: "1 Walk-in slide. 2 Differences between MK and ERP LN Hands-on Demonstration David Cervelli Managing Consultant April 26, 2006."— Presentation transcript:

1 1 Walk-in slide

2 2 Differences between MK and ERP LN Hands-on Demonstration David Cervelli Managing Consultant April 26, 2006

3 MK to ERP LN DIFFERENCES  ERP LN – MK History  ERP LN Development History  MK / ERP LN Union  Environment  Data Conversion  Hands-on Demonstration  Training  Benefits / Conclusions

4 4 MK / ERP LN HISTORY  1978 Created by Jan Baan  1979 first Baan sale  Company grew quickly throughout Europe  1993 ASK purchased basic application for next generation ERP from the little- known Dutch company  1994 Computer Associations purchased ASK  1999 Poor management and financial irregularities nearly bankrupt Baan  August 2000 Invensys PLC. acquired Baan for $708 million  June 2003 SSA purchased Baan for $135 million  Late 2004 Planned release of ERP LN version 6 – Gemini  2005 Combined Baan / MK solution release  Jan Baan currently on the Board of Directors of WebEx

5 5  MK and Baan parted ways mid-1990’s  Baan product aggressively developed  Development was designed to allow Baan to compete for larger companies  Competitors: SAP and Oracle  Baan application evolution  Become more polished  Broader application functionality  Better interface  Many 3 rd party products  Scalable to very large BAAN / ERP LN DEVELOPMENT HISTORY

6 6 MK / ERP LN UNION  MK Application will be upgraded / merged into ERP LN in 2005  The combined product was set to be called SSA Open Source  MK and ERP LN were once the same product but evolved in different directions with different focus  Significant differences exist between MK and ERP LN  Costly endeavor:  Data Conversion  Training and Testing  Business Processes  Customizations

7 7 ENVIRONMENT ERP LN 5x to 6 (Gemini in Beta released late 2004)  UNIX or Microsoft NT  Both very reliable and able to support large environments  Oracle, MS-SQL, Sybase (NO ISAM)  True ODBC, very scalable and numerous 3 rd party tools  Primarily UNIX / Oracle or Microsoft NT / MS-SQL environments  Fairly mature and stable. Version 4x had some stability issues. Version 5x has been a fairly sound release.

8 8 HARDWARE  Same as MK  Unix  NT - Intel  Linux

9 9 DATABASE  ISAM no longer available  MS-SQL, Oracle, Sybase support  True ODBC  No Hash Keys  Improved performance due to improved drivers  Maintenance and tools are similar to MK  Tables have been renamed  tiitm001 - tcibd001  tdsls040 - tdsls400  tfacr011- tfacr200 and many more

10 10 INTERFACES – DIFFERENT LOOK AND SIMILAR FEEL  Cleaner more Mature Interface  More GUI look and feel but not fully Microsoft complicated  MK users will see similarities in Sales, Purchase and Inventory modules  Financials, AP and AR very different

11 11 DATA CONVERSION Tables evolved differently in MK and ERP LN  Customers  Vendors / Suppliers  Item Master  Sales  Purchasing  BOMs, Routings, Inventory  Warehousing  Accounts Receivable, Accounts Payable  General Ledger

12 12  Business Partners (Customers and Vendors) share some tables  ‘Roles’ distinguish Business Partner activities  You can Sell To or Buy From the same Business Partner ERP LN BUSINESS PARTNERS

13 13 MK / ERP LN CUSTOMER DIFFERENCES MK  tccom010 Customers  tccom012 Postal Address  tccom013 Delivery Address ERP LN  tccom100 Business Partners  tccom130 Addresses  tccom110 Sold To Business Partners  tccom111 Ship to Business Partners  tccom112 Invoice To Business Partners  tccom113 Pay From Business Partners  Customers are now called Business Partners  Addresses are kept in one table  Tables are organized by functionality

14 14 MK / ERP LN VENDOR DIFFERENCES MK  tccom020 Vendors  tccom022 Postal Address ERP LN  tccom100 Business Partners  tccom130 Addresses  tccom120 Buy From Business Partners  tccom121 Ship From Business Partners  tccom122 Invoiced From Business Partners  tccom124 Pay To Business Partners  Vendors are now called Business Partners  Addresses are kept in one table; shared with customers  Tables are organized by functionality

15 15 MK / ERP LN ITEM MASTER DIFFERENCES MK  tiitm001 Item Master ERP LN  tcibd001 General Item Data  tcibd200 Ordering Data  cprpd100 Planning Data  tcibd007 Costing Data  whwmd400 Warehouse Data  tdisa001 Sales Data  tiipd001 Production Data  tdipu001 Purchase Data  Tables are organized by functionality  Item Master changed substantially  Similar to MK but has matured  Many additional fields and features have been added  Project is part of Item Key

16 16 MK ERP LN SALES DIFFERENCES MK  tdsls040 Sales Order Header  tdsls041 Sales Order Line  tdsls050 Sales Header History  tdsls051 Sales Line History ERP LN  tdsls400 Sales Order Header  tdsls401 Sales Order Line  tdsls450 Sales Header History  tdsls451 Sales Line History  Tables names changed but functionality remains same  Additional fields added  Similar look and feel  Similar behavior  More options  Improved visibility and reporting ERP LN table tdsls401 combines MK tables tdsls041 and tdsls045

17 17 MK / ERP LN PURCHASING DIFFERENCES MK  tdpur040 Purchase Order Header  tdpur041 Purchase Order Line  tdpur050 Purchase Header History  tdpur051 Purchase Line History ERP LN  tdpur400 Purchase Order Header  tdpur401 Purchase Order Line  tdpur450 Purchase Header History  tdpur451 Purchase Line History  Tables names changed but functionality remains  Additional fields added ERP LN table tdpur401 combines MK tables tdpur041 and tdpur045

18 18 MK / ERP LN BOM AND ROUTING DIFFERENCES MK  tibom010 BOM’s  tirou020 Routings ERP LN  tibom010 BOMs  tirou101 Routing Codes by Item  tirou102 Routing Operations

19 19 MK / ERP LN INVENTORY DIFFERENCES Inventory has been split into separate Warehouse modules: wh wmd – Warehousing Master Data wh inh – Inventory Handling wh inr – Inventory Reporting Separate ERP LN functions exist for warehouse inbound, outbound, analysis, lot control, planning, and more MK  tdinv010 Inventory ERP LN  whwmd210 Warehouse - Item Data  whwmd215 Item Inventory by Warehouse  whinr140 Inventory by Warehouse  tcibd100 Item Inventory

20 20 ERP LN WAREHOUSING  All inventory transactions are now sent though a Warehouse module  Sales Orders are released to and shipped in the Warehouse Module  Purchase Orders are received in the warehouse module  Control passes from Sales, Purchasing, Production to Warehousing, then back after material transactions are performed

21 21 MK / ERP LN OPEN A/R AND A/P DIFFERENCES MK  tfacr011 Open AR  tfacp010 Open AP  tfacp011 Open AP Detail ERP LN  tfacr200 Open AR Items Sales Invoices and Receipts  tfacp200 Open AP Items Purchase Invoices and Payments

22 22 MK / ERP LN GENERAL LEDGER DIFFERENCES MK  tfgld009 Chart of Accounts  tfgld014 GL Transactions  tfgld015 posted GL Transactions ERP LN  tfgld008 Chart of Accounts  tfgld102 Non-Finalized Transactions  tfgld106 Finalized Transactions  Finance changed significantly  Retraining will be required for MK users

23 23 FINANCIAL SET-UP AND FUNCTIONALITY  Financials are very different; not much in common  More functionality  More options  More complicated set-up  New modules  Central Invoicing  Cash Management  Company configuration: Single-Single, Single-Multi, Multi-Multi options  Improved visibility and reporting  Easier reconciliation  More steps in the posting process

24 24 FINANCIAL INTEGRATIONS  Integration Transactions/Stock & WIP/Transaction Log > Integration Mapping

25 25 SSA ERP LN Demonstration

26 26 ERP LN TRAINING  In general, much of the ERP LN application functions like MK  Overall system maintenance and management are very similar between MK and ERP LN  Users need to be trained but this should be less painful than learning a new application  Conversion may be opportunity to improve business processes  Finance users will need the majority of training  All customization and reporting will need to be recreated

27 27 SUPPORT AND DOCUMENTATION  Support very good  Documentation is fairly good. Better than MK.  Fairly mature and stable product.  Version 4x had some stability issues. Version 5x was much improved and LN is a sound release.  SP2 been available since early 2006

28 28 DYNAMIC ENTERPRISE MODELER – DEMs  Visual tool that helps user navigate through ERP LN  Does not provide default field level instructions within session  Good for documenting processes; text can be added  Can be used to streamline process tasks  Aids users in getting to session

29 29 TOOLS AND DEVELOPMENT  Similar development to MK  Programming is comparable  Can use SQL queries and stored procedures within code, which is extremely powerful.  Form development is very different  VRC’s structure is the same but naming is different

30 30 MORE BOLT-ON’S  Workbench  Reporting  Financial tools  Other SSA and 3 rd party tools

31 31 OVERALL  MK users will feel at home  Training is required but will be far easier than going to new application  LN is a sound, robust application  Improved visibility and reporting  What MK could have been but never got there

32 BENEFITS AND CONCLUSIONS  Benefits include converting to a new, more mainstream application without many of the issues  Converting from MK to ERP LN is far easier than installing a new application  ERP LN is a mature and robust solution  ERP LN brings many more features  Fully ODBC compliant  Training will be required  Many 3 rd party solutions  Data Conversion will be needed  Draw resources and knowledge from a 3 rd party provider, if needed  Benefits are worth the effort

33 33 Q U E S T I O N S ? David Cervelli Managing Consultant Strategic Systems Group, Inc.


Download ppt "1 Walk-in slide. 2 Differences between MK and ERP LN Hands-on Demonstration David Cervelli Managing Consultant April 26, 2006."

Similar presentations


Ads by Google