Effective Date and Revision for Affected Objects

You can specify an effective date for an affected object or set the use-up date (defined in Supply Planning) as the effective date. An affected object can become effective on completion of the workflow, or on a future date.

Revisions for Affected Objects

Here’s what you need to know about revisions for affected objects.

If an object is assigned to multiple change orders, each revision must have different effective dates. For example,
Revision B resulting from change order B001, can be effective January 1.
Revision C resulting from change order C001, can be effective January 6.

When assigning an affected object to a change order, you select the particular revision that you want to modify, and also enter the new revision for the modified object.
The revision you want to modify includes either of the following:
- Revision that's currently effective. Note that you can't select a revision that's pending approval.
- Revision that's scheduled to be effective in future and resulting from a change order in the Scheduled status.

Effective Date for Affected Objects

Here’s what you must know about the effective date:

The effective date for the modified version must include a date that's in-between the existing effective dates. For example, revision B can be effective January 1 and revision C can be effective January 6. So the modified version can include an effective date January 4.
To ensure that item rules run effectively when you update rows in the affected objects table, the application prompts you to save changes to lifecycle phase and effective dates separately.
Note:
If you modify the effective date after you modify the lifecycle phase while saving the change order, the application prompts you to save lifecycle phase changes before saving the effective date. If you first modify the effective date, the application prompts you to save the effective date changes before saving the lifecycle phase changes.
When you use the Fill Down, Fill Up, and Fill Selected functions to save effective date changes across multiple rows, the changes are automatically saved separately. So you won't see a validation message if you modify lifecycle phase values immediately after that.

Set Use-Up Date as the Effective Date

When you remove or replace a component, you can view and select a use-up date specified in a supply plan as the effective date for the affected object. The use-up date calculation helps you identify the optimal effectivity dates for structure components that are being removed or replaced on engineering and commercialization change orders.

Here’s how you set the use-up date when you remove (or replace) a component:

Click the Affected Objects tab on the change order.
Open the affected object that contains the component you want to remove (or replace).
Navigate to the Structure tab.
Select the component you want to remove and click Actions > Remove.
Click Save and Close.
Click Actions > Calculate Use-up Date on the Affected Objects tab.
The Select Use-Up date dialog box appears with the use-up dates defined in the referenced plans for the component (in the Supply Planning work area).
Select the use-up date and click OK.
The date you select is populated in the Effective Date column on the Affected Objects tab. If you manually update the effective date, any existing values for Plan Name and Use-Up Item are cleared out.
Save your changes.

Some additional considerations:

The Calculate Use-Up Date action is only visible if the Supply Chain Planning offering is enabled.
If you've enabled Supply Chain Planning but aren't using Planning use-up dates, the Calculate Use-Up Date action won't retrieve any use-up dates.
The Plan Name and Use-Up Item columns are hidden by default. You can use View > Columns to show these columns if you’re using planning use-up dates.
When you add the effective date using the Calculate Use-Up Date action, the time is set to 00:00:00, because Use-Up Date is a date-only attribute.
The affected item’s effective date automatically changes to Effective on Approval if the specified effective date is in the past by the time the final approver (for the final approval status) approves the change order. If this happens, the Plan Name and Use-Up Item values are cleared out.
If you update the affected object's lifecycle phase, you must first save the lifecycle phase change before updating the effective date using Calculate Use-Up Date.