Revision management

This parameter—MFGREV—controls whether key changes to a work order for a versioned product need to be audited.

Note - settingsRefer to the TRACKMATWO—Track a WO component change parameter if you need to audit changes to non-versioned production bills of material (BOMs).
Refer to the TRACKOPEWO—Track a WO operation change parameter if you need to audit changes to non-versioned routings.


Yes: "Critical" changes to components of a versioned production BOM or operations in a versioned routing for a work order are audited. The audit information is saved whenever it occurs.

Note - informationThe audited events are changes to work orders that form an integral part of the manufacturing process. As each of these changes needs to be tightly controlled, they’re 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 product.

Audited events

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 adds 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.

Direct events

Each of the following audited events is considered to be a "critical" change in the context of amendments to work orders for versioned products. A user making the change needs to be authorized.

Note - settings

Users can only make direct component events if the ECCWOCOM—WO component critical changes parameter is set to Yes.

Users can only make direct operation events if the ECCWOOPE—WO operation critical changes parameter set to Yes.

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

Audited component event Audited operation event Audited action
Add component Add operation Component: Selecting the Add unexpected material or Add sub-assembly (phantom) action from the Actions icon
Operation: Selecting the Additional operation not expected action from the Actions icon
Exclude or cancel component Exclude or cancel operation Selecting the Exclude line action from the Actions icon
Reinstate canceled component Reinstate canceled operation Selecting the Reactivate action from the Actions icon
Edit required component quantity Edit operation planned quantity Component: Editing the Requirement qty field (RETQTY)
Operation: Editing the Planned quantity field (EXTQTY)
Assign or edit specific manufacturing operation for a component Edit production resource Component: Editing the Op. field (BOMOPE)
Operation: Editing the Work center (EXTWST) or Number of resources field (EXTWSTNBR)
Edit pick list component issue statement   Editing the Pick list code field (PKC)
  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

Each of the following audited events is considered to be a "critical" change in the context of amendments to work orders for versioned products. A user making the change does not need to be authorized.

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

Note - informationEditing some key fields in the work order header can result in the product to be released or routing operations being reloaded with the default information from the BOM / routing record. Previous changes to the components / operations are removed. The components / operations are reloaded, resulting in a tracked event.
Note - warningThe work order header event itself is not audited, only the resulting event on the BOM components or routing operations.
Audited component event Audited operation event Audited action
Edit start date

Editing the Start date field (STRDAT)

Note - dangerThe 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.
Edit planned quantity BOM: Editing the Release qty field (UOMEXTQTY)
Routing: Editing the Planned quantity field (MFGEXTQTY)
Edit released product version Edit routing version Editing the Major version field (ECCVALMAJ / ROUECCMAJ) or Minor version (ECCVALMIN / ROUECCMIN) field
Delete released product

Tables updated

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

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 Components or Operations tab, select Revision history from the Actions icon on an edited component/operation sequence number line. The revision history includes the revision reason and a revision code, and key details from the edited 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:

The global variable GMFGREV is associated with this parameter.

Functions impacted

The following function is associated with this parameter:

  Manufacturing > Planning > Work order

Activity codes

The following activity code is associated with this parameter:

  ECC:  Product version management

Comments

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

Refer to the TRACKMATWO—Track a WO component change parameter, which audits changes to components of non-versioned production BOMs.

Refer to the TRACKOPEWO—Track a WO operation change parameter, which audits changes to operations in non-versioned routings.

Note - settingsThe ECC—Product version management activity code needs to be active to use the version management functionality.