Transcript Manman to SSA ERP LN Migration

Manman to ERP LN Migration
August 2006
Strategic Systems Group, Inc.
David Cervelli
info@ssgnet.com
Manman to ERP LN











Strategic Systems Group Overview
Manman to ERP LN Migration
Environment
Conversion Process
Manman to ERP LN Conversion (short list)
Manman / ERP LN Differences
Conversion Schedule Highlights
Conversion Methodologies
Conversions Pitfalls
Successful Conversions
Conclusions
Strategic Systems Group
Overview
 Founded in 1991
 Software Development for Classic Manman, MK, Baan and
ERP LN
 Platforms and Applications: Manman, Manman/X, MK, Baan
IV and V, SSA ERP LN, Great Plains, Oracle and Webbased Applications
 Worked with Computer Associates as Implementation
Partner
 SSA-GT Preferred Business Partner
 Performed many conversions to/from Manman, Baan and
MK
 Active CAMUS and SSAU Member
Strategic Systems Group
Overview
SSG worked closely with ASK and Computer Associates:
 Pre and Post-Sales Support
 Installed, Implemented and Trained Clients as a
Computer Associates Partner
 Performed Level One Phone Support for Manman and
MK as a Computer Associates Partner
 Provided Application and Technical Training at Client
Sites and Computer Associates Offices for both
Customers and Support Personnel
 Current SSA Business Partner responsible for data
migrations to SSA ERP LN
Manman to ERP LN Migration



Manman Application is being retired
SSA offering a license swap from Manman to
ERP LN at reasonable cost
Conversion efforts and investments include:







Hardware
Data Conversion
Training
Pilot Testing
Business Process Impact Analysis
Customizations
Three to Six Month Business Impact
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, numerous 3rd 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.
Conversion Process





No two conversions are the same
All conversions have some similarities (both
good and bad conversions)
Project Manager should be internal company
employee
Cross-functional business teams should
represent all significant departments
Pilot test and perform user training with your
company data
Conversion Process


Identify gaps and business process changes early
Identify migration and process issues
 Manman Customer and Suppliers become Business Partners
 Manman Addresses
 Financial Integration Mapping

What data will be converted?
 Master Data
 Open Transactions
 History
 Historical companies
 3rd party databases


Will Manman system be retired or used for historical
purposes?
Will 3rd party products be migrated to LN?
Master Tables

Master tables contain data that must be migrated
 Customer Master
 Bill To – Ship To Masters
 Vendor Master
 Item Master
 Bill of Materials
 Routings
 Chart of Accounts

Structural differences between applications will
require a process to map and translate data from
Manman to ERP LN
Production Tables
Production tables
 Open transactions; data used in day-to-day operations
 Data must be migrated to ERP LN (manual or
programmatically)
 Inventory
 Open Accounts Receivable
 Open Accounts Payable
 Open Sales Orders
 Open Purchase Orders
 Open Production Orders
 Data structure is different between Manman and ERP LN;
cross-reference tables will be required to migrate this data.

Historical Data




How will you access Historical data?

Accounts Payable Distribution

Closed Sales Orders / Sales History

Closed Purchase Orders / Purchase History

Closed Production Orders / Production History

Sales Order Bookings

Receipt History

Closed Accounts Payables

Closed Accounts Receivable Transaction Log
Migrating historical data into ERP LN may be not worth the cost
Option 1: Leave data on the Manman system

Data can be accessed for historical purposes

Manman system would need to remain online for some time
Option 2: Data warehouse

Move historical data to a data warehouse for user access

Eliminate Manman from active maintenance and upkeep
Manman to ERP LN Differences







Business Partners
Enterprise Units
Financial Set-up and Processing
Cash Management Module
 A/R receives cash
 A/P processes payments
Central Invoicing
Enterprise Planning
Numerous others
Manman to ERP LN Conversion



(Short List)
Customer File Mapping
 Bill To number
(ERP LN 6 characters, Manman 10 characters)
 Ship To number
(ERP LN 6 characters, Manman 10 characters)
 Customer Financial Group
 Line of Business
 Area
 Route
 Terms of Payment
Vendor File Mapping
 Supplier Number (ERP LN 6 characters, Manman 10 characters)
 Line of Business
 Area
 Route
 Terms of Payment
Item Master Mapping
 Item Type; Item Group
 Cost Price Component
 Product Type
 Single Code
 Price Group
 Statistics Group
 Order Policy; Order System; Order Method
ERP LN Business Partners
Business Partners (Customers and
Vendors) share some tables
 ‘Roles’ distinguish Business Partner
activities
 You can Sell To or Buy From the same
Business Partner

Manman / ERP LN Customer Differences
Customers are now called Business Partners
 Addresses are kept in a separate table
 Tables are organized by functionality

Manman



BILMAS Customers
CUSFIL Postal Address
CUSFIL Delivery
Address
ERP LN






