Change Order (dmchm0150m005)

Use this session to generate a change order. A change order provides a generic mechanism for any ERP-controlled link entity. A change order date is specified to put the linked entity into effect.

Each proposal has a list of proposed effective dates. These dates are recorded as change order dates. The user can update a change order date in the details session. A change order that is independent of a change proposal is known as a parent change order.

To control the effective/expiry dates of multiple change orders, the user can define a parent/child dependency with another change order. Hierarchical dependencies between change orders creates a bill of change orders. The bill of change orders hierarchy is limited to two levels only. In the bill of change order, the child change order date and parent change order date are the same. If the change order date is set to a date later than the approval date of a change, the approval date of the change is considered and the change order date is set to this date . If activity dates must be changed after an approval, a new change must be created with new dates by revising the proposal.

Change: The change ID. Click the browse arrow to select a change ID from the Changes (dmchm0111m000) session and link the ID to the change order.
Status: The change status.
Proposal: The change proposal for the selected change. Click the browse arrow to select a proposal from the Change Proposal (dmchm0120m000) session.
Status: The change proposal status.
Change Order: The change order ID. The change order provides a generic mechanism for a controlled ERP-linked entity.
Description: The description of the change order.
Change Order Date: The change order date. Each proposal has a list of proposed effective and expiry dates, specified in UTC date and time format. These dates are recorded as change orders dates. The date specified is stamped on the linked entity. A change order must not be postdated.
Parent Change Order: The parent change order. A parent change order is not linked to change and proposal.
Date: The parent change order date. This date is applicable to the child change order.

Note: The parent change order must not be postdated.
Created By: The logon code of the user who creates the change order.
Creation Date: The date and time on which the change order is created.
Modification Date: The date and time on which the change order is modified.