RequiredbyDate Change

RequiredByDate for an order defines the time at which the order plan should be executed. It can be mentioned at both the order header level or/and the order line level. In terms of dependency in the order plan, it generates a time dependency (with absolute time) for a plan item along with dependency on other executing plan items (point dependency) if any. Once the absolute time is reached, time dependency is considered as satisfied.

Following are the preconditions for the order line requiredByDate change amendment type:

  1. The number of order lines in the amendment request must match with those in the original order request.
  2. The lineID, productID, action, and UDFs in all the order lines in the amendment request must match with those in the original order request.

Following is the process of calculating a time dependency with respect to requiredByDate.

  • If requiredByDate is set on the order level only, the start time dependency applies to all plan items with no leading dependencies
  • If requiredByDate is set on the order line level only, the start time dependency applies to plan items for that order line
  • If requiredByDate is set on the order header level and on the order line level, the following behaviour applies:
    • If requiredByDate in Order Header is later than requiredByDate in order line, then the start time used is the one at order level
    • If requiredByDate in Order Header is earlier than requiredByDate in line item, then the start time used is the one at order line level

RequiredBydate Amendment type allows for changing the required date for an order when it is not in its FINAL stages as mentioned earlier. The following matrix defines the conditions to identify a RequiredByDate change amendment type:

Original header date Original line date New header date New line date IsAmendment
Past Dated Past Dated past dated but greater than originalheader date past dated but greater than originalheader date No
Past Dated Past Dated Same as original Future Dated Yes, for that particular Order Line
Past Dated Past Dated Future Dated Same as original Yes, for all order lines
Future Dated Past Dated Back Dated Same as original Yes, for all order lines
Future Dated Past Dated Future date than original Same as original Yes, for all order lines
Past Dated Future Dated Same as original Same as original No
Past Dated Past Dated Futrure Dated Future Dated Yes, for all order lines. The time dependency will be calculated as explained earlier.
No Date Past Date Back dated Same as original No
No Date Future Date Back dated Same as original No
No Date No Date Future Dated Fuutre Dated Yes, for all order lines. The time dependency will be calculated as explained earlier.

The default behaviour in 2.1.1 for required by date change is not to create compensation or restart any plan items. Below matrix defines the amendment behaviour based on plan item status

Plan Item Status Description
Pending Plan item dependency time will be updated so the plan item triggers at the amended required by date.
Suspended Not permitted. Any required by date changes are ignored. As the plan item is already started, it is not possible to change the start date.
Complete Not permitted. Any required by date changes are ignored. As the plan item is already completed, it is not possible to change the start date.

The value of rollback UDF in order is ignored in this case as no compensation or restart plan items are created.