Service Writer System

(placeholder)

What are Tables and How are They used in SWS?

1.  Lookup Table 

2.  Customer Codes



3.  Work Order Descriptions



4.  Tax Codes and Rates



5.  Criteria



6.  Work Status



7.  Message Line



8.  Release Agreement



9.  SYS Code



10. Tire Condition



11. Tire Reason



12. Tire Type



13. Tread Type



14. Parts Information Entries



15. Preliminary Type Information



16. On Order Category



17. On Order Description



18. On Order ID


Service Writer System TABLES

Tables are used throughout the SWS to eliminate re-keying redundant information, reduce keying errors, allow user flexibility, and accommodate each company’s requirements.  All tables are initialized with default values that can easily be changed, if necessary, to meet your company’s needs.  



     Below are some of the tables used in the SWS.

1.Lookup Table -used throughout the system to specify the company name, address, telephone information, default tax rate for your state and other general information about your company.



2. Customer Codes -used in the Customer Master to specify the current status or integrity of the customer.



3.Work Order Descriptions -used in open and history orders to define the type of work performed in the work order.   



4. Tax Code and Rates -used throughout the system to specify tax codes and their associated tax rate.  Some special codes exist such as 0% tax code for tax-exempt sales and EX tax code for labor charges.



5.Criteria -used to define scheduled maintenance criteria using either a time or mileage factor.  For example, state inspections may be required every 365 days (annually) and oil changes may be required every 15,000 miles.  These criteria can be tracked for every unit entered in the SWS.  There is no limit to the number of criteria that may be defined.  This is accessed through the Unit Detail screen.



6.Work Status -used in open and history orders to specify the current status of the work being performed.       

7.Message Line -specifies the message line that prints along the bottom of the open and history orders.       

8.Release Agreement -specifies the release agreement that prints along the bottom left hand side of a work order for the customer to sign.       

9.SYS Code -used in work orders and purchase orders to specify the system code of the work order (not utilized by all companies).       

10.Tire Condition -used in tire sub-system to specify the condition of the tire.

11.Tire Reason -used in tire sub-system to specify the reason that action was taken on the tire.

12.Tire Type -used in tire sub-system to specify the brand of the tire.

13.Tread Type -used in tire sub-system to specify the tread-type of the tire.

14.Parts Information Entries -used to specify any additional information you want to retain for any vehicle, trailer, piece of equipment, etc. This is accessed from the Open Orders, History Orders and Unit Detail.



15.Preliminary Type Information -used on the preliminary order, this table specifies the information to be printed on the form.  Three areas are printed: 1) Comment - which prints at the top of the form: 2) Total Description - which prints next to the total amount; 3) Line Message - which prints along the bottom of the preliminary order.  Because there is specific processing performed for Packages, Re-sales and Estimates, there must be one entry for each of the three designated types of preliminary orders: PAC (packages), RES (re-sales), and  EST (estimates). 



16.On Order Category -used in purchase orders to specify the expense category of the items being ordered.       

17.On Order Description -used in purchase orders to define the type of purchase being ordered (i.e. Customer Order, Stock Order, etc.). 


18.On Order IDs -used in purchase orders to specify various codes. For example, if using our core feature, define ID1 in this table with the core code you want to use.  Then, all parts either prefixed with ID1’s value or who’s core code is set to ID1’s value are processed as cores being returned to the vendor, and they are accumulated and reported in the core total field of the purchase order.