Understand Change Types

A change type includes default attributes and defines the change workflow. The application includes predefined change types based on which you can create change orders and new change types.

To use change orders, you must create at least one change type. The change type can be end-dated if it's not used in any change orders that have a workflow in progress.

To create a change type based on predefined types:

In the Setup and Maintenance work area, go to the following:

• Offering: Product Management

• Functional Area: Change Orders

• Task: Manage Change Order Types

This table provides information on the predefined change types and supported features.

Change Type	Description	Supports Revision Control	Supports Audit Report	Supports Redline Modifications
All Change Types	Used to indicate the hierarchy of change types and the inheritance of extensible flexfields across change types. Although this appears in the UI, you can’t create changes using this type.	NA	NA	NA
Engineering Change Order	Used when tracking major changes during the design phase of the item. The revision number is automatically incremented when you make changes.	Yes	Yes	Yes. Displays the following modifications in redline: item detail, extensible flexfields, structure, AML, and attachment.
Change Order without Revision Control	Used when revision control isn't required or when changes are minimum. For example, replacing an existing manufacturer part with a similar part supplied by another manufacturer.	No	Yes	Yes. Displays the following modifications in redline: AML, extensible flexfields, and item detail.
Change Request	Used when suggesting changes for a released item. For example, a supplier could request changes in certain specifications.	No	No	No
Deviation Change Request	Used when deviating from a process or specification for a specific time period. For example, suggesting the use of a substitute component as a temporary means of resolving an issue.	No	No	No
Commercialization Change Order	Used during the commercialization phase of the product. Can be created and edited in Product Information Management. Also available in Product Development as read-only.	Yes	No	Yes
Problem Report	Used to implement Quality Management for engineering design and development through Product Development. It's also required to enable supplier collaboration for issue identification and resolution. A problem report is a type of quality issue, such as a defect, deficiency, or a significant variation in a product's expected appearance or performance. This change type is applicable only for users in the Quality Management work area.	No	No	No
Corrective Action	Used to implement Quality Management for engineering design and development through Product Development. It's also required to enable supplier collaboration for issue identification and resolution. A corrective action is a type quality action to mitigate a quality issue and prevent its further occurrence. This change type is applicable only for users in the Quality Management work area.	No	No	No

Note:

• The 8D corrective action inherits attributes from its parent, the predefined Corrective Action change type.

• Changes made to a change type won't be applied to any existing change orders (created from the change type).