tccom100
tccom130
tccom110
Partners
tccom111
Partners
tccom112
Partners
tccom113
Partners
Business Partners
Addresses
Sold To Business
Ship to Business
Invoice To Business
Pay From Business
Manman / ERP LN Vendor Differences
Vendors are now called Business Partners
 Addresses are kept in a separate table
 Tables are organized by functionality

Manman


VNDMAS Vendors
VNDMAS 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
Manman / ERP LN Item Master Differences



Tables are organized by functionality
Item Master changed substantially
Manman

IM Item Master

ERP LN








tcibd001
tcibd200
cprpd100
tcibd007
whwmd400
tdisa001
tiipd001
tdipu001
General Item Data
Ordering Data
Planning Data
Costing Data
Warehouse Data
Sales Data
Production Data
Purchase Data
Manman / ERP LN BOM and Routing Differences

Manman


PSF BOM’s
RTFIL Routings

ERP LN

tibom010 BOMs
 tirou101 Routing Codes by
Item
 tirou102 Routing Operations
Manman / 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 modules exist for warehouse inbound,
outbound, analysis, lot control, planning, and more

Manman
 Invfil Inventory

ERP LN
 whwmd210
 whwmd215
 whinr140
 tcibd100
Warehouse - Item Data
Item Inventory by warehouse
Inventory by Warehouse
Item Inventory
Manman / ERP LN Sales Differences



Tables names changed but functionality remains same
Additional fields added
Manman

SOEFIL S/O Header
 SODFIL S/O Line
 SOEFIL S/O Header
History
 SODFIL S/O Line
History

ERP LN




tdsls400
Header
tdsls401
tdsls450
History
tdsls451
Sales Order
Sales Order Line
Sales Header
Sales Line History
Manman / ERP LN Purchasing Differences
Tables names changed but functionality remains
 Additional fields added


 ERP LN
Manman
 tdpur400
 POMAS P/O Header
Header
 POFIL P/O Line
 tdpur401
 POMAS P/O Header
Line
History
 tdpur450
 POFIL P/O Line
History
History
 tdpur451
History
Purchase Order
Purchase Order
Purchase Header
Purchase Line
Manman / ERP LN Open A/R & A/P Differences

Manman



ARFIL, INVIL
Open AR
VCHFIL
Open AP
PADFIL
Open AP Detail

ERP LN


tfacr200 Open AR Items
Sales Invoices and Receipts
tfacp200 Open AP Items
Purchase Invoices and
Payments
Manman / ERP LN General Ledger Differences




Training will be a key requirement
Finance changed significantly
Financial Integrations added
Manman


GLMAS
Chart of Accounts
GLDFIL
GL Transactions

ERP LN



tfgld008 Chart of Accounts
tfgld102 Non-Finalized
Transactions
tfgld106 Finalized
Transactions
Financial Integration Mapping
Benefits
Mapping
Dimension
Values
 Better financial
information
 Easier access to
Dimensions
Chart of Accounts
data
 Drill downs
Cost
Financial Integration Mapping
 More complex
set-up
Conversion Schedule Highlights











Choose and Install Hardware
Install ERP LN Software and Database
Configure ERP LN test company
Conduct Functional Overview Training and
Gap Analysis
Convert Data from Manman to ERP LN
Test Initial Data Conversion
Train, Train, Train
Test, Test, Test
Adjust ERP LN Parameters and Data
Conversion Processes
Reconvert Manman Data to ERP LN
Go Live on ERP LN
Conversion Methodologies
SSA-GT Tool
Migrates data directly from Manman to LN
 Converts data
 Supports mapping
 Still need to validate data after it is migrated
 Not a turn key solution
 Customer is responsible
 Data mapping
 Data validation
Conversion Pitfalls




Don’t do it all at once
 Keep major business restructuring changes separate
from the implementation
 Time phase the implementation, if feasible
 Stick to the scope of the project; don’t fall prey to
‘creeping elegance’
Resource Allocation - don’t be a one person
implementation team
Recognize the impact the conversion can have on day to
day operations immediately following conversion
Maintain clear scope on customizations and
modifications
Successful Implementations
 Project Management
 Planning
 Scope containment
 and much more
 Cross Functional Implementation Team
 Business Process Impact and Gap Analysis
 Business Requirements Definition
 Well Orchestrated Data Migration
 Training and Pilot Testing
 Other Requirements:
 Interface to disparate systems
 Customizations and modification
 Migrating disparate data
Bring it all together
Project
Management
Risk
Management
Data
Conversion
Process
Documentation
ERP
Implementation
Business
Requirements
Interfaces &
Disparate
Systems
Training
and
Pilot Testing
Customizations
Conclusions




Converting from Manman to ERP LN is challenging but
manageable
Key Issues
 Resource Allocation
 Training and Testing
 Data Conversion
 Business Process Impact
 Scope Management
Consider keeping an ODBC-Compliant repository for the
Manman Data
If needed, draw resources and knowledge from a 3rd
party provider
Questions
?
David Cervelli
Strategic Systems Group, Inc.
info@ssgnet.com