Effective/Expiration Dates on Order Constraints

Effective and Expiration date fields (Order Base only) can be used to constrain when order releases are created from the order base. If you leave these fields blank, Oracle Transportation Management follows the typical rules for order release creation.

Therefore, if you want Oracle Transportation Management to automatically create order releases when you create the order (packaged data) or when you issue release instructions (line items), leave these fields blank. Otherwise, if you decide to impose these constraints, releases are only created when the bulk planning process is initiated.

• If you enter both an Effective and Expiration date, Oracle Transportation Management checks this time window against the system date on the Oracle Transportation Management Application server to determine whether order releases can be made for the order based on predefined order instructions. If the system date is within the time window specified, an order release is automatically created.
• If you enter an Effective date only, Oracle Transportation Management creates order releases on or after that date.
• If you enter an Expiration date only, Oracle Transportation Management creates order releases up to, and including, that date.

If you set Effective and Expiration dates, you should also define release instructions for the order so that the appropriate order release is created once the time window becomes active.

The Status section of the initial order base page indicates whether the release time window is active or out of date.