| Change Proposal |  |
| The change proposal is a version-controlled entity of a change. A new change proposal is created by default when a change is created. The proposal can be approved or rejected. When the proposal is approved, the status of change changes to Approved. If the proposal is rejected, the status remains the same ( Created ). If the proposal is rejected, you can create a new proposal with all the linked entities. Attach relevant ERP objects and the change orders to the proposal to govern the effectivity dates of the linked objects. The reviewers assigned to the committee and made specific to the change provide the recommendations for the proposal. The proposal has the following status: Created Under Review Approved Rejected The chairperson of the change committee has the final authority to approve or reject the proposal. Tasks are attached to the proposal with the estimated dates and can be executed after the change is submitted for review. After the proposal is approved the change can be completed. The change proposal has the following status: Created: The initial status of a new change proposal. Under Review: The change proposal is submitted for review. Reject: The change proposal is rejected. Approved: The change proposal is accepted. Tasks are done: All the tasks linked to a proposal are completed. Revise: Revise the approved Change proposal. The status reverts to Created. The change status commands in the Changes (dmchm0111m000) session are the following: Freeze: Halts the change proposal and no objects can be linked to the proposal at this stage. Unfreeze: Reactivates the change proposal. Cancel: Cancels the change and the proposal becomes ineffective. After cancellation no modifications or revision is possible. You can cancel the change before the approval of change. Complete: Completes the change process. Related topics Change Order Task Group Reviewers List Linking to ERP entities |