Overview of Change Type Setup

You can create and configure a change type based on predefined change types.

Change objects that you create from the change type inherit properties such as default assignee, entry and exit criteria, automatic promotion and demotion, attribute configuration, and so on.

For example, you can create a change type named Circuit Board to manage the approval of all circuit boards. You can then create a change order by selecting the change type as Circuit Board. The change order inherits properties such as default assignee, entry and exit criteria, automatic promotion and demotion, and so on.

You can configure change types using the Manage Change Order Types task. Here’s how you access the task.

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

  • Offering: Product Management

  • Functional Area: Change Orders

  • Task: Manage Change Order Types

The change types are listed in the following hierarchy on the Manage Change Order Types page:
  • First or top level (All Change Types) - includes predefined and copied change types. Note that you can’t create changes using All Change Types. This is only used to indicate the hierarchy of change types and the inheritance of extensible flexfields across change types.

  • Second level - predefined change types.

  • Third level - change types copied from predefined change types.

    Additionally, you can only add alphanumeric characters and underscores in the Internal Name field on the change type. (You can’t use hyphens when you create a new change type.)

Here are the tabs that appear on a change type:

  • Policy - configure the following: number generation method, item effective date, autocomplete settings for canceling the change, commenting options when users remove change participants, assignee role, default assignee, change priority, and change reason.
  • Workflow - use additional workflow controls to control actions by change participants.
  • Propagation Rules - cascade item structure changes from source to target organizations in commercialization change orders.
  • Creators - define which user roles can create change orders (or change requests).
  • Attributes - control the visibility of trading partner reference attributes and configure extensible flexfields for a change type.