Previous	Next		Contents	Index	Navigation	Glossary	Library

Effective From / Effective Date	First date and time the component or operation becomes effective. For components, the effective date is the first day a component becomes effective for a bill. For routings, it is the first day an operation becomes effective in a routing.
Effective To / Inactive After	Last date and time the component or operation is effective. After this date, you can no longer assign the component to a bill or the operation to a routing.
Inactive On	The first date and time the component or operation is inactive. As of 12:00AM on this date, you can no longer assign the component to a bill or the operation to a routing. If this date equals the effective date, the component or operation is inactive.

To avoid confusion, make sure that effective dates for one revision do not overlap with those of another.

For example, if you must introduce three new components to a bill in a specific order, you should assign each change to the appropriate parent item revision. So, component 1 of revision B may be effective today, component 2 of revision C tomorrow, then component 3 of revision D may be effective the following day. If there are two operations on a routing and you replace the first operation with a new operation, you should set the effective date for the new operation to the date the operation you are replacing becomes inactive.

Effective dates can be either the current date or a date in the future; you cannot enter a date in the past.

For components, the default effective date is the later of the current date or the date entered for the bill. If an inactive date already exists for the operation sequence/item combination, the default effective date of any subsequent rows with the same operation sequence/item combination is the same as the inactive date. That means that the subsequent operation sequence/item combination becomes effective immediately after the previous one becomes inactive.

You cannot assign duplicate components to the same operation with overlapping effective date ranges. For example, suppose component A001 at operation 10 is effective from 10-JAN to 14-FEB. You may not add another component A001 at operation 10 to the bill with an effective date of 10-FEB.

Use Oracle Master Scheduling/MRP to identify any overlapping effective dates.

See Also