MAS 500 Migration Troubleshooting. Darrick Coles Development Manager MAS 500. Introductions Overview What is Data Migrator? Goals Architecture Key concepts Existing migrations Migration preparation. Data tips Performance tips A typical migration. Agenda.
Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
MAS 500 Migration Troubleshooting
Development Manager MAS 500
What is Data Migrator?
A typical migration
Just follow the steps in order
Icons for available activities in the current step
Have sales and implementers read this—it’s packed with MAS 90 to MAS 500 migration tips
If a migration exists, the Migrate button will be enabled
If an extraction exists, this button will be enabled—you can enable it, too
MAS 90 or
Vendors* and classes
Customers* and classes
Bill of materials and routings
Product group pricing
Customer/product group pricing
Sales commission plans
Transactions and balances
Open sales orders
GL account history
Posted invoices (open and closed)
Posted vouchers (open and closed)
Inventory cost tiers and bin quantities
* Including custom fields
Tax classes and codes
Sales tax accounts
Product price groups
Purchase product lines
Sales product lines
Vendor payment terms
Customer payment terms
MAS 90, MAS 500 market space
Read the documentation: MAS 500 Assisted Company Setup has lots of information and hints about the differences between MAS 90/200 and MAS 500
Clean up before migrating
Know and use available resources: sales and implementation
Know their business and how they use MAS 90
What’s their favorite thing?
What do they take for granted?
Familiarize yourselfwith the differences
Don’t assume this is a simple upgrade: PLAN, TEST, CHECK PERFORMANCE, SPOT CHECK VALIDATIONS
In MAS 90 and MAS 200, costs are maintained at the operation level; in MAS 500 they are maintained at the work center level. There are several additional differences between how MAS 90 / MAS 200 and MAS 500 handle costs including:
MAS 90 / MAS 200 does not allow for setup costs
MAS 500 does not allow for per-piece costs
MAS 500 does not allow for cost as a percent
Before migrating your MAS 90 / MAS 200 manufacturing data, carefully plan your new MAS 500 manufacturing system to take the different costing methods into account.
The work center ID in MAS 500 is created by combining the MAS 90 / MAS 200 work center and operation codes to create a unique identifier. The full MAS 90 / MAS 200 work center and operation codes are used for the work center description in MAS 500. No schedule information is migrated from MAS 90 / MAS 200.
List of Work Centers and OperationsFrom Work Order Setup, select Work Center Maintenance, then click the Printer button. From Work Order Setup, select Operation Code Maintenance, then click the Printer button.
INSERT StgReasonCode (ReasonCodeID, Description, ProcessStatus, SessionKey)
SELECT Cancellation_ReasonCode, Description, @NOT_PROCESSED, @_iSessionKey
WHERE Cancellation_ReasonCode IS NOT NULL
INSERT StgSalesTeam(SessionKey,SalesTeamID, Description, ProcessStatus)
SELECT @_iSessionKey, Division, Description, @NOT_PROCESSED
WHERE NULLIF(Division, '') IS NOT NULL
...is that true?
Dirty Read:Check this, but only do reading with this checked!
Cache Size: Bigger is better
Burst Mode:Will reduce number of times file is locked
NOTE: Version 3.7 ODBC driver performs faster than 3.6 and 3.61
See documentation menu: ODBC 3.x at
http://pvx.com/ for ODBC setup