Track a WO operation change

This parameter—TRACKOPEWO—controls whether changes to a work order operation need to be audited.

Yes: Changes to work order operations need to be audited. Changes to operation sequence numbers in a routing for a work order are audited. The audit information is saved whenever it occurs.

No: Do not audit changes to a work order operation.

Refer to the MFGREV—Revision management parameter if you need to audit changes to operations for version-managed routings.

When an event occurs that the audit control table can audit, a reference is generated for the event as a sequential revision number. The user can add a free-format comment up to a maximum 50 characters to explain the reason for the change. This "revision reason" is written to the appropriate audit table to provide traceability for the event.

A revision reason is optional.

Direct events

Audited events made directly by the user include, but are not limited to the following:

Audited event	Audited action
Add operation	Selecting the Additional operation not expected action from the Actions icon
Exclude or cancel operation	Selecting the Exclude line action from the Actions icon
Reinstate canceled operation	Selecting the Reactivate action from the Actions icon
Edit production resource	Editing the Work center (EXTWST) or Number of resources field (EXTWSTNBR)
Edit operation planned quantity	Editing the Planned quantity field (EXTQTY)
Edit operation time	Editing the Setup time (EXTSETTIM), Unit time (EXTUNTTIM), or Run time field (EXTOPETIM)
Edit labor	Editing the Labor wk C (EXTLAB) or No. lab res. (EXTLABNBR) field
Edit subcontracted service	Editing the Subcontract product field (SCOITMREF)

Indirect events

Audited events made when the work order header is edited include, but are not limited to the following:

The work order header event itself is not audited, only the resulting event on the routing operations.

These events result in the routing operations being reloaded with the default information from the routing record. Previous changes to the operations are removed. The operations are reloaded, resulting in a tracked event.

Audited event	Audited action
Edit planned quantity	Editing the Planned quantity field (MFGEXTQTY)
Edit routing	Editing the routing Number field (ROUNUM)

Tables updated

Operation events are recorded in the Work order—operations audit table (MFGOPEREV).

Viewing audit details

You can view the audit details from the work order. On the Operations tab, select Revision history from the Actions icon for an edited operation sequence number. The revision history includes the revision reason and a revision code if they were entered, and key details from the operation line. The most recent event displays on the first line of the table, the top line. Amended fields are highlighted.

Level of localization/Global variable

This parameter is defined at the level Site. It belongs to Chapter GPA (Manufacturing) and the Group WOM (Work Order management). The following parameters are also associated with this chapter and group:

CMPUSBCTR (Usable component control)
CUMMAT (Material accumulation mode)
MFGREV (Revision management)
RELSTRDAT (Level on WO start date change)
RELUPD (Upgrade upon execution)
TRACKMATWO (Track a WO component change)

The global variable GTRACKOPEWO is associated with this parameter.

Functions impacted

The following function is associated with this parameter:

Manufacturing > Planning > Work order

Comments

This parameter audits changes to operations in non-versioned routings.

Refer to the MFGREV—Revision management parameter, which audits changes to operations of version-managed routings.