Revision history on Work order

By | August 30, 2021

Sage X3 provide us functionality where we can keep a track on the modification done on existing work order. If any of an operation or component is modified we will be able to track the critical changes. We will be able to check which field is modified and the reason of modification done by user.  Not only it tracks the modifications, it also tracks if any of the components is added to the existing work order. Sage X3 highlights the modified fields and those fields or line appears in red. This tracking history is very useful and time saving incase where user needs to know what changes are made to the existing work order.

To enable the tracking history of components and operations of work order we need to follow the below steps.


Select the GPA chapter and go to the details of WOM (work order management) group. You will able to find a screen as shown in below screen shot.

Here you will find two parameters i.e. TRACKMATWO and TRACKOPEWO which we need to set on yes.

Fig 1: Parameter values

When these two parameters are set to “Yes” and changes are made to a component or an operation on a work order, the changes are recorded to the following two tables:
MFGMATREV this is work order materials audit table and MFGOPEREV is for work order operations audit table.
When making changes to a component or an operation line, a “Revision reason” can be entered manually but this revision reason is not mandatory, and it can be left blank. This ‘revision reason’ field helps other users to know for what reason the work order is modified.
Once a change is made, the revision can be viewed by using the Revision history action from the Actions icon on the component or operation line as shown in the below screen shot.

Fig 2 : Revision history on action button

The revision history for the changes made to an operation or a component will be available after saving the changes. For example, if a new component is added, the “Revision code = Add” will show that a new component was added. However, it is not mandatory to add a revision reason for changes to components on non-versioned products. After saving the changes, the revision code changes to “Modify” and the new revision line displays the changes in red.
Refer the below screenshot.

Fig 3: Revision history

The top line in the revision history always reflects the current values of the changed fields in the component line. The revision history is displayed in reverse chronological order from newest to oldest.
Hence by following all the above steps we can keep a track on modification of operation and components of a work order.