| Change Proposal (dmchm0120m000) |  |
| Use this session to review a change proposal. Change process A default proposal is created when a change is created. You need authorization to add new proposals. The session enables you to link various components. Example of affected objects include task, task group, reviewer, and change order. Affected objects are linked to the change proposal and the review process runs. Reviewers review the change before final review by the chairperson of the committee. The chairperson approves or rejects a proposal. After the approval action, the objects controlled by Change Management take the value of the change order dates. The linked and affected objects dates also take the value of the change order dates. The Bill of Change Order mechanism is used to control the effectivity or expiry of date of more than one change order. The authorized user performs the actual tasks and completes the change. After the change is approved, an authorized user can revise the proposal after the user copies the linked entities with a new change order. The Specific menu commands Approve... Submits the proposal for review. This command is available for a fixed or non-fixed reviewers mechanism. Approve: Approves the proposal of a change. Reject... Rejects the proposal that has been submitted for review. Freeze... Enables you to make the change inactive. Unfreeze... Activates an inactive change. Cancel... Cancels the change before submission for review. Revise: Revise the approved change process and create a new one. Complete... Completes the change. Link Affected Objects Links objects to the change proposal. Browse Browse for the properties, linked objects, tasks, task groups, reviewers list, and change orders that are related to the change proposal. Secondary Status Use a secondary status for the proposal. Note The user's access to specific life-cycle status commands, depends on the authorizations. Related topics Change Management (CHM) Change Proposal Task Group
Fields | Description
Change | The change ID that provides status information of the lifecycle for all changes.
Status | The status of the change.
Simple CHM | If this check box is selected, the Simple CHM option becomes available. Simple CHM is a mechanism that involves simple change management principles. The authorized user can perform the actions such as approve, reject, and so on, without invoking the change proposal session.
Description | The description or name of the code.
Proposal Version | The change proposal ID. To create a new proposal, the user must define a mask. An error message appears if you create a new proposal without a mask.
Status | The change proposal status.
Owner | Enter the proposal owner's role. Click the browse arrow to select the role from the Roles (tcppl0160m000) session.
Tasks Actual Cost | The total tasks actual cost, which is the sum of actual costs of all the tasks defined for the proposal of a change. The currency code also appears here.
Tasks Estimated Cost | The total task's estimated cost. The amount is the sum of actual costs of all the tasks defined for the proposal of a change.
Number of Task Groups | The total number to task group linked to the proposal of a change.
Total Number of Tasks | The total number of tasks linked to the proposal of a change.
Number of Tasks Done | The total number of tasks that are implemented and that have the status Done.
Number of Tasks in Work | The total number of tasks that have not yet been implemented and have the status In-Work.
Recommended Solution | Enter the recommended solution.
Advantages | Enter the advantages of recommended solution.
Disadvantages | Enter the disadvantages of recommended solution.
Approval Date | The proposal approval date and time.
Status Date | The date and time when the status of the proposal is changed.
Secondary Status | The user-defined status. Secondary status is defined in the Object Statuses by Object (dmsys0520m000) session. Use the browse arrow to select the required secondary status from the session. Example: A change with Created status can have the secondary status Created by Employee, Created by Customer, and so on. This step is not a mandatory step in the change process. You can use this feature, if required.
Created By | The user who creates the proposal. This field is a read-only value and cannot be edited.
Creation Date | The creation date of the proposal. The UTC date and time format is used.