Change header types provide enterprises a way to accommodate business processes and classify types of changes within a change category. For example, you can define different change header types such as Quality Change, Product Change, and Performance Change to capture the various types of changes in your enterprise.

After creating and saving the basic information for a change header type, you can associate the following to the type:

• Attribute Groups and Pages

• Codes

• Workflow

• Configuration

• Organization Policies

   To create a change header type:

1. On the Change Management Categories page in the Setup Workbench, select a change category, then select the Types tab in the lower half of the page.

2. If you already know of a similar change header type, select it and click Duplicate. Otherwise, click Create.

3. On the Create <Change Category Name>Type page, enter information in the following fields:

   • Name- Required. Enter the name of the new change header type.

   • Description - Optional.

   • Start Date and End Date - Required. Use the Start Date and End Date fields to designate the date range in which you can use the change header type.

   • Number Generation

     Required. Select a number generation method.

     Note: To enable autonumbering, you must enter both a prefix and the next available number.

     • Sequence Generated

       If the change header type numbering method is sequence generated, then all change headers will be automatically generated based on the sequence generation rules specified here. You can specify a prefix, starting number, and increment.

     • User Entered

       If you specify user entered, then the user is required to manually enter a number for new headers of this change header type.

       Note: The User Entered number generation method is not supported for the New Item Request change category.

     • Function Generated

       Enables you to associate user-defined functions based on change type attributes. These functions will automatically create change numbers in the sequenced defined in the function.

       See: Creating User-defined Functions.

     • Inherit From Parent

       If the change header type numbering method is inherited from the parent, then the change header type number generation method will be the same as that defined for the parent change category.

       Note: Inherit From Parent only appears as a Number Generation selection choice for the change header type when the associated change category's (the parent) Number Generation is set to Override at Type Level.

     Note: When importing new item requests using a spreadsheet, the associated change header type must have Sequence Generated or Function Generated autonumbering. User Entered autonumbering results in an import error.

   • Subject - Required. You can specify that the subject of the change header type is an item, item revision, item and component, or nothing. Add Subject Selection Criteria to optionally restrict the subject by other related attributes such as catalog category, item lifecycle phase or item type. For example, you can set up a change order header type named Production Motherboard Change where the subject of the change is restricted to items in the Motherboard catalog category with an item lifecycle phase of Production.

   • Assignee Type - Optional. You can set up the change header type to assign change objects by Person, Group, or Item Role. A user may have more than one role for an item because you can assign item roles at the organization, item catalog category, and item level. If you choose to assign change objects by item role, then you need to choose an Assignee Type that specifies the level in which to look up the assignee by item role:

     • Group - Assigns the change header to members of the specified group.

     • Item Role at Catalog Category Level - Assigns the change header to users with a role on the subject item that is inherited from the item catalog category.

     • Item Role at Item Level - Assigns the change header to users with a role on the subject item.

     • Item Role at Organization Level - Assigns the change header to users with a role on the subject item that is inherited within the organization.

     • Person - Assigns the change header to the person specified.

   • Assignee - If you selected an assignee type, then select an item role or group for the assignee type.

4. Click Apply.

After creating and saving the basic information for the change header type, you can complete the change header type setup as described in the following tasks.

   To associate attribute groups and pages with a change header type:

Associate attribute groups defined for headers to a change type. These attribute groups enable you to capture additional information regarding the type of change created, or business process-specific attributes required to process the change. You can create pages for a change header type and then organize the attribute groups associated with the change header type in a logical manner.

1. On the Basic Information page of the change header type to which you wish to associate attributes groups, click Attribute Groups.

2. Click Add Attribute Groups.

3. Search for and select the attribute groups you wish to associate and click Apply.

To associate pages with a change header type

4. On the Basic Information page of the change header type to which you wish to associate attributes groups, click Pages.

5. On the Pages page, click Create Page.

6. Enter the basic information in the required fields. Note that the number entered in Sequence determines the order in which the page links appear on the change object's detail page.

7. Click Add Another Row in the Attribute Groups section. Enter the Sequence number to specify the order in which the attribute groups will appear on the page.

8. Click Apply.

   To associate codes with a change header type:

Specify the valid codes for Priority, Reason and Classifications for the change header type (Classification codes are only available to change header types based on the Change Order category). This enables you to limit the available values for a user to only the selected values for each of these codes. To create these codes, refer to Creating Priority, Reason, and Classification Codes.

1. On the Basic Information page of the change header type to which you wish to associate attributes groups, click Codes.

2. On the Codes page, select the valid priorities and reasons codes for the change header type.

3. Click Apply.

   To configure a change header type:

Depending on your business process, you can elect to enable only certain primary attributes and sections for a change header type. For example, for a Supplier Requested Issue, you can disable the People section, as you may not want the Supplier to have visibility on who has what role in your organization.

1. On the Basic Information page of the change header type, click Configuration.

