MANMAN Data Migration - Strategic Systems Group

Download Report

Transcript MANMAN Data Migration - Strategic Systems Group

MANMAN DATA MIGRATION
MK
BaaN
Oracle
Many other ERP applications
Strategic Systems Group
www.ssgnet.com
info@ssgnet.com
MANMAN DATA MIGRATION
Overview






Benefits of Automated Data Conversion
General Approach & Considerations
Data Manipulation
Go-Live Data Conversion
Alternative Approaches
Conclusions
AUTOMATED DATA CONVERSION
Benefits






Data consistency
Referential integrity between tables
Fewer errors
Faster than manual methods for large
numbers of records
Accurate field translations
Effective for multiple sites
GENERAL APPROACH
New ERP
application
Classic Manman
Data Manipulation
SSGBusIntell
ASCII file
extracts
File Transfer
from Manman
system
ASCII extract
files
Access
ASCII file
format
ASCII formatted
import files
File
Transfer to
new ERP
application
GENERAL APPROACH








Identify files and fields to be converted
Perform data mapping
Define conversion from old to new values
Extract data from Manman
Add new application defaults
Convert data to new format
Testing and validation
Upload data into new ERP application
GENERAL APPROACH




Static data should be converted through the
automated data conversion process
Files with a smaller number of records
should be entered manually
Transactional data should be entered
manually
Determine timing as it will affect month-end
and any other signification reporting dates,
for example, inventory and G/L overlays
GENERAL APPROACH
Static Data

Identify files and fields to be converted

Static data should be transferred using
automatic data conversion
Item Master
 Product Master
 Inventory by Location
 Bills of material
 Routings
 Employees

■ Vendors
■ Customers
■ Ship-to addresses
■ Pricing table
■ General Ledger
■ G/L History
GENERAL APPROACH
Transactional Records

Transactional records entered manually





Open
Open
Open
Open
Open
Accounts Payable
Accounts Receivable
Purchase Orders
Sales Orders
Work Orders
GENERAL APPROACH
Historical Data

The following historical data can be
extracted from Manman and preserved for
inquiry and reporting using SSGBusIntell:






Accounts Payable Distribution
Accounts Receivable History
Closed Production Orders
Purchase Order History
Purchase Receipt History
Historical stock balances
GENERAL APPROACH
Historical Data

Removing the historical data from Manman
can meet the following organizational
needs:


The end-user will have Manman data available
for reporting and inquiry
I/T can take the Manman system off-line to
eliminate maintenance requirements
GENERAL APPROACH
Optional Data

The following data can be converted
manually or automatically, or some of it
may not apply to your environment:





Bills of Material
Routings
Operations
Lot Master and Variable Features
Approved Supplier List
GENERAL APPROACH
Data Mapping

Data mapping & related considerations




Define matching files
Define matching fields
Define field translations & cross-references
Identify table dependencies
GENERAL APPROACH
Data Mapping to MK
Manman Files
MK Tables
Item Master
Product Master
Inventory by Location
Bills of Material
Routings
Vendors
Bill-to Customers
Ship-to Customers
Pricing file
G/L History
tiitm001
tiitm001
tdinv001
tibom010
tirou020
tccom020
tccom010
tccom013
tdsls032
tfgld011
tfgld012
Item Data
Item Data
Item Data by Whse
Bill of Material
Routing
Suppliers
Customers
Delivery Address
Prices by Price List
G/L Balances
G/L History
GENERAL APPROACH

Automated Data Conversion

Output format
ASCII file
Variable field lengths
Delimited with “|”
No trailing delimiter
No quotes around strings
Numeric values for enum fields
GENERAL APPROACH

Automated Data Conversion





Special handling may be required for:
Date fields
Field alignment
Decimal point
Right justification
Combined fields
Special characters
Output example (pricing by price list)
SPL|100015|999999|01011994|00000000|45.21|0|1
DATA MANIPULATION


Export data from Manman
Load data into Access




Perform translations and conversions from
Manman values to value in new ERP
application
Add new defaults and required fields
Extract data from Access
Upload data into new ERP application
Automated Data Conversion
Solution


SSGBusIntell provides an ‘off-the-shelf’
solution that meets approximately 80%
of the data conversion requirements
SSGBusIntell consists of a series of data
extracts that take data from Manman to
an Access or SQL database
Automated Data Conversion
Solution

SSGBusIntell static data extracts from
Manman:





Customer Master
Vendor Master
Item Master
Employees
Inventory
Automated Data Conversion
Solution

SSGBusIntell data extracts from Manman:










Accounts Payable Distribution
Accounts Receivable History
Closed Work Orders
Purchase Order History
Purchase Receipt History
General Ledger Detail and Summary
Open Sales Orders
Open Accounts Receivable
Open Purchase Orders
Open Production Orders
GO-LIVE DATA CONVERSION

Sample Conversion Sequence













General Ledger accounts
Item master
Vendor master
Customer master
Employee master
Delivery addresses
Bills of material
Routings
Prices by price list
Item data by warehouse
Manual data entry of A/R, A/P, S/O, P/O, W/O
Go live
G/L history
ALTERNATIVE APPROACHES

Modify standard SSGBusIntell extracts
to:
Build translation and cross-references into
the data extracts
 Create new default values using Manman
values
Use Quiz extracts to enhance SSGBusIntell
data extracts


Advantages





SSGBusIntell contains 80% of the data needed
for most data conversions
SSGBusIntell extracts can easily be modified to
add
 Cross references
 New values based on Manman values
Software development time is limited or not
required, depending on conversion requirements
Results can be achieved more quickly
SSG has good knowledge of Manman data
structures and tools
CONCLUSIONS


Compare benefits of SSGBusIntell data conversion
tool to cost of software development to create
conversion scripts from ‘scratch’
Suggestions for success
 Go slow and plan conversion carefully
 Focus on the static data
 Assemble a team with varied application and
technical skills
 Save some energy for post-conversion
difficulties