General parameters > Chapter Manufacturing > Parameter MFGREV (Revision management) 

This parameter controls the auditing of key changes to a work order for a versioned product.

'Yes' - 'Critical' work order events must be audited. That is, information about certain events that occur to existing work orders for versioned products (BOMs) is saved whenever they occur.

 The audited events are changes to work orders that form an integral part of the manufacturing process. As each of these changes must be tightly controlled they are considered to be 'critical changes' within the context of amendments to work orders.

'No' - Do not audit changes to a work order for a versioned BOM.

Audited events

This parameter allows you to track when certain events occur to a work order for a versioned product (BOM) whenever they occur.

When an event occurs which the audit control table requires to be audited, an audit reference is generated for the event. This is a sequential revision number. A mandatory free-format comment (maximum 50 characters) must be provided by the user explaining the reason for the change. This 'revision reason' is written to the appropriate audit table to provide traceability for the event.

Direct events

Each event listed in the table below is is considered a 'critical' change in the context of amendments to work orders for versioned products. They can only be made by an authorized user:

  • Direct component events can only be made by users with parameter ECCWOCOM (WO component critical changes) set to 'Yes'.
  • Direct operation events can only be made by users with parameter ECCWOOPE (WO operation critical changes) set to 'Yes'.


Audited component events


Audited operation events


Addition of a component
(Using the Add unexpected material or Add sub-assembly (phantom) action (from the Actions icon))

Addition of an operation
(Using the Additional operation not expected action (from the Actions icon))

Excluding (or cancelling) a component
Reinstating a (cancelled) component
(Using the Exclude line or Reactivate actions respectively (from the Actions icon))

Excluding (or cancelling) an operation
Reinstating a (cancelled) operation
(Using the Exclude line or Reactivate actions respectively (from the Actions icon))
Changing the required quantity of a component
(Field Requirement qty)
Changing the production resource that is to be used for an operation
(Fields Work center or Number of resources)


Changing a pick list component issue statement
(Field Pick list code)

Changing the planned quantity for an operation
(Field Planned quantity)

Assigning, or changing, a specific manufacturing operation for a component
(Field Op. (Operation))

Changing machinery running costs
(Fields Setup time, Unit time or Run time)


Changing labor costs
(Fields Labor wk C, No. lab res. or Subcontract product)

Indirect events

Certain changes to key information in the work order header information can result in events occurring to components or operations indirectly that must be tracked.

Each work order header event listed below is therefore considered a 'critical' change in the context of amendments to work orders for versioned products. They can be made by any user:

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

  • Component events:
    • Changes to the work order start date;
    • Changes to the planned quantity;
    • Changing the version of the product to be released;
      • These events result in the products to be released being reloaded with the default information from the BOM record. Previous changes to the components are removed. The components, therefore, are reloaded, resulting in a tracked event.
    • Deletion of a product to be released.

  • Operation events:
    • Changes to the planned quantity;
    • Changing the defined routing;
    • Changing the routing version;
      • 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, therefore, are reloaded, resulting in a tracked event.

 The rule when using versions is that consistency between the start date of the work order and the version is demanded. If the production start date is changed this might necessitate a different version of the product or routing version to manufacture the product to be released.

Tables updated

Component events are recorded in the Work order - materials audit (MFGMATREV) table.

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

Viewing audit details

You can view the audit details by clicking Revision history from the Actions icon on a component or operation line in a work order (Components tab/Operations tab).

The revision history includes the revision reason, a revision code and key details of the event. The most recent event is displayed on the first (top) line of the table. 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 :

The global variable GMFGREV is associated with it.

Functions impacted

The following functions are associated with this parameter :

 Manufacturing > Planning > Work order

Activity codes

The following activity codes (sorted by type) are associated with the parameter :

 ECC : Product version management

Comments

This parameter only applies to a work order for a versioned product.

 Activity code ECC must be activated to use the Version management functionality.