2. On the Configuration page, select the sections and primary attributes to enable for the change header type.

3. Click Apply.

   To associate workflows with a change header type:

Define the various statuses for the change header type under the workflow tab. You can specify the valid statuses for promotion and demotion as well as associate one or more workflows with each status. For an Approval status, you can only select an Approval type workflow.

You can associate multiple workflows to a change status and specify one of them as a default. Use any one of the associated workflows at run time.

When you create a status you specify a status type. These status types determine some of the operational characteristics of the change header during its workflow:

• Open

  When a change header has a status of Open, users can update the change object. However, there are two exceptions:

  • If the workflow is running and Update Allowed is not selected, you cannot update the change object.

  • If an Open status follows an Approval status within a workflow, you cannot update the change object. You cannot update a change object once it has gone through an approval process.

• Scheduled

  Users cannot update the change object (unless reopened). Scheduled change objects are picked up and implemented by the auto-implement manager. Change headers must be Scheduled before they can enter the Implemented status.

• Released

  Ready to be scheduled or implemented. Cannot be updated (unless the change is reopened).

• Approval

  A workflow is mandatory for this status. Once the Approval is granted, the change object cannot be updated. You can associate a workflow template containing an approval request step for Approval status types only.

• Implemented

  The changes specified in the change object take effect. Implemented change objects cannot be reopened and canceled. Once implemented, no further changes can be made. For each change header type, only one status can use Implemented. Implemented must always be the final status.

Certain workflow types can be associated with the statuses defined here. Following are the associations between status type and workflow type for non-new item requests:

Following are the associations between status types and workflow types for new item requests:

1. On the Basic Information page of the change header type, click Workflow to define the workflow for the change header type.

2. On the Workflow page, click Add Another Row in the Statuses section.

   Note: The statuses of Open and Completed were automatically associated with the header type when the header type was created.

3. Specify a number that indicates the order in which the statuses are executed, and select a status.

4. Optionally, select a default workflow for the status.

5. Click Apply.

6. After creating a workflow for a change header type, you can click the Update Properties icon to specify for each status the valid promotion and demotion statuses and assign one or more workflows. For workflows that contain an Approval status, you must assign a workflow template that contains at least one Request Approval step. You can also select the following for each Approval workflow:

   • Enable Digital Signature

     The Enable Digital Signature list only appears when electronic records and signatures are enabled for Oracle Engineering.

   • Allow Updates

     Selecting this option enables the user to cancel a change line during the Approval status.

   • Auto Promote

     Selecting this option and specifying a valid promotion status enables the system to automatically promote the change to this status after successful completion of the Approval status.

   • Auto Demote

     Selecting this option and specifying a valid demotion status enables the system to automatically demote the change to this status after failing the Approval process.

7. Click Apply.

   To specify organization policies for change headers:

For change orders only, you can specify organization policies for change header types such that task templates and propagation rules are applied to every change order created in a specific organization. Task templates identify the specific tasks that must be performed before a status is considered complete (for details, see Creating Task Templates). If a business is comprised of hierarchically related organizations, the changes specified in a change order may need to be propagated to several other organizations in your company. For example, you may have an organization, Vision Operations, which has two manufacturing organizations in the VisionMfg hierarchy named Seattle Manufacturing and Chicago Manufacturing. You initially create change orders in the Vision Operations organization. Once the change orders reach a certain status in the workflow (for example, Scheduled), the change orders can be propagated (for example, copied to the destination organization with the Status initially set to Open) to the two manufacturing organizations in the hierarchy.

You can set up the organization policy such that a change order is automatically propagated downward to the other organizations in the hierarchy whenever the change order reaches a particular status. However, the changes only propagate to the organizations within the hierarchy to which the user entering the change order has access. For example, if another user who only has security access to the Vision Operations and Seattle Manufacturing organizations enters change orders under this organization policy, the change orders only propagate to Vision Operations and Seattle Manufacturing and not to Chicago Manufacturing.

1. On the Basic Information page of the change order header type for which you wish to create organization policies, click Organization Policies.

2. On the Organization Policies page, add the organization to which you want to add the organization policy.

   Click Add Another Row.

3. Select the newly added organization, then click the Task Template tab.

4. Click Add Another Row to specify the task template you wish to use. Note that you can assign more than one task template. You can specify the status in which to start the task and the status in which to complete the task.

5. Click the Propagation Rules tab. Before specifying the organization hierarchy for propagation, you have the option of selecting a particular status that, when entered, will automatically propagate the change order to a default organization hierarchy. To do so, select Auto Propagate and specify the Status for Propagation. If you wish to manually propagate change orders, do not select Auto Propagate.

6. In the Organization Hierarchy for Propagation table, click Add Another Row, then select the Organization Hierarchy to which the change order will be propagated. While you can add more than one organization hierarchy to the propagation rules, the change order can only be propagated to one. Also, you can select one organization hierarchy as the default to which all change orders are propagated.