Hello All, I'm writing a blog about all the call-outs when migrating from Work Order to Production Management, including migration considerations and field mapping. Has anyone experienced anything worth mentioning not listed below?
Migration:
Step 0000 in WTs - every work order in old version must have this step; must define step description (I use BOM header). Prior to this, you may need to set up a work center and operation code to use in this step.
Step 0000 in Routers - same scenario as above for router-to-template migration.
Labor Scaling Method - converts as Templates per Parent vs. Parents per Template and needs to be fixed after migration
Enhanced Scheduling Hours – may convert incorrectly and should be imported after migration
Labor Budget and Scheduled Hours on Step 000000 - are zeroed out and should be imported after rmigration
Cust #/Name on WTs made for SOs - some WTs may not display this information; since these fields are not in the WT header table, I created UDFs and populated them.
Field Mapping:
Work Ticket No. - exists only in the PM WT header table. WT detail, WT step, etc. tables have only the WT key.
Work Ticket Status Comment - in Work Order this was a single field in the WO header table, hence one value per WO; in PM it is a field in the PM Step table, therefore there can be one value for each step, i.e. multiple values per WT. Migration tool populates every step with the WO header value.
------------------------------
Susan Pawlowic
Sage 100 Solutions Architect
RKL eSolutions, LLC
spawlowic@rklesolutions.com(717) 735-9109 Ext. 4352
------------------------------