Setup Tasks to Define Changes
Before you can create change orders, you must complete these tasks in the Setup and Maintenance work area (for the Product Management offering):
Task |
Description |
---|---|
Manage Change Reasons |
Change Reasons are used to categorize and establish the cause or reason for a change. Change reasons are required for creating changes. |
Manage Change Priorities |
Change Priorities are used to identify the criticality of changes. Change priorities are required for creating changes. |
Manage Change Statuses |
Change Statuses enable you to manage a change through its life cycle. |
Manage Change Order Types |
All changes are assigned a change type. You must create at least one change type based on predefined change types. |
Manage Change Order and New Item Request Header Descriptive Flexfields |
Used to manage the header-level descriptive flexfields for change orders and new item requests. You can create entry and exit criteria using descriptive flexfields. |
Manage Change Order and New Item Request Line Descriptive Flexfields |
Used to manage the line-level descriptive flexfields for change orders. Note: Line-level descriptive flexfields for new item requests
aren't supported.
|
Manage Task Configurations for Supply Chain Management |
Define the task configurations for the change approval workflow. |
Manage Approval Groups for Supply Chain Management |
Define approval groups for the change approval workflow. |
-
The tasks listed in the table are applicable for change orders, change requests, problem reports, and corrective actions.
-
Using Groovy scripting you can only access global descriptive flexfields. Create actions, triggers, and conditions based on the values of the global and contextual descriptive flexfields. You can’t use Groovy scripting to access contextual descriptive flexfields on change orders.
Refer to the Oracle Fusion Cloud Applications Groovy Scripting Reference guide for more information on Groovy scripting.