The Sage 100 Work Order module was discontinued as of Version 2023. When you are upgrading from a Sage 100 version with the Work Order module to Version 2023 or higher, you will be converting the Work Order module to the Production Management module. For Licensing purposes, your old Work Order Module converts into three (3) Production Management Licenses. This will allow up to three people to utilize the PM Production Management Module, concurrently. Reach out to your RKL eSolutions CSM Customer Success Manager if you believe you will want to purchase additional licenses.
Prior to migrating your data to the new version with Production Management, there is some housekeeping that needs to be completed. After migrating the data, you may need to complete some additional tasks depending on how you were using Work Order in your old Sage 100 version and how you want Production Management to work moving forward.
Pre-Migration
step 0000
In Production Management, every work ticket has a Step 000000, which serves as the work ticket header. Step 000000 can be simply a placeholder for the work ticket header, but if needed it can also be a “working” step in that it can have a valid work center and activity code as well as materials and estimated hours, and against which issues, labor transactions, and other transactions can be processed. This will be the case for those work orders that already have a Step 0000. For the others, Step 0000 must be added to those work orders before the data is migrated; if this is not done, Step 0000 will be automatically added to those work orders with the same values as the first valid step on each work order.
Here are suggested steps for adding Step 0000.
- Create a Work Center and Operation Code
-
In Work Center Maintenance and Operation Code Maintenance, create a generic work center and operation code to assign to the new Step 0000 records.
-
- Export Work Orders Without Step 0000
- If none of your work orders have Step 0000, export all work orders using the WO1 table. You will have to fix them prior to migration by Importing a step 0000 for each existing work order.
- If some of your work orders have Step 0000 and others don’t, you will have to fix them prior to migration by either manually adding a Step 0000 in your source data company or writing a Visual Integrator Import to update all work orders to include a step 0000
- Import Step 0000
-
Create an import job to create Step 0000 for the work orders that don’t already have this step, assigning the new generic work center and operation code.
-
Work order purge
Run the Work Order Purge utility to move closed work orders into the history files.
Post- Migration
The following scenarios should be addressed after the migration:
data mapping
-
Labor Scaling Method – If you are using Parents per Template as your labor scaling method, check your templates and work tickets, as these may have converted as Templates per Parent. If this is the case, use Visual Integrator to export the steps and import the correct method.
-
Enhanced Scheduling Hours – if you are using the Enhanced Scheduling features in Production Management, these hours may be incorrect and require an export of the data from Work Order and import of the correct data.
Step 000000 Labor Budget and Scheduled Hours
-
Whether or not you imported Step 00000 with empty labor budget and scheduled hours prior to migration, check these hours in the converted work tickets.
-
If they did not convert correctly, an export of the data from Work Order and import into Production Management may be required to adjust these hours.
Customer Number and Name on Work Ticket Header
-
If you have Make for Sales Order work tickets, ensure that they all display the customer number and name on the work ticket header screen; this can be done by performing a custom lookup or creating a Crystal report. Some of the work tickets may not show this information.
-
Since the customer number and name are not fields in the Production Management work ticket header table, custom UDF fields will need to be created and added to the work ticket header screen, and an import will need to be performed to populate those fields.
-
New work tickets should display this information properly, so once the existing work tickets in question have all been completed and are in history, these custom fields can be removed from the screen.
custom reports and forms
No work order tables or fields will be converted to Production Management tables and fields for custom forms, custom reports, or custom report settings with added Work Order tables. These tables and fields will all need to be added to the converted Crystal reports.
There are a few considerations to keep in mind when adding Production Management tables and fields into these custom reports:
Work Ticket Number
- In the Work Order module, the Work Order Number field is included in every Work order table.
- In the Production Management module, this field exists only in the PM_WorkTicketHeader table. All other Production Management tables identify the work ticket by a WorkTicketKey field. To add the Work Ticket Number field to custom reports or settings, you will need to do one of the following:
- Add the PM_WorkTicketHeader table to the report and link it to the next logical Production Management table via the WorkTicketKey field.
- Add the Work Ticket Number field as a custom UDF field to the applicable tables. If adding to any history tables, you will need to perform export and import jobs to populate the history data.
Work Ticket Status Comment
-
In the Work Order module, the Work Order Status Comment exists in the WO1 (Work Order Header) table, thus there is one Status Comment value per work order.
- In the Production Management module, this field exists only in the PM_WorkTicketStep table; each step record can have a different value. During the conversion process, Sage 100 places the WO1Status Comment field value in each of the step Status Comment fields.
Work Center Fields
-
Charge Labor at Employee Rate – this field now resides in Work Ticket Class Maintenance and is called Cost Labor at Standard.
-
Charge Labor at Employee Rate (WO) – used the employee payrate from Production Employee Maintenance.
-
Cost Labor at Standard (PM) – uses the hourly rate in Activity Code Maintenance (formerly Operation Code Maintenance).
Therefore, if the work center in Work Order has this box checked, the data conversion process result should be that the Production Management Cost Labor at Standard field in Activity Code Maintenance should be unchecked, and vice versa.
This means that you can have this option enabled or disabled for different activity codes in the same work center, if desired.
-
Outside Processing – this field is now an option in the Classification picklist in Activity Code Maintenance.
-
Comments – these fields have been eliminated.
Activity Codes
-
Planned Cost Rate/Piece - this field has been eliminated.
- Run Time Format-Activity Code-renamed to Calculation Method
For additional assistance in converting the Work Order Module to Production Management or purchasing additional licenses, each out to your RKL eSolutions CSM Customer Success Manager.
Want More Sage 100 Tips & Tricks?
Make sure to subscribe to our blog to stay up-to-date on the latest insights and trends. We're dedicated to providing valuable resources for businesses looking to optimize their financial management with Sage 100.
Check out these blogs to help get you started!
How to Reverse a Cash Receipt
How to Reverse an Invoice Posted to the Wrong Month
Understanding the Purchases Clearing Report
How to Setup ACH Processing in Accounts Payable
