Cumulative Order Selection

The selected cumulative order has start and end effective dates that include the transaction effective date. The following table explains how a cumulative order is selected, based on the effective date entered.


If...	Then...
A cumulative order has a blank start effective date, its effective interval is from the end effective date into the indefinite past,	it will always be selected if the transaction effective date is on or before the end effective date.
A cumulative order has a blank end effective date,	its effective interval is from its start effective date into the indefinite future. It will always be selected if the transaction effective date is on or after the start effective date.
A cumulative order has blank start and end effective dates,	it will always be selected.
No cumulative order is found matching the criteria,	one is immediately created. The start and end effective dates are set according to the setting of the End Eff Default Method field in Repetitive Control (18.22.24).
The dates in the new cumulative order overlap with the dates in another cumulative order,	the dates in the new cumulative order are adjusted forward or backward to prevent overlap.

The cumulative order create process retrieves the routing in effect as of the transaction effective date, and copies it to the cumulative order. For each operation in the routing, this process retrieves the product structure in effect as of the transaction effective date, and copies it to the cumulative order operation. When accessing the product structure, phantoms are blown through.

A cost roll-up is then performed on the new cumulative order. The calculated operation costs are recorded by operation in the cumulative order routing. These costs are used for WIP valuation reporting and calculating variances.